[linux-audio-dev] soft synth as a plugin

[Josh Green]

On Fri, 2002-10-18 at 11:16, Paul Davis wrote:
> >but personally i find it much more desirable that the plugin provides
> >effectively a widget which can be added to a container (provided by the
> >host) rather than the plugin creating its own window. its just much
> >neater..
> 
> this makes no difference to the problem. whether the plugin creates a
> widget or a window, the integration of the event loop is still a
> central blocking problem.
> 

Please enlighten me, what was the problem then with multiple GUI
toolkits? IIRC it had to do with not being able to integrate multiple
applications together very well (at least as far as the user interface).

It seems like something of this nature should be implemented at a layer
above the GUI toolkit, like the window manager for example. If there was
a way to layout multiple X windows (interface elements) on a single
window and be able to edit their dimensions, manage placement, etc, GUI
toolkit would not matter so much. This also seems to kind of tie back
into the metadata/session storage discussion that was going on before. I
like the idea of multiple programs working together in a Linux
music/audio session, but I can forsee the nightmare of having dozens of
windows scattered all over the desktop.

> >I thought Gtk(mm) is a more natural choice, since it is freely available
> >on all platforms, voila.
> 
> many Qt users feel otherwise. and wxWin is available too, along with
> several other kits.
> 
> --p

GTK doesn't support as many platforms as I would like (although I use it
with Swami/Smurf). It doesn't natively support Mac OS X (yet?) and
probably will never support Mac OS classic. wxWin seems to kick ass in
this regard. I'm currently really liking the Glib/GObject/GTK+ layer
effect. All my non GUI stuff is written using GObject so its GUI
independent and I can do OO programming and stick with C (C++ has scared
me away a little, although I can understand the advantages). Cheers.
	Josh Green