KDE Blogs 

Oh boy. Gwenview uses 83% more memory than Kuickshow (http://kde-apps.org/content/show.php?content=9847 - the last comment as of now). BTW I especially like the "83%" part - it's just one case and the measurement is imprecise, but it can't be "about 80%" or "almost double". Reminds me of all those "hair 74% stronger" ads. Anyway. Read More

I took me more than a week to be back on the right timezone, process all the emails,voicemails from various persons, and I'm still not fully 100% operational, but I'm getting there ( I hope). And while I was processing all this "stuff" I realised that I wanted to write something, and this something doesn't mean it's a piece of software, it can be anything. Since I'm notin top shape yet, I have no clue of what this something can be ... maybe I will take 2 asperines and go to sleep tonight and I will have forgotten this .... or maybe not

How can KDE developers find ways to make binary packages of bleeding-edge code directly available to be run by usability experts for early feedback? And if you are less interested in cooperating with usability people (like mornfall ;-P ), you may still ask yourself: How can KDE developers make their bleeding-edge packages available to beta-testers? How let translators see (in their actual, lively GUI context) the strings they work on? How to enable art designers to actually *run* a program they are contributing icons and other artwork for? How can these groups of non-technical KDE contributors (who are not typically compiling KDE every night from the latest checked-out sources) get a full preview of what will go out to our users on Release Day? How can this happen long before the final release, practically 5 minutes after the code was written and compiled, and long before there are official packages created by everyone's favorite distro? Read More

Need a funny start for this week? Try Microsoft tries to recruit me by Eric S. Raymond.

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

Some of you may have first heard of this at aKademy. Jan and I are conducting a simple survey of developers in order to get a better idea of your development style and how we can make the Human Interface Guidelines (HIG) better and more attractive for you to use. Read More

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. Read More

I managed to get a lot of work done today, but not the kind I was aiming for. Things are still insane here at my job in DC so instead of the KDE Usability work I was planning on getting done (sorry Jan, maybe Monday) I get to deal with more crap updates and fight the battles which were usually reserved for the middle of the week (FYI: Just because it VALIDATES for §508 Accessibility it does not mean it is accessible!). Read More

One of the things I'd hoped to do at aKademy was to get some discussion going about using QCA in Qt4. Unfortunately I had a cold, and spent much too much time sleeping and feeling unmotivated instead. So I thought I'd try to kick off some discussion about it now. I'm also going to post this to kde-core-devel, and that is where the discussion should take place. Read More

First, it was just for shits and giggles folks. Don't take it so seriously ;) That said, quite a few folks wonder why I set 'restrict=linux' and not 'restrict=kde' or some such thing. Well, the answer is quite simple... If you'd click through to the parameters explanation link that I posted in the methodology section you'd see that Google has only four topic restrictions: US Government, Linux, Macintosh and FreeBSD ;) There is no KDE restriction. Read More