Difference between revisions of "Google Summer of Code"

From Inkscape Wiki
Jump to navigation Jump to search
 
(88 intermediate revisions by 12 users not shown)
Line 1: Line 1:
 +
<div style="max-width:70em; margin-left: auto; margin-right: auto">
 
= Welcome to Inkscape! =
 
= Welcome to Inkscape! =
  
Line 7: Line 8:
 
We've mentored about half a dozen students a year since GSoC started.  Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student!  We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.
 
We've mentored about half a dozen students a year since GSoC started.  Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student!  We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.
  
If you are interested in joining us this summer, it is time to get your proposal ready. You can choose a proposal from our list of suggestions or come up with one of your own. In either either case, you must give us a detailed outline of what you plan to do. It is highly recommended that you discuss your idea as early as possible with Inkscape developers. They not only can give you guidance as you flesh out your proposal but ultimately you must convince them that you can do the work planned in the time allotted.
+
If you are interested in joining us this summer, it is time to get your proposal ready. You can choose a proposal from our list of suggestions or come up with one of your own. In either either case, you '''must''' give us a detailed outline of what you plan to do. It is '''highly''' recommended that you discuss your idea as early as possible with Inkscape developers. They not only can give you guidance as you flesh out your proposal but ultimately you must convince them that you can do the work planned in the time allotted. '''If you have not discussed your proposal with Inkscape developers before you apply, your application will be rejected!'''
  
 
= Student Applications =
 
= Student Applications =
  
 
* Google program information:
 
