GTK-- vs. QT

spirality asks: "The company I work for is getting ready to decide on a GUI Toolkit for our Computational Modeling Toolkit (CoMeT, www.cometsolutions.com). We would like C++ compatibility and ports to various Unices and Win32 platforms. Not supprisingly we've come up with two choices, GTK-- and QT. I've attempted to compare the two by doing alot of web surfing and searching, but I've come up with things that are consistently one or more years old. So, the question I pose is what are the (dis)advatages of GTK-- and QT, and why would I choose one of these toolkits over the other? Overall functionality, momentum for future growth, ease of use, licensing, and pretty much anything else is relevant to our decision." With QT now at version 3.0 and GTK now in the 1.2.x revisions, maybe it's time to give the two libraries some fair comparison and discuss the new features, advantages, and disadvantages of each?

Comments

Why not wxWindows?

[joerg]

Why don't you consider using wxWindows? It is a great portable toolkit for free (LGPL licensed).

wxWindows has a very rich feature set for building GUIs, plus many other benefits like portable classes for threads, networking, ipc, file i/o, serialization and much more. It is available for almost any kind of UNIX-like OS, for any Windows version, and some more platforms like VMS.

It is a shame that wxWindows doesn't yet get more attention.

Portability to Win32

[kintel]

AFAIK, the Win32 port of GTK+ is more or less a one-man show, making GTK pretty unstable and lagging behind on Windows.
In addition, Qt now has a Mac OS X port.

Add this to the excellent commercial support from Trolltech.

Design and language issues not taken into account.

What about wxWindows?

[SerpentMage]

Ever tried wxWindows? I and my company use it. IT IS REALLY nice and easy to use. And it is open source. Best of all it does "little" things like printing...