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 :)

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

I started to have a deeper look into D-BUS as I will require an IPC facility if I want to provide a Qt4 API of QDS and still access KDE services.

So after I installed the dbus-1.0 packages, it played a bit the included tools, starting a session bus and watching output with dbus-monitor.

I've got myself a new toy: a Soekris net4801

Here is a nice gallery of images for it.

In the more distant future it is supposed to take over the position of the firewall on my home network, but right now it is fair game for doing geek stuff ;)

Obviously the thing itself is already cool, but an advanced geek won't be satisfied that easily

Since it is currently en vogue to ponder about the use of the KDE name, I have no other joice to join the fun ;)

While the focus has been on the topic of applications, it also applies to developers:
when can a developer call himself a KDE developer?

Barry Hawkins blogs about his reasons why he thinks working on free Java implementations is a good thing.

Being a long time JavaLobby subscriber I have read several pieces of pro and contra and enjoyed several flamewars in the articles' trackbacks or forums :)

One item I care about but that really seldom comes up in this discussions is installing Java runtime environments (JRE).

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 :)

Free software development is all about feedback.
Feedback from other developers, non-coder contributors to the project,
your packagers and your users.

Sometimes you get very few feedback, which could either mean you are not
reaching anyone or everyone is so satisfied with the projects current state.

For my on sanity I assume the latter :)