The last few days saw a couple of threads on the dbus mailinglist about topics we KDE users got used to love in DCOP.
For example how to start browsing for interfaces on applications connected to the bus, in D-BUS terminology called introspection, how to know which session busses are currently active for a user and how to work with users session busses from the system bus.

The last two features are known to DCOP commandline client users as

dcop --all-sessions

and

Last week Cornelius blogged about having some D-BUS Fun using the Qt3 D-BUS bindings I had backported from Harald Fernengel's Qt4 bindings.

Later that week an email conversation between Cornelius, Will Stephenson and myself resulted in the decision to put the bindings into KDE's SVN repository for shared development.
They do now live here and eagerly await your contributions :)

Lets talk SWF. A lot of people seem to be mentioning Gnash today. Some seem to think it's a giant step for FSF. I think it's really funny. It's really funny (or sad - it depends how you look at it) how a giant win for FSF is taking a wonderful Public Domain project and basically just releasing it under GNU GPL.

Today I reworked the QDS architecture so it doesn't require the application developer to delegate QApplication creation to QDS.

The main reason for this requirement has been the desire to use a KDE service implementation, which needs a KApplication instance.

Just reached a releaseable state in my efforts to backport the Qt4 D-DBUS bindings to Qt3.
Basic usage works as expected, but I don't know yet if the marshalling code is sufficient for real world use as Qt4's QVariant is a lot better than one from Qt3, e.g. allowing user defined types.

This tar archive contains the a qt3/ sub directory meant to go into a dbus CVS checkout.

After spending some time on implementing a DBUS proxy object, i.e the service object's peer on the client side, I finally found the 100% CPU usage problem I mentioned in my last blog

One of the cool things about Qt that seems to be ignored is the QLayout classes. Most of us are content to use simple things like QHBox and QVBox layouts to get what we want. But what happens when you need more complex behavior? Well the trolls gave us the ability to create new layouts with a trivial amount of code...

I haven't been blogging for a while. Mainly because I simply haven't felt like it and I've been going through some things lately. But I promised that I'm going to show some movies of things I've been doing. There's really no good way of showing OpenGL effects, vns2swf just doesn't handle it. So those will come later.

Ok, that was a lie, no cowbells ;)

Getting tired of the primitive example application I had for QDS I deciced to create a better one,
including a GUI one can take
screenshots of :)