The challenge

October 21, 2007

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.

2 Messages »

  1. http://bugs.kde.org/wizard.cgi

    “If you have found a problem in your KDE version or if you want to have a nice new feature in a future KDE version, you can use this form to let us know about it.”

    Comment by Mark — October 22, 2007 @ 1:28 pm

  2. I would disagree a bit; the tiny lines are a distraction. If I have some kind of figure to show, I expect:

    An Anteater In Spring

    {Picture of skinny anteater}

    {spotting data, e.g. the locale and date, control reticle on the X axis and variable on Y, key features etc}

    {raison d’etre, e.g. ‘If there has been a fall to stop ants tunneling out from cover, anteaters will not have eaten ants since then. They are not cute enough to get scraps in town in the meantime.}

    Instead of course we have naked arbitrary lists without so much as ownership info attached (e.g. a gimp tools window kde stlyles would just be this floating contextless thing; unfortunately of course it is particular to the app and not generic.) and with huge wastes of space going in; they just unveiled a new scheduler with multiple timezones considered, but each zone’s progression of hours gets a massive featureless swath of 24oo hours in lieu of some sunup/sundown shading, expected facility hours, &c.
    It sure looks (works) better than it used to in almost all cases;
    but I wonder if the efficiency of the app is being fed as though it were an entelechy instead of a coincidentally coherent cuckoo clock for X11.

    Comment by Ankh if you love Whole Zombi Grain — October 27, 2007 @ 9:42 am

RSS feed for messages on this post.

Leave a message

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong> .

Please use the blockquote tag to quote. Comments containing quotes in other ways will be deleted.


-