Sun, 25 Apr 2004 21:55:23 +0200, Jan a dit :
> Looks good. When you feel this has fleshed out, there should be some
> documentation (but I'm still `waiting' for the \book stuff to
> stabilize before writing real documentation, eg).
OK, of course. Even if the internals will change, the interface, which
is still simple, can be documented. I'm beginning a draft.
> Maybe the explanation of #{ #} should already be moved/added to NEWS
> file?
a possible explanation for NEWS.texi:
* LilyPond expressions can be embedded into Scheme, thanks to the
`#{ ... #}' syntax. Within such a block, Scheme forms, for
instance variable names, can be introduced thanks to a `$'
character (`$$' has to be used to issue a single `$' character).
These forms are then 'printed' in the pattern, as if they were
called by (display).
#(define (textoffset dx dy)
(ly:export
#{ \override Voice.TextScript #'extra-offset = #(cons $dx $dy) #}))
\score {
\notes {
c'^"normal text"
%% the following statement is the same as
%% \override Voice.TextScript #'extra-offset = #(cons 2 -3)
#(textoffset 2 -3)
c'^"text with offset"
}
}
nicolas
_______________________________________________
lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
