Linked by Thom Holwerda on Wed 19th Jan 2011 22:04 UTC
Xfce When we reported on the release of Xfce 4.8, we ignored a statement inside the release announcement about the lack of new features coming to the BSD world. The statement was a bit disconnected from the rest of the press release, but Xfce developer Jannis Pohlmann has published a blog post giving a few more details about the issue.
E-mail Print r 6   · Read More · 84 Comment(s)
Thread beginning with comment 459179
To read all comments associated with this story, please click here.
dbus
by Soulbender on Thu 20th Jan 2011 11:02 UTC
Soulbender
Member since:
2005-08-18

I'm a bit confused about this really. I was under the impression that user-space desktop apps used dbus for this. Isn't this just matter a of writing a dbus service for BSD that mimics the udev dbus service interfaces?

Edited 2011-01-20 11:08 UTC

Reply Score: 2

RE: dbus
by TheKhan on Thu 20th Jan 2011 14:17 in reply to "dbus"
TheKhan Member since:
2011-01-20

Not really, thunar-volman uses the udev library for device management and notification etc.. So someone in BSD camp will need to implement the same backend for *BSD, probably using devfs. That is what happened with HAL as well.

A common abstraction layer, such as HAL helps a lot in terms of interoperability, because most applications end up using it in terms of device related operations. So it is a single coding effort to implement a BSD backend in HAL, which was done. Now with udev and libudev, coding will be needed for every other component that uses it directly.

The KDE folks are doing it in the best way imho, implementing their own hardware abstraction. Then every other KDE app uses that, and you only needed to implement a BSD or any other backend for the abstraction layer.

Reply Parent Score: 2

RE[2]: dbus
by Soulbender on Thu 20th Jan 2011 19:37 in reply to "RE: dbus"
Soulbender Member since:
2005-08-18

That is what happened with HAL as well.


But the HAL api was only accessed by desktop apps thru dbus. All you needed to do to "port|" HAL to a new platform was to somehow implement the same dbus interfaces (by no means a simple task though. I know, I tried). Why wouldnt udev be done the same way?

Reply Parent Score: 2