Subject: Re: [linux-audio-dev] ladspa plugin GUI proposal
From: Paul Barton-Davis (pbd_AT_Op.Net)
Date: Fri May 26 2000 - 17:44:27 EEST
In message <Pine.LNX.4.10.10005260657140.25202-100000_AT_luca.pas.lab>you write:
>> Karl JH Millar wrote:
>> There has been some discussion of using multiple toolkits simultaneously. I
>> think this is a terrible idea, even if it is possible. In overly complicates
>> things, and makes it very difficult, if not impossible for a plugin's displa
>y
>> to appear in the same toplevel window as other widgets.
>
>this definitely is a problem, even though i suspect
>gtk and kde can reparent windows owned by other processes
>somehow...
I think that the GtkSocket/GtkPlug widgets are based on this general
idea, but they may require that both sides of the "connection" be
using GTK+. So I am not actually convinced that GTK+ *can* do this.
Besides, it doesn't solve the more general issue. Anyway, I would be
happy to standardize on:
"if a host allows a plugin to construct its own GUI, and if
the plugin actually does so, that GUI will appear in its
own, detached window."
As benno pointed out, this is the model for VST (and in fact, most
other) plugins.
>(which raises the small issue of determining which
>toolkits are supports by each plugin)
i think you mean "which toolkits are used by each plugin", right? its
just another part of the GUI spec for the plugin. Once again, if the
host doesn't support the toolkit(s) used by the plugin, the host can
either reject the plugin, or build the (G)UI itself, which it may have
decided to do anyway.
--p
This archive was generated by hypermail 2b28 : Fri May 26 2000 - 19:52:43 EEST