Lilypond exportation: roadmap?
As in the subject, is there any sort of 'roadmap' about Lilypond exportation development? I use - and appreciate - MuseScore to create sheets to be edited and refined with Lilypond, and so I'm very interested about this function development.
Thanks!!!
Comments
As a start you may list the feature you really want to be developed.
In reply to Features missing by [DELETED] 5
Thanks for your reply! I'd particularly appreciate a clearer, neater parts organization - i.e. more similar to Frescobaldi (the software, not the composer!)'s one.
I find the parts organization, as it is in MuseScore exported files, a bit intricate, if I can say so; as I could notice, MuseScore exportation organizes parts in series of \context blocks, which - in my humble opinion - can bring to a very intricate structure in more complex pieces. I also find it uncomfortable to edit, and generally I prefer copying all the parts' notes in a new-written structure.
Frescobaldi tends to avoid the use of \context blocks, using instead a simpler and neater succession of \new ones. I think this reflects the more recent Lilypond trend, and I'd appreciate very much a similar approach.
In a more general way, I'd appreciate very much if MuseScore could contemplate any sort of interoperability with Frescobaldi or other Lilypond front-ends, in order to make the editing work simpler.
I hope I've written in a readable English, and I beg you to excuse me if I some imprecisions occurred - I'm now a novice of Lilypond, and I'm learning it day after day: I don't know a lot of things yet, but I'm trying to improve.
Thank you very much!!!