Google Summer of Code
- 1 Welcome to Inkscape!
- 2 Student Applications
- 3 SOC Features
- 4 The "two patches" rule
- 5 Suggested Ideas
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).
- Google program information
- Summer of Code Application form
- Inkscape-specific information
(TODO complete the list)
- Live Path Effects
- 2Geom refactoring project - port most geometry code to 2Geom
- Node tool rewrite
- D-Bus scripting API
- Connector tool improvements
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). 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 jabber/IRC channel and ask developers for help. To get you started on Inkscape development, here is a list of (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program.
Suggested "easy" bug fixes or improvements
- Bug #530957 “Save as dialog regression with filename”: (MS Windows) File save dialog - the "save/save as/save a copy" dialog should fill in a suggested file name *without* extension. For example, if I am working on a file "hello.svg", and press "save a copy", the file name input field should have the text "hello" in it.
- Bug #408566 “Program won't save files without given extension on Win32”: (MS Windows) A folder in the path with a dot '.' in its name prevents automatic adding of the file name extension and saves the file without suffix.
- Bug #561503 “Setting grid origin has no effect”: (all platforms)
- Font editing and creation features, e.g. designing SVG fonts using styles
- 'New From Template' dialog
- kidscape - Condensed version of Inkscape aimed at young kids and small form factor devices
- Cutter control - Enable Inkscape's use with vinyl cutters.
- Guides Improvements
- Importing of 3D scene files in 16 file formats using Open Asset Import Library
- xar-to-svg converter - Converter for Xara Xtreme to Inkscape
- KML SVG translation - For use of Inkscape with Google Earth or Maps
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. DONE
- ICC Color Management for cairo outputs - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.
- Text layout rewrite: Move flow-text into Inkscape name space. Add support for hyphenation, paragraph indentation, underlining, etc.
Better SVG standard coverage
- Full SVG viewbox support
- Multiple Page support
- Improve SVG compliance. Current status of W3C test suite compliance.
- Improve handling of CSS. We use libcroco which is unmaintained. Inkscape SVG output is full of unnecessary style attributes.
Improve Inkscape SVG for use on Web
A proposal should fix most if not all of these problems:
- Fix "plain" SVG to not remove <script> section, etc.
- Fix saving SVG to not modify CDATA (e.g. change & to &).
- Add option to set viewbox attribute to Document Properties.
- Font fallbacks.
- Easily add/edit hyperlinks.
- Better CSS support.
- Option to add title to SVG (searchability and accessibility).
- Remove XML prolog/DOCTYPE.
- Move sodipodi namespace items to Inkscape namespace.
- Power Stroke - Modulated width stroke LPE.
- More Live Path Effects - There is a lengthy list of ideas to choose from here.
- 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
- 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
- Add Mesh gradients in Inkscape name space with appropriate editing interface. (Note that Cairo now supports meshes.)
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/