linuxaudio.org

> From: Sean Bolton

quoted text
> if the GUI is in another process, its really absurdly hard for the

> host to add its own controls to the window. not impossible, but a

> level of hard that doesn't actually buy the user (or developer)

> anything. this means that the kinds of generic "every plugin" controls

> like "bypass" or "preset" that ardour adds to LADSPA and AU windows

> would vanish. not a huge cost, but a real one.

Not very hard, but think more in terms of functionality, not implementation.
e.g. my plugin API can provide the GUI a string "Commands for Parameter 23:"

- "MIDI Learn, Unlearn, Edit...".
The user can right-click any knob on the GUI and get a menu of functions the

*HOST* provides for that parameter... With ZERO dependence on the type of

GUI. I really like that the feature works with ANY GUI toolkit. The host is

free to provide as few or as many options as it needs.
That one example of thinking in a platform independent way, without being

absurdly hard to implement, in fact real easy.
Jeff McClintock
_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-dev