<div class="gmail_quote">On Thu, Sep 24, 2009 at 9:57 AM, Boudewijn Rempt <span dir="ltr"><<a href="mailto:boud@valdyas.org">boud@valdyas.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Looks like the discussion has run its course, so I want to make a shortish<br>
summary, juxtaposing the things mentioned. There were a couple of interesting<br>
things noted! But that doesn't mean we've found our direction.<br>
<br>
There are quite a number of contradictions:<br>
<br>
flexible, comprehensive app <---------> polish and usability<br>
platform for experimentation <---------> stable application for users<br></blockquote><div><br>Can be solved by experimental and stable branches. Instead of makeing experiments in trunk, you would have a seperate testing ground which allows to merge new experiments earlier. Ideally we could keep the stable branch in releaseable state most of the time.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
creating images <---------> manipulating images </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
integrated in koffice <---------> attractive to artists<br>
corel painter <---------> photoshop<br>
competing with gimp <---------> competing with mypaint<br></blockquote><div><br>I think Krita is somewhere in the middle. There was an very interesting video posted by the Durian project:<br><a href="http://durian.blender.org/news/tutorial-painting-time-lapse-by-david-revoy/">http://durian.blender.org/news/tutorial-painting-time-lapse-by-david-revoy/</a><br>
<br>It's not only amazing art, but also very interesting from workflow point of view (for me as non-artist). I especially noticed how often he switches between from MyPaint to Gimp and back. Each time the image needs to be save and opened in the other app. I think switching between different workspaces/modes would be much better. For example we could have different workspaces for painting, image manipulation and vector drawings.<br>
<br>The dockers system we currently is quite flexible and allows lots of customization, but it mixes too much different things in my option. The dockers should adapt to the task I want to do at some point. For example I have very often a situation where I was first editing some shape layer and then switch to a pixel based layer. While editing the shape layer I use the add shape, stroke properties and styles docker, but these are useless when editing pixels. So I tend to close and reopen dockers quite often.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
go all node <---------> continue with the current core<br></blockquote><div><br>I think sooner or later we end up with a node system. It's not "all node" vs current corre, but the current core could be used a base to evolve into a node-based system. As Cyrille said this should be in seperate branch. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Use cases I've seen in the thread:<br>
<br>
* photo manipulation<br>
* HDR workflow (for film or for pictures?<br>
* illustrations and comics<br>
* sketching<br>
* integration with movie workflow, blender<br>
* web development (what is that, actually?)<br>
<br>
Can all these things work in one application?<br></blockquote><div><br>Yes, I think so. Also the last point has other requirements the the rest in terms of fidelity.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Reasons to work on Krita:<br>
<br>
* can do experimentation<br>
* want to create an app I can use<br>
* it's fun to work on<br>
* prefer qt, c++ over gtk, c (I find this a bit disappointing, this can<br>
hardly become a compelling reason for people to use the application)<br>
<br>
Work flows<br>
<br>
And there are differences in the way we work personally that also influence<br>
the characteristics of Krita: Cyrille paints using small brushes, I tend to<br>
use big brushes on big, high-res canvas. That means a very different workflow.<br>
I love enkithan's comic book artist use-case, and I think we need more of<br>
them. (It also makes clear that we need to work on memory consumption and<br>
performance first thing! 1000 dpi A4...)<font color="#888888"><a href="https://mail.kde.org/mailman/listinfo/kimageshop" target="_blank"></a></font></blockquote><div><br>4K (<a href="http://durian.blender.org/news/4k_glimpse/">http://durian.blender.org/news/4k_glimpse/</a>) ;) <br>
</div></div><br>