Seriously, though. I've experimented with chording keyboards in the past. Conceptually they're quite cool, but their advantages are outweighed by the finickiness of having to master a new set of split-second timing issues. I can only imagine having zero tactile feedback on top of all that. (And then opting for zero visual feedback as well?)
Ten Finger Touch Screen Keyboard
21–30 of 61 posts
Re: Ten Finger Touch Screen Keyboard
#22Re: Ten Finger Touch Screen Keyboard
#23Asetniop is a terrible name. It might be very intuitive to those who know your key arrangement, but for newcomers, the name conveys nothing.
Re: Ten Finger Touch Screen Keyboard
#24For what it's worth, the first mouse was intended to be used in conjunction with a chorded keyboard when Doug Engelbart invented it in 1963: http://dougengelbart.org/images/pix/img0030.jpg
Re: Ten Finger Touch Screen Keyboard
#25Re: Ten Finger Touch Screen Keyboard
#26Microsoft patented the idea a while back and among other sucky things about patents, they may simply not implementing it at all.
http://www.patentbolt.com/2012/05/microsoft-invents-portable...
Re: Ten Finger Touch Screen Keyboard
#27The keyboard trainer seems to be slightly broken, ASET != ARST and NEIO != NIOP. I'm on Win7, Chrome 23 http://i.imgur.com/cdQdj.png
Re: Ten Finger Touch Screen Keyboard
#28Direct link to the virtual keyboard trainer (set your input manager to US/qwerty first): http://asetniop.com/keyboardTutorial.html
Very cool, but the fact that the keyboard on the screen doesn't match the output (input?) nor the asetniop 'idea' makes it incredibly confusing and was enough for me to say 'ok, I'm done'. Unless it's just a problem that I'm experiencing, it doesn't seem like the author (or anyone) ever tested this tutorial out.
Re: Ten Finger Touch Screen Keyboard
#29Re: Ten Finger Touch Screen Keyboard
#30Why is "p" a non-chorded letter? Clearly the other letters were chosen because they're the seven most common letters in the English language. But letter number 8 is "h", followed by "r". "p" is way down at #19. Is it just to maintain some semblance of compatibility with QWERTY? This seems short-sighted.