DeviceKit-power future plans
Kay Sievers
kay.sievers at vrfy.org
Mon Aug 18 10:23:18 PDT 2008
On Mon, 2008-08-18 at 12:50 +0100, Richard Hughes wrote:
> On Fri, 2008-08-15 at 23:23 +0200, Kay Sievers wrote:
> > On Fri, Aug 15, 2008 at 12:41, Richard Hughes <hughsient at gmail.com> wrote:
> > > On Wed, 2008-08-13 at 11:58 -0400, David Zeuthen wrote:
> >
> > >> - What's up with the libdevkit-power? Is this a C wrapper for the D-Bus
> > >> service? I think we want to export this... just use proper and nice
> > >> D-Bus bindings instead.
> > >
> > > Well, it's mainly because dbus-glib sucks as a binding. Originally the
> > > library was static as was just used internally, but I made it shared so
> > > that I could reuse giant chunks of it in the modified
> > > gnome-power-manager.
> >
> > Are you sure that is needed? Why does g-p-m will need a lib to use the
> > D-Bus interface? If you need that, does the interface export the
> > things in the right way?
>
> Ohh, it's not needed, it's just a convenience wrapper to make working
> with a set of dbus objects a bit nicer. It might make more sense to just
> copy the couple of files from project to project, although it does make
> keeping them in sync a pain.
Yeah, would be cool if you can copy it. The stuff in there should
really not be exported that way by the service itself.
It would also be nice, to rename that thing in the source tree. There
should be nothing close to a "libdevkit-power" that is provided by the
service implementation. It would become the de-facto API to the service,
which we want to avoid. Such a lib, over time, would get functionality
and fixes, instead of changes/fixes to the D-Bus interface/service
itself where they belong.
Thanks,
Kay
More information about the devkit-devel
mailing list