1 May
2004
1 May
'04
6:30 a.m.
On Sat, May 01, 2004 at 12:38:43 +0200, Tim Goetze wrote:
[Steve Harris]
There UI's, not GUI's, thye might require X, but equally they might
require a MIDI fader box, or a games console controller, or any other
wacky device you can imagine.
But yeah, the idea is that if you dont run the UI the plugin will still
come up in the state it was last. Its not mandatory to use configure() or
provide a UI, probably many can do without - eg. a piano keyboard driven
pitchshifter doesnt really require a custom UI and definatly doesnt need
configure.
- Steve
Everything that goes over configure() is/can be
prietary to the plugin, it
would be up to the plugin author wether they documented or not.
The only requirement is that data is passed that way do that the host can
restore the state reliably.
so gui-less application is eventually possible by running the gui
for configuration, saving the state and restoring it when running
headless. that or the plugin author provides configuration info.
sounds fair enough, but still requires you to install X and the
toolkit of the plugin's choice.