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

Re:licensing Qt == dangerous

[fault0]

That's complete bullshit. Qt's commercial license has no clause like that. Only Qt's educational program has something like that, and no one is talking about that here.

Go away, troll.

Re:Some REAL points

[21mhz]

QT is OO by design. GTK-- is OO by kludge.

And the end result is different because..?

> QT 3 gives you access to SQL-databases from its widgets.

Why?
To make it easier to build database-driven applications without having to twiddle between two libraries.

If I understand correct, the other poster talks about database access from visible GUI elements. This is insane, by my book. Having an embeddable database viewer component is probably a good thing, but bolting it into library widgets is perpetrating unnecessary bloat. An object-oriented database layer can be helpful though, for you weaklings, hehe.

Don't get me wrong, I love GTK and I hate KDE, but QT just feels nicer and works nicer, and as much as I'm loathe to, I have to admit that.

Sorry, but you're a fucking troll.