Subject: [linux-audio-dev] [ ardour ] whats going on
From: Paul Davis (pbd_AT_op.net)
Date: Tue Mar 27 2001 - 06:42:18 EEST
well, as a continuation of the work represented by the aes program, i
am currently splitting up the "gtk_ardour" code from the "ardour"
code. this is motivated by a separate but related project that i am
undertaken to initiate a keystroke-driven mixing program for use by
blind users.
much like the divisions in quasimodo between gtk_quasimodo and
stephane conversey's server-quasimodo, there will be at least two
interfaces that use the code in ardour that is already GUI
independent. the gtk-based stuff will continue to function as a plugin
for aes. the keystroke one (not even curses, just keystrokes and
shell-like responses) will interact with aes in a way as yet to be
determined.
this will also facilitate work by anyone who wants to use the
internals of ardour to produce a very different GUI to go with it.
the end result is probably going to force a major overhaul in the CVS
repository, but thats the least of my concerns right now.
i don't enjoy this work very much, and its mostly a distraction from
the real tasks at hand (bugs, peakfile usage, the editor), but i
believe (strongly) that its part of a necessary process to convert the
existing codebase into a useful resource with more flexibility than
the current scheme. the GUI independent code in ardour should really
be reusable by other people, and it is, but right now, the source
structure doesn't make it clear that this is so, or how to go about
doing it. i think that the new source structure will make this much
clearer, just as the libaudioengine/aes split makes it clear how to
use the AudioEngine model that has developed over the last year.
--p
This archive was generated by hypermail 2b28 : Sat Apr 07 2001 - 15:38:48 EEST