Jump to content

Krita/ActionPlan2

From KDE Community Wiki
< Krita
Revision as of 17:33, 7 July 2010 by Halla (talk | contribs) (Created page with '27 akademy: 1 day: writing down issues with abr (we postpone implementation) Windows! 28: check and fix performance with big scaled-down predefined brushes like deevad's 29: cust...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

27 akademy: 1 day: writing down issues with abr (we postpone implementation) Windows! 28: check and fix performance with big scaled-down predefined brushes like deevad's 29: custom brush creation 30: PaintOps that copy pixels are not aware of pixel transparency http://bugs.kde.org/show_bug.cgi?id=217124 21: 1w Refactor brush selection widget so that particle type can be selected with current GUI 32, 33: session management for tools, colors, etc. 34, 35: release readiness


June

  • Week 24: ABR Brush support, we have unfinished business here.

Steps:

    • 1. create separate paintop that mimics Photoshop and the parsed dynamic values
    • 2. implement abr loading of the dynamics into paintop
    • 3. possibly merge with autobrush


  • Week 25 ABR Brush suppert+ (one week is not enough), VBR brush support

(it seems easy, text file with GIMP settings just to match our Autobrush)

  • Week 26 Create workflow for quick creation of brushes from the image

in canvas (here are the specs http://docs.gimp.org/en/gimp-using-variable-size-brush-creating.html) + enki said it looks really good + maybe just need to fix the Custom brush dialog

July

  • Week 27 Refactor brush selection widget so that particle type can be

selected with current GUI

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)

August

  • Week 31 Week of filter's performance, cache the calls of

transformation https://bugs.kde.org/show_bug.cgi?id=233004, profile filters and try to optimize some of them so that they are usable for painting

  • Week 32: Spent one week to setup Windows development for Krita, document it on wiki extensively so that it is easy for other hackers, and fix compilation errors for Windows
  • Week 33, 34, 35: release readiness: A Bug A Day Keeps the Doctor Away (or

something like that -- we'd need to carefully preselect the bugs if we want to do that! Many bugs will take more than a day.)

Related links

Discussion points

Boud

  • gradient improvement might be a nice task for one week
  • dockers from enki mail?
  • asking Peter to help with the design, since I'm totally uncertain what would be best here (week 30)
  • not sure about the importance of this item (week 26)
Retrieved from "https://community.kde.org/index.php?title=Krita/ActionPlan2&oldid=3895"