> At this point, here's the complete all-in-one .ly template. [...]
It would be nice if you could format this to avoid line lengths longer
than 80 characters. As the non-HTML part of your e-mail shows, the
code becomes very hard to read otherwise.
Werner
I wouldn't worry so much about overriding that define, as svg-end can
only be used at that one spot or the output file would be corrupted.
A patch that included a proper override was provided 9 years but
ignored. I'll get the relevant parts of the patch up-to-date as it is
proving potential.
Than
At this point, here's the complete all-in-one .ly template. Much cleaner
and without risks to mess the code, for the user. In addition, it has not
to be patched: just open and use the generated .svg file.
Hope it could be included in the snippets repo. Thanks all for your
collaboration!
%
To Stefano and Elaine:
really, it's better to avoid scripting on scripting on scripting, IMHO. SVG
is designed to be lovely coupled with JS, and the output file should be
all-inclusive. Nor HTML is required. Only Lilypond and any SVG viewer
(including browsers). The override of internal stuff pro
Hello Aaron,
I understand that it is potentially dangerous because this is not API but
we are accessing it like API. However, looking at the code, svg-end is
referenced only inside its def file (framework-svg.scm), as a dummy append
to the output file:
http://git.savannah.gnu.org/gitweb/?p=lilypo
On 2019-12-14 6:16 am, Paolo Prete wrote:
However, how can I make it work for multiple pages output?
Another approach would be to modify how LilyPond generates SVG output,
so that the script in question is inserted just before the closing
element:
\version "2.19.83"
svg-script = #(de
Hi Paolo, I was also having that concern.
Elaine replied in a new thread with a solution for that, in which instead
of adding the script to the svg files with lilypond you just use an
external script. I haven't tested it yet but it seems to me like that'll be
a cleaner approach, you just include t
Hi Stefano,
your suggestion produces the script for every page, but it requires to
manually add a property in the \paper scope. Instead, I would like to
automatically set this property, and leave the user to set all the score
properties (including the paper's one) without messing up the code addin
Hi Stefano,
your suggestion produces the script for every page, but it requires to
manually add a property in the \paper scope. Instead, I would like to
automatically set this property, and leave the user to set all the score
properties (including the paper's one) without messing up the code addin
> From: Stefano Troncaro
> To: Paolo Prete
> Cc: Aaron Hill , lilypond-user <
> lilypond-user@gnu.org>
> Date: Sat, 14 Dec 2019 19:13:43 -0300
> Subject: Re: A Javascript test code for modifying ties and slurs with mouse
> Hi Paolo,
>
> Since Aaron's svg-script function creates an empty \markup,
On Fri, Dec 13, 2019 at 11:47 AM Flaming Hakama by Elaine
wrote:
>
>
>
>> From: Ignacio Lois
>> To: lilypond-user@gnu.org
>> Date: Thu, 12 Dec 2019 12:02:42 -0300
>> Subject: Weinberg Drumkit Map
>> Hello everyone,
>>
>> Lately I was pointed in Norm Weinberg's direction for a standard drumkit
>>
Robin Bannister writes:
> The non-mapping cases
>\markup \box \concat { "X" "Y" "Z" }
> and
>#(markup #:box #:concat ("X" "Y" "Z"))
> give one box without complaints
>
>
> The mapping case
>\markup \concat \box { "X" "Y" "Z" }
> gives 3 boxes without complaint, but
>#(markup #:con
Hi Paolo,
I reckon this isn’t easy to write, since you have to basically split the
expressions up into individual elements and analyse them.
You can sometimes reduce effort by ‘cheating’ using simultaneous
expressions within the voice like in this mockup: (if you explicitly
instantiated the
> From: Paolo Pr
> To: Urs Liska
> Cc: lilypond-user
> Date: Sat, 14 Dec 2019 02:59:58 +0100
> Subject: Re: A Javascript test code for modifying ties and slurs with mouse
> Thanks Urs and Elaine for your appreciation.
>
> Note that the same algo I wrote with (relatively) short code can be
> app
Hi Paolo,
Since Aaron's svg-script function creates an empty \markup, you can use the
properties oddFooterMarkup and evenFooterMarkup of the \paper block to have
your script embedded at the end of every page. Look:
%%%
\version "2.19.83"
svg-script = #(define-sche
Thanks Aaron, it did the trick.
However, how can I make it work for multiple pages output?
On Sat, Dec 14, 2019 at 4:26 AM Aaron Hill wrote:
> On 2019-12-13 5:59 pm, Paolo Pr wrote:
> > First of all, I need to add with Lilypond a tag to the svg
> > file
> > just before the ending tag
That should work. It might need some completing though. Is there a drummer
in the house?
On Fri, 13 Dec 2019, 16:47 Flaming Hakama by Elaine, <
ela...@flaminghakama.com> wrote:
>
>
> From: Ignacio Lois
>> To: lilypond-user@gnu.org
>> Date: Thu, 12 Dec 2019 12:02:42 -0300
>> Subject: Weinberg Dru
Hi all,
I think this function would be very useful for solving the limitations of
the current cross-staff interface:
crossStaffExpr = #(define-music-function (parser location staffUpMusic
staffDownMusic beamPosition) (ly:music? ly:music? number?) .
Example:
\crossStaffExpr = { c '[ d'
Il giorno ven 13 dic 2019 alle 23:48, Thomas Morley
ha scritto:
The feature embeds the source as an *attachment* within the PDF. I
would assume both evince and Foxit know how to handle attachments.
If so, then they refuse to tell me how to participate.
And I will not spending hours to resea
19 matches
Mail list logo