<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Tuesday 15 September 2009, Boudewijn Rempt wrote:<br>
> * stability: we have serious stability issues. Going out on a limb, I'd say<br>
> that most are related to integration issues with KOffice libraries, instead<br>
> of problems in our own core code.<br>
What kind of stability ? It would be nice if they are recorded in bugs.kde.org, currently of the crashes, there is only the shiva filter bug that I can reproduce.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> * being part of a suite: not a problem for me, but I keep running into<br>
> people who tell me that they won't use Krita because it is part of KOffice.<br>
> Silly of them, but it means we are losing out on users and potential<br>
> constributors who are way more part of the graphics/art scene than most<br>
> people in the KOffice community.<br>
I am not convinced those people would start use krita even if it was stand alone, they are just using it as an argument. On all major distribution you can install krita seperately from koffice. I think they are just looking for excuses.<br>
If krita was stand alone they would tell you I want a port to "Gtk" (I ofteen see a lot of those coming to Scribus irc channel with such a request). They will always find a reason.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> * fit and finish: we have lots of really cool features, but they all feel a<br>
> bit unfinished (masks), or very unfinished (brush presets, color mixer).<br>
> Which means not many people can really make use of them. When we move to<br>
> git, I would like to have a main tree and a staging tree where all the new<br>
> features land first only to be moved to main when they are really good<br>
> enough.<br>
that's probably how we are going to work with koffice as a whole. Especially if we move to a feature release every three monthes cycle ;)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Cyrille Berger</p></body></html>