This weekend have so far resulted in 5 commits on Krita. In particular on the scaling stuff. Krita has for way too long had some outstanding quality issues with scaling. The edge pixels were transparent and the images themselves were too blurry.

Just see this page from over 2 years ago: http://gis-blog.leonde.de/index.php/2006/11/10/scaling-algorithms-in-krita/

Well this weekend was the day to end the misery. I started with implementing bicubic filtering which removed the blur, and went on to fix the transparent edges. The main part of the bug was actually a simplerounding error, but looking into the issue i also found that the filter weights were being applied wrongly, so I fixed that too.

But that was not all. The code for mixing of colors couldn't handle negative weights which gave some weird colors popping up weird places in the images. After some debugging all it took to fix it was clamping the resulting rgb values to not be negative.

After that I fixed some regressions regarding progress feedback while scaling, and right now I've bugged Sven Langkamp to help me with the selection stuff in the transform tool. Funny thing is I was his mentor on a GSoC about selections two years ago and now he is the one who helps me

Anyway here are the results so judge for yourself (I've used the same original as in the blog I referred to above and bicubic filters in all cases).

Photoshop 7:

Gimp 2.6.1:

Krita (trunk):

I'm quite pleased as it looks very similar to photoshop.

[image:3453 size=original nolink=1 node=3453]

I've worked a bit on the scale dialog for Krita. Neither the old one from the 1.x series nor the new one in current KOffice2 alpha releases were good enough. I've mailed a bit with Ellen which only confirmed that it is indeed a difficult dialog to get right.

In the end I reordered some items, so I hope it's a bit easier to figure out how to use it. I think it has become quite good, but judge for yourself. So much cool stuff coming in KOffice 2.0

Kross, the scripting framework, is one of the pillars new with KDE4. While the project started already a while back in 2004 it enveloped over the time to a rather big codebase. During the KDE4-process one of the main-goals was to decrease the codebase what can be even more difficult then writting new code.