Chris Cannam wrote: >>I'd like to ask what would be the preferred way: > > > I vote for this, probably: > > >>1) Create a whole new exporter class, which handles the new way of >>exporting Lilypond > > > Provided you reuse via cut and paste as appropriate. We can always include > both classes.
OK... I'll start with a brand new exporter class. > -*- > > This might be OK, depending on just how unreadable: > > >>2) Code everything in the existing class while maintaining the old >>output for old versions (may result in not easy readable code) Not more unreadable than code in general is when it try to do things in to rather different ways in the same code. That's mean a whole lot more of if-statements. But I'll do the new class instead. 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
