[Kde-hardware-devel] API Stability of upower

[Dario Freddi]

On Friday 19 March 2010 19:50:53 Michael Biebl wrote:
> 2010/3/19 Dario Freddi <drf54321 at gmail.com>:
> > On Thursday 18 March 2010 14:40:05 Richard Hughes wrote:
> >> On 15 March 2010 22:48, Dario Freddi <drf54321 at gmail.com> wrote:
> >> > I am mostly concerned about API stability. If there was an (even
> >> > partial) guarantee of API stability I would be extremely happy,
> >> > however I am mostly interested in knowing if any big changes to the
> >> > public interfaces are planned in the near future, to avoid wasting my
> >> > time and starting a versioned dependency hell.
> >> 
> >> Nope, no big changes are planned. We might tweak here and there, or
> >> add a few methods, but I'm mostly happy with what we've got now.
> > 
> > Ok, thanks. I'll start giving it a shot then.
> 
> I think what should be mentioned though is, that new projects should
> use the new libupower-glib library and not libdevkit-power-gobject.
> 
> The latter is mostly there, so existing apps keep working until they
> are ported over to libupower-glib.
> 
> Or are you planning to only use the D-Bus API?

(Preamble: I already read through the API docs)

I am definitely planning to use DBus. After all, it looks to me like 
everything needed is in the DBus interface(s) and there are not non-standard 
types around (btw, good job in that), so there's not a big advantage in using 
the glib library over dbus - which is definitely how things should be.

The only thing I actually dislike is the Changed() signal, which makes no 
mention of which property was actually changed, forcing me to analyze the 
whole DBus interface to find out what changed. If the glib library addressed 
this issue providing a changed signal that would also list what got changed 
(a-la-hal, just to make it clearer), I could consider it.

Of course, the best solution would be having this kind of signal into the DBus 
interface :)


> 
> Cheers,
> Michael

-- 
-------------------

Dario Freddi
KDE Developer
GPG Key Signature: 511A9A3B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-hardware-devel/attachments/20100319/e655fe46/attachment.sig