Difference between revisions of "Google Summer of Code"

From Inkscape Wiki
Jump to navigation Jump to search
Line 115: Line 115:
== Live Path Effects related ==
== Live Path Effects related ==

* [https://blueprints.launchpad.net/inkscape/+spec/power-stroke Power Stroke] - Modulated width stroke LPE.
* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.
* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.

Revision as of 00:40, 4 March 2011

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

Successful SOC Projects from Previous Years

  • 2005
    • Connectors
    • Inkboard
    • OCAL Interface
    • DXF Import / Export
  • 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

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.

Suggested Ideas

Generic ideas

Import/export projects

Internal work & performance improvements

  • Continue C++ification.
  • Improving 2Geom where necessary (e.g. boolops).
  • 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

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.

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
  • 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/