* Google program information:
** [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Home page].
+
** [https://summerofcode.withgoogle.com/ Home page].
** Summer of Code Application form.
+
** Summer of Code Application form. Applications open at 18:00 UTC on March 16th.
  
 
* Inkscape-specific information:
 
* Inkscape-specific information:
 
** [[SOC Application Template]].
 
** [[SOC Application Template]].
 
** [[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.
 
** [[SOC Writing Project Proposals]] - some guidelines for proposals.
 
** [[SOC Writing Project Proposals]] - some guidelines for proposals.
 
** [[SOC Selection Criteria]] - how we rate applications.
 
** [[SOC Selection Criteria]] - how we rate applications.
  
'''Student Applications for GSoC 2014 must be submitted to the GSoC site by 19:00 UTC on March 21st 2014.'''
+
'''Student Applications for GSoC 2020 must be submitted to the GSoC site by 18:00 UTC on March 31st 2020.'''
  
 
= The "two patches" rule =
 
= The "two patches" rule =
  
We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the Bazaar code repository).
+
We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the code repository).
 +
 
 
The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it.  
 
The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it.  
 
Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code!
 
Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code!
You can join our [http://inkscape.org/discussion.php jabber/IRC] channel and ask developers for help.
+
You can join our [https://inkscape.org/community/discussion/ IRC] channel or [https://chat.inkscape.org/channel/team_devel Rocket Chat] and ask developers for help.
  
 
== Suggested "easy" bug fixes or improvements ==
 
== Suggested "easy" bug fixes or improvements ==
  
To get you started on Inkscape development, you can find (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program by searching our [https://bugs.launchpad.net/inkscape bug-tracker] for bugs tagged with 'easy-fix'.
+
To get you started on Inkscape development, you can find (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program by searching our [https://gitlab.com/inkscape/inkscape/issues/ bug-tracker] for bugs tagged with 'easy-fix'.
  
 
= Performance Evaluation =
 
= Performance Evaluation =
Line 48: Line 51:
 
Remember: ''we want you to succeed!''
 
Remember: ''we want you to succeed!''
  
= Suggested Ideas =
+
= Suggested Project Ideas =
 +
 
 +
The following is a list of formal project suggestions, but do not feel limited to only these - some of our best contributions have been unique ideas that students had in mind from other sources!
 +
 
 +
See also [[Development Project Ideas]], [[Refactoring projects]], [[Projects]], and https://blueprints.launchpad.net/inkscape/
 +
 
 +
==P1. Better CSS Style Sheet Support==
 +
 
 +
Enhance Inkscape's support for CSS style sheets.
 +
 
 +
* Estimation of difficulty: Moderately hard
 +
* Potential mentors: Tavmjong Bah
 +
* Programming skills needed:  C++
 +
* Prerequisites: Experience with CSS style sheets.
 +
 
 +
<u>Detailed Description</u>
 +
 
 +
Inkscape has rudimentary support for CSS style sheets that can read and parse one internal style sheet. A 2016 GSoC project added a simple style dialog that can create and modify the internal style sheet. The dialog is very limited and is not intuitive to use. A 2017 GSoC project added support for CSS 3 selectors. More work has been done recently. This project will extend the usefulness of that dialog by making it more user friendly and by extending its functionality.
 +
 
 +
<u>Use Cases</u>
 +
 
 +
* Support externally created SVGs.
 +
* Producing better SVGs for the Web.
 +
* Changing style on multiple objects at once (palettes).
 +
 
 +
<u>Related Material</u>
  
Please note that your project proposal must be realistic: if you promise too much, we will most likely think you have not understood at all what it is about and will reject your proposal.
+
* [https://www.w3.org/TR/CSS2/ CSS 2 Specification]
 +
* [https://www.w3.org/TR/css-2015/ CSS 2015 Snapshot]
  
== Generic ideas ==
+
==P3. Slice items==
 +
[[File:Cuttool.png|200px|thumb|right|Example of result of the split using straight lines only]]
 +
Add slicing Live Path Effect (LPE)
 +
* Estimation of difficulty: Moderately hard
 +
* Potential mentors: Jabier Arraiza (Spanish, some English)
 +
* Programming skills needed:  C++
  
* Font editing and creation features, e.g. [https://blueprints.launchpad.net/inkscape/+spec/designing-svg-fonts-using-styles designing SVG fonts using styles]
+
<u>Detailed Description</u><br />
* [https://blueprints.launchpad.net/inkscape/+spec/new-from-template-dialog 'New From Template' dialog]
+
The goal is a LPE, to slice items.<br />
* [https://blueprints.launchpad.net/inkscape/+spec/kidscape-project kidscape] - Condensed version of Inkscape aimed at young kids and small form factor devices
+
It accept a path parameter (storing a path) as cutter.<br />
* [https://blueprints.launchpad.net/inkscape/+spec/cutter-control Cutter control] - Enable Inkscape's use with vinyl cutters.
+
The effect create pieces by the split path.<br />
* [https://blueprints.launchpad.net/inkscape/+spec/guides-improvement Guides Improvements] - Especially a dialog that lists all guides and allows operations on them would be very very nice.
+
Can be added multiple times to add more splits.<br />
 +
We have the code of mirror symmetry LPE and rotate copies LPE as reference.<br />
 +
Also we can force or better ask to convert strokes to path previously to apply the effect (one line command, but we need advert is a destructive LPE)<br />
 +
Study generate a HTML image map definition.<br />
 +
<u>Use Cases</u>
 +
* Better item slicing.
 +
* Create HTML image maps
 +
* Split a item and use for example on PNG export option export as separate objects.
  
== Import/export projects ==
+
==P5. UI-Free Inkscape ==
  
* Importing of 3D scene files in 16 file formats using [http://assimp.sourceforge.net/ Open Asset Import Library]
+
* Estimation of difficulty: Difficult
* [https://blueprints.launchpad.net/inkscape/+spec/xar-to-svg-converter xar-to-svg converter] - Converter for Xara Xtreme to Inkscape
+
* Potential mentors: Marc Jeanmougin
* [https://blueprints.launchpad.net/inkscape/+spec/kml-svg-translation KML SVG translation] - For use of Inkscape with Google Earth or Maps
+
* Programming skills: C++, CMake
 +
* Prerequisites: Minimal knowledge of build systems. Experience with GtkMM helpful.
  
== Internal work & performance improvements ==
+
<u>Detailed Description</u>
 +
Inkscape currently builds with X11 and gtk and a lot of graphical dependencies. But since it is allowed to run in commandline, and there are controlled environments (servers) that use it to convert svg to png and to perform actions, there should be no need to force it to build with those. The main goal of this project is to add a WITH_GUI compilation flag that when OFF, does *not* link Inkscape with any graphical dependency. While much work has been done towards this goal, much remains to be done. As a next step, Inkscape's "verbs" which are mostly GUI dependent (even if there is no reason to be) need to be converted to Gio::Actions.
  
* Improve startup time and initialization performance.
 
* Continue C++ification.
 
* Improving 2Geom where necessary (e.g. '''boolops''' and '''python bindings''').
 
* [https://blueprints.launchpad.net/inkscape/+spec/icc-for-cairo ICC Color Management for cairo outputs] - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.
 
* [http://wiki.inkscape.org/wiki/index.php/TextRework Text layout rewrite]: Move flow-text into Inkscape name space. Add support for hyphenation, paragraph indentation, underlining, etc.
 
* Units (inch, cm, px): the codebase has 4 different pieces of code for handling units! Refactoring into *one*. Allow users to choose which unit to use by default.
 
  
== Better SVG standard coverage ==
+
<u>Use cases</u>
 +
* Server installs, scripts
  
* Full SVG viewbox support
+
==P6. Refactoring==
* [[multipage | Multiple Page support]]
+
* Estimation of difficulty: Moderate
* Improve SVG compliance. [http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/index.html Current status of W3C test suite compliance].
+
* Potential mentors: Tavmjong Bah
* Implement SVG 2.0 (and related) items such as:
+
* Programming skills: C++
** Vector Effects (non-destructive boolean-ops would be a good start)
+
* Prerequisites: proficient C++.
** Marker color matching stroke
 
** [http://www.w3.org/TR/SVGMobile12/single-page.html#painting-SolidColorElement Solid-color support] (Named colors, would deprecate the single-stop gradient approach we currently use)
 
** [http://www.w3.org/TR/css3-color/ CSS3 color support]
 
** CSS3 2d transforms (duplicates current attributes)
 
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_position Stroke position]
 
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_dash_adjustment Stroke dash adjustment]
 
Note: Some of the above items are somwhat low hanging fruit and would need a few of them to make a good proposal, others alone are worthy of a full GSoC project.
 
  
== Improve Inkscape SVG for use on Web ==
+
<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. Refactoring is an important skill of which many books have been written. Here's a chance to gain valuable experience!
  
A proposal should fix most if not all of these problems:
+
See https://wiki.inkscape.org/wiki/index.php/Refactoring_projects for some ideas of projects.
  
* Fix "plain" SVG to not remove <script> section, etc.
+
==P7. SVG 2 Support with SVG 1.1 Fallback or Polyfills ==
* Add option to set viewbox attribute to Document Properties.
+
* Estimation of difficulty: Variable
* Easily add/edit hyperlinks.
+
* Potential mentors: Tavmjong Bah
* Better CSS support.
+
* Programming skills: C++, JavaScript
* Option to add title to SVG (searchability and accessibility).
+
* Prerequisites: Experience in C++  and/or web development.
* Remove XML prolog/DOCTYPE.
 
* Move sodipodi namespace items to Inkscape namespace.
 
  
== Live Path Effects related ==
+
<u>Detailed Description</u>
 +
Inkscape supports a wide range of SVG 2 features. Some are supported only in rendering, some in both rendering and editing. Many of the features
 +
of SVG 2 have yet to (and may never) make it into browsers. This project is to expose more SVG 2 features in Inkscape and to ensure they can be
 +
exported to SVG 1.1 and/or supported in browsers by  writing <i>polyfills</i> which implement missing functionality using JavaScript.
  
* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.
+
==P8. Add Text and Image Support to Live Path Effect System ==
 +
* Estimation of difficulty: Hard
 +
* Potential mentors: Jabier Arraiza (Spanish, English(not native))
 +
* Programming skills: C++
 +
* Prerequisites: Experience managing bitmaps
 +
<u>Detailed Description</u>
 +
Live Path Effects are non destructive effects applied to paths and shapes standalone or inside a group.<br />
 +
This is done keepeng a reference to the original data to reaply when needed.<br />
 +
But ignore text and image elements.<br />
 +
Things to do:
 +
* Study add image, text, both and maybe others SVG elements to the LPE system.
 +
* Create/adapt minimun one LPE for each new type of element acepted as reference. Suggestion Perspective-Envelope.
 +
<u>Use cases</u>
 +
* Apply live effects to images and text based in C++ code in a non destructive way even in groups with mixed elements types.
  
== Tools and shapes related ==
+
==P9. Path Library Improvements ==
 +
* Estimation of difficulty: Hard
 +
* Potential mentors: Tavmjong Bah, KK
 +
* Programming skills: C++
 +
* Prerequisites: Strong math skills, specifically in geometry.
 +
<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.
 +
Specifically, the functionality needed is
 +
* Path offset/inset functions.
 +
* Path simplify.
 +
* Stroke to path function.
 +
* Line scanning (used for flowing text into a shape).
  
* Multi shape editing - ability to edit more than 1 shape (like ellipse or star) at once, with extra features like resizing rectangles by dragging their edges.
+
==P10. Your project ==
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]
+
* Estimation of difficulty: Variable
* Further development of [http://generalpicture.com/svg/shapeopera.html Shape Opera], a simple Javascript framework for  morphing Inkscape PATH shapes.
+
* Potential mentors: Marc Jeanmougin
* Extend the Symbols dialog to include generic objects.
+
* Programming skills: usually C++
* [https://blueprints.launchpad.net/inkscape/+spec/inkscape-connectors Connector tool improvements] - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)
+
* Prerequisites: good ideas
* [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet/Chamfer tool]
 
* Move Mesh gradients to Inkscape name space with appropriate editing interface and export fallback. Note, Inkscape trunk has an experimental implementation based on the proposed mesh syntax for SVG 2.
 
  
Please do not feel limited to the above ideas - some of our best contributions have been unique ideas that students had in mind from other sources!
+
<u>Detailed Description</u>
 +
The most successful GSoC we had in the past were students coming with their own past, use cases and ideas for Inkscape. Many basic tools like 3d cubes or connectors you can see in Inkscape now have been brought by brilliant people (like you) with ideas. If we think that your project fits with Inkscape (ie: has its place with a vector graphic editor), we can help you refining your ideas and help bring shiny new stuff to life!
  
For more ideas, please see https://blueprints.launchpad.net/inkscape/
+
<u>Use cases</u>
 +
* Amaze us!
  
 
= Successful SOC Projects from Previous Years =
 
= Successful SOC Projects from Previous Years =
Line 146: Line 203:
 
** A test suite
 
** A test suite
 
* 2009
 
* 2009
** [[GSoC 2009 Node Tool Rewrite|Node tool rewrite]]
+
** [[GSoC2009 Node Tool Rewrite|Node tool rewrite]]
 
** D-Bus scripting API
 
** D-Bus scripting API
 
** Connector tool improvements
 
** Connector tool improvements
Line 161: Line 218:
 
** [[Tiling tool|On-canvas support for Tessellations]]
 
** [[Tiling tool|On-canvas support for Tessellations]]
 
** Creating python bindings for lib2geom
 
** Creating python bindings for lib2geom
 +
* [[Google Summer of Code 2013|2013]]
 +
** Recolor Tool
 +
** Improved Units Support
 +
** Electronics CAD Support
 +
** New From Templates Dialog
 +
** New Raster to Vector Algorithm
 +
* 2014
 +
** Better Support for SVG Paints
 +
** Robust Boolean and Stroking Operations for 2Geom
 +
* 2016
 +
** [[GSoC 2016 Better data structure for selections|Better data structure for selections]]
 +
** [[Style Editor|CSS Style Sheet Editor]]
 +
* 2017
 +
** SVG 2 Text Support
 +
** Better CSS Style Sheet Support
 +
* 2019
 +
** Mesh gradient and hatches polyfills. Paint server dialog.
  
 
[[Category:Developer Documentation]]
 
[[Category:Developer Documentation]]
 +
</div>

Latest revision as of 12:31, 5 March 2020

Welcome to Inkscape!

For quite a few years Inkscape has been successfully participating in Google Summer of Code.

GSoC is a program where Google funds the development of specific features in open source software by university students. You don't need to be a Computer Science student to apply. Features to be developed are picked by Inkscape administrators from the pool of proposals submitted by students.

We've mentored about half a dozen students a year since GSoC started. Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student! We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.

If you are interested in joining us this summer, it is time to get your proposal ready. You can choose a proposal from our list of suggestions or come up with one of your own. In either either case, you must give us a detailed outline of what you plan to do. It is highly recommended that you discuss your idea as early as possible with Inkscape developers. They not only can give you guidance as you flesh out your proposal but ultimately you must convince them that you can do the work planned in the time allotted. If you have not discussed your proposal with Inkscape developers before you apply, your application will be rejected!

Student Applications

  • Google program information:
    • Home page.
    • Summer of Code Application form. Applications open at 18:00 UTC on March 16th.

Student Applications for GSoC 2020 must be submitted to the GSoC site by 18:00 UTC on March 31st 2020.

The "two patches" rule

We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the code repository).

The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it. Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code! You can join our IRC channel or Rocket Chat and ask developers for help.

Suggested "easy" bug fixes or improvements

To get you started on Inkscape development, you can find (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program by searching our bug-tracker for bugs tagged with 'easy-fix'.

Performance Evaluation

GSoC has two formal evaluation points, at the mid-term and at the end. These evaluations determine if you receive the stipend from Google. In order to receive a pass for the evaluations you will need to show adequate progress toward your project's goals.

To help you meet your goals and so that your mentor can better evaluate your progress you need to:

  • Have frequent, public discussions of your progress. (Don't rely on just your mentor for advice.)
  • Have a public Inkscape branch for your code to which you commit regularly.
  • Give weekly status reports.

For the final pass, you will normally be required to merge your code into Inkscape trunk.

Remember: we want you to succeed!

Suggested Project Ideas

The following is a list of formal project suggestions, but do not feel limited to only these - some of our best contributions have been unique ideas that students had in mind from other sources!

See also Development Project Ideas, Refactoring projects, Projects, and https://blueprints.launchpad.net/inkscape/

P1. Better CSS Style Sheet Support

Enhance Inkscape's support for CSS style sheets.

  • Estimation of difficulty: Moderately hard
  • Potential mentors: Tavmjong Bah
  • Programming skills needed: C++
  • Prerequisites: Experience with CSS style sheets.

Detailed Description

Inkscape has rudimentary support for CSS style sheets that can read and parse one internal style sheet. A 2016 GSoC project added a simple style dialog that can create and modify the internal style sheet. The dialog is very limited and is not intuitive to use. A 2017 GSoC project added support for CSS 3 selectors. More work has been done recently. This project will extend the usefulness of that dialog by making it more user friendly and by extending its functionality.

Use Cases

  • Support externally created SVGs.
  • Producing better SVGs for the Web.
  • Changing style on multiple objects at once (palettes).

Related Material

P3. Slice items

Example of result of the split using straight lines only

Add slicing Live Path Effect (LPE)

  • Estimation of difficulty: Moderately hard
  • Potential mentors: Jabier Arraiza (Spanish, some English)
  • Programming skills needed: C++

Detailed Description
The goal is a LPE, to slice items.
It accept a path parameter (storing a path) as cutter.
The effect create pieces by the split path.
Can be added multiple times to add more splits.
We have the code of mirror symmetry LPE and rotate copies LPE as reference.
Also we can force or better ask to convert strokes to path previously to apply the effect (one line command, but we need advert is a destructive LPE)
Study generate a HTML image map definition.
Use Cases

  • Better item slicing.
  • Create HTML image maps
  • Split a item and use for example on PNG export option export as separate objects.

P5. UI-Free Inkscape

  • Estimation of difficulty: Difficult
  • Potential mentors: Marc Jeanmougin
  • Programming skills: C++, CMake
  • Prerequisites: Minimal knowledge of build systems. Experience with GtkMM helpful.

Detailed Description Inkscape currently builds with X11 and gtk and a lot of graphical dependencies. But since it is allowed to run in commandline, and there are controlled environments (servers) that use it to convert svg to png and to perform actions, there should be no need to force it to build with those. The main goal of this project is to add a WITH_GUI compilation flag that when OFF, does *not* link Inkscape with any graphical dependency. While much work has been done towards this goal, much remains to be done. As a next step, Inkscape's "verbs" which are mostly GUI dependent (even if there is no reason to be) need to be converted to Gio::Actions.


Use cases

  • Server installs, scripts

P6. Refactoring

  • Estimation of difficulty: Moderate
  • Potential mentors: Tavmjong Bah
  • Programming skills: C++
  • Prerequisites: proficient C++.

Detailed Description 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. 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.

P7. SVG 2 Support with SVG 1.1 Fallback or Polyfills

  • Estimation of difficulty: Variable
  • Potential mentors: Tavmjong Bah
  • Programming skills: C++, JavaScript
  • Prerequisites: Experience in C++ and/or web development.

Detailed Description Inkscape supports a wide range of SVG 2 features. Some are supported only in rendering, some in both rendering and editing. Many of the features of SVG 2 have yet to (and may never) make it into browsers. This project is to expose more SVG 2 features in Inkscape and to ensure they can be exported to SVG 1.1 and/or supported in browsers by writing polyfills which implement missing functionality using JavaScript.

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

  • Estimation of difficulty: Hard
  • Potential mentors: Jabier Arraiza (Spanish, English(not native))
  • Programming skills: C++
  • Prerequisites: Experience managing bitmaps

Detailed Description Live Path Effects are non destructive effects applied to paths and shapes standalone or inside a group.
This is done keepeng a reference to the original data to reaply when needed.
But ignore text and image elements.
Things to do:

  • Study add image, text, both and maybe others SVG elements to the LPE system.
  • Create/adapt minimun one LPE for each new type of element acepted as reference. Suggestion Perspective-Envelope.

Use cases

  • Apply live effects to images and text based in C++ code in a non destructive way even in groups with mixed elements types.

P9. Path Library Improvements

  • Estimation of difficulty: Hard
  • Potential mentors: Tavmjong Bah, KK
  • Programming skills: C++
  • Prerequisites: Strong math skills, specifically in geometry.

Detailed Description 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. Specifically, the functionality needed is

  • Path offset/inset functions.
  • Path simplify.
  • Stroke to path function.
  • Line scanning (used for flowing text into a shape).

P10. Your project

  • Estimation of difficulty: Variable
  • Potential mentors: Marc Jeanmougin
  • Programming skills: usually C++
  • Prerequisites: good ideas

Detailed Description The most successful GSoC we had in the past were students coming with their own past, use cases and ideas for Inkscape. Many basic tools like 3d cubes or connectors you can see in Inkscape now have been brought by brilliant people (like you) with ideas. If we think that your project fits with Inkscape (ie: has its place with a vector graphic editor), we can help you refining your ideas and help bring shiny new stuff to life!

Use cases

  • Amaze us!

Successful SOC Projects from Previous Years

  • 2005
  • 2006
    • Support for SVG Filters
    • Filter Effects
    • PDF export
    • Inkboard Protocol Spec / Lib Conversion
  • 2007
    • Text Style Improvements
    • PDF import
    • Live Path Effects
    • 3D Box Tool
    • UI for SVG Filter Effects
    • Raster Functionality
    • Importing from, and Exporting to, a remote ccHost instance
  • 2008
    • SVG Fonts support
    • 2Geom refactoring project - port most geometry code to 2Geom
    • lib2geom: interactive applications showing off the power of lib2geom
    • Tech drawing abilities
    • A test suite
  • 2009
  • 2010
    • Cairo-based rendering
    • C++ification of SP Layer
  • 2011
    • Rendering caching
    • Javascript support improvements
    • CSS support improvements
  • 2012
  • 2013
    • Recolor Tool
    • Improved Units Support
    • Electronics CAD Support
    • New From Templates Dialog
    • New Raster to Vector Algorithm
  • 2014
    • Better Support for SVG Paints
    • Robust Boolean and Stroking Operations for 2Geom
  • 2016
  • 2017
    • SVG 2 Text Support
    • Better CSS Style Sheet Support
  • 2019
    • Mesh gradient and hatches polyfills. Paint server dialog.