[kln2-devel] what needs doing
Brought to you by:
wiecko
|
From: Marek W. <Mar...@fu...> - 2004-04-27 03:44:33
|
Hi e-body,
If anyone feels like doing any of the following, please write a
short note to kln2 devel not to double the work. Thnx.
As I said in the previous e-mail, I'm leaving for almost two
weeks - I'm sorry, but I will not be able to assist you if there
is any confusion about the new code. :(
In general we need to
I. make the piano2name exercise more like the old v1.1 from
user's point of view (for example similar kinds of comments
in comments box)
II. make name2piano really work.
====================================
I. things in piano2name (the one that is activated at startup as
a default):
__Easy_n_simple__:
1. make a midi sound whenever a piano key is highlighted (this
one should be really simple!)
2. when starting - coherent strings on the start/stop button and
start/stop menu action
3. disabling checkboxes and sliders during test (new slots of
pianokbd and buttonsbox, say "prepareForTestStop()" and
"prepareForTestStart()" connected to starting(), stopping()
signal - if you would like to do this, see how does it happen
that in the main window some menu actions are disabled during
tests)
4. maybe after selecting a new exercise, its short description
should appear in comments box?
5. when sliding a slider above the piano kbrd it jitters over
B-C and E-F (there is no black key, so I tried to make it not
stop in between, but apparently I missed something)
__Bigger_tasks_(but_still_shouldn't_require_much_of_code_change)__:
6. better stings in during-test and after-test comments (more
like in 1.1 exercise)
7. lessons (ranges of keys/active names) for the new exercises; for
notes' names I would suggest the same order as in the staff exercises:
C&G, keys around C, keys around G etc; + some reasonable key ranges
8. graphics for the piano keyboard; it is terribly flat; I don't
think we should change the view to anything isometric etc. But
within this, straight view, I think the keys should have little
shadows:
-white keys - dark shadow on lower edge
-black keys - a highlight by top edge
(a bit like in M$Windows freeware "vanBasco's KaraokePlayer",
but better ;); if you would like to do this, see how it is done
for Note class - there is a QCanvasEllipse inherited but a nice
picture is displayed; here, a piano key inherits
QCanvasPolygonalItem, but we want a nice picture.
9. make the main window aware of number of questions in a test
(signal-slots only!) current question number and make the
"clock" above results box run during a test
10. calculate reasonable test lengths for new exercises (right
now there is a hard-coded number of 10 questions in each test)
11. there are probably still thousands of little things which
need correcting - feel free take one up :)
====================================
II. About the second part: "make name2piano really work":
Well, it does work; kind of. It is shown, the test can be
started; the only problem is that ... when a question is
selected it is actually never shown and when an answer is
provided it is never checked. ;)
It's all about FancyButton and NameButtonsBox. We need
re-implementation of highlightForTest() and checkAnswerByXXX().
It shouldn't be that difficult once you'll understand how
PianoKbdKey and PianoKbd work in piano2name exercise work.
Regards,
~Marek
--
\/ /|\ Marek Wieckowski
##### | | |
= . . = \|/ Institute of Theoretical Physics
U | Warsaw University
/ ~ \___ |
<| | |
> . < | http://www.fuw.edu.pl/~wiecko
<<___>> | http://klearnnotes2.sourceforge.net
|