Slashdot Mirror

← Back to Stories (view on slashdot.org)

GTK-- vs. QT

Posted by ryuzaki0 on from the technical-comparisons dept.

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?

2 of 325 comments (clear)

  1. Re:Some _REAL_ points by GiMP · · Score: 2, Troll

    Yes, vim is just a text editor. Which is exactly my point. You have an application for each function you need to do, and thats it. No bloat, no mess.

    Why would I want an app to do my Automake/Autoconf stuff? So I can spend days debugging it? So I don't learn anything and become dependant clicking a mouse? Its so easy to click those buttons in Kdevelop when I'm ssh'ing to my application server.

    I must admit that I've never used Gtk--, as I don't write code in C++. I have written code with Gtk+ and Gtk-perl, and I found it quite easy and enjoyable.

  2. Re:Some REAL babble (was Re:Some REAL points) by GiMP · · Score: 2, Troll

    A text environment is not a restriction, it is directly oppossite of such. It is the only environment capable of being productive.

    Sure, I can't play quake on a piece of paper.. although I can play it on a terminal.. However, that is not the point. Quake is a game..
    KDevelop is an IDE.

    When you are doing development which doesn't require more then a text editor, why limit yourself to learning a GUI environment? That will be really helpful when ssh'ing to your box or X windows crashes.

    And yes, I assumed that QT is a GUI toolkit because anything more would be terrible bloat. It shouldn't become a library for providing everything.

    I laugh when I hear people who think that pointing and clicking is faster then Vi commands and the power of the shell.