Implement functions that compile the example scores depending on their type. I.e. they should compile them and do the necessary cleaning up afterwards (remove unnecessary files, rename .preview files (or compile differently from the beginning).
Really think about how LilyPond, LaTeX and Python share their work here. Consider practical work-flows equally as other considerations (e.g. one shouldn't be too restricted to having Python trigger LilyPond, it's better if one can compile scores directly via CLI or in Frescobaldi)
uliska
commented
6 years ago
Implement functions that compile the example scores depending on their type. I.e. they should compile them and do the necessary cleaning up afterwards (remove unnecessary files, rename .preview files (or compile differently from the beginning).
Really think about how LilyPond, LaTeX and Python share their work here. Consider practical work-flows equally as other considerations (e.g. one shouldn't be too restricted to having Python trigger LilyPond, it's better if one can compile scores directly via CLI or in Frescobaldi)