Subject: Re: [linux-audio-dev] ladspa GUI round 2
From: Paul Davis (pbd_AT_Op.Net)
Date: Thu Mar 29 2001 - 23:33:17 EEST
>I'm not sure what routing you images, but I would like to see:
>
>---------- ----------
>| | | |
>| Host |--->| Plugin |
>| | | |
>---------- ----------
> ^ ^
> | |
> | |
>---------- |
>| GUI |<-------/
>----------
>
>Obviously the GUI needs to be linked to the plugin in some way, but I
why ? the GUI sends control messages to the host, and all it needs is
a way to identify the plugin, not to communicate with it.
>I was imagining that the plugin would only invoke the gui if/when the host
>requested it, or mauybe the plugin should just broive the host with a
>method or data required to open the custom interface.
this brings up a good point. a plugin that was running under a
console-only host and has a Qt plugin should probably be advised to
not bother starting the GUI process. how best to do that ? do we have
the host pro-actively initiate the GUI (allowing it to choose not to
do so), or do we have the host tell the plugin that the run-time
environment is <console|xwindows|something-else> ?
--p
This archive was generated by hypermail 2b28 : Sat Apr 07 2001 - 15:56:04 EEST