Hi hindlemail,
I would submit that “empty panes” aren’t an intuitive idea. They might be to developers (who know they’re “hiding” until invoked), but to users an empty space is a
non-entity–it doesn’t exist (ergo “empty”). I think the difficulty of the “empty panes” model is also demonstrated by my attempts to get resources in a side-by-side alignment rather than stacked. I tried toggling the view, dragging and dropping, everything I could think of, but I couldn’t make it happen. And then I opened another resource in a “empty pane” and it opened to the side. That was very unexpected! It means one has to be quite intentional about which resource one opens when and where… I don’t think changing the name (e.g., “Show empty panes”) would have helped me to understand the conceptual framework behind the “empty panes”. I’m still not sure that I do…
I would also suggest that going to the menu after clicking “New Pane…” isn’t a very likely move for most users (not this one, anyway). It’s nice that the menu option changes, but it’s rather hidden and doesn’t help to explain why clicking X on /one/ pane closes all of them… That’s behaviour I haven’t encountered before.
For what it’s worth,
Paul