lily4jedit-devel

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

[Joshua K. <zz...@us...>]

Thanks for your advice Bert :) Sometimes I just think too complicately. So for this case, I'll add relative mode for quickly using algorithm A. (Come to think of it, its something like the lilyComp modification I did last time). The only flaw to the relative notes is that, the octaves might be be correct if the keys are not enter consecutively. Then again, like you said, something doesnt need to be so perfect, so I guess I'll make do with it. Time to work on it!

Joshua


======= At 2005-03-17, 17:36:52 you wrote: =======

>Joshua,
>
>don't make the relative mode too complicated! It should be very easy to 
>implement, because you don't have to recognize relative blocks! It would 
>be perfectly satisfiable, if I set the first octave manually, (quicklily 
>would use no octave shifting) and all the following pitch is calculated 
>relative to the previous one. We need not not know about the absolute 
>meanings of the pitches, but we can know, that there is one octave shift 
>between pressing the 'c' key and pressing the 'm' key.
>
>We don't want to be perfectly smart in all situations, because we just 
>can not, because we are not a lilypond interpreter. The same is true for 
>durations. We can try to guess the duration of the previous note, 
>similarly like in what-beat.bsh, but can keep it as the user's 
>responsibility as well.
>
>Actually this is the same conceptual scheme than with the key 
>recognizer. We don't want to recognize the would-be state of the 
>lilypond interpreter at any caret position. We just try something to 
>provide a not too bad default, but the user will be able to change it 
>very easily. For example, when the user turns on quicklily mode, we can 
>show him the guessed key using the MacroUtils.showTimedWindow method 
>(for usage example see macros/what-beat.bsh) and allow him to change the 
>key with a keystroke.
>
>I find very important to not fall into the error or TeX: wanting to know 
>everything, and missing to know just anything.
>
>Bert
>
>

= = = = = = = = = = = = = = = = = = = =

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

[Joshua K. <zz...@us...>]

>There lily4jedit-develis one problem: if I turn quicklily on and turn of, somehow some
>assignment don't disappear. For example backspace and pg-up/down do not
>	work.

This is now fixed. This means can use any shortcuts for quicklily keys even though its already binded to another action. Upon quicklily untoggle, bindings will return to the previous action. 

For now, configuration of bindings in done in the QuickLilyManager. I'll hope to integrate the onscreen piano to configure bindings for quicklily. also, spestov says ADD + should be fixed in jedit 4.3.

1 bug however, is in the english mode, trying to adjust the note fs will turn the note into c. any ideas?

Joshua

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

>For now, configuration of bindings in done in the QuickLilyManager. I'll hope to integrate the onscreen piano to configure bindings for quicklily. also, spestov says ADD + should be fixed in jedit 4.3.
>  
>
Great. I hope it is fixed, we should try some day. However, this creates 
a dependency of our 0.2.8 on jEdit 4.3. Perhaps we should stay at 4.2 
until 4.3 gets stable. If we don't demand 4.3 we can note users that the 
quicklily features does need 4.3

Bert

>1 bug however, is in the english mode, trying to adjust the note fs will turn the note into c. any ideas?
>
>  
>
I don't know. Scales.xml and notenames.xml looks good.

Bert

>Joshua
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
>Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
>for the chance to win $25,000 and application distribution. Enter today at
>http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
>_______________________________________________
>Lily4jedit-devel mailing list
>Lil...@li...
>https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
>
>
>  
>

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

Committed relative mode last night.  Do see if its compatible. 

Have the language mode been able to work with you?

In English mode, lets say a cs when raise an octave resets the sharp.
It doesnt happens for default. I wonder where the problem lies.

Joshua

