Linked by Thom Holwerda on Mon 6th Jul 2009 15:43 UTC
Qt As some had already anticipated when Nokia acquired Trolltech, the next version of the Maemo platform will have its application framework based on Qt instead of Gtk+. This news was announced at the Gran Canaria Desktop Summit. While the switch to Qt may seem a major defeat for the GNOME community, this isn't exactly true, as many of the underlying technologies will still be GNOME-centric.
Thread beginning with comment 371900
To read all comments associated with this story, please click here.
Comment by Mark Williamson
by Mark Williamson on Mon 6th Jul 2009 15:59 UTC
Mark Williamson
Member since:
2005-07-06

<quote>glib, dbus, gvfs, bluez, telepathy, avahi, gstreamer, gconf</quote>

Out of those, surely at least dbus, telepathy, avahi and bluez are all desktop-neutral? Did that perhaps mean to say Gnome-compatible or *even* "developed by Gnome people", as opposed to Gnome-centric? Because they are things that can be / are used by other desktop environments too ...

Reply Score: 8

RE: Comment by Mark Williamson
by boldingd on Mon 6th Jul 2009 16:05 in reply to "Comment by Mark Williamson"
boldingd Member since:
2009-02-19

I'm trying to figure out why you'd use glib, or what you'd use it for, if you're mainly writing software in C++ on QT. My understanding was that glib mainly provided an object system for C: C++ has its own, different object system already.

Reply Parent Score: 4

flynn Member since:
2009-03-19

I'm trying to figure out why you'd use glib, or what you'd use it for, if you're mainly writing software in C++ on QT. My understanding was that glib mainly provided an object system for C: C++ has its own, different object system already.

GObject is just one part of glib. The library also offers other things such as data structures and utility functions for all sorts of things. However, QtCore offers largely the same things.

Reply Parent Score: 5

Elv13 Member since:
2006-06-12

GLib is an optional dependency of Qt. I think Qt can share even loop and some other part with glib so only one will run in the background and be loaded in memory, even if both Qt/KDE and Gnome apps are used at the same time.

Reply Parent Score: 2

TemporalBeing Member since:
2007-08-22

True...my guess though is that they will eventually push away from GNOME and are using this as a stepping stone. The whole:

1) Add new stack with compatibility for the old
2) Start deprecating the old stack
3) Remove the old stack and be completely on the new

Qt is great; and has a lot of advantages - signals/slots is one that is far superior to Message Maps (Gtk, MFC). It also plugs in easily with other toolkits (Gtk, Win32, Cocoa) and can use other signal/slot implementations (e.g. Boost) either out-right or in parallel, and can switch out its message loop too if desired.

Any how...that's my guess.

Reply Parent Score: 4

"Gnome" stack in harmattan
by vivainio on Mon 6th Jul 2009 18:37 in reply to "RE: Comment by Mark Williamson"
vivainio Member since:
2008-12-26

True...my guess though is that they will eventually push away from GNOME and are using this as a stepping stone. The whole:

1) Add new stack with compatibility for the old
2) Start deprecating the old stack
3) Remove the old stack and be completely on the new


They have very little reason to throw away the "Gnome" stack, because it's pretty much the standard Linux stack these days. Having it around allows them to leverage the work of others, and contribute back to Linux.

Also, a lot of that stack is just a bunch of daemons. It's not like you have to be married to Gnome to benefit from it. They "just work" in the background.

Ironically, even if dbus is often (misguidedly) pushed as "Gnome" technology, it's Qt that has the world-class dbus bindings (QtDbus). This is good, considering that dbus is at the heart of what is happening in Linux userspace these days.

Reply Parent Score: 6

Daniel Borgmann Member since:
2005-07-08

And this is how it should be. Developing software for ego is pointless, software is developed for usefulness. It doesn't matter one bit how "GNOME centric" a library is, what matters is that these are all technologies that together build the foundation of what is known as "the GNOME project". "GNOME" isn't just a bunch of people or corporations who strife for personal recognition, it's a rallying flag for many diverse (but interoperable) free software desktop technologies.

Reply Parent Score: 3