On Tue, 2011-01-25 at 07:52 +0300, Alexandre Prokoudine wrote:
Hello, teams :)
Google has just announced GSoC2011.
http://google-opensource.blogspot.com/2011/01/google-summer-of-code-announce...
The timeline is here: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/tim...
Excellent!
A few thoughts:
1. We need to update the Inkscape GSOC Wiki page:
http://wiki.inkscape.org/wiki/index.php/Google_Summer_Of_Code
2. I may be wrong, but I have the sense that we have a fairly high failure rate for accepted projects. What can we do to improve the project selection?
3. I would like to see some projects devoted to improving Inkscape fundamentals:
1. SVG support. You can see the current status of our performance on the W3C test suite at:
http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/...
and compare it to browser support at:
http://dev.w3.org/SVG/profiles/1.1F2/test/status/implementation_matrix.html
2. Improved handling of CSS. The CSS parser we use (libcroco) is not maintained.
http://www.freespiders.org/projects/libcroco/
The SVG output of Inkscape is full of unnecessary style attributes.
3. Improving Inkscape SVG for web use. Here's a list we came up with earlier:
* Fix "Plain" SVG to not remove <script>, etc. * Fix saving SVG to not modify CDATA (e.g. change & to &). * Add option to set viewbox attribute to Document Properties. (multiple viewbox support would be good) * Move flowed text into Inkscape namespace. * 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
Tav