Slashdot Mirror
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?
... a "flamebait" or "troll" story category ...
I wanted to take Friday off too, but the boss said I couldn't.
Guess you'll have to do your own homework.
Something to keep in mind even though it's still in it's very early stages... IBM is behind a new Java API for GUI's called SWT (Standard widget toolkit). In a nutshell, it's sort of a combo of AWT and Swing. It uses mostly native widgets (like AWT) for better performance, memory footprint, and native L&F... but also makes use of emulated widgets (like Swing) for the occasions when a particular peered component may not exist on a given platform.
More info on SWT can be found at the Eclipse website as well as a good intro article here. Right now it supports Win32 MFC as well as (somewhat ugly) Motif for Linux, but Qt and GTK ports are being worked on. As always with Java, portability is a strong consideration, and the hope is that an app written with SWT will work on a wide variety of platforms and native toolkits.