D-Bus requirements of knm-0.7

[Helmut Schaa]

Am Montag, 17. Dezember 2007 12:21:57 schrieb Michael Biebl:
> Kevin Krammer schrieb:
> > I had hoped the bindings would get used by projects using D-Bus on KDE3,
> > but unfortunately adding them to the D-Bus bindings page and blogging
> > about them a couple of times doesn't have been enough marketing and
> > projects like KDE bluetooth put quite some effort into using low-level
> > D-Bus with basic event loop integratation instead :-/
> >
> > KNetworkManager is AFAIK probably the only real project using it right
> > now. This has improved finding bugs tremendously.
> >
> > If any packager needs anything changed please be free to contact me
> > directly at any time.
>
> I don't want to sound negative, but given the fact that KDE4 is around
> the corner and as you said, almost every project using the old-style qt3
> dbus bindings, do you think it's still worth the effort to work on this
> new qt3 dbus bindings (and porting knm to it)?
> Please consider that this will add additional workload for all
> distributions, which now have to package two qt3-dbus libraries.
> Are the advantages of this "new" qt3-dbus bindings so compelling to
> justify this?

Yes!

I first tried to use the old qt3 bindings but _every_ simple API change 
introduced by NM threw me back some hours. Using Kevins DBus-bindings a lot 
of work is done automatically (generating proxys and interfaces).

Btw. the NM-0.7 DBus API changed extremely since 0.6.x and it got much more 
complex too (in other words: it is hard to find a method that did not change 
or did not get removed).

Another advantage is the similarity to the Qt4 DBus bindings. We do not know 
exactly how networking will look like in KDE4 but a lot of code written for 
KNM-0.7 can be reused either in KNM itself or in SOLID.

Regards,
Helmut