lily4jedit-devel

[Lily4jedit-devel] Re: easier LilyPond tutorial?

[Bertalan F. <fo...@fr...>]

I get this back to lily4jedit-devel, because it is not related to 
lilypond development.

>Maybe the user can click on a link on the tutorial mode to start the wizard or it may launch automatically.
>  
>
Not everything is to be configured, only the things that are really 
necessary to run the tutorial. Running the configuration wizard should 
remain an option.

>For now there some shortcuts to LilyTool Plugin options and GlobalOptions-shortcuts or context menu. 
>  
>
Well, I'm not sure we should provide the Global Options, because it is 
three clicks to earn them otherwise (however, they can remain in the 
Development menu)

>I also think its a good way to configure lots of options in the start, eg. 
>Do you want the recommended docking settings? Yes, and they (eg NoteVisualiser, keyboard) are docked.
>Do you want want the default quicklily shortcuts? Yes, and the shortcuts are added.
>Do you like the compile fragment context menu? Checked and it added.
>Or, would you like all recommended settings? Yes, and tata, the "ideal" settings is configure without breaking the rules of jEdit (or, is this bending them?)
>  
>
Yes, they can become a configuration wizard (note that there is a Wizard 
Wizard, if you would like to try it)

>If it is really nessary to kill Acrobat, Runtime.getRuntime().exec() could be use to run Acrobat in a thread then kill/stop the thread (http://java.sun.com/j2se/1.5.0/docs/guide/misc/threadPrimitiveDeprecation.html)
>  
>
That's true, but I don't want to close Acrobat if it is already running.

>Or another way to prevent running lilypond again on a same fragment is creating a hash or Message Digest in the file name.
>  
>
OK, but the point is that we may want to create the same file for the 
same fragment.

Bert

[Lily4jedit-devel] Re: easier LilyPond tutorial?

[Joshua K. <jos...@gm...>]

>To compile this fragment,
>
>- Place the caret inside the fragment.
>- Select LilyPond > Help > Tutorial > Compile fragment

Sorry, something I forgot to add. 

Since the special Lilypond Tutorial mode is activated, is there a need
for the user to use use the command "compile fragment"? (which is
takes 4 moves to get to that command)

Would it be better if the user lilypond command is involved (by icon,
menu, shortcut), but when it detects that lily tutorial is on, it will
compile the fragment.

>(note that there is a WizardWizard, if you would like to try it)

I'll attempt to try it, but my prioity now is quicklily ;)

> OK, but the point is that we may want to create the same file for the
> same fragment.

I think if the fragment is unchanged, it will always hash to a same
values, eg. {a b c} will always produce xyz123, so lilyxyz123.ly does
not need compiling. {a b c'} would create a different hash, lets say
xzz133 so lilyxzz133.ly can be compiled.

Joshua

Re: [Lily4jedit-devel] Re: easier LilyPond tutorial?

[Bertalan F. <fo...@fr...>]

>>(note that there is a WizardWizard, if you would like to try it)
>>    
>>
>
>I'll attempt to try it, but my prioity now is quicklily ;)
>  
>
Great :-) Now there's a FilePicker, too :-)

>  
>
>>OK, but the point is that we may want to create the same file for the
>>same fragment.
>>    
>>
>
>I think if the fragment is unchanged, it will always hash to a same
>values, eg. {a b c} will always produce xyz123, so lilyxyz123.ly does
>not need compiling. {a b c'} would create a different hash, lets say
>xzz133 so lilyxzz133.ly can be compiled.
>  
>
That's true. I just wanted to note that we might not want to create lots 
of ly/log/ps/pdf files for every little modification.

Bert