Difference between revisions of "Google Summer of Code"

From Inkscape Wiki
Jump to navigation Jump to search
(→‎Suggested Ideas: categorization, cleanup)
Line 51: Line 51:
* Switching primary rendering engine from Livarot/libnr to Cairo
* Switching primary rendering engine from Livarot/libnr to Cairo
* [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.
* [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.
* Improve text layout: Move flow-text to Inkscape name space, Add support for hyphenation, paragraph indentation, etc.


== Better SVG standard coverage ==
== Better SVG standard coverage ==

Revision as of 10:44, 14 June 2010

Welcome to Inkscape!

For a few years Inkscape was successful in 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.

The Inkscape team plans to focus this summer on codebase cleanup and refactoring. This will affect the type of projects we can accept this year; we're looking for ones that either won't affect core code too significantly (such as Extension scripts, or File Input/Output formats) or that would actually result in improving the state of the codebase (adding tests, modularization, etc.). Students who have already been active developers in Inkscape previously will be allowed more latitude to work on core code (particularly if it will result in cleanup/refactoring of their past work).

Student Applications

SOC Features

(TODO complete the list)

  • 2008
    • 2Geom refactoring project - port most geometry code to 2Geom
  • 2009

Suggested Ideas

Generic ideas

Import/export projects

Internal work, rendering, speedups

  • C++ize the SP layer and make XML nodes private.*
  • Remove livarot in favor of 2Geom, improving 2Geom where necessary (e.g. boolops).
  • Switching primary rendering engine from Livarot/libnr to Cairo
  • ICC Color Management for cairo outputs - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.
  • Improve text layout: Move flow-text to Inkscape name space, Add support for hyphenation, paragraph indentation, etc.

Better SVG standard coverage

Live Path Effects related

Tools and shapes related

  • 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.
  • Transformation Anchors
  • Further development of Shape Opera, a simple Javascript framework for morphing Inkscape PATH shapes.
  • Add a palette of objects to Inkscape. Such a palette would contain often used objects and would allow categorizing such objects. Examples of categories: UML, electric, network.
  • Connector tool improvements - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)
  • Arrowhead/marker improvements
  • Fillet/Chamfer tool

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!

For more ideas, please see https://blueprints.launchpad.net/inkscape/