Hi!<br>I'm also interested in helping to improve Tuxtype participating in GSoC. <br>I am a student of University of Informatics and Radioelectronics in Minsk, Belarus.<br>I have choosen your project, because I have recently written keyboard training program for blind people. <br>
My father mastered keyboard using my program.<br><br>My thoughts and ideas so far?<br>Use GNU gettext for localization - completely agree. Shouldn't take much time and definitely worth doing.<br><br>More content (practice sentences, finger exercises, etc.):<br>
I'd suggest to add new teach methods, based on special typewriting courses.<br>For example, add special lessons for left/right hand, for functional keys and so on..<br><br>It would also be good to add some 'intelligence' to the program: calculation of number of mistakes and<br>
other statistics, changing task "on the fly" depending on how it goes.<br><br>Having in-game support for editing words and lessons would be very convenient for users - it's exactly what's needed.<br><br>
I'd also propose to add special mode for blind people. In my keyboard simulator I implemented two training modes: <br>letters and words pronunciation, i.e. all tasks and error messages were pronounced. I think it's not very difficult to implement also.<br>
<br>About Auto-detection of "typeable" characters:<br>I looked at the sources of port Tuxtype port for Maemo(<a href="http://www.maemo.org">www.maemo.org</a>) and found out that their version of SDL doesn't return <br>
any unicode symbols at all, only keycodes. Despite of this fact they manage to make tuxtype working by adding one optional <br>field to keyboards.lst file - keycode. What do you think about this approach?<br>If you're interested in looking at their changes I can prepare patches and send them to this list.<br>
<br>Best regards, Max Usachev.<br><br>