Subject: Re: [linux-audio-dev] Re: proposed initial DTD for LADSPA-gui-xml .. licensing issues ...
From: David Benson (daveb_AT_idealab.com)
Date: Mon Nov 27 2000 - 14:38:58 EET
On Mon, 27 Nov 2000, Steve Harris wrote:
> On Sun, Nov 26, 2000 at 09:33:22PM -0500, Paul Barton-Davis wrote:
> > the proposal, back in march or whenever, was to add:
> >
> > const char *(*xml_gui_description)();
> >
> > to the plugin API, and allow that it could be NULL if the plugin
> > author chose not to supply a spec for the GUI in this way.
>
> Much better. I can defualt it to loading foo.xml, as long as I can find
> what directory my .so file is in.
Actually, it seems like it's the hosts responsibility
to look for a file on the file system (in particular,
i'd prefer these files could be in separate dirs -- for standards
compliance it is a must since one is arch-dependent and the other
arch-independent.)
That is, i'd leave get_xml == NULL in this case
and have the host-specification talk about this.
Perhaps we could have a way of indicating that a
plugin comes "bundled" with some xml, so that the host
could print a more informed error message.
> Hints at the possiblity of dynamic/multiple interfaces too, depending on
> when xml_gui_description() is called.
>
> if (getenv("RUNNING_IN_ARDOUR")) {
> return ardour_lookalike_gui;
> } else {
> return other_thing;
> }
Hmm. Usually we complete the standard before
making incompatible extensions to it :)
- dave
This archive was generated by hypermail 2b28 : Mon Nov 27 2000 - 15:29:42 EET