Hi Paul,
>>A system like this could easily generate a simple plugin GUI (like a array of
>>sliders) in whichever UI-toolkit
>>
>
> its worth noting that this works already for LADSPA plugins without
> any GUI specification at all. its how GLAME, ecamegapedal, ardour, snd
> and many others build plugin GUIs - they just look at the list of
> control ports.
this would be the case, if we would use a generic wrapper. If the plugin supplies the
xml
everything is possible.
>
> the problem is that it doesn't handle complex plugins that have dozens
> or even hundreds of parameters that need grouping in certain ways. it
> also doesn't handle plugin parameters that need to be mapped to string
> form, or curves, or whatever. this needs the ability to group controls
> onto "pages", and to be able to use widgets that are relatively
> specialized. this is quite hard to do :)
>
> I enclose the mostly-approved LADSPA XML GUI DTD from last year. Many
> readers will be familiar with it.
>
I my approch I strictly divide between functional descriptions and style related
descriptions.
I would favour if the plugin just supplies functional-desc. und the users
chooses the style related things by choosing a theme.
Otherwise we quickly end up with plugin which look like those vst things (*wurgs*).
Stefan
--
\|/
<@ @> Stefan Kost private business
+-oOO-(_)-OOo------------------------------------------------------------- - - - - -
| __ Address Zwenkauer Str. 24 HTWK Leipzig, Fb IMN, Postfach 300066
| /// 04277 Leipzig 04277 Leipzig
| __ /// Germany Germany
| \\\/// Phone +49341 3910483 +49341 30766101
| \__/ EMail [EMAIL PROTECTED] [EMAIL PROTECTED]
| WWW http://www.sonicpulse.de
|http://www.imn.htwk-leipzig.de/~kost/about.html
===-=-=--=---=---------------------------------- - - - - -
