i'm having a coding frenzy at home at the moment while waiting
for my adsl to be installed. amazing the amount of work you can
get done when irc, mail and even sane tv listings are all unavailable.

The skinny: two people have reported that KStars will not compile for them; both are using Redhat 9 and gcc 3.2.2. The error message is:

lx200classic.cpp:29: structure `eqNum' with uninitialized const members

Last night I did a lot of bug fixes and janitor work on bugs.kde.org and others were also working hard to get some stuff done before the string freeze that hits us as of today. Still we (#kde-pim) realized that we are not quite there, which is why we will most probably release Kontact as version 0.8 with the following features disabled:

It's snuck up on me. It's been growing item by item until it can go unnoticed no longer. Yup, my TODO list has become so long, I can no longer ignore it. So, I thought i'd write it down. I imagine that I haven't gotten everything I need to do on here, but here's some of it.

Today news sites repeated the monthly Microsoft execute says "Linux is insecure" articles. And while they are comparing apples with oranges (as Linux distributions ship with far more servers and network services than Microsoft offers), it's hard to deny the fact that Linux is also insecure. Essential and security critical packages like OpenSSH, LSH and OpenSSL had exploits in the last weeks and this should have convinced the last conservatives that it is not possible to write a complex server in C without having a remote exploit per year. All these exploits were caused by manual memory management that is relatively hard to avoid in C. But that's not even the point that I want to make, you can also have security problems in other languages. What free software (and also the proprietary competition mostly) lacks is a way to make securing your computer easy.

So, I've been rather quiet on the KDE front lately. I've been busy, though. As much as it might shock and dismay a lot of you, I've been playing around with GNOME. I've even immersed myself in it, seeing exactly how their desktop works and taking notes of things that I like and don't like. The main reason for this is that I was reading through a thread on the Nautilus mailing list entitled "We're going all spatial."

Time to redo the digest. I'm getting bored with what is produced, and frustrated with the limitations of static pages. Most complaints I receive are from developers whose work isn't highlighted.

So, my goals are:

I know, that I should study geography / history these days (and will, too), but instead of doing that I am _again_ working on kmameleon... This week there has been some drastic changes in the (core) of the kmameleon proggy, so basically this is what is new:

I have been thinking about how to store the data in Kalzium (chemistryapp in kdeedu). Currently I have a class called kalzium in which 110 "elements" are. An "element" is of course an object which stores the data available for one of the 110 elements in the periodic table.

I give a pointer of the kalzium-object to every object I create, and which needs the data. For KDE 3.3/4 I would like to restructure a lot in Kalzium. So my question is: what is the best way to store my data. Of course the data doesn't change. The user can't add any data. So I could use a global

I haven't written much about KJSEmbed for the last couple of weeks because I've been concentrating on squashing bugs in kasbar, but over the last couple of days I've had a chance to work on some kjsembed stuff that has been becoming more and more important.