Jan Nieuwenhuizen wrote > Yes, that's correct. It's an ugly optimization that's needed because > lilypond would otherwise be too slow for interactive use. It will > probably only work (or seem to work) if the changes made are small > enough. Currently, partial engraving is line-based but we could > even go to measure-based. > > My hopes for Schikkers List (if any) are that it would aid in a guile > scheme to sneak the LilyPond dinosaur into the GUI age and thus help > keeping it's relevancy up. > > If something like Schikkers List would take-off that could trigger > a real need for partial compilation supported by LilyPond itself. > This is an enormous effort and is not likely to happen any > time soon, giving the overwhelming interest there has been in the > LilyPond community for anything GUI-related.
Thanks Jan. Just a quick follow up question: does Schikker's List use its own custom version of LilyPond (that has been optimized for partial compilation) or does it use standard LilyPond with external code providing for the partial compilation? Just curious... Thanks, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Serious-feedback-and-improvement-headroom-tp161193p161569.html Sent from the Dev mailing list archive at Nabble.com. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