On Thu, 17 Mar 2005 20:11:46 +0800, Joshua KooOOoOOo
<zz...@us...> wrote:
> Thanks for your advice Bert :) Sometimes I just think too complicately. So for this case, I'll add relative mode for quickly using algorithm A. (Come to think of it, its something like the lilyComp modification I did last time). The only flaw to the relative notes is that, the octaves might be be correct if the keys are not enter consecutively. Then again, like you said, something doesnt need to be so perfect, so I guess I'll make do with it. Time to work on it!
> 
> Joshua
> 
> ======= At 2005-03-17, 17:36:52 you wrote: =======
> 
> >Joshua,
> >
> >don't make the relative mode too complicated! It should be very easy to
> >implement, because you don't have to recognize relative blocks! It would
> >be perfectly satisfiable, if I set the first octave manually, (quicklily
> >would use no octave shifting) and all the following pitch is calculated
> >relative to the previous one. We need not not know about the absolute
> >meanings of the pitches, but we can know, that there is one octave shift
> >between pressing the 'c' key and pressing the 'm' key.
> >
> >We don't want to be perfectly smart in all situations, because we just
> >can not, because we are not a lilypond interpreter. The same is true for
> >durations. We can try to guess the duration of the previous note,
> >similarly like in what-beat.bsh, but can keep it as the user's
> >responsibility as well.
> >
> >Actually this is the same conceptual scheme than with the key
> >recognizer. We don't want to recognize the would-be state of the
> >lilypond interpreter at any caret position. We just try something to
> >provide a not too bad default, but the user will be able to change it
> >very easily. For example, when the user turns on quicklily mode, we can
> >show him the guessed key using the MacroUtils.showTimedWindow method
> >(for usage example see macros/what-beat.bsh) and allow him to change the
> >key with a keystroke.
> >
> >I find very important to not fall into the error or TeX: wanting to know
> >everything, and missing to know just anything.
> >
> >Bert
> >
> >
> 
> = = = = = = = = = = = = = = = = = = = =
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
>

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

I can't see any difference.

I show you what I do, what I see and what I want to see

c m
c g
c g'

c q w m
c c' d' g
c c' d g,

Another question: how do I redefine the keys?

Thanks,

Bert

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

Ha, it was just one variable mistake. It is now fixed in the cvs.

Joshua

On Sat, 19 Mar 2005 13:12:59 +0800, Joshua Koo <jos...@gm...> wrote:
> I'm sorry, I think I created a bug somewhere before I commited, after
> it worked. I'll try to see where went wrong.
> 
> As for shortcuts, for now, under global options > plugin:lilytool >
> you can be able to find quicklily actions.
> 
> But i would be changing it to use a custom dialog, so it wont comflict
> with other edit actions shortcuts.
> 
> Joshua
> 
> On Fri, 18 Mar 2005 20:59:32 +0100, Bertalan Fodor <fo...@fr...> wrote:
> > I can't see any difference.
> >
> > I show you what I do, what I see and what I want to see
> >
> > c m
> > c g
> > c g'
> >
> > c q w m
> > c c' d' g
> > c c' d g,
> >
> > Another question: how do I redefine the keys?
> >
> > Thanks,
> >
> > Bert
> >
>

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

Looks good.

Another suggestion: handle backspace specially: delete the last thing 
the user has typed, not just one character. This way the relative mode 
can be work more better as well.

Bert

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

I've committed some simple fixes regarding quicklily.

Bert

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

Thanks, I have just cvs-ed the quicklily backspace.
Joshua

On Sat, 19 Mar 2005 11:33:37 +0100, Bertalan Fodor <fo...@fr...> wrote:
> I've committed some simple fixes regarding quicklily.
> 
> Bert
>

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

>- The notepad - sharpens on my machine and not flattens.

This is a bug with jEdit. 
You find that you can use the notepad + with any actions because + is
also a sepator for modifiers actions.

I've file a bug on their site.
https://sourceforge.net/tracker/index.php?func=detail&aid=1166530&group_id=588&atid=100588

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

Fine! I just wanted to suggest that numbers don't append, but change 
duration, and you've done before I would have said :-)

There is one problem: if I turn quicklily on and turn of, somehow some 
assignment don't disappear. For example backspace and pg-up/down do not 
work.

Bert

Re: [Lily4jedit-devel] QuickLily suggestions - part 1

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

Its apparentenly a programming error on my part. The actions binded to
the shortcuts were not stored and reverted when quicklily is invoked.
I'll try to solve it when I'm back home.

Joshua

> There is one problem: if I turn quicklily on and turn of, somehow some
> assignment don't disappear. For example backspace and pg-up/down do not
> work.