Hi Marc, all,

On Thu, Mar 6, 2014 at 1:51 AM, Marc Hohl <[email protected]> wrote:

> Am 06.03.2014 00:12, schrieb Simon Albrecht:
>
>> [...]
>>
>> Why is this not in the LSR or even in
>> http://lilypond.org/doc/v2.18/Documentation/notation/graphical-notation?
>>
>
> AFAIK there is no way to use scheme engravers in the documentation yet,
> and the frame engraver is written in scheme.
>
> But including it into LSR would be quite helpful. Any volunteers are
> highly apprechiated ;-)
>
> Marc
>
>
I'm a bit conflicted about this.  Once the LSR is upgraded, it might be
possible to upload it there, where it will be more accessible to others and
in a safe place.

On the other hand, the method it uses to incorporate the new grobs is
problematic, and might even interfere with compiling the LSR (not sure).
 You'll run into problems when you use it with a batch of files (rather
than compiling files singly): there's bleed-over between sessions, so you
get errors concerning redefinition of the added properties.

This is really the only way there is to add a new grob now from an ly file,
though.  My motivation in using this method was convenience.  There's no
need (yet) to work in a development environment, and it's easy for others
to try it out and offer suggestions without needing to apply patches.  Once
it's in a usable state, I would move the various parts into their rightful
places: the grob definitions into define-grobs.scm, for example.
 (Bleed-over problem solved.)

Honestly, I'd love for this to make it into the code base someday.  There's
obviously use for it.  I must say, though, that the prospect of perfecting
it is a bit daunting and endless.  (One look at the code will make my
point, I think :) )  I frankly don't know when I would be able to devote
time to finishing it.   And I could certainly use assistance.  Finding bugs
is helpful, but the big issues are ones of Lilypond internals and coding,
I'm afraid.  As far as suggesting enhancements--that's best left for when
the thing works without a hitch!

As I remember it from when I last left the code, the latest problem is
getting the thing to work with multistaff boxes.

(And it would be nice to get the thing to interface with the actual code
for barlines, so there's no need to draw fake barlines for the repeat
structures.  If this interface isn't reasonably possible, that feature will
need to go.)

End to rambling thoughts.

--David
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to