What are some different ways to use ink in a source code editor?
I can envision using ink markup during a presentation to emphasize or explain a point, but what else might ink be used for?
Would ink editing gestures, similar to these, be useful?
Imagine somone standing up or moving around while they are describing a block of code. Would they be able to make code changes without a keyboard in a reasonable amount of time if they were using a stylus? Are there enough expressive and easily recongizable gestures that would make gesture editing worthwhile?
Actually, I’m not sure that gestures in themselves are the answer. A floating toolwindow or button might provide a more direct and useful way of accessing editing functions. Another non-gesture feature that seems like it would be quite useful is a way to incrementally drive the Intelisense listbox while handwriting individual letters.
Any other ideas?
My experience writing a tool for programming Python with Ink soured me on the idea of handwriting method names. Driving Intellisense (well, I reflected the Python properties directly, but it was Intellisense-y) worked better, but still…
I think comment diagrams are the key feature (class / sequence / collaboration diagrams) and it looks like you’ve solved that. BTW, to what is the ink anchored (that is, is it screen relative, relative to a tag in a comment field, etc.)?
Intellisense is so fast via typing that a pen/ink permutation seems like it’s a must. Whatever solution, it would need to be just about as fast. Actually, Intellisense can be slow if you’re hunting for something–so that’s a thing to keep in mind too when coming up with an alternative.
In terms of the ink annotations, the ink overlay is line based and the ink annotations in the toolwindow are tag based. The problem comes up in the former case what to do when deleting the line that a comment is anchored too. Much debate here.
I actually don’t think tablets will “catch on” in the way you’ve been evangelizing (but, that said, I have two). They WILL increase their market share, because they include extra features, but it’s not compelling (now) unless you need to write alot.
Also, (with the voice interface), I can’t see talking to the tablet all day developing code (in an office setting where most of us are).
I think the tablet is a stepping stone technology. It needs one more “breakthrough” component to ignite the marketplace, and be a “firestorm” (Uh, I just got back from Fantastic 4 movie, so sorry about the allusions).
Anyway, what would you say to an “input glove”, for example, with which you could write directly, do “command actions”, perhaps even interact with VR (Virtual Reality) software, and able to reach into the desktop and directly manipulate application interfaces?
I enjoy your thought challenges, and how you back up a lot of your ideas with concrete code snippets. So, what do you think?
Thanks
IMO, when code is deleted, dialog a question, and either delete the ink comment (choice 1), or recalculate an anchor based on the ink’s “spatial” position in the code.
Let people get a handle on the ink and move it, too.
My $.02