Linked by Thom Holwerda on Mon 16th Feb 2009 14:07 UTC
Editorial Late last week we ran a story on how the Google Chrome team had decided to use Gtk+ as the graphical toolkit for the Linux version of the Chrome web browser. It was a story that caused some serious debate on a variety of aspects, but in this short editorial, I want to focus on one aspect that came forward: the longing for consistency. Several people in the thread stated they were happy with Google's choice for purely selfish reasons: they use only Gtk+ applications on their GNOME desktops. Several people chimed in to say that Qt integrates nicely in a Gtk+ environment. While that may be true from a graphical point of view, that really isn't my problem with mixing toolkits. The issue goes a lot deeper than that.
Permalink for comment 349411
To read all comments associated with this story, please click here.
Torsten Rahn
Member since:

Umm, why would it make more sense for the tabs to be at bottom for a terminal app?

Because the user's prompt and visual focus is at the very bottom of the terminal window 99% of the time on average (as long as you are in command line mode).

That's pretty much different from a web browser or an editor where you start to read at the top as soon as you open a new Url and keep the text you are interested in about in the center of the viewport when scrolling.

So arranging the tabs at the bottom of the terminal window keeps the names of the sub windows within reach of your visual focus.

Reply Parent Score: 6