Combined view done right

When NetNewsWire 3.0 got released, one of the most prominent new features was the combined view which basically gives you a combination of the list and the detailed view … think: Weblog ;-) Yesterday I finally gave it a try (normally being a fan of the classic view) and came out with some mixed feelings.


First of all: I like the idea of a combined view since I normally just move from item to item by hitting the space-key and focus only on the detailed-view area of the application. So I thought: “Why waste at least 30% of my screen real estate for a view that I don’t use at all?”

But if you’re using primarily the keyboard for navigating the combined view in NetNewsWire is far less useful than you would expect. This has nothing to do with how you navigate, though, but more with how NNW renders the feed items. The problem is, that the latest item is not necessarily at the top of the screen which makes reading way more tiring esp. if you’re working on a screen with a resolution > 1024x768 since you always have to focus on a different area of the screen.

NNW3's combined view

Then I went over to Google Reader since I remembered also seeing such a “combined view” there. Google Reader calls it the “Expanded view” but it’s basically the same, just with a small difference: Here the item you’re currently reading (as indicated by using the “Next item” button or the space key) is always at the top of the screen

Expanded view in  Google Reader

Thanks to this Google Reader in my eyes has become way more usable than NetNewsWire. Sadly also on Google Reader it doesn’t always work, so sometimes you will end up with the current item in the middle of the screen. But when thanks to it’s height an item gets render again at the top of the screen, the next one will do the same (until another “accident” happens :-( ). I only experiences this while using the space-key for navigation and it seems works better when you use the j/k keys and then scroll manually.

In NetNewsWire using the +/- keys doesn’t change this behaviour, though.

comments powered by Disqus