All opinions expressed are those of the authors and not necessarily those of OSNews.com, our sponsors, or our affiliates.
  Add to My Yahoo!  Subscribe with Bloglines  Subscribe in NewsGator Online

published by Thom Holwerda on 2007-10-21 20:02:41 in the "GUI" category
Thom Holwerda

About seven months ago, Eugenia wrote on her blog:

Don’t you think that this looks sweet? The statusbar/toolbar font is -2 points smaller than the default font size (minimum size is 8pt). We filed a bug report on GTK+ over a year ago about this but no one seems to care, even if it makes the windows look so much better (applications like Baobab that now comes in Gnome 2.18+ by default would greatly benefit from it because it has a lot of toolbar text). So far in my Gnome desktop I had to disable the toolbar text completely, but with these changes I would leave it on. BeOS and Mac OS X’s toolbar font is also smaller than the rest of the fonts and it?s details like these that make these UIs look “cleaner”. The devil is in the details.

Eugenia and I regularly disagree, but on this one, I agree wholeheartedly with her. Let me explain.

A window is a user interface element comprised of several different areas. From top to bottom, a standard window is made up out of the window title, menubar, toolbar, actual content area, and a statusbar. See the below schematic representation.

Furthermore, a window may contain loads of other areas, such as an address bar, or additional menubars like the bookmarks toolbar in many web browsers. In addition, each window has widgets, such as scrollbars window manipulation widgets (close, minimise, maximise, etc.). Lastly, the content area itself can be divided up into different areas, but you can forget that for the moment.

All these elements of a window need to be differentiated. You see, users need to be able to instantly recognise where each of the standard window areas are, so that he can quickly familiarise himself with said window. You can achieve differentiation in a lot of different ways - by using colours, separating horizontal lines, font differentiation (both typeface as well as font style), those sorts of things.

The challenge, of course, is to strike a perfect balance between easy differentiation on one side, and a clean appearance on the other. If you use all of the differentiation possibilities I just mentioned, you’ll end up with a very messy and cluttered window - achieving exactly the opposite of what you are aiming for. However, if you disregard all of these features, you will end up with, yes, a very clean window - but also a window that is very hard to navigate because it is very difficult to see where one area ends, and the other starts.

Consequently, I’ve been following the KDE4 maturation process with great interest. I have been very eager to see how the KDE guys would balance the scale between easy differentiation, and clean looks - especially taking into account KDE’s history of, well, dumping widgets all over the place. And sadly enough, only a few months before the final release of KDE 4.0, this is what KDE4 looks like.

There is no typeface differentiation. No font style differentiation. No colour differentiation (except for the content area). No colour differentiation. I could live with all that, were it not for the fact that it also lacks… Separating lines. Titlebar, menubar, toolbar - they are on big blob of white. Sure, themes can be changed and all that, but as has been repeated often on the ‘net, defaults matter. And if this is the default, it’s simply a fcuking mess. They put “clean” atop their list of priorities, but ended up with something so clean, it’s close to unusable.

To prove my point, I added a few separating lines between the window areas, and see how much it cleaned up already, by using just a few 1pix lines! Clickety-click for full-size.


Comments

published by Thom Holwerda on 2007-04-18 21:58:02 in the "GUI" category
Thom Holwerda

This has to be one of the most brilliant emails I have ever seen.

> Hi,
> The attached is a patch to gnome-about.c in libgnomeui
> for your consideration. It adds a line “GNU Network
> Object Model Environment” to the “about GNOME” dialog
> box, as well as a hyperlink from the word “GNU” to
> www.gnu.org. I think it is a good idea to show
> explicitly what “GNOME” stands for.

I thought it was generally considered that “GNOME” was really “Gnome”
and that the acronym was silently being consigned to the
“Really awful acronyms” chapter in the history books.

> Right now no
> where is the full name of GNOME displayed and that can
> be confusing to the new user. Tbis additional display
> also helps promoting the concept of Free Software.

How is it confusing to users?

As opposed to the confusion arising from seeing
“GNU Network Object Model Environment”
and thinking “WHAT THE FUCK IS THAT ABOUT????”

(Bear in mind, I’m in no way a ‘new user’
and I still think “WHAT THE FUCK IS THAT ABOUT????”
whenever I’m presented with
GNU Network Object Model Environment)

iain

What’s funny is that I sometimes get in misunderstandings on mailing lists because especially Americans are offended by my traditional Dutch approach– get right down to business, no sugarcoating, no sweet talking, and maybe throw in a little (biting) sarcasm here and there. This email has the exact same style, and I like that.

If all OSS m-l’s were like that, they’d be a lot more productive.


Comments