Linked by Thom Holwerda on Mon 6th Jul 2009 15:43 UTC
Permalink for comment 371928
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-06
Huh? BlueZ was developed by Qualcomm annd is part of the Linux kernel. It has no special relationship with GNOME. Whith the exception of GLib, none of the listed technologies have any special relationship to GNOME. Just because a neutral technology was first implemented in GNOME doesn't turn it into "GNOME-centric". E.g. D-BUS: It was GNOME was the first to officially embrace it, but GNOME also had more to gain by it, because Bonobo seems to have bigger defiencies than DCOP had (at least according to IBM): "DCOP is a solution for KDE, but is tied to Qt and so is not used in other desktop environments. Similarly, Bonobo is a solution for GNOME, but is quite heavy, being based on CORBA. It is also tied to GObject, so it is not used outside of GNOME. D-BUS aims to replace DCOP and Bonobo for simple IPC and to integrate these two desktop environments. Because the dependencies for D-BUS are kept as small as possible, other applications that would like to use D-BUS don't have to worry about bloating dependencies." http://www.ibm.com/developerworks/linux/library/l-dbus.html?ca=dgr-...