[kln2-devel] Re: KLearnNotes2-devel digest, Vol 1 #10 - 2 msgs

[Mo <Mo...@no...>]

Hello all!

Sorry for the delay in comments. I have read the topic regarding
accidentals and have posted some of my comments below. 

Thanks!
-Mo

> // In future we may implement double sharps and double flats,
> // but let us keep things simple for now.
> 
...
> 
> // what to do with integer representation of the name?=20
> // we have to check how it is used; should we number
> // * all the notes (like 0=3DC, 1=3DC#, 2=3DDb, 3=3DD )
> // * distinct note's positions (like 0=3DC, 1=3DC#/Db, 2=3DD)
> // * only base notes (like it is now - 0=3DC, 1=3DD )
> // * or abandon the integer representation as an unclear
> //   one?

Which ever representation we go with, we should keep in mind that 
all notes can be represented in 5 different formats: 

Natural
Flat
Sharp
Double Flat
Double Sharp


> Implementation:=20
> 

> - extra buttons (ordered in piano keyboard style? but maybe two
>   sets of 'black' keys: one above with sharps, one below with
>   flats?:
>   C#   D#     E# F#
> C    D     E  F     G=20
>   Db   Eb  Fb    Gb
> and so on ? )=20
> 

Lots of graphical clutter if we put down all possible note 
graphics. Perhaps just add two more buttons: sharp/flat? Though 
not sure how this will work with our current implemenation. 

I think a better way would be to draw out a keboard and make the
users click on the graphical keyboard instead of the names of the
notes as it is now. This will add a bit of a learning curve for none
piano players but its a small one. Learning the keys of a keyboard 
is part of musicianship anyways.

A graphical keyboard instead of actual graphics of character notes
will make for less clutter and users won't get lost in searching for 
actual characters names of notes. And also, it will make sense to 
new musicians if we ever introduce chords. I have had friends that
didn't understand chord structures until they saw it layed out on 
the piano.