Well , i am back after i spend one week working on some projects in my company.
I hope someday maybe somebody will pay me just for doing what i like to do :-)
We can dream, always...
Anyway, first change: moving contact import to gaducommands.cpp again.

So this is my first blog entry. I will try to add something every now and then if it makes sense. Let's see how useful it becomes. I think it has great potentials. Number two on my wishlist would be a wiki on developers.kde.org. Anyone? :)



I finally got the program out and everyone seems to be happy about it. To all that are wondering: "reserved" really means "reserved" on the slots that are marked as such They will be filled until the conference starts.

Geiseri definitely made my day with this site, so I wanted to thank him by fixing kspell. I looked over the logs to see which commits broke it. It was broken twice in revision 1.101 (coolo commit) and then in 1.104 in a commit of Don's patch by Laurent. I fixed it but the code I saw there did not make me happy at all. If Laurent won't want to maintain it, I'll start doing it since it simply begs for a maintainer.

So, a quick primer for people who aren't familiar with me.

I wrote and maintain the dotNET widget style. A lot of people have given me a bunch of different compliments on it, so I've gotten kind of a big head. dotNET is about to be renamed, although I'm not sure as to what it's going to be renamed to - my own preference at this point is heavily leaning towards calling it 'Bytecode' but we'll see if anybody comes up with something more clever or appropriate.

DCOPWidgets are widgets that are accessble via dcop. You can load a UI file that was built in designer and then access it from any lanuage that can talk via dcop.

User Interface File:
The first step is to create a UI file for use with your program in Qt designer. Every widget you wish to access from dcop should have a name so KDE can build the interface for you.

KSplash plugin loading scheme changes, and probably will change again before 3.2. Grid spacing on kdesktop needs to be made flexible. No Perl: Python or Ruby?

Alright, this time less philosophy and more "what I'm doing and thinking about doing, as if you care" ...

I am nearly ready to start working on some major KControl issues, but am stalled on a couple of fronts. Hoping inspiration (and some bits of code i'm waiting on) will arrive soon.

I've got a couple of patches to some smaller KDE apps that were sent to me and then abandoned. I'll have to fix them up some, and just discard others. Not sure what prompts someone to start in on something and then just leave it halfway?

Okay, the members page is in a usable state, but I think im going to have to rewrite the module because it wont use any of the current filters or i18n stuff.

Image galleries are up and running. Each image can be a maximum of 1meg with a max usage of 5megs each user or 50 images. Im in the process of getting apache to also not allow images here to be linked elsewhere. This is to save bandwidth. You can link images in your own posts with no problems. The process to do this is to upload your image, view the image, copy the image location url on the server, and include it in a img tag.

Just testing the site while i hack KJSEmbed.

This is a test blog with image Test