meta-meta / dodecathedral Goto Github PK

Ear Training will be an exercise.

Each exercise type might have its own
-methods for completion, note checking,
-rules for different types of games
-dynamically created sets of delta sequences
-scoring and unlocking based on rules

Play Complete Song
Break Song into cumulative parts
Ear Training
-interval to get to next note
-interval to get to note after n moves
Simon

play exercises just by sounds. no visual cues. small bits to start with. user has to repeat the notes

when a random sequence is demoed, allow the user to select to save the sequence to a favorites collection

I suspect maybe Processing just takes a while to draw text the first time. Need to investigate.

add a blinking arrow to the sides of a menu with more pages

the pure data patch in this branch is causing an overflow error in the jni local reference table (exceeding 512 references).

Error goes away when some of the voices are removed for the patch.

Need workaround

add a frames per second counter for development

Drone represented as a pulsating dot on the map.
Pinching on a panel changes drone to that pitch.
That pearl on the map lights up and the whole map rotates to put that selection at the top.

-lock should be on exercise collections
-menus become invisible as a result of the exercise collection being locked
-an exercise collection can have a completion status
--all sequences played correctly after demo
--all sequences played correctly x amount of times without demo
--all sequences played correctly first try
--last time played (require a retest if it gets stale)
----maybe sequences get unlocked in a branching way and you have to stay fresh on a random sequence here or there on lower branches to keep the higher branches open

-an exercise collection can have one or more prerequisites

<prerequisites>
    <playedCorrectlyNoDemo>
          <deltaSequenceCollection name="churchModes"/>
    </playedCorrectlyNoDemo>
     <overallScore>500</overallScore>
</prerequisites>

-combination of completion status (from user data class) and menu depth and branch can be used to calculate relevant score to determine whether to unlock

-randomly generated exercises of increasing length.
-get more points for completing longer delta sequences

create a serializable class for user data:

-stats on exercises completed.
--play correctly after demo
--play correctly x amount of times without demo
--play correctly first try
--last time played (require a retest if it gets stale)
----maybe sequences get unlocked in a branching way and you have to stay fresh on a random sequence here or there on lower branches to keep the higher branches open

-exercises available

menu option to have drone not playing constantly