Free/open source projects that succeed seem to follow the pattern of moving as much functionality as possible out into plugins/modules that can be decoupled from the core code. This makes for something of a "Darwinian" development process as individual plugins can be written, debugged put into the optional list, tried out, used, and ultimately replaced. Also it makes it easier to code, test and understand the code.
I would suggest: - have test benches for plugins so they can be debugged and tested independently of the main program. - use Cinelerra-independent standard interfaces if possible, so that the plugins can be reused in other projects, and other project's plugins can be used in Cinelerra. Generally go for standard everything (and cross-platform) if at all possible, you get more people who already know it: - C or C++, python, ant, wxWidgets (what does Cinelerra use at the moment?) - there is a standard Edit Decision List (EDL) format out there; could Cinelerra use that too? -- Regards, Martin ([EMAIL PROTECTED]) IT: http://methodsupport.com Personal: http://thereisnoend.org
