Google Summer of Code - Revision history

Joneuhauser: Replaced content with "Category:Developer Documentation {{Template:MovedToOtherSite|topic=Google Summer of Code|new_url=https://gitlab.com/inkscape/inkscape/-/blob/master/doc/gsoc/summerofco..."

2025-02-13T12:06:34Z

Replaced content with "Category:Developer Documentation {{Template:MovedToOtherSite|topic=Google Summer of Code|new_url=https://gitlab.com/inkscape/inkscape/-/blob/master/doc/gsoc/summerofco..."

Show changes

Mc: add links to repo

2025-02-05T13:14:43Z

add links to repo

← Older revision		Revision as of 13:14, 5 February 2025
Line 19:		Line 19:

	* Inkscape-specific information:		* Inkscape-specific information:
	** ~~[[SOC~~ Application ~~Template]]~~.		**Application template: https://gitlab.com/inkscape/inkscape/-/blob/master/doc/gsoc/application_template.md
			**On-repository information: https://gitlab.com/inkscape/inkscape/-/blob/master/doc/gsoc/summerofcode.md?ref_type=heads
	** [[Roadmap \| Inkscape Roadmap]] - to see our overall objectives.		** [[Roadmap \| Inkscape Roadmap]] - to see our overall objectives.
	** [[Projects \| Inkscape Development Project Ideas]] - broader list of development ideas.		** [[Projects \| Inkscape Development Project Ideas]] - broader list of development ideas.
Line 25:		Line 26:
	** [[SOC Selection Criteria]] - how we rate applications.		** [[SOC Selection Criteria]] - how we rate applications.

	'''Candidate Applications for GSoC ~~2024~~ must be submitted to the GSoC site by 18:00 UTC on April ~~2nd 2024~~.'''		'''Candidate Applications for GSoC 2025 must be submitted to the GSoC site by 18:00 UTC on April 8th 2025.'''

	= The "two patches" rule =		= The "two patches" rule =

PBS: Mark affinity designer importer as completed

2025-01-02T19:08:24Z

Mark affinity designer importer as completed

