Jump to content

Krita/GSoC2010: Difference between revisions

From KDE Community Wiki
Halla (talk | contribs)
Created page with '= Pentalis = TODO to the midterm * <del>Fixing the current glitch with duplicated hatching</del> * <del>Pressure sensitivity to make lines thicker </del> * <del>Adding a mode wit...'
 
Pentalis (talk | contribs)
Line 13: Line 13:
* <del>Clean all the code: 4 space indentation, use self-explaining long names</del>, <del>change class names to the definite ones</del>, <del>eliminate all chalk brush residuals</del>.
* <del>Clean all the code: 4 space indentation, use self-explaining long names</del>, <del>change class names to the definite ones</del>, <del>eliminate all chalk brush residuals</del>.
* <del>Link GUI. Only a window left.</del>
* <del>Link GUI. Only a window left.</del>
* Implement the functions described by the GUI, from easiest to hardest or from most important to least important.
* <del>Implement the functions described by the GUI, from easiest to hardest or from most important to least important.</del>
* (<del>Most important: Scratch off algorithm</del> not so important, the algorithm would slow down both development and the user's computer by a huge amount, this may not be implemented; <del>stylus setting sensitivity</del> Implemented; <del>Hard: interval based settings</del> <del>this was obsoleted by a discussion in IRC</del> I'm reconsidering this, contrary to what others may think, the need for a DISCRETE list of settings controlled by the GUI is real and not perceived, the tool can only reach its full potential in that way).
* (<del>Most important: Scratch off algorithm</del> not so important, the algorithm would slow down both development and the user's computer by a huge amount, this may not be implemented; <del>stylus setting sensitivity</del> Implemented; <del>Hard: interval based settings</del> <del>this was obsoleted by a discussion in IRC</del> I'm reconsidering this, contrary to what others may think, the need for a DISCRETE list of settings controlled by the GUI is real and not perceived, the tool can only reach its full potential in that way).



Revision as of 15:41, 12 July 2010

Pentalis

TODO to the midterm

  • Fixing the current glitch with duplicated hatching
  • Pressure sensitivity to make lines thicker
  • Adding a mode without sub-pixel precision
  • Making an intuitive GUI to let
  • Pressure sensitivity to make more lines
  • Ability to make crosshatching
  • Enabling pressure sensitivity to create crosshatching

Roadmap:

  • Finish the GUI containing all the widgets for a finished brush. Finished rc1, Evaluating design. Finish the GUI containing all widgets for a final release; crosshatching will have a prototype simplified interface.
  • Clean all the code: 4 space indentation, use self-explaining long names, change class names to the definite ones, eliminate all chalk brush residuals.
  • Link GUI. Only a window left.
  • Implement the functions described by the GUI, from easiest to hardest or from most important to least important.
  • (Most important: Scratch off algorithm not so important, the algorithm would slow down both development and the user's computer by a huge amount, this may not be implemented; stylus setting sensitivity Implemented; Hard: interval based settings this was obsoleted by a discussion in IRC I'm reconsidering this, contrary to what others may think, the need for a DISCRETE list of settings controlled by the GUI is real and not perceived, the tool can only reach its full potential in that way).


Currently doing:

  • Considering how to approach impasto.
  • Finishing the hatching brush. Fixing small remaining bugs.
  • Intoxicating with yoghurt
  • Heading to sleep after a long day of doing interesting things and learning, see today's commit 00:02, 27 June 2010 (PDT)
  • Linking the last bits of GUI 11:39, 21 June 2010 (PDT)
  • Linking the GUI 05:19, 18 June 2010 (PDT)
  • Learning how to link new GUI widgets to the general config widget: the basic curve dialog and the BrushTip dialog. 07:08, 17 June 2010 (PDT)