On Wed, May 20, 2015 at 3:04 AM, Avdi Grimm <avdi@avdi.org> wrote:
I dunno if this is useful to anyone, but I was rolling around concepts in my mind and this is something I came up with:
[image: Inline image 1]
This takes some cues from modern IDEs, but it also differs in that it doesn't make the assumption that you want to see just one "buffer" at a time, and that "split window mode" isn't sufficiently powerful to handle the need for lots of windows open on lots of little methods.
Interesting idea. It might be better to use a breadcrumb rather than the three pulldowns and I think Playground tends to need more room. One idea I've contemplated, since often my many open windows result from following some path investigating senders/implementors of other senders/implementors, is that it would be useful to have a tree structure docked to the side that records that hierarchical path of investigation. This would help in cases when I want to back up a few steps to investigate another path but usually I've lost the needed window (so I just open another one). This would also help when it came time to prune an investigation, since windows often hang around longer than needed since its hard to remember which windows below to which path of investigation. Ideally you might collapse the middle items of a path. cheers -ben
