Hi Michael, Apologies but don't have too much time at the moment to comment, but I would like to say that whatever requirements we gather up, it would be *very* nice to record them and organize them into milestone points that could lead up to a release. Having milestones would also help testing as we could say "these features were implemented for the M3 release; please focus testing on these features". Besides the milestones, it might also be worth keeping a queue of features for a Csound 5.2 or 6.0. steven On 10/27/05, Michael Gogins wrote: > I'm open to suggestions here. One advantage of CsoundVST for Python work, is that it gives you the ability to stop a running performance by clicking on a button; CsoundVST bails out of the csoundPerformKsmps loop in that case. > > I'd be quite interested to hear your thoughts -- or anyone's thoughts! -- on how Csound 5 can, will, or should be used. A wish list would be nice. My interests focus on writing compositions as code including both orchestra and score stuff, but I would like to know what people would like to see: is a GUI front end important, a DSSI plugin important, a VST plugin important, language interfaces, etc. > > Thanks, > Mike > ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net