>> (B). native api: support whatever toolkits you like explicitly >> in each plugin. > > in this case let's just let the plugin fork separate gui process (we >cannot forbid it anyway) and based on further experience we will see if >we need more organized support for this method). how can "the plugin" do this, when "the plugin" doesn't know anything about GUI's ? Remember, all UI's are initiated by the host. --p
- [linux-audio-dev] ladspa gui recap David Benson
- Re: [linux-audio-dev] ladspa gui recap Kirk Reiser
- Re: [linux-audio-dev] ladspa gui recap David Benson
- Re: [linux-audio-dev] ladspa gui recap Erik Steffl
- Re: [linux-audio-dev] ladspa gui recap Paul Barton-Davis
- Re: [linux-audio-dev] ladspa gui recap David Benson
- Re: [linux-audio-dev] ladspa gui recap Paul Barton-Davis
- Re: [linux-audio-dev] ladspa gui r... David Benson
- Re: [linux-audio-dev] ladspa g... Paul Barton-Davis
- Re: [linux-audio-dev] ladspa gui recap Erik Steffl