GSoC/2019/StatusReports/hellozee: Difference between revisions
| Line 56: | Line 56: | ||
* [https://hellozee.github.io/topsy_turvy_5th_week/ Topsy-turvy 5th Week] | * [https://hellozee.github.io/topsy_turvy_5th_week/ Topsy-turvy 5th Week] | ||
* [https://hellozee.github.io/it_coming_alive/ It is coming alive] | * [https://hellozee.github.io/it_coming_alive/ It is coming alive] | ||
* [https://www.hellozee.dev/a_few_more_steps/ A few more steps] | |||
==== Commits and Differentials ==== | ==== Commits and Differentials ==== | ||
| Line 66: | Line 67: | ||
* [https://invent.kde.org/kde/krita/commit/56600569da672c67a332c0f6f03e18131c110841 Anchor points are saved now] | * [https://invent.kde.org/kde/krita/commit/56600569da672c67a332c0f6f03e18131c110841 Anchor points are saved now] | ||
* [https://invent.kde.org/kde/krita/commit/da0cf17c6c97d6e75968e2d8125a17987f4372e6 Selection works as expected] | * [https://invent.kde.org/kde/krita/commit/da0cf17c6c97d6e75968e2d8125a17987f4372e6 Selection works as expected] | ||
* [https://invent.kde.org/kde/krita/commit/1615e9129bcd31b21b3bde6d44e3d4d76a1e159e Checkpoints are drawn now, :)] | |||
* [https://invent.kde.org/kde/krita/commit/34386d2f7ea0ca09fad2ca7ca904575769d77025 Implemented dual checkpoint procedure, somewhat like PS] | |||
Revision as of 04:39, 18 July 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.
Implementations Status
Status report on each goal implementation.
KisMagneticWorker
Goal: Implement the worker for the algorithm and the corresponding unit test.
Current Status Done
Related blog posts
- Initial Post
- Understanding boost::astar_search
- Another week with boost
- Done with boost
- Deliverable 1 : [✓]
Commits and Differentials
- Adding an initial framework for the test
- Applying Laplacian of Gaussian on KisPaintDevice
- Added the heuristic function for the boost::astar_search
- Implemented boost::graph interface for KisPaintDevice
- an intesity function to the graph for reading threshold
- Implemented boost::astar_search using the KisMagneticGraph wrapper
- heuristic function takes threshold into account now
- Fixed the intensity function
- Finished the Algorithm
- Added docs and completed the test
KisToolSelectMagnetic
Goal: Implement the frontend required for the tool
Current Status Improving user experience and finishing up the UI
Related blog posts
Commits and Differentials
- Initial take on the UI
- Reduced the number of calls KisPaintDevice::exactBounds() is called
- Creates a bouding rectangle before searching
- LoG now runs on tool activation
- Optimized the algorithm, implemented checkpoints
- Selection can be done with the Magnetic Lasso
- Anchor points are saved now
- Selection works as expected
- Checkpoints are drawn now, :)
- Implemented dual checkpoint procedure, somewhat like PS