<div dir="ltr">HI, all!<div><br></div><div>> <span style="color:rgb(0,0,0)">Finally, it's probably also worth having a very broad idea of what the </span><b style="color:rgb(0,0,0)">long-term plan</b><span style="color:rgb(0,0,0)"> for Krita is.</span></div><div><span style="color:rgb(0,0,0)"><br></span></div><div><span style="color:rgb(0,0,0)">I would like to propose a long-term goal like that: "better support of mobile devices". I'm not sure about the details, but it might be a good idea to allow let people using Krita for professional work at workstations to use the same app for sketching on their tablet and/or touch/stylus-based laptop.</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 9, 2023 at 12:12 AM Emmet O'Neill <<a href="mailto:emmetoneill.pdx@gmail.com">emmetoneill.pdx@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Oh, and, another thing I've been thinking about for a while is the idea of a "<b>workflow project</b>", where we hone in on one simple use case like "comics", "character design", etc. <br></div><div>From there we can come up with a list of concrete problems and potential improvements related to that use case, and we plan projects based on that.</div><div>I think this could motivate us in the short term to work together on more closely related projects and focus future updates on things that we know will make a big impact for certain kinds of artists. </div><div>(As in, Krita 5.X is mostly geared towards <i>comics</i>, then Krita 5.Y is focused on <i>painting</i> improvements, then animation, and so on.) <br></div><div><br></div><div>Finally, it's probably also worth having a very broad idea of what the <b>long-term plan</b> for Krita is.</div><div>So for example if we want to have a major UI overhaul that defines Krita 6 (or something like that), we can come up with guidelines now that we can gradually put into place over time.</div><div><br></div><div>Hopefully I haven't suggested these things before, I'm still feeling a bit sick and drowsy. lol<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 8, 2023 at 2:47 PM Emmet O'Neill <<a href="mailto:emmetoneill.pdx@gmail.com" target="_blank">emmetoneill.pdx@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Oh yeah, good thinking. Let's set up a meeting in the coming weeks.<br></div><div>Honestly, I totally forgot about this document. But judging by how much of this stuff we made good progress on, making it was probably a good move. :)</div><div><br></div><div>Here are a few quick notes wrt the stuff that I know most about:<br></div><div><br></div><div>For <b>animation</b>, I think that the most important remaining items on that list are:</div><div><ul><li>Reference frames (though this might require some changes to rendering overlays/onion skins, iirc)<br></li><li>Audio waveform view (no clue how how work is involved in this one frankly)<br></li><li>Animation clips (I don't think this would be too much technical work, but this would require us to design a nice ux/workflow)</li></ul><div>The rest of the points are in the nice-to-have category, but probably not worth prioritizing.</div><div><br></div><div>And when it comes to <b>storyboarding</b>, I think the main limitation of Krita as a boarding tool is that each scene is confined to the same canvas size.</div><div>This means that it's hard to express common shots where "camera" movement (panning/trucking/etc) is involved.</div><div>(I'm not sure if that explanation is clear, but I have some storyboard books here that I could share as examples.) <br></div><div><br></div><div>I think supporting variable scene canvas sizes would be a big job and probably require changes to the document and image.</div><div>It's probably something that we need if we want to take storyboarding to the next level, but I'm not sure if that's worth prioritizing over other things/workflows.</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 8, 2023 at 2:38 AM Halla Rempt <<a href="mailto:halla@valdyas.org" target="_blank">halla@valdyas.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On woensdag 8 november 2023 11:13:05 CET Halla Rempt wrote:<br>
<br>
> ==== Clipping Masks (nobody) ====<br>
> <br>
> No action, though Wolthera has an open MR with support for PSD text, shapes and guides.<br>
<br>
There's also <a href="https://invent.kde.org/graphics/krita/-/merge_requests/1813" rel="noreferrer" target="_blank">https://invent.kde.org/graphics/krita/-/merge_requests/1813</a> <br>
<br>
<br>
<br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Dmitry Kazakov</div>