On Tue, 2007-02-27 at 11:01 +0100, Pieter Palmers wrote:
The "renders panels from stylesheets" is
what I am referring to. Phat
is
has very nice widgets, but AFAIK it stops before the container
level.
That's where the widget 'system' comes in: a system that manages
widgets
such that you don't have to care about that. Just write a UI
description
and have the system generate the UI for you (at run time).
right. you could argue that LV2 might offer enough metadata to help a
host build a good UI, but my approach is meant to give plugin coders
more control. i know from my experience with plugin developers that they
like to set apart their works "from the competition", and spend a great
deal on presentation. providing them with a set of highly customizable
(hardware-like) widgets + a document-like format to describe a panel is
the goal here. yes, it's nothing big. it's just about making this
special field more accessible. the result will be screenshots showing
off a lot of beautiful panels that people are used to from commercial
applications. the effect will be "i want this, it looks good. i want to
play with it."
of course there is nothing wrong with a beauty of logic beneath the
surface that waits to be discovered by the attentive and insistent.
however, inside of everyone, there is a little child easily amazed by
beauty, with a longing to possess, touch, move and play with the things
it adores.
and, in my opinion, playing around is something very important in music.
--
Leonard Ritter
-- Freelance Art & Logic
--
http://www.leonard-ritter.com