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, snippet [DONE] 2) test the same mechanism for at least two other properties: [IN PROGRESS: I'm currently testing the position of the Beams] 3) once we have had proof that the mechanism works in general, extract the generic API template in JS [TODO] 4) fix points like the ones you listed in the generic template [TODO] I will certainly need help, and I already have a question regarding the Beams, which I am about to post on the user ml thanks for your help! Best, P On Mon, Dec 16, 2019 at 10:31 AM Urs Liska <li...@openlilylib.org> wrote: > > 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* > > automatically activate the functionality but provides a command to > > selectively switch it on and off or apply it to only one curve. > > There may be people who don't want the whole score to be polluted > > with the control points but only see the slur they want to edit. > > > Forgot one thing here: In addition to have an includable file in the > LilyPond directory I'd suggest making it also available through a > command line option. This will make it easier to use the functionality > from external scripts or editors. > > >