.. but this scripting thread that keeps going and going on kde-core-devel is pathetic. Bah! Currently I am no longer reading the thread and simply deleting every email with scripting in the subject. He who codes decides and as soon as an application is working properly in any scripting language (therefore the bindings are working fine) it should be shipped inside a module. Period. If it creates an extra dependency then so be it. I assume cmake will be made smart enough to make sure that when the bindings are not there the application will not be built and cmake will not bail out with a "requires these and these bindings" error. If you feel that you have to have the same app in C++ then code it yourself. Again he who codes decides. You need it in C++ and you make it better than the scripting version, fine we ship both versions as long as they are properly maintained. That goes for any software we put inside the modules like it has always been done.

Damn, it has been more than 2 years since I wrote an entry here. I simply have too little time to do anything code-wise for KDE. Last week I subscribed again to some lists to see what is happening in KDE land for 4.0 but I dont have the time to code. I've always had this idea to make a electronic schema/layout editor but if things keep going like they have been going then I'll never get around to it.

Yesterday at work we found some problem with backtrace on linux ia32 when it was being called from a signal handler. So i said lets see if this works on Itanium or if it is a more genereic Linux problem. Guess what, on Linux IA64 there is no signal generated on a divide by zero, the result is 0 and the program terminates normally... WTF ???

Wow, it has been more then 5 months since i posted here... This really requires an update :)

Yes i have implemented it in Kompare and committed it to CVS but unfortunately it is not activated atm. It is not open for discussion before people start begging me about activating it because it is not in the release plan and it is way too late for new features.

... Kompare seems to be in a useful state again atm. I did a lot of hacking on it and moving a lot of code around and i think the code is a bit cleaner now and easier to maintain.

I also fixed some bugs:

• scrolling in the view (it currently still does not work fully yet but i'll keep on improving it).
• navigating with ctrl+up and ctrl+down, it only navigated into half of the differences in a file.

Outstanding bugs i will fix before 3.2 is released:

It's been a while since i posted last but i fixed some merging bugs... I dont know why they happened but i guess it is because i suck. I should not have committed this stuff before properly trying if it was safe to commit.

Things i fixed are like:
* proper handling of the exit status (diff can return 2 (trouble according to the man and info pages) and there are still differences)
* removed some unneccessary files

This week I also fixed some compiler warnings about using deprecated methods.

It has finally happened: i merged the make_it_cool branch for kompare into head.

Now all i have left to do is kill that branch by removing all files in it. I just hope you will enjoy the changes, i know it is still buggy but i'm working on that here. If you find bugs in it just report it to bugs.kde.org and not here, i might miss your bugreports if you post them here.

Hi,

this is my first blog entry and i am using to introduce my self a bit for those who dont now me. My real name is Otto as you can see in the members section and i mainly work on kompare and some other programs if people ask me to look into that.