<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">For 2.9 i would like to add:<br>
- LayerGroups for PSD files (save/load). This is the most
important thing. This will be better integration between
PS/Painter/SAI and Krita.<br>
- Possibility to draw on FileLayer and save it. This will be
integration between Blender and Krita. In this way we can exchange
layers between the apps. <br>
<br>
These are the most important features. <br>
And ofcourse "Line quality" as already Boud mentioned. We need the
same lines quality as PS/Gimp have. To get our brushes scalable.<br>
<br>
Thanks.<br>
<br>
<br>
<br>
21.02.2014 21:02, Sven Langkamp пишет:<br>
</div>
<blockquote
cite="mid:CAAmsBfkOeGavp1juFz0p1VMZb9F0_Arq=FGL3QoasALMASbsdA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Feb 19, 2014 at 11:04 AM,
Boudewijn Rempt <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:boud@valdyas.org"
target="_blank">boud@valdyas.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Krita
Roadmap<br>
-------------<br>
<br>
2.8 will be awesome, but after 2.8 comes 2.9...<br>
<br>
During the 2.8 beta phase, we've been lucky to have had a
lot of input on areas where Krita should be better. The
main areas are:<br>
<br>
* MDI interface (more than one document loaded in one
window)<br>
</blockquote>
<div><br>
</div>
<div>I would give this the top priority, because it's the
single feature that has be merged before we go to 3.0 and
will likely also need a lot of work. </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
* Mask handling: creating and converting masks is not as
easy as it should be.<br>
<br>
* Selection handling: modifying selections is really
inconvenient at the moment<br>
<br>
* Line quality: we should try and figure out how better
anti-alias especially thin lines. This wasn't a problem
before because our display quality wasn't very good, but
since that's excellent now, it is a problem<br>
<br>
* Performance of the color correction system: the final
conversion step for display is now holding us back. We
might be able to move that to the GPU as well, for the
OpenGL canvas<br>
</blockquote>
<div><br>
</div>
<div>Have you measured the impact of that? I have seen many
comments about bad performance recently. Users expect fast
painting with the biggest brush on a 10k x 10k image.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
* Text and vector tools. We share these with Calligra. The
current system is a hybrid of ODT, ODG and SVG. Creating
and manipulating text is difficult, the difference between
the two text tools is hard to explain, and finally, the
results aren't good and we cannot save all features the
gui offers.<br>
</blockquote>
<div><br>
</div>
<div>That's a very tricky problem. I know that the current
system has a lot of shortcoming, but there is currently no
good alternative for it. We have to keep backwards
compatibility, so we can't throw it out. The problem with
the text are more related to bugs in the text tools rather
than the fileformat (the shadow problem is too). Even if
we throw it out, it would take months to replace the text
tools alone and years if you want to reach the
capabilities of other applications.</div>
<div><br>
</div>
<div>In any case the text shapes and text tools would have
to be replace, if you want to store as SVG we would likely
need massive changes in Flake too. We have seriously
question is that is really a justified change, considering
how much effort would have to be dumped into it.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
* The dirty brush proposal and related preset handling
issues<br>
<br>
This is obviously already more than we can handle in one
release period, so we need to prioritize. Also, I might
have forgotten a topic that is more important than any of
these!<br>
<br>
Then there is the roadmap towards 3.0. 3.0 should be our
Qt5 release, which means no refactoring, just porting. For
that to be as smooth as possible, at least the MDI
refactoring should have landed, and any other big
refactorings that influence which dependencies we have.<br>
<br>
</blockquote>
<div><br>
</div>
<div>I would add:</div>
<div><br>
</div>
<div>*Unified shortcut confguration: Currently many users
are confused that the shortcuts for the actions and the
input manager shortcuts are split over two locations.
These should be combined into a single UI. The same
unification should be done for the done for saving
shortcuts so everything is saved to shortcut profiles
(which should be a resource). </div>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Krita mailing list
<a class="moz-txt-link-abbreviated" href="mailto:kimageshop@kde.org">kimageshop@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/kimageshop">https://mail.kde.org/mailman/listinfo/kimageshop</a>
</pre>
</blockquote>
<br>
</body>
</html>