Okay, some more thinking on the framework section... Perhaps the master framework should handle GUI drawing for all modules. That way, module writers don't have to worry about drawing a GUI. All they need to do is report their parameter names, types, and ranges back to the master app.
I'm imagining an Ableton-ish interface, with a set of blocks up top to show modules and routing, with a window down below holding the master section and then drawing the controls for the highlighted module. I'll see if I can draw up a mock-up of what I see in my head, but I'm no graphic artist, so it might be rough, but it'll at least make me feel like I'm doing something useful. :) What else should the master framework do? Interfacing with JACK/ALSA, processing MIDI input, allow scripting, stuff like that, maybe? More pot-stirring to come, I'm sure. -- Darren ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
