In response to Elaine and Urs
1) I already thought about the way to automatically feedback the
modifications to the original .ly file, instead of the alert() string.
Again, it will be 100% JS + SVG. Just have a little patience ;-)
Basically, Lilypond will have to import the original .ly code as
-- Forwarded message --
> From: Urs Liska
> To: lilypond-devel@gnu.org
> Date: Mon, 16 Dec 2019 10:18:36 +0100
> Subject: Re: A snippet for editing curves using the mouse and reporting
> changes to the .ly file
> Hi Paolo,
>
> I have followed the discussion but didn't have the
Hi Urs,
of course the points you listed must be fixed. I was already aware about
them.
I'm following a specific workflow, and those points will be fixed at a
later time. Meanwhile, it's a good idea to keep track of them.
The workflow is as follows:
1) prepare an * usable *, even if limited,
Am 16.12.19 um 10:18 schrieb Urs Liska:
* For integration in LilyPond the functionality should be wrapped into
a single file that can be included. Including the file should
automatically activate the functionality.
Maybe there should be a second includable file that does *not*
Hello,
the snippet attached to this mail allows the tuning with the mouse of the
curves generated by Lilypond so that the changes can be reflected on the
original .ly file.
The tuning is done on the generated SVG file, as explained in this thread
(but you can look at the code of the attached
