Linked by Thom Holwerda on Wed 20th Oct 2010 22:22 UTC, submitted by vivainio
Ubuntu, Kubuntu, Xubuntu This is kind of... Well, good news, I suppose? It depends on where you allegiances lie, but it seems like Ubuntu is warming up to the idea of using Qt to develop applications. It's no secret that Qt is a far more advanced development framework than Gtk+, so it only makes sense for Ubuntu - a GNOME/Gtk+ distribution - is looking at it.
Thread beginning with comment 446312
To read all comments associated with this story, please click here.
Technical superiority to GTK
by tristan on Thu 21st Oct 2010 13:50 UTC
tristan
Member since:
2006-02-01

I've heard a lot -- including in this article -- about Qt's technical superiority to GTK, but searching online only seems to bring up entirely one-sided fanboy comparisons with little technical detail.

So, could anybody tell me briefly, what is it that makes Qt so much better? What can you do with Qt that you can't do with the combination of GObject, GIO, GTK, Cairo, Clutter, GStreamer, and so on?

This isn't a troll, I'm genuinely curious: I know quite a lot about programming the "G" world and next to nothing about the "Q" (or "K") worlds, and I'd like to expand my knowledge.

Reply Score: 2

RE: Technical superiority to GTK
by lemur2 on Thu 21st Oct 2010 14:29 in reply to "Technical superiority to GTK"
lemur2 Member since:
2007-02-17

I've heard a lot -- including in this article -- about Qt's technical superiority to GTK, but searching online only seems to bring up entirely one-sided fanboy comparisons with little technical detail.

So, could anybody tell me briefly, what is it that makes Qt so much better? What can you do with Qt that you can't do with the combination of GObject, GIO, GTK, Cairo, Clutter, GStreamer, and so on?

This isn't a troll, I'm genuinely curious: I know quite a lot about programming the "G" world and next to nothing about the "Q" (or "K") worlds, and I'd like to expand my knowledge.


I'm not a developer, but surely this would be a start:

http://qt.nokia.com/products/developer-tools/

http://en.wikipedia.org/wiki/Qt_Creator

Qt Creator is a cross-platform C++ integrated development environment which is part of the Qt SDK. It includes a visual debugger and an integrated GUI layout and forms designer.


http://en.wikipedia.org/wiki/QML
http://en.wikipedia.org/wiki/Qt_Quick

http://en.wikipedia.org/wiki/Qt_Creator#Version_Control_Systems

http://en.wikipedia.org/wiki/Qt_Creator#Qt_Simulator

http://en.wikipedia.org/wiki/Qt_Creator#Targets
Qt Creator provides support for building and running Qt applications for desktop environment (Windows, Linux, and Mac OS) and mobile devices (Symbian, Maemo, and MeeGo). Build settings allow you to quickly switch between build targets.

When you build an application for a mobile device target with a device connected to the development PC, Qt Creator generates an installation package, installs in on the device, and executes it.


Find out more here:
http://qt.gitorious.org/qt-creator/pages/FrequentlyAskedQuestions

Reply Parent Score: 2

tristan Member since:
2006-02-01

Thanks, but perhaps I should have been clearer; my query wasn't so much "how can I learn about Qt", but rather *why* should I learn about Qt? What would it get me? Why is it better than the technologies that the Gnome world uses?

You can find a lot of things saying "Qt is superior" without any real details about what makes it superior.

Again, this isn't meant to be a troll or an invitation to a flamewar. Like I said, I know quite a bit about GTK development -- I do it for a living -- and I'm wondering what it is I'm "missing out on".

Reply Parent Score: 2

RE: Technical superiority to GTK
by phoenix on Thu 21st Oct 2010 17:05 in reply to "Technical superiority to GTK"
phoenix Member since:
2005-07-11

So, could anybody tell me briefly, what is it that makes Qt so much better? What can you do with Qt that you can't do with the combination of GObject, GIO, GTK, Cairo, Clutter, GStreamer, and so on?


The nicest thing about QT is that it's one framework, one coding style, one set of APIs, one environment, one dependency.

Trying to write a GTK+/GNOME app can lead to multiple coding styles, multiple API styles, tonnes of dependencies, and so on.

It's the different between using an IDE for coding, and using a mishmash of editors and command-line tools.

Reply Parent Score: 5

Neolander Member since:
2010-03-08

Trying to write a GTK+/GNOME app can lead to multiple coding styles, multiple API styles, tonnes of dependencies, and so on.

It's the different between using an IDE for coding, and using a mishmash of editors and command-line tools.

Not sure it's a good comparison. In some cases (e.g. when you really need fine-grained control on the compilation + linking process, like in kernel development), going text editor + command line is just the best option. In other (arguably most) cases, it's IDEs which rock. One should use the right tools for the right job.

On the other hand, I can't think of a situation where tons of dependencies with various coding styles could be a good thing.

Edited 2010-10-21 17:51 UTC

Reply Parent Score: 3