<!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 Monday 14 September 2009, Boudewijn Rempt wrote:<br>
> This is a follow-up on an irc discussion we had last week on where we want<br>
> to go with Krita.<br>
><br>
> The situation is this: right now, MyPaint is a better ArtRage replacement<br>
> than Krita and Gimp is quite quickly becoming a better Photoshop<br>
> replacement than Krita.<br>
><br>
> MyPaint is fast, uses 16 bits/channel, supports ora, has a nice brush<br>
> engine (although it's not too hard to make a paintop for krita that uses<br>
> MyPaint's brush lib, it's definitely going to be _slow_). There are a<br>
> couple of issues with its user interface, especially for tablet users since<br>
> it relies on keyboard shortcuts a lot, but nothing really problematical. I<br>
> actually use MyPaint myself more often than Krita nowadays!<br>
><br>
> Gimp now has layer groups, is integrating gegl, going to get a<br>
> single-window interface in the next release and with all the work being<br>
> done by Peter Sikking, the user interface is getting really polished. There<br>
> are even people working much better brush dynamics for Gimp.<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>To be honest, my model application has always be my first love (well my second one, but deluxe paint [1] isn't exactly a model for a modern app ;) ) jasc's paintshop (never used it since it was bought by Corel). And especially it's hability to mix vectors with pixels, and now we have that !<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>> So -- what is the story about Krita? What can make Krita compelling to the<br>
> artist? I think it makes sense to individually identify why we are<br>
> personally working on Krita and what we want to get out of it in the first<br>
> place, and to use that to develop a vision for Krita that we can work<br>
> towards.<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>Like Dmitry, I started with Krita because I didn't like Gimp UI, and I don't know (nor like) how to write code in C... And I keep going on now, because I want to have fun with images, and with algorithms around images :)<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>> It also makes sense to identify the really big problems in Krita, both in<br>
> relation to that vision (so that will have to wait) and problems we know<br>
> about right now, like:<br>
What kind of problems ? Bugs or features that don't fill the vision ?<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>[1] http://en.wikipedia.org/wiki/Deluxe_Paint<br>
-- <br>
Cyrille Berger</p></body></html>