Action plan 2

enki enkithan at free.fr
Sun May 16 21:23:20 CEST 2010


On 15/05/2010 22:22, LukasT.dev at gmail.com wrote:
> Hello,
>
> I'm proposing new plan [1] after we are almost done with old Action plan.
> Adam is taking the color stuff in GSoC and the session management is not done,
> but I moved it to Action plan 2. The MMX/SSE/SSE2 thing in pigment might be
> probably done by some student as university project - see [2].
>
> We have Dmitry in GSoC so he can overtake canvas stuff (mirroring, rotation) I
> have a history of fails there :/. Russia for the win! Or Cyrille said it is on
> his TODO, so maybe France for the win.
>
> Feel free to discuss the weeks. The aim is Blender people + Comic book use
> case. What do you think is important and is missing?
>
> [1]http://wiki.koffice.org/index.php?title=Krita/ActionPlan2
> [2]http://lukast.mediablog.sk/log/?p=222&cpage=1#comment-2523
> _______________________________________________
> kimageshop mailing list
> kimageshop at kde.org
> https://mail.kde.org/mailman/listinfo/kimageshop
>
>
>    

"Week 28 https://bugs.kde.org/show_bug.cgi?id=135899 a.k.a session 
management. Save the state of the brush engines into kra. Some 
elaboration on related settings will be done (e.g. tools should be saved 
too, e.g. opacity and composition mode of freehand tool) "

I'd prefer having the setting saved per user, instead of in the .kra 
file. While it can be an advantage sometimes, saving in the .kra can be 
a problem when exchanging files with someone else (ex: set the opacity 
to 0, and send the .kra to your friends :p).

"Week 29 http://forum.kde.org/viewtopic.php?p=154926#p154926 Improve 
presets handling"

I think saving of opacity and mode in presets should be optional. 
Otherwise, it will cause problem when the user wants to use several 
presets with the same composite mode (for example, erasing). Each time a 
preset would be loaded, the composite mode would have to be switched again.
Another solution could be to make tool presets, but that seems to be a 
lot of work.


Maybe the Action Plan is too focused on paintops. I think other primary 
features should be polished too, especially if Krita is used for 
texturing or matte painting :

I.layer stack :
     1.improve drag&drop (if the "dragged" layer can't be made a child 
of the hoovered layer, then drop it between the current layer and the 
previous/next one).
     2- conversion between layer, mask and selection :
         -global selection <--> alpha mask.
         -layer transparency --> global selection (Idealy, ctrl+click on 
the layer preview would trigger it).
         -applying/dropping a mask to its parent.
         and optionnally:
         -shape layer <--> vector selection --> raster selection and mask.
         -shape layer --> raster layer.

II.mask :
     1-fix inconsistencies in masks by switching to a 
mask=selection=greyscale image paradigm. Then, masks and local 
selections would be the same thing, the user would just change the view 
mode by clicking a button. It'll make the workflow simpler, and allow 
powerful features:
         - gradient, paint tool and filters could be used to edit a 
selection (in mask or image mode).
         - painting in a mask would be the same than painting in a paint 
layer.
         - no need to show a selection in filter/generators layers, etc...

III.selection :
     1.allow selection tools to move the selection.

IV.paintops :
     1- bring back the automatic preview, or at least a single dab, like 
in autobrush, so that it's possible to set-up static settings like angle 
and softness. The dab could be reused later for smaller preset preview 
(like in Custom Brushes).
     2- merge pixel, eraser, pencil, mix and soft paintops (Better break 
presets now, than when we'll have millions of users :p)

V. shortcuts:
     1- add a keyboard shorcut (E ?) to switch between the eraser and 
normal mode.
     2- Call the Edit>Clear action when the Del. key is pressed.

VI. move tool:
     1-move along an axis with modifiers.




More information about the kimageshop mailing list