From: Tobias D. <tob...@gm...> - 2009-04-09 14:18:52
|
Hi, Am Thursday, 9. April 2009 16:00:58 schrieb Martin Andrews (LMMS): > But (as far as I understand it) the QT GUI would only need to present > itself if the LV2 plugin didn't specify it's own GUI (with the > dependency on GTK in the plugin, rather than LMMS). Yeah that's possible. Didn't take a deeper look at LV2 yet. > So, the need for a LV2 GUI part would be limited to an > alternative/fall-back 'autocreated' GUI which would consist of a large > bunch of sliders and switches - yes ? Yes - like done for LADSPA plugins. I think we should start writing a generic framework which generates a control panel for all kind of plugin types. This would avoid duplicate effort when adding GUI support for GUI-less VST plugins (this is planned for 1.0). This way we would have one unified plugin GUI generator for LADSPA, LV2 and VST. Should I start with a generic model/view approach for plugin control panels and you're starting with basic LV2 integration? Or do you want to make up the framework based on current LADSPA code on your own? > If so, I'm guessing you'd like the GUI components to be sourced from > the LMMS source-tree for consistency? And (this is further down the > road), maybe the LV2 plugin directory could have some kind of layout > file in it, to organize the controls more nicely? Yes - definitely use LMMS' views (widgets) and the models behind them so all controls can take part in the powerful automation- and controller-framework :-) Maybe you want to join our IRC channel so we can continue discussing there. I'll join at about GMT 8:30 PM (in 6 hours). Toby |