I wonder if pushing forward with animation features might benefit krita development in the same way it does for blender in the future.

--- edit ---

issue fixed in Krita 3 pre-alpha

--- edit ---

issue fixed in Krita 3 pre-alpha

--- edit ---

issue fixed in Krita 3 pre-alpha

i'm hoping there will be funding for layer ui improvements (maybe as a stretch goal) for scott.

the layer ui, and the fact that you can't automove a selection, are workflow issues at the moment.

nharmony wrote:i'm hoping there will be funding for layer ui improvements (maybe as a stretch goal) for scott.

the layer ui, and the fact that you can't automove a selection, are workflow issues at the moment.

Could you make a proper wishbug for this one? We can use that to determine how much needs to be done and how many hours that'll cost.

The selection thing is already a wishbug
https://bugs.kde.org/show_bug.cgi?id=322683

Bouds temp solution isn't great, it requires switching tools. I hate to mention Photoshop because I know his brain will explode, but hopefully you know what I mean. A selection is drawn, and you can just hover over it, and it will change to a "move selection" type cursor. There shouldn't have to be any switching of tools.


The layer thing would be in reference to this thread

viewtopic.php?f=288&t=123326

which scott, yourself and boud have already participated in. Scott said in thread that he hasn't actually looked at the code to determine how easy it would be, but I think boud has some idea. I can try to break it down, by this weekend, and put it in a wishbug. I believe UI stuff shouldn't be left too late, even if its a "boring" Kickstarter option.

Hey guys, these are things involving layers and layer usability that I hope to see. They are things that slow my workflow down (paint/illustration) I wonder if one (or all) of these could be potential stretch goals, or goals in general. I was gunna wishbug, but really its like a united layer project, and some of these things already exist in the tracker.

LAYER UI (Scott Petrovic?) (4)

I won't go into too much detail, just want to layout the tasks. I can current think of (4) for the layer UI

• Layer visibility toggle separation. It has been discussed, that layer visibility is probably used the most, and should infact be separated from everything else within its own column. This will make it easier for toggle and drag functionality to be used later.
• Colour coding layers, an artist can use this in a variety of ways.
• Possibly move icons "lock, alpha lock, inherit alpha" away from the stack, and just place them in the layer docker header. Current Ui creates unnecessary clutter.
• toggle and drag functionality (this probably won't be limited to layers and will probably end up throughout Krita eventually?)



Layer Usability (Oskar Świerad?) (4)

Multiple selections

• The ability to select multiple layers, right click and add them to new groups, or use shortcut to achieve the same thing.
• The ability to select multiple layers/groups and apply a transform to all layers at once, rather than having to flatten an image to do so. It's also pretty cumbersome to add multiple layers to a group just to perform a transform, too.
• Same can be said for inherit alpha, seems strange to have to add everything to a group before this function actually works. The user has no way of knowing this has to be done. Perhaps it should just be greyed out unless it is in a group.
• Hover over layer, and press delete key to delete layer.


Other (2)

• Rotating/Ratio brush shortcuts. The brush edit menu isn't so "accessible" so user is forced to use alternative, like rotate canvas which isn't as efficient in most cases, and performs poorly without open gl.
• The ability to draw a selection, and move that selection without having to switch tools. (I'm talking about actual "marching ants" selection itself, not the content of the selection.

They don't seem like huge tasks to me, but i'm just a silly artist with no coding experience, what do i know? *inhales paint fumes*

Okay -- thanks for the writeup. I sort of need this compared to what we already have listed in bugzilla bugs and wishes, and then a new overview bug added with this info & links to the existing bugs. It's also something that someone who wants to get into Krita can get started on, it's exactly the sort of improvement that makes a huge difference for users and is a good way to get into Krita coding.

no problem, sorry I didn't proof read before I submitted, lots of mistakes.

nharmony wrote:no problem, sorry I didn't proof read before I submitted, lots of mistakes.

It may sound silly, but we get so much feedback a day, that all details start swimming around. Having users help out organising this like you did is a really big help actually. Hence I asked if you could make a wishbug

For anything that I might be assisting on this coming year with Krita, these are my current goals.

1. Write a book about using Krita (this takes a while)
2. Analyze and potentially update a few areas on the user interface that are heavily used.
a. New dialog -- Needs to be simplified and use more "progressive disclosure" (have some mockups on my computer right now)
b. brush editor -- need to think about updating design to condense and have a better user flow
c. layers docker -- make updates based off of forum suggestions. The current direction is pretty good.
d. assistants -- have a better user experience and direction for using assistants. Managing assistants is a little clunky now.

I don't know how many of those things I am going to get to (hopefully at least one!). For 3.0 and shortly after, I will probably be trying to finish the book - so I will not be having many commits at all. After that is finished, I will probably start dipping my toes back into design and development. Note that I am just focusing on UI and work flow -- nothing really "new". I will be getting as much feedback as I can along the way with everything.

@therahedwig no problem. That's completely understandable.

@scott, forgive me, the names where only suggestions, and mainly to do with the subject of cost investigation, which relates to number 2 on your list, about "analyzing" the issues. I should be clear, though, that I don't expect them to even make the stretch goals. I won't be shaking my fists at the monitor if I don't see them there. Obviously, as a user, i'd rather it be left to someone who could do it faster, but I have to respect the idea of giving everyone a chance to contribute (GSOC etc.)

Anyway, i've said my piece, trying to keep forum posts to a limit. I'll continue to report bugs I should share some art next week, gotta prove that I do actually use the software, lol.

Goodluck guys!