Difference between revisions of "Android/Music Tutor"

From theGleep.com
Jump to: navigation, search
(Created page with "I'm not saying much about it right now. But I'm going to enjoy using this app for myself.")
 
Line 1: Line 1:
 
I'm not saying much about it right now.  But I'm going to enjoy using this app for myself.
 
I'm not saying much about it right now.  But I'm going to enjoy using this app for myself.
 +
 +
<noinclude>
 +
<includeonly>
 +
 +
What I'll do is have a queue of "notes" (queue == first in/first out list).  Each note will be pulled off the queue and the image it represents will be loaded into the UI...then I will execute an "animation" against it to cause it to "slide" from right-to-left.
 +
 +
 +
 +
Once *that's* working, all of the "notes" will be stacked up on each other, so I'll add some logic to fix that:
 +
 +
* when the note gets animated, I will add it to an "active animations" queue
 +
 +
* the "slide" instructions will be updated to end (length-of-animations-queue * width-of-a-note) before the left side of the screen.
 +
 +
 +
 +
Once *that's* working, it'll be time to honor user input:
 +
 +
* wire each button to check if the "head" note in the animations queue is the note for that button
 +
 +
* when the note matches the button:
 +
 +
+ remove it from the animations queue
 +
 +
+ re-animate all of the remaining notes in the queue to "slide" left by (1 * width-of-a-note)
 +
 +
 +
 +
at this point, it will be "playable" - but FAR from finished!  I hope to get to here by next friday.
 +
 +
 +
 +
The *next* major step will be handling "active" notes:
 +
 +
* when the user gets the note right before it's done with the animation
 +
 +
* The user is VERY likely to answer while an animation is active, but there are other notes "done" with the animation...like, three notes "stopped" and a fourth note "sliding"...so I need to queue up the "move left by (1 * width-of-a-note) to happen *AFTER* the sliding stops...or revise the active animation to end (1 * width-of-a-note) later than it currently does...
 +
 +
 +
 +
(Hopefully this will be done in two weeks)
 +
 +
 +
 +
After that, I have:
 +
 +
* "Playing" the note for the button that's pressed (maybe even in "pause" mode...)
 +
 +
* changing staffs (trebble cleff vs bass cleff)
 +
 +
* scoring
 +
 +
* Help
 +
 +
+ instructions
 +
 +
+ about
 +
 +
+ donations
 +
 +
* configuration
 +
 +
+ type of fretboard
 +
 +
+ User information for registering high scores (later)
 +
 +
* Keyboard
 +
 +
* Fretboard
 +
 +
* high-scores (online)
 +
 +
* "playing songs" - feeding a song into the game so the player learns the song.
 +
 +
 +
* levels
 +
 +
  + speed
 +
 +
  + number of notes
 +
 +
  + allow sharps
 +
 +
  + allow flats (will require adding "flats" to the collection of pictures)
 +
 +
  + use "keys"
 +
 +
    - add key signature pictures to slide in
 +
 +
    - add "naturals" to the collection of pictures
 +
 +
    - support key signature to evaluate for correct input
 +
* Mic support
 +
</includeonly>
 +
</noinclude>

Revision as of 12:19, 2 May 2011

I'm not saying much about it right now. But I'm going to enjoy using this app for myself.