Comment #22 on issue 2449 by [email protected]: Redesign stream event class representation
http://code.google.com/p/lilypond/issues/detail?id=2449
Of course, the last comment is rubbish except for indicating Patch-new state: our submission system is not really helping much beyond the first submission.
The last patch turns the event class hierarchy into something maintained in the Global context and initialized from the EventClasses property. It also futzes different ad-hoc user interfaces onto scheme-text-spanner.ly. Nothing to be proud of: this just gets rid of the architectural insanity of tampering with global variables for grob definitions and event classes. But I suck at creating user interfaces and did not really think much about this, only tried getting something working.
So please comment what you'd consider usable here. The mechanisms are workable, but most of the rest is ridiculous.
