> I'll look into more detail when I build cabbage. What's the difference
> between menu and combobox? Also what exactly does the textctrl do?

Menu creates the main menu bar for the compiled application as you
have in most applications. This changes the compiled application form
a simple dialogue based interface to something a little more advanced.
>From a menubar you can call functions to start/stop Csound, open the
CsOptions dialogue and things like that. You can also use a dropdown
menu from the main menubar as a combobox type of control. TextCtrl is
just like a label. It can be used to monitor values from Csound or
send numerical data to an instance of Csound.

> I've googled, but it seems it can work on windows but has problems elsewhere...

This isn't such a big problem as most hosts provide GUI interfaces for
plugins so there is not much need to build independent interfaces,
although it would be nice. What might be nice is if people building
plugins using csLADSPA for example could also compile them as
standalone instruments using cabbage. Again, this shouldn't be
difficult to do.

With regards to parsing the cabbage syntax of a csd file I have simple
C++ class that does all the parsing. It's not dependent on wxWidgets
so it would be very easy to use it in other applications. It might be
something that simplifies integrating cabbage into quteCsound, if
that's something you might be interested in. Best thing is for me to
fix the linux build, let you have a look and then we can discuss it
further.

One other thing that I would like to do is to consolidate the existing
simple plugins frameworks such as csLADSPA, csVSTi and csVSTfx, and
add implementations for AU, Lv2, and directx. If we consildate the
syntax so that each uses the same simple syntax then users can share
csound plugins across hosts and platforms. Someone using csound driven
plugins on cubase can then share they're plugins with someone using
Ardour. That's perhaps something for another thread...

Rory.