Re: ANN: Spontini-Editor 1.0 released
Hello Saul, maybe if you can show us what the problem is we might be able to find some way to get the behaviour you want from a recent lilypond version. Valentin 21.10.2021 04:15:59 Saul Tobin : > Got it, thanks. > > This particular project is quite large and can't be updated past 2.18 due to > a change in the behavior of staff changing during part combining, which > breaks the method I use for managing wind staves. I'm not aware of a way to > accomplish comparable functionality in 2.19 or newer. I spent a few months a > couple years ago trying to write a patch but I eventually gave up. > > On Tue, Oct 19, 2021, 12:15 AM Paolo Prete wrote: >> Hello Valentin, >> >> porting the scheme/LilyPond functions used by Spontini-Editor, in its >> internal library, from 2.18 to 2.19, would not complete the compatibility. >> In fact, the editor relies on the SVG code generation too, which had changes >> during these years of LilyPond development. >> Therefore, the only way that Saul could use to accomplish what he asked, is >> to convert his score from 2.18 to >=2.19.84 and then feed Spontini-Editor >> with the converted score. >> >> >> Best, >> P >> >> >> >> On Tuesday, October 19, 2021, Valentin Petzel wrote: >>> Hello Saul, >>> >>> in many cases a 2.23 ly file will be compatible with a 2.18 Lilypond. >>> >>> The only problematic cases should be when Spontini uses overrides that did >>> not exist in 2.18 (which shouldn't be that many) or if you are using music >>> function that have changes names or syntax, which can also be amended by >>> renaming the new ones to old ones or creating wrapper music functions, so >>> you can have a few definitions that can simply be removed for 2.18. >>> >>> But is there any reason for using such an old Lilypond version? >>> >>> Cheers, >>> Valentin >>> >>> 19.10.2021 01:39:59 Saul Tobin : >>> Any possibility of using this with a Lilypond 2.18 project? >>>
Re: ANN: Spontini-Editor 1.0 released
Got it, thanks. This particular project is quite large and can't be updated past 2.18 due to a change in the behavior of staff changing during part combining, which breaks the method I use for managing wind staves. I'm not aware of a way to accomplish comparable functionality in 2.19 or newer. I spent a few months a couple years ago trying to write a patch but I eventually gave up. On Tue, Oct 19, 2021, 12:15 AM Paolo Prete wrote: > Hello Valentin, > > porting the scheme/LilyPond functions used by Spontini-Editor, in its > internal library, from 2.18 to 2.19, would not complete the compatibility. > In fact, the editor relies on the SVG code generation too, which had > changes during these years of LilyPond development. > Therefore, the only way that Saul could use to accomplish what he asked, > is to convert his score from 2.18 to >=2.19.84 and then feed > Spontini-Editor with the converted score. > > > Best, > P > > > > On Tuesday, October 19, 2021, Valentin Petzel wrote: > >> Hello Saul, >> >> in many cases a 2.23 ly file will be compatible with a 2.18 Lilypond. >> >> The only problematic cases should be when Spontini uses overrides that >> did not exist in 2.18 (which shouldn't be that many) or if you are using >> music function that have changes names or syntax, which can also be amended >> by renaming the new ones to old ones or creating wrapper music functions, >> so you can have a few definitions that can simply be removed for 2.18. >> >> But is there any reason for using such an old Lilypond version? >> >> Cheers, >> Valentin >> >> 19.10.2021 01:39:59 Saul Tobin : >> >> > Any possibility of using this with a Lilypond 2.18 project? >> > >> >>
Re: ANN: Spontini-Editor 1.0 released
Hello Valentin, yes, that would be the best way. Cheers, Paolo On Tuesday, October 19, 2021, Valentin Petzel wrote: > Hello Paolo, > > I did not mean it this way. I meant it like: In most cases one can prepare > a > score using Lilypond 2.23 (so using Spontini) that is compatible with a > Lilypond 2.18 version. > > So Saul can probably use Spontini and 2.23 to do his tweaks and still > obtain a > 2.18 compatible file. > > Cheers, > Valentin > > Am Dienstag, 19. Oktober 2021, 09:15:31 CEST schrieb Paolo Prete: > > Hello Valentin, > > > > porting the scheme/LilyPond functions used by Spontini-Editor, in its > > internal library, from 2.18 to 2.19, would not complete the > compatibility. > > In fact, the editor relies on the SVG code generation too, which had > > changes during these years of LilyPond development. > > Therefore, the only way that Saul could use to accomplish what he asked, > is > > to convert his score from 2.18 to >=2.19.84 and then feed Spontini-Editor > > with the converted score. > > > > > > Best, > > P > > > > On Tuesday, October 19, 2021, Valentin Petzel > wrote: > > > Hello Saul, > > > > > > in many cases a 2.23 ly file will be compatible with a 2.18 Lilypond. > > > > > > The only problematic cases should be when Spontini uses overrides that > did > > > not exist in 2.18 (which shouldn't be that many) or if you are using > music > > > function that have changes names or syntax, which can also be amended > by > > > renaming the new ones to old ones or creating wrapper music functions, > so > > > you can have a few definitions that can simply be removed for 2.18. > > > > > > But is there any reason for using such an old Lilypond version? > > > > > > Cheers, > > > Valentin > > > > > > 19.10.2021 01:39:59 Saul Tobin : > > > > Any possibility of using this with a Lilypond 2.18 project?
Re: ANN: Spontini-Editor 1.0 released
Hello Paolo, I did not mean it this way. I meant it like: In most cases one can prepare a score using Lilypond 2.23 (so using Spontini) that is compatible with a Lilypond 2.18 version. So Saul can probably use Spontini and 2.23 to do his tweaks and still obtain a 2.18 compatible file. Cheers, Valentin Am Dienstag, 19. Oktober 2021, 09:15:31 CEST schrieb Paolo Prete: > Hello Valentin, > > porting the scheme/LilyPond functions used by Spontini-Editor, in its > internal library, from 2.18 to 2.19, would not complete the compatibility. > In fact, the editor relies on the SVG code generation too, which had > changes during these years of LilyPond development. > Therefore, the only way that Saul could use to accomplish what he asked, is > to convert his score from 2.18 to >=2.19.84 and then feed Spontini-Editor > with the converted score. > > > Best, > P > > On Tuesday, October 19, 2021, Valentin Petzel wrote: > > Hello Saul, > > > > in many cases a 2.23 ly file will be compatible with a 2.18 Lilypond. > > > > The only problematic cases should be when Spontini uses overrides that did > > not exist in 2.18 (which shouldn't be that many) or if you are using music > > function that have changes names or syntax, which can also be amended by > > renaming the new ones to old ones or creating wrapper music functions, so > > you can have a few definitions that can simply be removed for 2.18. > > > > But is there any reason for using such an old Lilypond version? > > > > Cheers, > > Valentin > > > > 19.10.2021 01:39:59 Saul Tobin : > > > Any possibility of using this with a Lilypond 2.18 project? signature.asc Description: This is a digitally signed message part.
Re: ANN: Spontini-Editor 1.0 released
Hello Valentin, porting the scheme/LilyPond functions used by Spontini-Editor, in its internal library, from 2.18 to 2.19, would not complete the compatibility. In fact, the editor relies on the SVG code generation too, which had changes during these years of LilyPond development. Therefore, the only way that Saul could use to accomplish what he asked, is to convert his score from 2.18 to >=2.19.84 and then feed Spontini-Editor with the converted score. Best, P On Tuesday, October 19, 2021, Valentin Petzel wrote: > Hello Saul, > > in many cases a 2.23 ly file will be compatible with a 2.18 Lilypond. > > The only problematic cases should be when Spontini uses overrides that did > not exist in 2.18 (which shouldn't be that many) or if you are using music > function that have changes names or syntax, which can also be amended by > renaming the new ones to old ones or creating wrapper music functions, so > you can have a few definitions that can simply be removed for 2.18. > > But is there any reason for using such an old Lilypond version? > > Cheers, > Valentin > > 19.10.2021 01:39:59 Saul Tobin : > > > Any possibility of using this with a Lilypond 2.18 project? > > > >
Re: ANN: Spontini-Editor 1.0 released
Hello Saul, in many cases a 2.23 ly file will be compatible with a 2.18 Lilypond. The only problematic cases should be when Spontini uses overrides that did not exist in 2.18 (which shouldn't be that many) or if you are using music function that have changes names or syntax, which can also be amended by renaming the new ones to old ones or creating wrapper music functions, so you can have a few definitions that can simply be removed for 2.18. But is there any reason for using such an old Lilypond version? Cheers, Valentin 19.10.2021 01:39:59 Saul Tobin : > Any possibility of using this with a Lilypond 2.18 project? > > On Sun, Oct 17, 2021 at 6:21 PM Jon Arnold wrote: >> Looks promising. The ability to edit slurs with a mouse is huge. >> >> On Sun, Oct 17, 2021 at 2:07 PM Paolo Prete wrote: >>> Hello all, >>> >>> I just drafted a new release (1.0) of Spontini-Editor, which is now >>> compatible with LilyPond 2.23.0 to 4 >>> >>> https://github.com/paopre/Spontini >>> >>> Furthermore, it offers a tool that allows you to include or exclude blocks >>> from the building process of the score. >>> >>> I encourage the use of the editor, which I could test intensively, because >>> it is essentially bug-free, it works perfectly on a Raspberry PI (or any >>> similar cheap hw) and it allows you to create *very complex* piano scores. >>> >>> Any feedback is greatly appreciated! >>> >>> HTH >>> P.
Re: ANN: Spontini-Editor 1.0 released
Sorry, this is not possibile. Best, Paolo On Tuesday, October 19, 2021, Saul Tobin wrote: > Any possibility of using this with a Lilypond 2.18 project? > > On Sun, Oct 17, 2021 at 6:21 PM Jon Arnold > wrote: > >> Looks promising. The ability to edit slurs with a mouse is huge. >> >> On Sun, Oct 17, 2021 at 2:07 PM Paolo Prete wrote: >> >>> Hello all, >>> >>> I just drafted a new release (1.0) of Spontini-Editor, which is now >>> compatible with LilyPond 2.23.0 to 4 >>> >>> https://github.com/paopre/Spontini >>> >>> Furthermore, it offers a tool that allows you to include or exclude >>> blocks from the building process of the score. >>> >>> I encourage the use of the editor, which I could test intensively, >>> because it is essentially bug-free, it works perfectly on a Raspberry PI >>> (or any similar cheap hw) and it allows you to create *very complex* piano >>> scores. >>> >>> Any feedback is greatly appreciated! >>> >>> HTH >>> P. >>> >>
Re: ANN: Spontini-Editor 1.0 released
Any possibility of using this with a Lilypond 2.18 project? On Sun, Oct 17, 2021 at 6:21 PM Jon Arnold wrote: > Looks promising. The ability to edit slurs with a mouse is huge. > > On Sun, Oct 17, 2021 at 2:07 PM Paolo Prete wrote: > >> Hello all, >> >> I just drafted a new release (1.0) of Spontini-Editor, which is now >> compatible with LilyPond 2.23.0 to 4 >> >> https://github.com/paopre/Spontini >> >> Furthermore, it offers a tool that allows you to include or exclude >> blocks from the building process of the score. >> >> I encourage the use of the editor, which I could test intensively, >> because it is essentially bug-free, it works perfectly on a Raspberry PI >> (or any similar cheap hw) and it allows you to create *very complex* piano >> scores. >> >> Any feedback is greatly appreciated! >> >> HTH >> P. >> >
Re: ANN: Spontini-Editor 1.0 released
Looks promising. The ability to edit slurs with a mouse is huge. On Sun, Oct 17, 2021 at 2:07 PM Paolo Prete wrote: > Hello all, > > I just drafted a new release (1.0) of Spontini-Editor, which is now > compatible with LilyPond 2.23.0 to 4 > > https://github.com/paopre/Spontini > > Furthermore, it offers a tool that allows you to include or exclude blocks > from the building process of the score. > > I encourage the use of the editor, which I could test intensively, because > it is essentially bug-free, it works perfectly on a Raspberry PI (or any > similar cheap hw) and it allows you to create *very complex* piano scores. > > Any feedback is greatly appreciated! > > HTH > P. >
ANN: Spontini-Editor 1.0 released
Hello all, I just drafted a new release (1.0) of Spontini-Editor, which is now compatible with LilyPond 2.23.0 to 4 https://github.com/paopre/Spontini Furthermore, it offers a tool that allows you to include or exclude blocks from the building process of the score. I encourage the use of the editor, which I could test intensively, because it is essentially bug-free, it works perfectly on a Raspberry PI (or any similar cheap hw) and it allows you to create *very complex* piano scores. Any feedback is greatly appreciated! HTH P.
