There are two modifications the team behind this project can make that should please at least some touch-typists.
First, they can modify the glass top of the device to have vertical "brackets" raised from each key, along with a raised dot or underscore on each key, similar to the way that the F and J keys on a standard keyboard today have raised underscore marks on them to allow touch typists to find the "home row" in a pinch. Thus, even with a single surface, a touch typist can find each key by feel. It would look a little something like this:
[ . ] [ . ] [ . ] [ _ ] for A, S, D, F -- for example. Left shift: [ _____/] Right shift: [\_____] Space: [---------------] and so on.
Second, the software can be written to rule out the "touch-and-hold" key repeat function, similarly to the way OSX Lion already behaves. That way a touch typist can rest his or her fingers on the keys, just as we do now, and the keyboard will only interpret taps, not holds, as keystrokes.
First, they can modify the glass top of the device to have vertical "brackets" raised from each key, along with a raised dot or underscore on each key, similar to the way that the F and J keys on a standard keyboard today have raised underscore marks on them to allow touch typists to find the "home row" in a pinch. Thus, even with a single surface, a touch typist can find each key by feel. It would look a little something like this:
[ . ] [ . ] [ . ] [ _ ] for A, S, D, F -- for example. Left shift: [ _____/] Right shift: [\_____] Space: [---------------] and so on.
Second, the software can be written to rule out the "touch-and-hold" key repeat function, similarly to the way OSX Lion already behaves. That way a touch typist can rest his or her fingers on the keys, just as we do now, and the keyboard will only interpret taps, not holds, as keystrokes.