Re: [Denemo-devel] ReadingNoteNames Varaitions

[Richard Shann]

On Fri, 2009-06-26 at 08:02 +0100, Richard Shann wrote:
> On Thu, 2009-06-25 at 13:09 -0500, Jeremiah Benham wrote:
> > 
> > 
> > 
> > On Jun 24, 2009, at 11:42 AM, Richard Shann <address@hidden>  
> > wrote:
> > 
> > > On Wed, 2009-06-24 at 10:25 -0500, Jeremiah Benham wrote:
> > >> I began creating variations on ReadingNoteNames. So far I have:
> > >>
> > >> LineOrSpace:
> > >> User enters an "l"
> > >
> > > It's nice to see some scripts. A few ideas:
> > >> LineOrSpace:
> > > The instruction was difficult to read (I read | for l) perhaps make  
> > > the
> > > instruction
> > > Insert letter L for line and S for space
> > > (accept upper or lower case then ...)
> > 
> > What is the best way to do this? 
> I can't claim any expertise here. In C you would just force the case
> (tolower say) and then just test for that. 
> However, I have had a thought that would make these sorts of scripts
> easier to write:
> I propose we could have a
> 
> (d-FindDirective-standalone tag)
I found a sneaky way to do this, via a script, so it now available. It
creates a standalone directive but keeps the cursor on the directive, so
that you can go on to set the fields without having to move the cursor
left back on to it.

> 
> which would move the cursor to a standalone directive with the named
> tag. (Variants for forward/backward and chord/note/staff directives).
> 
> The idea is that you could put a markers in the music and be able to
> find them again, rather than trying to keep track of the cursor (which
> can be tricky in Denemo because of its concept of an appending postion -
> cursor stopping on the barline). Specifically the ReadingNoteNames works
> by putting up notes & then changing their noteheads - relying on
> tracking where the cursor is. Instead the note could have a directive
> attached marking it as the note prompted for, and then the note can be
> found again even if the user has moved the cursor meanwhile.
To make this possible I have created a d-NextStandaloneDirective
command. With this (and querying the tag field) you can find a directive
marking a point in the music.

Richard



> 
> I think the infrastructure may all be in already - I recall writing
> stuff for doing named bookmarks using the old LilyPond inserts. So this
> is largely cosmetic: in particular we could now have a command
> 
> (d-PutDirective-standalone tag)
> 
> which would put a directive without setting any fields, which is what
> you would do to place a named marker to mark a spot in the music, but
> without it having any effect on the print out or the midi out or even
> the display.
> As a bonus, the existence of such a command makes it easier to explain
> DenemoDirectives - at the moment creating a DenemoDirective is a
> side-effect of setting a field - e.g.
> (d-PutDirective-standalone-display "mytag" "hello")
> creates a directive and sets the display field.
> Now we can describe this as
> 
> (d-PutDirective-standalone "mytag");;; create a standalone directive
> (d-PutDirective-standalone-display "mytag" "hello");;; set its display field
> 
> although in practice we would omit the first line.
> 
> Richard
> 
> 
> > Should I chain a bunch of "or  
> > swithes" or should have a function that searches a list for mathing  
> > string returning TRUE if found FALSE otherwise. I am thinking I'm c  
> > here but I will translate it to scheme.
> > 
> > Jeremiah
> > 
> > 
> > >
> > > or what about space bar for space.
> > >
> > >> if the note is on a line or "s" if it is on a space.
> > >>
> > >> UpDownOrSame:
> > >
> > >> User enters a "u" if the interval goes up, a "d" if the interval  
> > >> goes down, and an "s" if the interval stays the same.
> > > what about arrows, accepting forward or backward arrow for the same.
> > >
> > >> CountSteps:
> > >> User enters a number for each interval couting the number of  
> > >> diatonic steps that are used to make up the interval.
> > >>
> > >> DiatonicInterval:
> > >> User enters the diatonic interval number. So c up to e would be 3  
> > >> for third. c down to b would be 2 for snd. c staying on c would be  
> > >> 1 for unison.
> > >>
> > >> I also wrote anouther. It is called StepSkipOrSame. I have not  
> > >> commited it because I am not sure what the user input should be.
> > >
> > >> The user should enter a letter/number depending if the interval  
> > >> steps up the scale, skips up the scale, or stays the same. I  
> > >> thought of then letters t=step, k=skip, and a=same. But this is all  
> > >> contingent on the fact that they no how to spell.
> > > hmm arrows and control-arrows? You are thinking of little children  
> > > here -
> > > they get the hang of things quickly but they wouldn't use written  
> > > instructions - the adults would read those and
> > > show the kids, I guess.
> > >
> > > I think the feedback could be much improved now, with the ability to
> > > insert any graphic into the music - so a correct answer could cause  
> > > the
> > > insert of a nice big Tick sign (d-DirectivePut-standalone-graphic
> > > "BigTick" "BigTick") with some gx, gy and minpixels to position it and
> > > give it some space.
> > >
> > > And for older kids we could sound intervals and ask them to identify  
> > > by
> > > inserting the note...
> > >
> > > Richard
> > >
> > >
> > >
> > >>
> > >> Jeremiah
> > >>
> > >>
> > >> _______________________________________________
> > >> Denemo-devel mailing list
> > >> address@hidden
> > >> http://lists.gnu.org/mailman/listinfo/denemo-devel
> > >
> > >
> > >
> > > _______________________________________________
> > > Denemo-devel mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/denemo-devel
> 
> 
> 
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel