For your information, I am currently working on migrating the MusicXML parser from the current DOM parser to the (new) pull parser, which is also used for reading MuseScores .mscx files.
As this is a significant effort (the MusicXML importer is about 8500 lines of code), it is most efficient to do it while the MuseScore core is quite stable (which is now, before we start work on new things for the post 2.0 release). Due to the obvious risk, this should not be included in 2.0 anymore. It is my intention to be ready for commit soon after 2.0 is done. Note that I consider neither of the current open MusicXML importer issue a showstopper and do not intend to work on these until the pull parser migration is done. If anyone disagrees please let me know. Finally, consider this a request to try to limit MusicXML importer changes to a minimum until the migration is done, or consult me about how to do this without causing a significant merge effort. Regards, Leon. -- View this message in context: http://dev-list.musescore.org/Migrating-MusicXML-import-to-pull-parser-tp7579106.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
