Incremental Blogger

Coding with a pen

"...one of the things that has really struck me while working on Pynk is that it’s really unacceptable to take 30 seconds to get “io.Ink.Strokes.ToString()” into the machine." Larry O'Brien.

Yeah, there's going to need to be some trial-and-error creative work here. Maybe integrating IntelliSense with an ink correction UI will help. Maybe a code-oriented recognizer will work too that adjusts the recognizer based on the context. Note sure.

Or maybe a more radical approach might work. Just for kicks, what would it be like to have a coding IDE where you could leave "code as ink." What does this mean? Well, so what if a function or variable name is misrecognized? What you want to be able to do is refer to the same variable or function later and maybe you could do that with some kind of pick and place metaphor or have a list of close matches pop up--rather than re-entering the token exactly. This might make more sense in a graphical view of the code, but it might work in straight code too. Again, not sure. It's one of those things that would be fun to experiment with and probably won't have an obvious solution until dozen's of non-obvious ones are tried.