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

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.

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.

Hooray, there is a new NEdit release! Today the first release candidate of NEdit 5.4 was announced. There were three features I was missing from NEdit up to now:

• Start scrolling before the cursor has reached the end of the screen to make sure you always have the overview of a few lines in advance
• An option to show whitespace at the end of lines
• Hiding the mouse pointer when you start typing

All these features are implemented now (and a couple more). I tried the new version and the new features and immediately liked it. That makes NEdit the perfect editor for me. Congratulations to the NEdit team for this marvelous job.

KStars should have a decent telescope control by 3.2. The current client/server architecture in INDI is scalable and would be very handy in observatories or when controlling multiple telescopes. I haven't committed anything in quite a while as I have been moving from one location to another within town and will finally settle soon!

this isn't a rant. it's just off-topic. so there. =) if you're not into music, esp of the folk fest variety, save yourself the boredom and don't click the Read More link.

coming up with titles for blog entries isn't fun/easy, but having to pick node terms is really bloody annoying. especially since it's this long listbox that pushes the body waaaay down the page. couldn't it at least be after the body where i could ignore it? and have "KDE General" (or what-have-you) selected by default?

ok, enough metablogging, here's what i'm up to today.

I spent a few hours today fixing the last release issues for Jabber. Not everything went as expected since I missed the string freeze but at least a few things were ironed out. Looking forward to this Kopete release, I hope it will give us better publicity than the last releases which made us *crash* mostly *crash* known for *crash* *crash* instability.

I didn't think that I'm going to write a blog describing OLS, but I wanted to point out a few things: