Hi,
I'm not sure I entirely follow you.
Capella and overture support is currently a single file (ove.cpp,
cap(x).cpp). It's more or less the same for GP. We could move these files
each one in its own library but there is not much value to it I believe.
Regarding the clean and reusable interface, it's more or less what we
already have. I called it "MuseScore internals" in my previous email
because this interface is a direct line to the MuseScore internal model.
Unfortunately, for this very reason, this interface is not very stable. If
we change something in the inner model, for a new feature or an
optimisation, the interface changes too. We could fix the interface but
that would reduce our speed to innovate.
MusicXML is the perfect way to solve this problem. It provides a relatively
stable model and a converter just need to fill it. Of course, it means
MuseScore needs to have a great MusicXML importer, but I hope it does :)
In any case, take a look to the code and if you see room for improvements,
please contribute!
lasconic
------------------------------------------------------------------------------
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
