<!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 Wednesday 16 September 2009, enki wrote:<br>
> Boudewijn Rempt wrote:<br>
> > There are some very interesting things about mypaints brush engine. One<br>
> > of them is that MyPaint used to be really stroke based, i.e., it would<br>
> > store strokes, and strokes were intended to be editable at a later stage.<br>
> > It's still possible to change the brush parameters and see the last<br>
> > stroke change accordingly. I have got a version of the mypaint brush<br>
> > engine integrated in a krita paintop, but never got it finished enough to<br>
> > allow painting. The other thing about mypaints brush engine is that it<br>
> > works in 15 bit pre-multiplied rgb.<br>
><br>
> What makes MyPaint powerful is that all brush options are combined in<br>
> one paintops. So for example, you can create a smudge + airbrush +<br>
> jittering+ pixel pencil preset.<br>
> Most of mypaint's features are available<br>
> in Krita, but scattered between different paintops. I think that Brush<br>
> options should be shared more between paintops. Sensors are a step in<br>
> the good direction, but more paintops need to use them.<br>
That's the goal :)<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>The "smudge + airbrush" was the idea behind the color source of the "dynamic brush", the color source is not available in 2.1, but I hope to make it back in 2.2 (at least for the brush op).<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>> >> Keyboard shortcuts is something I miss in Krita a lot. I consider it a<br>
> >> big bug when I can't configure shortcuts for Tool Docker. I investigated<br>
> >> the issue a little, but not much...<br>
> ><br>
> > Yeah, that's one of those things that broke during our integration with<br>
> > KOffice. It worked quite well in 1.6, but is broken right now. And<br>
> > investigating the fix takes so much time.<br>
><br>
> Here shortcut seems to works well, but the tools I need are not in the<br>
> list.<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>Yes that's a problem, we can't associate Q/KAction to tools since then that means you can't type a text in a text shape (if you have single letters associated to tool). So we would need a way to insert the tools in the shortcuts editor (this probably needs change in KShortcutsDialog).<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>