Subject: Re: [linux-audio-dev] ladspa GUI spec status?
From: Robert Jonsson (robert.jonsson_AT_dataductus.se)
Date: Thu Feb 22 2001 - 13:12:38 EET
.Steve Harris wrote:
> On Thu, Feb 22, 2001 at 03:32:14PM +1100, Conrad Parker wrote:
>
>> yup -- any X program can be embedded in another, this is a feature
>> of X11 (reparenting, in X11-speak).
>
>
> I was actually thinking of a completly independent window from the app,
> but that was interesting, thanks.
>
> I have an idea for a plugin that needs to load a pcm file when it starts,
> poping up a file load diaglog is the only sane thing I could think of.
>
> Other things I thought of were setting an environment variable (yuk), or
> always loading from, say /tmp/sampleN.wav where n is a plugin parameter
> (also yuk), or combinations of the two.
I would vote for a config file. The config file could contain a whole
bunch of wave files. When using the plugin you could choose between them
with one of the parameters.
If using a GUI approach and many plugs where instantiated at the same
time it could easily become unbearable. For instance during loading of a
song...
Also I'm mildly sceptic to gui toolkit dependencies INSIDE of a plugin.
Aren't GUI toolkits mutually exclusive? Atleast I don't think it's
possible to link against both gtk and qt in the same program.... should
that not also apply to plugins??
>
> The right answer of course is not to use LADSPA, but I don't know of any
> alternatives just yet.
>
> - Steve
This archive was generated by hypermail 2b28 : Thu Feb 22 2001 - 15:23:13 EET