James McCartney wrote:
>
> OK I see. Well in this respect BeOS is ahead because their MediaKit
> already implements a way for media components to talk to each other.
> The downside is that it is a very complex API and you must use C++.
> 
> Such a framework on Linux would be very interesting.
>
I actually started this. With the ALSA sequencer it was easy to
implement the MidiKit classes. Though once I finished, I discovered
the signal mechanisms in Gtk--, which allow unrelated classes to be
connected to receive signals from each other. So I decided to implement
my classes using this mechanism instead of deriving from the MidiKit
base classes to implement functionality. I had never liked the
approach of requiring derivation in order to get functionality. It 
seems to always cause code-bloat.
 
Thomas

dupswapdrop: the music-dsp mailing list and website
http://shoko.calarts.edu/~glmrboy/musicdsp/music-dsp.html

>I actually started this. With the ALSA sequencer it was easy to
>implement the MidiKit classes. Though once I finished, I discovered
>the signal mechanisms in Gtk-- ...

Thomas - be sure to switch to Karl Nelson's new implementation of
this, libsigc++, which greatly reduces both the memory and run-time
cost of signal sending and receiving. Gtk-- will use this in some
RSN/future version.

     http://www.ece.ucdavis.edu/~kenelson/libsigc++/

Quasimodo uses this for all non-GUI inter-object signalling. Because
the GUI is GTK, it uses the current Gtk-- method, but these will
obviously become the some thing as soon as Gtk-- switches.

--p

dupswapdrop: the music-dsp mailing list and website
http://shoko.calarts.edu/~glmrboy/musicdsp/music-dsp.html