Ok I think I understand a bit more how things are organized. Correct me if I am wrong: - You want to minimize the dependencies between importers, and the Musescore model, i.e. libmscore. The main benefit is that you keep flexibility to change things without bothering of what it might break. The main drawback is that there is a further step for importing other filetypes, that is converting it into MusicXML. - There are GuitarPro, Capella and other file formats importers because they are historical, and light enough to be kept.
I have an unrelated question. Is there some data loss when saving to MusicXML instead of .mscz ? I imagine there is, or else .mscz would not be necessary. -- View this message in context: http://dev-list.musescore.org/Noteworthy-Composer-files-support-tp7579582p7580077.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
