KDE Blogs 

[image:3150 align=left size=thumbnail hspace=20] As you can see in this image, I managed to get plasma to run on a Neo1973 phone (using an openmoko image for the rest of the software). The only changes I needed to make to kde code where changes related to qreal not being a double on an ARM processor (except of course some hacks to actually make it cross compilable).

Good Morning Friends, do join us in a few hours for these fine IRC tutorials. And congratulations to Trolltech for including parts of Qt in KDE's svn for the first time. Even closer cooperation with our favourite framework authors is worth getting up early in the morning to publish the story for.

One picture is worth more than 10 words, but that's the limit for a blog entry :)

I posted this to k-c-d a couple days ago, but it generated zero response, so I thought I'd post it to the ol' blog in case any non k-c-d types might be interested. Read More

That went well. We even had some of SuSE's finest drop by, were they picking up tips? :) Logs available now.

Today Dutch parliament discussed plans of the ministry of Economic Affairs to encourage Free and Open Source Software in government. All major parties seem to understand the issues. Even news agencies are talking about 'vrije software' which is the right term ('Vrije' means 'free as in freedom'). Read More

KDE 4.0 RC 2 has been released so it's time for a new version of the most comprehensive KDE4 Live-CD: [image:3140 size=original hspace=50]

Like many KDE application, strigidaemon uses DBus to talk to other programs. Debugging inter-process communication is never very convenient and strigidaemon is no exception. So far, there are no unit tests for checking the quality of the DBus communication in Strigi. I set about to write some and found it was not so easy, so I'm documenting what I did for the benefit of all the other developers using DBus. Read More

Not mine, but one Korneliusz Jarzebski (in Polish) has done the numbers (pro-linux coverage in German) and produced a chart showing exactly how the RAM consumption of comparable KDE4 and KDE3 sessions measure up. The result is a mindblowing 39% smaller memory footprint in KDE 4. This just goes to show, that it's worth making large-scale changes to your desktop environment to get the fruit hanging on the higher branches. Wait for the mini- and micro-optimisations to start happening in KDE 4.x, too.

So someone just asked in #kde4-devel whether it was worth trying KDE 4 on a 2500Mhz/256Mb computer and I was characteristically careful and guessed "It will work, but won't be good.". Then I decided to put my money where my mouth is and booted my Thinkpad X60 with "mem=256M maxcpus=1", logged into KDE 4 and set the power saving policy to "Powersave", which throttles the CPU to 1Ghz and locks it there. And then I used KDE 4 some, started Konqueror, browsed about a bit, configured a few things with System Settings, started Kopete and chatted a little. And I was pleasantly surprised with how well it all works. With a "debugfull" build from SVN. With kwin_composite 3d eye candy, on Intel. With KDE 3 libraries loaded too (for KPowerSave, since it's not ported yet). As they like to say here in Franconia, it's like "a'Traum". Read More