Carl Sorensen <[email protected]> writes: > On 1/28/10 12:49 PM, "David Kastrup" <[email protected]> wrote: > >> Carl Sorensen <[email protected]> writes: >> >>> On 1/28/10 7:25 AM, "David Kastrup" <[email protected]> wrote: >>> >>>> Anyway, I think that likely the ambitus engraver would be a good >>>> candidate for reimplementing as a Scheme engraver. It would appear >>>> reasonably straightforward but not trivially so, and it is one of those >>>> things where augmenting the _code_ and behavior is likely to be better >>>> extensible in Scheme. >>> >>> I think it would be difficult to implement as a Scheme engraver, >>> because there need to be variables stored as part of the context that >>> are modified by different event handlers. But I could be wrong. It >>> wouldn't be the first time and is not likely to be the last. >> >> If you aren't wrong know, I hope you'll become so in future. I think >> that all the interactions of a "standard" engraver doing nothing out of >> the ordinary should be describable in terms of Scheme, even if the >> actual implementation might be C++ for performance reasons. > > Well, the ambitus engraver does do something out of the ordinary. It > watches for all the notes, but doesn't create grobs for any of them.
That's not unusual. Everything that needs to comprehend some passage of music (for example, chord namers) does that, and might create grobs in a different context. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
