GSoC/2019/StatusReports/hellozee: Difference between revisions

From KDE Community Wiki
< GSoC‎ | 2019‎ | StatusReports
(Upated the status report for 2nd June)
Line 1: Line 1:
== Porting Magnetic Lasso to Krita ==
== Porting Magnetic Lasso to Krita ==


The Magnetic Lasso was lost during the port from Qt3 to Qt4, this project tries to continue the working to port the tool to the current version of Krita
=== Summary ===
* '''Project Name:''' Porting Magnetic Lasso to Krita
* '''Proposal:''' [https://docs.google.com/document/d/1AF1U1Qb8JKS6Ky8pC_daDgeMDBrzVU8C7ulK_-0kg28/edit?usp=sharing View Proposal]
* '''Abstract:''' The Magnetic Lasso was lost during the port from Qt3 to Qt4, this project tries to continue the working to port the tool to the current version of Krita


== Work report ==
=== Project Goals ===
* Add the Magnetic Lasso Selection Tool in Krita.
* The tool when used should stick to the edges found in the picture.
* Starts after user left clicks and makes an anchor, edges are scanned from the anchor point.
* After the mouse moves a fixed amount of distance the tool automatically places another anchor point and uses it as a reference.
* The user can also manually set an anchor point, him/herself.
* The search radius which is used to determine, upto what area the tool would search for an edge as well as the frequency of anchors can be adjusted by the user.
* The above-mentioned parameters as well as the threshold for determining edges can be adjusted using the tool options widget.


== Links to Blogs and other writing ==


http://hellozee.github.io/posts/summer-is-coming/
=== Project related links ===
* [https://phabricator.kde.org/T10894 Phabricator Task]
* [http://hellozee.github.io/tags/gsoc/ Personal Blog]


http://hellozee.github.io/posts/boost_astar/
 
== Implementations Status ==
Status report on each goal implementation.
 
=== KisMagneticWorker ===
'''Goal:''' Implement the worker for the algorithm and the corresponding unit test.
 
'''Current Status''' Working on wrapping the KisPaintDevice to boost::graph for using boost::astar_search
 
'''TODO''' Generate proper test cases, for the testing the worker
 
==== Related blog posts ====
* [http://hellozee.github.io/posts/summer-is-coming/ Initial Post]
* [http://hellozee.github.io/posts/boost_astar/ Understanding boost::astar_search]
 
==== Commits and Differentials ====
 
* [https://invent.kde.org/kde/krita/commit/afcb9243c0a249b427780c1d17537a8f8fcf4d0c Adding an initial framework for the test]
* [https://invent.kde.org/kde/krita/commit/d4b3b07f4dcdbaa3ee33281582c52b7578a92405 Applying Laplacian of Gaussian on KisPaintDevice]
* [https://invent.kde.org/kde/krita/commit/3b86ab524e6934766503bdc883f6fb14346c6a7b Added the heuristic function for the boost::astar_search]

Revision as of 05:36, 2 June 2019

Porting Magnetic Lasso to Krita

Summary

  • Project Name: Porting Magnetic Lasso to Krita
  • Proposal: View Proposal
  • Abstract: The Magnetic Lasso was lost during the port from Qt3 to Qt4, this project tries to continue the working to port the tool to the current version of Krita

Project Goals

  • Add the Magnetic Lasso Selection Tool in Krita.
  • The tool when used should stick to the edges found in the picture.
  • Starts after user left clicks and makes an anchor, edges are scanned from the anchor point.
  • After the mouse moves a fixed amount of distance the tool automatically places another anchor point and uses it as a reference.
  • The user can also manually set an anchor point, him/herself.
  • The search radius which is used to determine, upto what area the tool would search for an edge as well as the frequency of anchors can be adjusted by the user.
  • The above-mentioned parameters as well as the threshold for determining edges can be adjusted using the tool options widget.


Project related links


Implementations Status

Status report on each goal implementation.

KisMagneticWorker

Goal: Implement the worker for the algorithm and the corresponding unit test.

Current Status Working on wrapping the KisPaintDevice to boost::graph for using boost::astar_search

TODO Generate proper test cases, for the testing the worker

Related blog posts

Commits and Differentials