3 ms·
This is really neat, great work! I wonder, do people perform the kind of edits that this makes efficient very often? For example, in the video it was predeterm
by ibdknox 14y ago
This is really neat, great work! I wonder, do people perform the kind of edits that this makes efficient very often?
For example, in the video it was predetermined exactly what was going to be moving and where it was going to go to. From my observations, these sorts of large scale changes are rarely handled so easily. Context helps people map things cleanly, and the contextual change of zooming in and out forces you to constantly rebuild that map. It's an issue I've seen over and over again with any zoom-oriented interface.
Regardless, this is cool work. We need new and interesting interfaces for code - I'm hoping to show some fun things myself at the Live Programming Workshop [1] at ICSE[2].
[1]: http://liveprogramming.github.com/2013/ http://liveprogramming.github.com/2013/
[2]: http://2013.icse-conferences.org/ http://2013.icse-conferences.org/
- westoncb 14y agoYes, the loss of context can be an issue--definitely. I hesitated to include the code collapsing/expanding aspects in the demo because it disguises something more important that's going on, which is unit selection. If I disable collapsed nodes, then when you 'enter' a function you would just see the tile boundaries change from being around each function to being around each line in the function. Hadn't heard of those workshops -- will take a look.
- westoncb 14y agoIn answer to your first question: I think these edits will have to be supplemented by more traditional operations, like forming selections based on textual search criteria for instance. So it's definitely not enough on its own--but it's important because when you do have to do this sort of thing, you can do it efficiently through an interface to the text that's consistent with contemporary tile-based ui.