- + code simplification: current music rendering code can be removed
- + high quality.
- + code shared with other projects: no duplicate/parallel work.
- + a plus for both solfege and lilypond.
- - less flexible: new lessonfile cannot run instantly
- - less flexible: every transposition needs to be built before use. Example: ID-interval with random generated questions can have 12 intervals x 2 directions x 12 transpositions... 288 graphics !?
- - less flexible: user cannot add transpositions
- - We cannot make full use of all lilypond rendering quality for
- horizontal music spacing (for example random generated rhythm!)
- dynamic rescaling (lily can use bolder fonts for smaller print, revise layout for print on letter/A4 paper)
- - increased download size
- - we'll need a public Lilypond server so teachers can create music fragments for lesson files
Tom Catos opinion:
- We will always need to generate some music at runtime, and because of that I don't want to use lilypond at build time for things where we use the
mpd (Music Parser and Displayer) module today.
- We will use lilypond generated graphics in the users manual, as we do today.
