============================================
== WHAT NEEDS CODING?
============================================

LESSON structure save/restore/add etc. can be tested on note-to-name
	EXERCISE in 'names of notes' SUBJECT
therefore we need to
* add individual testnotes selection
* add individual auto-designed tests
* custom-lesson add (to combo and to draws-pool) and save
	- saving should be in plain text
	- it should have SUBJECT and EXERCISE identifiers

the same save interface/way of adding to combo/draws-pool etc.
can then be used for other exercies in future

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

test RandomObject:
* add name-2-staff (name-2-chooseNote and name-2-guessNote)
	exercise

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

NEW INTERFACES:
* staff needs improvement to enable sequence exercises
	- it should have highlight possibilities and scrolling
* fretboard
	- how to sort this out? by pitch ? by fretboard point?
	- selecting tuning and number of strings
* keyboard

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

TECHNICAL STUFF which is quite independent of new exercise-types 
development:

* non-modal "mixer" popup dialog
	* master volume
	* midi volume
	* mic voulume
	* i-gain

* pitch input - based on console guitar tuners;
	the best I found is gtune-0.10, but it is not GPL-ed :(
	if no other good choice - write to authors of gtune 
	to ask for permission to use the code

	and add guitar tuner too

* timidity and other sound output choices - based on solfege;
	I have already read big part of solfege code, and extracted
	what is really important; what is left is porting this to 
	C++;
	by the way: the way solfege abstarcts synth is both 
	beautiful, and quite easy to implement in C++ (base class 
	with virtual functions!)
	
* input from a midi file
	look at how solfege creates file for timidity!
	* are there different midi file formats?
	* any authomatic phrasers for midi files?
	* how to extract one track?
