Chris Cannam wrote: > On Thursday 22 Sep 2005 09:15, Peter Mogensen wrote: > >>I'm currently trying to come up with the best template for a more >>structured Lilypond export. >> >>I think considering to change the current mapping, which is: >> // Lilypond Voice = Rosegarden Segment >> // Lilypond Staff = Rosegarden Track >> >>To: >>Rosegarden segment = Lilypond notes >>Rosegarden Track = Lilypond Voice >> >>...and then keep the score/staff definition seperate. > > That sounds reasonable to me.
Before I go through a lot of trouble to maintain the current functionality with Lilypond versions < 2.4 while at the same time re-organizing the way everything is output, I'd like to ask what would be the preferred way: 1) Create a whole new exporter class, which handles the new way of exporting Lilypond 2) Code everything in the existing class while maintaining the old output for old versions (may result in not easy readable code) 3) Change the existing class and maintain only support for version >= 2.4 Others? I do not expect to be able to get nice working (and tested) Lilypond for version 2.2 or older. On the other hand... if people don't feel strongly about still supporting these old versions, there's no reason for me to spend time worrying. Peter ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
