KDE Blogs 

I needed a short break from coding on the two projects that I've been working on for the last few days on so today I added support for both PPC AltiVec and AMD 3DNow instructions to the KCPUInfo class. Basically for completeness. Now take a deep breath and read the part that says "for completeness" again. I think it's a little funny how for most people just mentioning 3DNow, MMX, SSE or AltiVec is enough to recompile whole kdelibs and spend two days looking for speed differences. KDE is not at a point where assembly level optimizations would matter a lot. geiseri is working on a rather neat DCOP cli optimization. I've been playing with udev a little bit. In case you didn't notice - once you plug a device to your machine (be it usb, bluetooth or any hotpluggable device) KDE has no knowledge of it whatsover. If you ever connected a scanner or a usb digital camera you know what I'm talking about. With udev we could get that working. Pretty much all udev does is intercept the /proc/sys/kernel/hotplug calls and creates nodes. The plan is to make udev emit a signal saying that a device XYZ has been connected after creating the nodes. It's pretty trivial. The hard part is to do it in a desktop agnostic way. DBus, DCOP and on embedded devices simple scripts - they all have to be supported and to have a more complete device database available. I'm so happy kernel is getting there to finally do things like that. Oh, and finally to kill some time I finally started my "Transparency in KDE made easy". I was sick of all the questions about it and decided to write a whitepaper on it. I'm not yet sure where or when I want to publish it. Read More

So I'm excited; JuK is down to zero open bug reports. I think this is the first time that this has been true since about 2 days after it went into CVS. Read More

I recently noticed that handling of "Daylight Savings Time" (a.k.a. "Summer Time") did not work for any southern-hemisphere locations in KStars. I fixed it in HEAD and 3_1_BRANCH yesterday, a bit too late for 3.1.3, unfortunately (it will be in version M_PI if there is one ;) ) Read More

Hi everyone, It's fun to have this platform for developers and so I thought I'd put forward an idea I've been trying to promote for some time that seems to not get much traction in the community. Often I get a request that reads like can you add auto completion support for [your favorite scripting language here]? I dilligently reply "I don't actually use that language and we have a policy that these must be done by people who use them and can test them. However Quanta is set up so that users can add a language using XML." Now, please allow me some small degree of indulgence here... but isn't it weird that given these facts Read More

What would you think about a Jogger interface for kdedevelopers.org? For those who don't know Jogger, it is a Jabber component that allows you to post diary entries via any Jabber client, such as Kopete for example. To see it in action, you can see one installation at http://jogger.jabber.org. Read More

So okay, what do I want from a MUD client? a) Necessities a1) Complete scriptability (better in Ruby or Perl, then Python, custom languages won't do) a2) Bindable keys. Thats crucial since typing commands when you can bind it is a straight road to rip. a3) Triggers. While present in most clients they need be fast and easy to add. a4) Support for encodings other than Latin-1. a5) MCCP, Mud Client Compression Protocol, saves up to 95% of traffic. b) Fancies b1) Automapper c) My ideas c1) Battle screen. More on this later. Read More

lots of stuff is happening to kexi lately. (remember kexi is the database "frontend" in koffice). first of all kexi is now (after jowenn's commit) provideing konqueror like tabbing see http://blogs.kde.org/node/view/108 for a screenshot. Read More

How annoying. I fixed the yahoo bad account data log in bug that Bille (Will Stephenson) pointed out to me, but I can't commit for 0.7 because it has string changes. I suppose I shouldn't bitch much since i'm the one that imposed the string freeze. My original reasoning behind the string freeze was because it would give all the other kopete developers a small taste of what it would be like if/when kopete makes the move to kdenetwork. (not that we really needed the string freeze in the first place). So anyways, that change will go in HEAD when the branch is created in about 3 days from now. Read More

So, what have I been doing while MIA? I've moved house on 15min notice, for a start. I'm incredibly busy with school (assessment tasks, exams, you name it), and trying to get some work done while I still can. I don't even have a real net connection - if I drag my computer downstairs, I can get dialup to a NATed IP. Wa-hey. Read More

kdepim/libkdepim - (KDE CVS Commits) This is going to be something really cool. I now have an example configuration dialog which is automatically generated from an XML description of the configuration options. This includes an automatically generated API to the configurations options for convenient access by the application, it will support all the fancy config stuff like immutable entries etc., and it provides a configuration dialog to edit the options without needing to write any additional code. The best thing: It will be incredibly simple for a developer to use this. Drop the XML description of the configuration options into the source code directory, add custom code, if necessary, and you are done. You will get the configuration dialog for your application for free. It also fits very nicely into the Qt/KDE framework along the lines of XML-GUI and uic. cfgc (the configuration compiler) will be for configuration what uic is for user interface. Maybe it might even make sense to add a configuration designer to provide a GUI for editing the configuration descriptions. Let's see... Read More