← Older revision		Revision as of 19:08, 2 January 2025
Line 123:		Line 123:
	* Update the '''Synfig export''' to support the latest Synfig developments		* Update the '''Synfig export''' to support the latest Synfig developments
	* '''Import or export of TikZ'''. There are a few abandoned extensions out there (from which we can borrow), but it's very widely used in science - both import and export could serve an important function in the scientific workflow.		* '''Import or export of TikZ'''. There are a few abandoned extensions out there (from which we can borrow), but it's very widely used in science - both import and export could serve an important function in the scientific workflow.
	*'''Import of the proprietary fileformats''' of ~~Affinity Design,~~ Vectornator, Vectorstyler (~~especially the last two~~ seem in their infancy and users at some point will sit on a bunch of files that they can't open anymore because their SAAS model wasn't profitable) .		*'''Import of the proprietary fileformats''' of Vectornator or Vectorstyler (which seem in their infancy and users at some point will sit on a bunch of files that they can't open anymore because their SAAS model wasn't profitable) .
	*'''Import of CGM''' - old, but ISO standardized. Was supported once and dropped when the uniconvertor extension was removed for 1.0.		*'''Import of CGM''' - old, but ISO standardized. Was supported once and dropped when the uniconvertor extension was removed for 1.0.
	* '''Python based EMF / WMF importer -''' the current (core Inkscape) C extension is unmaintained and Python would probably be the right way to get more collaboration on it. A lot of public archives sit on mountains of EMF files. Note that the Document Foundation recently did a lot of work properly importing those files, so we can learn from them / maybe even join forces...		* '''Python based EMF / WMF importer -''' the current (core Inkscape) C extension is unmaintained and Python would probably be the right way to get more collaboration on it. A lot of public archives sit on mountains of EMF files. Note that the Document Foundation recently did a lot of work properly importing those files, so we can learn from them / maybe even join forces...
Line 269:		Line 269:
	** [https://gitlab.com/inkscape/inkscape/-/merge_requests/6578 Node-based filter editor]		** [https://gitlab.com/inkscape/inkscape/-/merge_requests/6578 Node-based filter editor]
	** [https://gitlab.com/inkscape/inkscape/-/merge_requests/6492 Improving UX of Node tool and Bezier tool]		** [https://gitlab.com/inkscape/inkscape/-/merge_requests/6492 Improving UX of Node tool and Bezier tool]
			** [https://gitlab.com/inkscape/extras/extension-afdesign Affinity Designer importer]

	[[Category:Developer Documentation]]		[[Category:Developer Documentation]]
	</div>		</div>

PBS: Add self to mentors list for "UI-free Inkscape"

2024-12-22T15:30:13Z

Add self to mentors list for "UI-free Inkscape"

← Older revision		Revision as of 15:30, 22 December 2024
Line 62:		Line 62:

	* Estimation of difficulty: Difficult - Long (350h)		* Estimation of difficulty: Difficult - Long (350h)
	* Potential mentors: Marc Jeanmougin		* Potential mentors: Marc Jeanmougin, pbs
	* Programming skills: C++, CMake		* Programming skills: C++, CMake
	* Prerequisites: Minimal knowledge of build systems. Experience with ~~GtkMM~~ helpful.		* Prerequisites: Minimal knowledge of build systems. Experience with GTKmm helpful.

	<u>Detailed Description</u>		<u>Detailed Description</u>

PBS: Add links to Documenting Livarot GSoC

2024-12-22T15:23:06Z

Add links to Documenting Livarot GSoC

← Older revision		Revision as of 15:23, 22 December 2024
Line 93:		Line 93:
	* Prerequisites: Strong math skills, specifically in geometry.		* Prerequisites: Strong math skills, specifically in geometry.
	<u>Detailed Description</u>		<u>Detailed Description</u>
	Inkscape relies on two geometry libraries for path manipulations: lib2geom and livarot. lib2geom is a generic modern library written specifically with Inkscape in mind. lib2geom is missing some functionality that Inkscape requires and that is found in livarot. This project is to move that functionality into lib2geom (or into separate files) using lib2geom path descriptions. A 2020 GSoC student did a significant amount of work understanding and documenting the issues involved. This project would be to build on his work.		Inkscape relies on two geometry libraries for path manipulations: lib2geom and livarot. lib2geom is a generic modern library written specifically with Inkscape in mind. lib2geom is missing some functionality that Inkscape requires and that is found in livarot. This project is to move that functionality into lib2geom (or into separate files) using lib2geom path descriptions. A 2020 GSoC student did a significant amount of work understanding and documenting the issues involved [https://gitlab.com/inkscape/inkscape/-/merge_requests/4416]. This project would be to build on his work.

	Specifically, the functionality needed is		Specifically, the functionality needed is
Line 253:		Line 253:
	** [https://gitlab.com/vanntile/inkscape-gsoc-2020 New dialog system.]		** [https://gitlab.com/vanntile/inkscape-gsoc-2020 New dialog system.]
	** [https://gitlab.com/rathod-sahaab/gsoc-2020-inkscape Command palette dialog.]		** [https://gitlab.com/rathod-sahaab/gsoc-2020-inkscape Command palette dialog.]
	** ~~Path operations~~.		** [https://gitlab.com/inkscape/inkscape/-/merge_requests/4416 Documenting livarot]
	* 2021		* 2021
	** [https://gitlab.com/inkscape/inkscape/-/merge_requests/3420 On canvas marker editing.]		** [https://gitlab.com/inkscape/inkscape/-/merge_requests/3420 On canvas marker editing.]

PBS: Add completed 2024 projects

2024-12-22T15:11:55Z

Add completed 2024 projects

← Older revision		Revision as of 15:11, 22 December 2024
Line 109:		Line 109:
	<u>Detailed Description</u>		<u>Detailed Description</u>
	The ''Paint Server Dialog'' allows a user to visually select a pattern or hatch to use in painting the ''fill'' or ''stroke'' of an object. This project would be to expand the dialog to cover gradients, meshes, and solid colors as well as make other improvements to the dialog. Interaction with the Inkscape's ''UX'' team will be required.		The ''Paint Server Dialog'' allows a user to visually select a pattern or hatch to use in painting the ''fill'' or ''stroke'' of an object. This project would be to expand the dialog to cover gradients, meshes, and solid colors as well as make other improvements to the dialog. Interaction with the Inkscape's ''UX'' team will be required.

	~~== P13. Node-based filter editor ==~~

	*Estimation of difficulty: Hard - Long (350h)
	* Potential mentors: Mc
	* Programming skills: C++
	* Prerequisites: Minimal knowledge of build systems

	<u>Detailed Description:</u> The filter editor is kind of hard to understand and master based on its current UI. Using a node-based tool for it, such as what can be done with https://notabug.org/grindhold/libgtkflow would help people create and master the filter primitives easier.

	[https://gitlab.com/inkscape/ux/-/issues/40 '''Full poposal''']		[https://gitlab.com/inkscape/ux/-/issues/40 '''Full poposal''']
Line 158:		Line 149:
	*[https://en.wikipedia.org/wiki/Cutting_stock_problem Linear nesting] is not too useful in SVG, but might be a good place to get acquainted with the problem. 2D cutting stock problem would be very interesting to have and would work great with the new multipage functionality.		*[https://en.wikipedia.org/wiki/Cutting_stock_problem Linear nesting] is not too useful in SVG, but might be a good place to get acquainted with the problem. 2D cutting stock problem would be very interesting to have and would work great with the new multipage functionality.
	*For efficient packing of free form objects, we might just re-implement [https://github.com/Jack000/SVGnest SVGNest] in Python. There are probably some more recent research papers which would be interesting to implement as a comparison.		*For efficient packing of free form objects, we might just re-implement [https://github.com/Jack000/SVGnest SVGNest] in Python. There are probably some more recent research papers which would be interesting to implement as a comparison.

	~~== P18. Improving UX of Node tool and Bezier tool ==~~
	*Estimation of difficulty: Medium - Hard, Short or Long depending on scope (175h or 350h)
	*Potential mentors: Tav, ??
	* Programming skills: C++,
	*Prerequisites: Computational geometry

	<u>Detailed Description:</u> This project would improve workflow of editing of geometry of paths. Combining strengths of Pen tool and Node tool with modifiers and new behaviors. This improvement should benefit pro users but also beginners. Good example of this implementation is in blenders new pen tool.

	~~'''[https://gitlab.com/inkscape/ux/-/issues/5 Full Proposal here]'''[[File:Imageasdasd.png\|thumb\|184x184px]]~~

	== P19. Improving UI of Live path effects ==		== P19. Improving UI of Live path effects ==
Line 285:		Line 266:
	** [https://gitlab.com/inkscape/inkscape/-/merge_requests/5335 GTK4 toolbar port preparation]		** [https://gitlab.com/inkscape/inkscape/-/merge_requests/5335 GTK4 toolbar port preparation]
	** [https://gitlab.com/inkscape/inkscape/-/merge_requests/5624 Customizable Appearance of Canvas Controls]		** [https://gitlab.com/inkscape/inkscape/-/merge_requests/5624 Customizable Appearance of Canvas Controls]
			* 2024
			** [https://gitlab.com/inkscape/inkscape/-/merge_requests/6578 Node-based filter editor]
			** [https://gitlab.com/inkscape/inkscape/-/merge_requests/6492 Improving UX of Node tool and Bezier tool]

	[[Category:Developer Documentation]]		[[Category:Developer Documentation]]
	</div>		</div>

Joneuhauser at 12:16, 14 June 2024

2024-06-14T12:16:55Z

← Older revision		Revision as of 12:16, 14 June 2024
Line 120:		Line 120:

	[https://gitlab.com/inkscape/ux/-/issues/40 '''Full poposal''']		[https://gitlab.com/inkscape/ux/-/issues/40 '''Full poposal''']
	~~==P14. Cached styles for inkex==~~

	*Estimation of difficulty: Medium - Short (175h)
	*Potential mentors: Jonathan
	* Programming skills: Python, CSS
	* Prerequisites: minimal knowledge of test-driven development

	<u>Detailed Description:</u> When inkex, the Python library behind Inkscape's extension system, computes styles, this is relatively slow, especially for documents with either many style sheets or documents with many elements / highly nested documents. This is because for each element, the XPATH of each CSS rule is computed, and then it is checked whether the current element is in the XPATH result. Then, the same computation is repeated for the parent. Since Python is not very fast itself, such inefficiencies quickly make style evaluation unusable for big documents.

	With this project, we would explore ways to speed up those computations, mainly using caching and more intelligent ways of evaluating CSS rules. Some approaches might be taken from [https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-engine-quantum-css-aka-stylo/ a recent firefox refactoring].

	~~Ideally, the caching will be tuned to support read-only (export), read-heavy (modify path), write-heavy (generate from path) and write-only (import) extensions, which have different caching needs.~~

	~~The work should be done in a test-driven development approach.~~

	== P15. Import and Export extensions ==		== P15. Import and Export extensions ==

Joneuhauser at 12:15, 14 June 2024

2024-06-14T12:15:58Z

← Older revision		Revision as of 12:15, 14 June 2024
Line 71:		Line 71:
	<u>Use cases</u>		<u>Use cases</u>
	* Server installs, scripts		* Server installs, scripts

	~~==P6. Refactoring==~~
	* Estimation of difficulty: Moderate - Short or Long depending on scope (175h or 350h)
	* Potential mentors: Tavmjong Bah
	* Programming skills: C++
	* Prerequisites: proficient C++.

	~~<u>Detailed Description</u>~~
	Inkscape began life as the C program Sodipodi. Sodipodi was mostly the work of one person who had a clear vision of how the code should work. A major motivation of the Inkscape fork was to allow others to easily contribute to development. This resulted in rapid development but at a cost: the code has become much messier and now lacks a clear vision. This project is to work on refactoring the code. Refactoring can take many forms. It could be creating a better directory structure with README's that describe the purpose and function of the code in each directory. This would include rewriting code to reduce dependencies across directories (which would help, for example, in achieving a headless version of Inkscape). It could be the continued transition from C to C++ which often results in major reductions in the number of code lines. Or it could be identifying and eliminating redundant code.

	~~A particularly ambitious project would be to replace the Garbage Collector by smart pointers.~~

	~~Refactoring is an important skill of which many books have been written. Here's a chance to gain valuable experience!~~

	~~See https://wiki.inkscape.org/wiki/index.php/Refactoring_projects for some ideas of projects.~~

	==P8. Add Text and Image Support to Live Path Effect System ==		==P8. Add Text and Image Support to Live Path Effect System ==

Adambelis at 10:10, 17 March 2024

2024-03-17T10:10:44Z

← Older revision		Revision as of 10:10, 17 March 2024
Line 210:		Line 210:
	[https://gitlab.com/inkscape/ux/-/issues/?sort=popularity&state=opened&label_name%5B%5D=Dialog%3A%3ALPE&first_page_size=100 '''Full Proposed designs''']		[https://gitlab.com/inkscape/ux/-/issues/?sort=popularity&state=opened&label_name%5B%5D=Dialog%3A%3ALPE&first_page_size=100 '''Full Proposed designs''']

			[[File:Imageasd.png\|right\|frameless\|466x466px]]
	== P20. Recolor Artwork ==		== P20. Recolor Artwork ==
	* ~~[[File:Imageasd.png\|right\|frameless\|369x369px]]~~Estimation of difficulty: Variable - Short (90h or 175h)		* Estimation of difficulty: Variable - Short (90h or 175h)
	* Potential mentors: Adam Belis ?		* Potential mentors: Adam Belis ?
	* Programming skills: usually C++		* Programming skills: usually C++

Adambelis: /* P20. Recolor Artwork */

2024-03-16T13:08:09Z

P20. Recolor Artwork

← Older revision		Revision as of 13:08, 16 March 2024
Line 212:		Line 212:

	== P20. Recolor Artwork ==		== P20. Recolor Artwork ==
	* Estimation of difficulty: Variable - Short (90h or 175h)		* [[File:Imageasd.png\|right\|frameless\|369x369px]]Estimation of difficulty: Variable - Short (90h or 175h)
	* Potential mentors: Adam Belis ?		* Potential mentors: Adam Belis ?
	* Programming skills: usually C++		* Programming skills: usually C++