[packagekit] QT bindings : restart from scratch, but they're coming back :-p
hughsient at gmail.com
Sat Oct 20 01:20:38 PDT 2007
On Sat, 2007-10-20 at 01:09 +0200, Adrien BUSTANY wrote:
> Richard Hughes a écrit :
> > On Sat, 2007-10-20 at 00:47 +0200, Adrien BUSTANY wrote:
> >> Hi there,
> >> I recently received a mail from Kevin Krammer, a KDE developper. He told
> >> me than binding libpackagekit by wrapping the functions and the glib
> >> loop inside Qt was not the best thing, and said that using the DBus
> >> interface would be cleaner and would make it easier for KDE devs to use
> >> the lib.
> > Sure. This means I have to be more careful with the DBUS interface
> > API :-)
> A documentation would be really nice. pk-applications's code's quite
> readable, but a real doc would be a plus. OTOH, once we get a Gtk and a
> Qt interface, maybe it won't be of great interest...
Sure, I'm really lazy when it comes to gtkdoc. I'll see what I can do in
the next few weeks.
> > There's no need to do them all, libpackagekit is a convenience library
> > after all. I would only do the ones you use.
> Yep. For now my approach has been : I want to implement function x,
> which depends on y and z, so bind z, y, then x. Maybe I can continue
> that way.
> >> I'll also have to implement the
> >> policykit bits, I know there's a policykit-gnome package but I don't
> >> know if there's one for KDE (I'm a GNOME user).
> > What's the KDE naming policy? Do you want to create a QT binding for the
> > lib and a KPackageKit for the UI bits? Reusing QPackageKit would be
> > great.
> No idea. I don't want to create a KPackageKit for now, as I said I'm a
> GNOME user, I don't even have KDE libs installed on my box. QPackageKit
> is a lib and a frontend, the lib will be easily reusable if KDE devs
> want to extend the interface. So I'm sticking to QPackageKit.
Sweet, good for me.
> >> That's all for today, see you for the next report :-)
> > Keep up the good work :-)
> I'm very motivated. I got some schoolwork in Ada, it's quite a pain :-)
> C++ unwinds me...
Heh, I do a lot of work in assembly at work, so C is actually quite high
level for me.
More information about the PackageKit