the three-pane question revisited


There were some good comments to my entry a few days ago "the three-pane question", as well as great posts in other weblogs from Eugene (of JetBrains, the makers of the excellent IDEA) and from Cristian. Thanks to everyone for the feedback.

Both Eugene and Cristian think the UI is good given the correct implementation, while some of the comments on the entry are against it (such as Russ's, or Bruno's). My personal intuition is that this change is good. There are all sorts of theoretical UI-reasons I can come up with for why the linear three-pane is better than the "old" version. For example, the eye-movement effect, that is better (particularly for western readers, without left-to-right writing/reading system), or that it's been studied to death how we read faster and how eyes get less tired when they have to move less horizontally (If you don't believe it, pick any book from your shelf. Count the words a few sentences at random. You'll rarely find more than 11 or 12 on average, maximum. This is not a coincidence).

What I find the most interesting, however, is that several comments in the entry felt that they'd have less real-estate for the content-viewing area, which is not the case. A simple example: look at the first drawing in the post, with the "classic" three-pane view, and assume that the first level pane has a width (at the base) of 1, while the second level pane has a height (at the far right) of 1 as well. Then assume that the height/width ratio of the display is 4:3, a standard TV or monitor (not those new fancy widescreen monitors though...) Okay, so the total area is 12. The area for the first-level pane is 3, the area for the second-level pane is 3 (because one unit is lost at the beginning from the 1st level pane, so 3 by 1). The content-view pane is 3 by 2, area 6.

Now, same widths for the second case: 1 at the base for both the 1st and 2nd level navpanes, which leaves 2 of width of the content pane. Area of 1st level nav: 3. Area for 2nd level nav, 3, area for content pane: 6.

Every single area is the same. Doesn't look like it, does it?

However, now, if you want to see more rows you can (by showing only one line per row) or if you want to retain almost the same level of information and still show more rows, you can do that too. No space lost.

All that said, some people might have their own reasons for why they'd prefer to keep the old UI (resolution used, or simply more comfort, and after all, that's what UI design is all about), so providing choice on the matter is probably a good idea. :)

Besides, there are other issues very specific to email that also have to be taken into account. This display mode is great for flow-formats like HTML, but in the comments Adrian pointed out that the display of quoted text emails would almost certainly require horizontal scrolling.

I've been playing on-and-off with an altogether different possibility, I'll post more details when I have processed it enough to explain it coherently.

I will add this though: I think that one of the problems with making an objective analysis of the linear three-pane UI (for everyone, for, or against it) is that it doesn't look radical. Where's the 3D? Where's the VR? Where are the visual gizmos? You call this "innovation"? We have sort of come to expect a certain "revolutionary" feel from UI changes over the years, and the linear three-pane UI disappoints there.

Anyway. More later!

Categories: soft.dev
Posted by diego on July 7 2003 at 12:48 AM
Comments (please see the comments & trackback policy).

First, of course I am all for having this as an option, you know I was just giving my HO.

Anyway, let's consider a book, and two simple "scenarios".

1. Divide the page vertically.
2. Divide the page horizontally.

In both cases only one half of the total page area is used for the "main content".

Which of the two would you find easier to read ?

Regardless of what you do, and how you do it, keep horizontal scrolling to a minimum (imagine turning a page for "each" line you read to finish it on the other side !!)

Posted by: Bruno at July 7, 2003 2:45 AM

One question which is worth
asking is this, though: is the 3 pane interface necessary at all? In
email ot netnews, where the fidelity of titles is very very poor(Jon
Udell has written a lot about this..), the 3 pane interface visually
helps us scan for threads and such. But otherwise, when we have good
titles or summaries, does a 3 pane interface (vertical or horizontal)
provide us enough real estate to view these well?

Radio Userland creates an interesting UI without the 3 pane effect, but
dosent let us hop quickly between feeds, which a 3 pane interface does.
But is feed hopping in an out of order sequence that frequent that we
need to provide space on the screen for feed names? Wouldnt a UI device
like a click that provides the feed l;ist and a second click on the
feed name which goes to the feed name suffice?

In other words, wouldnt a two pane interface suffice, with the left one
consistently taking the job of being the container for the third? Fort
of like the horizontal view finder on macosx, but far more loose in
thee vertical display, with both panes being for eg html if necessary,
or UI code in the feed names view or other container views... Then by
reducing the UI size vertically or using a cinema display, one could
utilize the width aspect of the screen to give a side by side book like
view..

I suppose the familiarity of the 3 pane interface trumps everything
else. But I do wonder that if such a user interface is what is desired,
why aggregator writers write one's own 3 pane UI? Why not use outlook
with a plugin, as Greg Reinacker does, or provide a RSS to IMAP
translation, as the Blogstreet guys do? It would free one ffrom having
to worry about UI...

Posted by: Rahul Dave at July 7, 2003 3:37 AM

As I said, I think that it can be done, or maybe there's an intermediate approach that could be even better: http://www.cristianvidmar.com/2003/07/07.html#a82

Posted by: Cristian Vidmar at July 7, 2003 10:30 AM

Read and agreed 100% with Cristian's approach.

As mentioned by him, Outlook does provide this option, which I have tried now and then, the only problem with this approach is when you have dozen of "rules" that automatically move incoming email to different folders (as is my case and that of many of my users), and you want to keep and eye on incoming email on different spaces/folders. Believe it or not, my use case scenario consists of at least 2000/3000 messages (intra/extranet) that get sorted to 20 different folders/rules a day. (Yes, we are moving out of email and building an adhoc app to handle this kind of volume :-)

Posted by: Bruno at July 7, 2003 11:09 AM

What about vertical layout? You could show the first level in the entire pane; upon clicking on an item, the pane collapses to show only that entry (or a summary thereof) and displays the second level list in the remaining space; and so on and so forth until reaching the leaf data item, in this case the email or content. You can dismiss any pane, that is, you can return to any level, which then redraws itself in the content area.

Remember that we read in a comb-like fashion where the "teeth" run from left to right (the comb's spine is on the left). You justify the horizontal layout you propose by analogy with reading, when in truth you place the spine at the top.

Matías.

Posted by: Matías Giovannini at July 8, 2003 5:42 PM

Copyright © Diego Doval 2002-2007.
Powered by
Movable Type 3.35