> chorded typing allows the users to input several letters at the same time and have a computer program generate a predicted word. Instead of typing h e l l o, a chorded typer mashes h, e, l, and o to produce the word.
It sounds like it relies heavily on autocomplete, which means it's unlikely to be useful for coding instead of just English text.
No, that means it's likely very useful for coding instead of English. You just need a custom dictionary. Code has a smaller vocabulary than prose, even with the domain-specific words that get used as identifiers . You could probably do pretty well with a dictionary that just has all the keywords in your favorite language, plus some common variable names. Heck I bet it'd be a win just to make the punctuation used in code have convenient chords.
Seems like it would be better to have the device be dictionary agnostic and leave it to your editor do know whether you're writing a comment, or code, or a string containing sql...
I wonder if it would make sense to latch into the syntax highlighter for something like Vim. Most syntax highlighters have a reasonable understanding of what context you are currently in, so conceivably the device could, for example, see that I'm inside a comment and revert to vanilla English, and then see that I'm back in code and change to F#.
I think it would. It seems like you'd want some amount of symmetry between contexts, otherwise learning separate ones would be too difficult.
Like the gesture for python's "create a for loop" would align with the english word "repeat" and in functional languages it might map to some manipulation that sets up recursion with a shortened list.
Actually coming up with a list of such a list of abstractions for app developers to map actions onto sounds like a dissertation for some psychologist somewhere.
It sounds like it relies heavily on autocomplete, which means it's unlikely to be useful for coding instead of just English text.