Re: ANN: LilyJSSVG, first pre-release (BIG improvement)
Hi Simon you have to download it and play with a common player, as explained in the homepage of the project. There's not an embedded viewer in Github, sorry. best, Paolo. On Mon, Jan 6, 2020 at 4:01 PM Simon Albrecht wrote: > Hi Paolo, > > On 05.01.20 23:32, Paolo Prete wrote: > > https://github.com/paolo-prete/LilyJSSVG/blob/master/LilyJSSVG.ogv > > > it seems like github can’t display the video—even the ‘raw’ option shows > a zero-length video. > > Best, Simon > >
Re: ANN: LilyJSSVG, first pre-release (BIG improvement)
Hi Paolo, On 05.01.20 23:32, Paolo Prete wrote: https://github.com/paolo-prete/LilyJSSVG/blob/master/LilyJSSVG.ogv it seems like github can’t display the video—even the ‘raw’ option shows a zero-length video. Best, Simon
ANN: LilyJSSVG, first pre-release (BIG improvement)
Hello all, I am very happy to announce the first version of the LilyJSSVG editor, after the various tests made in the previous days (I have not yet committed the release, but everything is ready). https://github.com/paolo-prete/LilyJSSVG As you can see, this version brings VERY IMPORTANT differences compared to the test versions: everything is in fact absolutely automated, and is achieved through the point-and-click system on the score, from which you can open drop-down menus for editing objects with The mouse. Instead of explaining all this in words, I suggest you see the following video, in which with LilyJSSVG I open a Beethoven sonata taken from the Mutopia project and modify it. https://github.com/paolo-prete/LilyJSSVG/blob/master/LilyJSSVG.ogv Obviously my intent is to create a complete editor. In the next few days I will insert various other grob to modify (hairpins, accidents, keys, brackets etc.). I really invite you to consider the features of this editor. 1) For the first time, objects can be modified with the mouse avoiding the unnerving trial and error process. Note that the system I used has nothing different from the tweaks and overrides that are normally done through a text editor. I kept the same names of the objects (Script, Beam, DynamicText etc.): the only difference is that here the coordinates are calculated and written directly with the mouse. So all this is not at all in opposition to Lilypond's logic, but rather strengthens it. 2) The editor doesn't need ANYTHING to compile. It is in fact generated by Lilypond himself! I did all this because I believe in Lilypond a lot and I use it often. I wanted to invest my time because in this way I speed up the writing of the scores. I really needed to speed up many operations, and I am achieving this result. But it would be really nice if you help me. Again: watch the video. In the coming weeks, after adding more grobs to modify, I will suspend the development. At this point, I will be able to actively dedicate myself to the project only if I am supported. The help I ask from you is 1) test 2) code cleaning 3) documentation 4) support for writing in Javascript. 5) Test on Windows / OSx For point 4) I am willingly available for those who want to learn how to add new features to the code. If supported, I will try to continue the work by adding a text editor with the various features of syntax highlighting etc. If I will not be supported, unfortunately I will devote myself to the project much more occasionally (I will however try to continue developing it, because I believe in it). Of course, I cannot do everything alone, and I would like to see the Lilypond development team (should I cross-post this to lilypond-devel ml?) saying something about the possibility of including this feature in the Lilypond project. HTH Paolo
Re: LilyJSSVG
On Sun, Dec 29, 2019 at 11:04 AM Martin Tarenskeen
wrote:
>
>
> On Sun, 29 Dec 2019, Paolo Prete wrote:
>
> > https://github.com/paolo-prete/LilyJSSVG
>
> > Unlike the previous script, there is no need for copy and paste: the
> editor offers a textarea that is automatically updated following mouse
> actions, plus a button
> > for compiling .ly files.
> >
> > You can make any changes you want. Save / compile and go on modifying:
> the functions requested by Urs have therefore been implemented.
> > It should be simple to use (a mini how-to is on the project's Github
> homepage and in the example .ly file).
>
>
> This project is growing into serious and really usable stuff. Thanks!
>
> remarks 1:
>
> I kind of liked the old copy/paste actions of the primitive preview
> versions. I liked that your script helped me to find the perfect values to
> enter in my \shape functions for Slurs for example. But in the endresult
> my lilypond score did not need to include LilyJSSVG.ly and did not need
> all these new \jsX versions of already existing commands.
> Or is this still possible, but I haven't understood how yet?
>
The previous implementation had two big disadvantages, which are avoided in
this version:
1) You had to copy/paste each modification. In the current way, instead,
you put the token ( \jsXXX ) only once before the corresponding grob. And
then the editor will be automatically updated at each modification.
Please note that the new expressions follow the Lilypond naming convention,
with a "js" prefix (which means that no additional names have to be
learned/remembered)
2) You could not compile and then apply a new modification (you had to
delete the expression and reset the shape to its default)
>
> remark 2: The LilyJSSVGCompileHelper.py script only works with Python2 and
> is not compatible with Python3.
>
> --
>
Sounds right. Please open an issue token in the project's page ("issues")
and I'll fix it asap
Best,
P
>
> MT
>
>
Re: LilyJSSVG
On Sun, 29 Dec 2019, Paolo Prete wrote: https://github.com/paolo-prete/LilyJSSVG Unlike the previous script, there is no need for copy and paste: the editor offers a textarea that is automatically updated following mouse actions, plus a button for compiling .ly files. You can make any changes you want. Save / compile and go on modifying: the functions requested by Urs have therefore been implemented. It should be simple to use (a mini how-to is on the project's Github homepage and in the example .ly file). This project is growing into serious and really usable stuff. Thanks! remarks 1: I kind of liked the old copy/paste actions of the primitive preview versions. I liked that your script helped me to find the perfect values to enter in my \shape functions for Slurs for example. But in the endresult my lilypond score did not need to include LilyJSSVG.ly and did not need all these new \jsX versions of already existing commands. Or is this still possible, but I haven't understood how yet? remark 2: The LilyJSSVGCompileHelper.py script only works with Python2 and is not compatible with Python3. -- MT
Re: LilyJSSVG
On 12/29, Paolo Prete wrote: > this is a first TEST pre-beta-beta (etc. etc.) version of a graphic editor > entirely in Javascript and generated by Lilypond itself. Made mainly for > fun in my spare time. > This GUI editor extends the functionality that I had experimented with the > snippet published a few days ago for the tuning of curves through the mouse > > https://github.com/paolo-prete/LilyJSSVG Very cool! I'm excited to try it. Mason signature.asc Description: PGP signature
LilyJSSVG
Hello to all, this is a first TEST pre-beta-beta (etc. etc.) version of a graphic editor entirely in Javascript and generated by Lilypond itself. Made mainly for fun in my spare time. This GUI editor extends the functionality that I had experimented with the snippet published a few days ago for the tuning of curves through the mouse https://github.com/paolo-prete/LilyJSSVG At the moment, in addition to the tuning of curves and beams, it is possible to position texts, dynamics and articulations. The code is designed to be easily extended, in order to add other objects to be positioned, in addition to the ones mentioned above: I created a template and a javascript API that allows this. For now, however, I still need to test what has been implemented before adding more features. Unlike the previous script, there is no need for copy and paste: the editor offers a textarea that is automatically updated following mouse actions, plus a button for compiling .ly files. You can make any changes you want. Save / compile and go on modifying: the functions requested by Urs have therefore been implemented. It should be simple to use (a mini how-to is on the project's Github homepage and in the example .ly file). Everything is ready to be tried. Please use version 2.19.83 for testing. At the moment I cannot provide support for other versions. Furthermore, in order to allow the editor to compile the Lilypond files, I created a Python script which is also included in the project, and which communicates with the editor by executing the compile command after pressing the "compile" button. This script has been tested on Linux, but should be compatible with other operating systems. Finally: everything has been tested on Firefox and Chrome browsers: I do not guarantee operation on other browsers, for now. Of course, I need your help to continue all this. Thanks to everyone who helped me with the Scheme part: now I need new support, because in the next weeks I won't have much time. In particular I need a person who does code cleaning for both Javascript and Scheme. But above all, there is a need to test all this as much as possible. Only in this way this project will have a future. If this works, the next feature will be adding point-and-click. And if this works, I would be glad if it could appear in openlilylib project (waiting for Urs' feedback) Best, P
