Linked by Thom Holwerda on Mon 6th Jul 2009 15:43 UTC
Thread beginning with comment 371915
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
"Gnome" stack in harmattan
by vivainio on Mon 6th Jul 2009 18:37
in reply to "RE: Comment by Mark Williamson"
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
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.
RE: "Gnome" stack in harmattan
by TemporalBeing on Mon 6th Jul 2009 23:59
in reply to ""Gnome" stack in harmattan"
"True...my guess though is that they will eventually push away from GNOME and are using this as a stepping stone.
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.
"
Well...what's common enough for Qt/Gnome/KDE to work together is not exactly GNOME specific, so I would hardly call that part of the GNOME stack - and that's really what is standard these days, not necessarily anything specific to GNOME. For instance, you don't need anything GNOME related installed to run KDE or any number of other Windows Managers - or Qt for that matter.
And if there's nothing GNOME specific, then why keep it around? Qt offers a lot of stuff (QStrings, QtDbus [as you point out], etc.) that are just so much easier to work with - and if you don't have to move between two toolkits, why do so?
Why make an SDK that has to support two toolkits, when using one gets you all you need and still maintains the compatibility? Qt does just that; so why keep around any GNOME-specific stuff in the long run? (Thus my original comment.)
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.
I'm not sure I've ever heard of D-Bus as being GNOME technology until this thread - I certainly wouldn't consider it so. I hear a lot more about it from KDE stuff as they use it extensively, and also FreeDesktop.org related stuff.




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.