"After a lot of hacking behind the scenes, a new initiative to improve KDE's interaction with network and hardware devices has been launched. Solid will provide a robust basis for the dynamic modern desktop in KDE, which needs to be aware of available hardware and networks, paving the way for innovative functionality. Users should see KDE applications taking advantage of Solid in KDE 4, from the most basic Plasma applets and complex applications to desktop-wide awareness. Developers will be able to take advantage of a robust, flexible and portable API and will be integrated into the Plasma engine. It will make use of existing technologies like HAL."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-11-14
I understand "DBUS" as a common interface for the desktop, one that is available for all apps, with a promise keep binary compatibility (just like the public API) in order to allow stable inter app/desktop communication, notifications, etc... allowing applications using other frameworks or even simple scripts to join the fun
Your vision is wrong then. DBus is just a message bus system. It works at the system level to be desktop agnostic. But it needs to be integrated in each desktop : the DM (or login, or whatever logs you in) must launch a dbus for each user.
And the message bus system means it handles broadcast of info, and ACL. IIRC dcop does not provide that, you have to query the info.
The binary stability is a requirement for such a system. I don't think DBus is ready yet for that, the latest 0.60 being ABI incompatible with 0.50.
Currently definition holds for KDE/dcop, but not for GNOME/DBUS
Thta's not true, DCop is more like a remote control, DBUS is more than that.
And I have to disagree with you when you say DBus is not integrated in Gnome.
DBus is integrated with gnome-vfs, which is part of the Gnome framework, and with the notification system IIRC. So you can't say DBus is not integrated in Gnome.
The way GNOME currently uses DBUS, is the same way KDE currently uses it: in isolated places
But depending on what these places are, you can say if it is integrated or not.
Integrated in a library (gnome-vfs, kio plugin) is not the same as just in an app (K3B).
Member since:2005-07-06
Your vision is wrong then. DBus is just a message bus system. It works at the system level to be desktop agnostic. But it needs to be integrated in each desktop : the DM (or login, or whatever logs you in) must launch a dbus for each user.
OK, OK, I know what DBUS is. What I said is what i think "integrating DBUS" means.
That's not true, DCop is more like a remote control, DBUS is more than that.
Wrong. dcop is much more than a remote control. It is much closer to DBUS than you seem to think.
DBus is integrated with gnome-vfs, which is part of the Gnome framework, and with the notification system IIRC. So you can't say DBus is not integrated in Gnome.
Yes, you are right. I stand corrected. I can say that dcop is more integrated in KDE than DBUS is integrated in GNOME, but I can't say that DBUS is not integrated in GNOME.
Member since:
2005-07-06
Oh, then I am curious. What do you mean by "GNOME doesn't use DBus?"
I don't know how he does, but here is how I see it:
I understand "DBUS" as a common interface for the desktop, one that is available for all apps, with a promise keep binary compatibility (just like the public API) in order to allow stable inter app/desktop communication, notifications, etc... allowing applications using other frameworks or even simple scripts to join the fun.
Currently definition holds for KDE/dcop, but not for GNOME/DBUS. The way GNOME currently uses DBUS, is the same way KDE currently uses it: in isolated places.