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.
Thread beginning with comment 349236
To read all comments associated with this story, please click here.
Qt <-> gtk+ integration
by slougi on Mon 16th Feb 2009 14:22 UTC
slougi
Member since:
2006-08-16

I am not going to comment on your post in general, but one think stuck out. You say:

Qt does a pretty good job of making sure its applications do not stand out graphically - or better put, it makes sure Gtk+ applications do not stand out in a Qt environment.

In my experience the opposite is true. Generally I think it's the Qt-based applications that integrate better with gtk+ environments, especially given QGtkStyle, which I believe will be the default Qt style in GNOME starting with Qt 4.5.

The GTK-Qt theme engine does not work quite as well in my experience.

Reply Score: 4

RE: Qt <-> gtk+ integration
by siride on Mon 16th Feb 2009 15:08 in reply to "Qt <-> gtk+ integration"
siride Member since:
2006-01-02

That's why you use QtCurve, which uses a similar theme engine for both GTK+ and Qt and uses the same color and style settings for both. The apps really do look fairly similar. It can even change the ordering of buttons if you are somebody who is anal about that.

Reply Parent Score: 2