2 ms·
> There is an underlying tree structure that you are hiding from the user. There shouldn't be, though. You're following a graph structure of cross-references,
by TeMPOraL 6y ago
> There is an underlying tree structure that you are hiding from the user.
There shouldn't be, though. You're following a graph structure of cross-references, in both directions (though it's less obvious here how to open panes for back references). It's not a tree.
> If I delete a pane from a column, its descendants stay open, making it even more confusing why I had them open in the first place.
Again, not a tree. Deleting panes opened from the pane you're deleting would be a bad thing, because some panes may be just intermediaries you used to find the semantic units you were interested in.
The GUI here is similar to Miller columns, but it's not actually Miller columns - it doesn't represent a tree.
- phailhaus 6y ago> You're following a graph structure of cross-references Yeah, that's tree-like. I've worked on a similar problem, giving users the tools they need to explore extremely large, dense connected graphs. When you go-to-definition, then show-references, then go to a usage from the first file, you don't go back. You continue forward to the next column, even though the fourth column is identical to the first. The columnar navigation guides you towards tree-like exploration, which is necessary because the actual web of relationships is impossible to effectively visualize all at once. Trees make it manageable. > some panes may be just intermediaries you used to find the semantic units you were interested in. That's true, which is why dragging panes is important. You can explore down a path, find the pane you're interested in, drag it over to the second column, then delete the cruft in one step. The problem with it now is that once you find the pane you like, you have to go back and manually delete every single node that you don't care about.