bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs.


From: lilypond
Subject: Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs.
Date: Wed, 11 Jan 2012 14:36:36 +0000


Comment #15 on issue 2171 by address@hidden: Patch: Implements DOM-id property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171

What is so special about DOM-id's that would warrant code hand-tailored to them and nothing else? I am pretty confident that this is fringe functionality. And when suddenly somebody figures that he'd like a COPE-id on something put out via SVG, what then? Copy, paste, repeat?

I think it would make sense to program this sort of functionality with a bit more focus on reuse. So that the next time someone wants to add another kind of Id, possibly even to a different backend, the code does not need reinventing or at least recopying.

Can you think about how this could be more general? It would have the advantage for you that people would stop pestering you to explain what a DOM-id is since that would then just be a detail relevant to your application of some more general XML-tagging algorithm.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]