Difference between revisions of "Google Summer of Code 2007"

From Inkscape Wiki
Jump to navigation Jump to search
(and/or is terrible grammar, OR is not XOR it is inclusive)
(attempt to organise and categorise suggestions, needs more work)
Line 13: Line 13:
= Project Ideas =
= Project Ideas =


== 3D capability ==
== File formats ==


Inkscape is a 2D drawing tool. However, very often it is used to draw 3D objects. It would be very cool to have more support from the program for doing that, instead of just drawing everything manually. Nothing too fancy - we're not going to compete with Blender; but even simple things can go a long way. What's listed below is just basic ideas; feel free to develop upon them or offer something entirely different in your proposal.
=== Native Import of Encapsulated Poscript (EPS) or Adobe Portable Document Format (PDF) ===
 
* A '''3D box tool''' would be able to:
 
:*draw a 3D box;
 
:*adjust any of its 3 dimensions by handles and numerically;
 
:*freely move the perspective vanishing point for each dimension;
 
:*switch any dimension from a vanishing point to direction (point in infinity,  lines are parallel) and back;
 
:*Allow subdivision of each face to create perspective grids;
 
:*when more than one 3D box is selected and their perspective is compatible, drag their common vanishing points/directions updating all selected boxes;
 
:*3D-rotate the entire selected 3D box (or several selected 3D boxes if they have a compatible perspective), thus moving all 3 directions/vanishing points in a natural way;
 
:*remember the last-set directions/vanishing points and create new objects in the same perspective, so you can quickly and easily draw an entire 3D scene with many boxes.
 
:In SVG, a 3D box will be represented as a group with a special extension attribute; the group would contain the 6 quadrilateral paths representing the sides of the box. Only the 3D box tool would treat this object as a whole; for all other tools it will be just a group, so you can select any of the paths, apply any style to it, delete it, etc. At the same time, the 3D tool would still be able to 3D-rotate and 3D-tweak the box while preserving any changed style and not restoring deleted sides (e.g. if you don't want to see the hidden sides, simply delete them as objects from the group).
: The extrude tool in Macromedia Freehand may also be of interest as a way of  creating the appearance of 3D. 
 
* '''3D guides''' can be a helpful addition to the 3D box tool. You would be able to create a new set of 3D guides from any 3D box and then use these guides for drawing with any tool that can snap to guides (e.g. the Pen tool). The guides would use different colors  for the three dimensions. Ideally the guides should remember which object they were created from and update when that object's perspective (the set of 3 vanishing points or directions) is edited in the 3D tool.
 
* '''Other primitives''': Sphere, Cylinder, Cone, Pyramid ...
 
* '''Perspective transform tool''' like in the GIMP
 
* '''Perspective grid tiling''': cloning an object to each field of a grid.
 
This is a big and infinitely expandable area. We do not expect any single student to cover all of this in a single summer. You can propose a reasonably useful subset of this functionality as your 2007 GSoC project.
 
<b>Mentor:</b>  Bulia Byak
 
== Native Import of Encapsulated Poscript (EPS) or Adobe Portable Document Format (PDF) ==


While SVG is becoming a common format for exchanging data between graphics programs, EPS and PDF are still much more common.  Inkscape's current EPS import is brittle, not as well maitained as we might like, and not available for all target platforms as it depends on 3rd party software.  The goal is to give Inkscape native EPS or PDF import capability.  
While SVG is becoming a common format for exchanging data between graphics programs, EPS and PDF are still much more common.  Inkscape's current EPS import is brittle, not as well maitained as we might like, and not available for all target platforms as it depends on 3rd party software.  The goal is to give Inkscape native EPS or PDF import capability.  
Line 66: Line 31:
<b>Mentor:</b>  ???
<b>Mentor:</b>  ???


== Native Import/Export of Corel Draw (CDR) files ==
=== Native Import/Export of Corel Draw (CDR) files ===


Corel Draw was and still is a very popular drawing application and many files exist in the Corel Draw format.  The user interface of Corel Draw is more similar in many ways to Inkscape than other graphics software making Inkscape more attractive to Corel Draw artists.  We are getting a lot of requests from users to support this format.   
Corel Draw was and still is a very popular drawing application and many files exist in the Corel Draw format.  The user interface of Corel Draw is more similar in many ways to Inkscape than other graphics software making Inkscape more attractive to Corel Draw artists.  We are getting a lot of requests from users to support this format.   
Line 76: Line 41:
* [http://sk1.sourceforge.net sK1] is a Corel Draw lookalike vector editor, at early stages of development but claiming to be able to read CDR files.  
* [http://sk1.sourceforge.net sK1] is a Corel Draw lookalike vector editor, at early stages of development but claiming to be able to read CDR files.  


* CDR files use [http://en.wikipedia.org/wiki/RIFF RIFF metaformat], which means you can easily find an open source library for reading the top layer of the format (try any open source app that can read WAV or AVI, which are also RIFF-based).
* CDR files use [http://en.wikipedia.org/wiki/RIFF RIFF metaformat], which means you can easily find an open source library for reading the top layer of the format (try any open source app that can read WAV or AVI, which are also RIFF-based). http://en.wikipedia.org/wiki/.cdr


A student for this project will need to plan the scope of the feature (we do not need to do all the fancy features, but basics need to be covered) and assemble, with the help of the mentor, a library of sample CDR files for testing.
A student for this project will need to plan the scope of the feature (we do not need to do all the fancy features, but basics need to be covered) and assemble, with the help of the mentor, a library of sample CDR files for testing.
Line 82: Line 47:
'''Mentor:''' Bulia Byak
'''Mentor:''' Bulia Byak


== Live Path Effects ==
== Raster Graphics ==
 
=== Inkscape / GIMP Bitmap Editing Integration ===
 
Currently, you can embed raster/bitmap images into Inkscape drawings, but editing them is a bit of a hassle because Inkscape isn't really "aware" of external bitmap editing tools.
 
This project would seek to correct this by modifying inkscape's image embedding code to interoperate more directly with external bitmap programs.  For instance, there would be an "open external editor" command that could be used when one or more bitmap images are selected.  Another idea would be to include some common bitmap modification commands from the external program, that can be run entirely within Inkscape.  A third idea is drag and drop of selections from the bitmap editor to Inkscape, and SVG selections from Inkscape to the bitmap tool.
 
As a proof of concept, the result should demonstrate this interoperability with GIMP and/or [http://www.gegl.org/ GeGL].  Note that the code should be developed such that in theory it should work with any bitmap editor, but we would only require demonstration of working with GIMP.
 
Also see:  http://sourceforge.net/tracker/index.php?func=detail&aid=862655&group_id=93438&atid=604309
 
<b>Mentor:</b>  TBD
 
=== Adding bitmap capabilities to Inkscape ===


As explained on [[LivePathEffects|this wiki page]], Live Path Effects allow arbitrary path-changing effects to be applied to any path object. Inkscape will remember the original path before the transformation was applied, so you will be able to remove the effect, chain several effects on the same path, adjust their parameters, etc. All the effects metadata will be stored in Inkscape-only attributes. At the same time, the resulting visible path (with the effects applied) is saved using pure SVG elements and attributes and thus visible to all SVG renderers, thus upholding Inkscape's basic principle of operation: drawings must look exactly the same in Inkscape as in any SVG-compliant renderer.
While the purpose of Inkscape is to be a vector editor, design in the real world requires dealing with bitmaps too. Inkscape can import the bitmaps, and have them as full canvas objects, but there is no significant bitmap operations in Inkscape. While there is no reason for Inkscape to replicate the functionality of The GIMP, it would be desirable to have a few simple operations available from Inkscape.


This approach will allow us to make many of the effects currently implemeted as extensions (in the Effects menu) live and interactive. Path randomization, putting pattern along path, blends, envelopes, various distortions - all these can and should be live path effects, not the clunky, slow, and inconvenient Python scripts. Fortunately, Inkscape architecture makes creating live path effects relatively easy.
This project will use the Inkscape extensions system to add a series of bitmap effects. The majority of the effects will be achieved through the integration of the ImageMagick bitmap handling libraries. GIMP may be another source.  These effects can then be run on bitmap graphics within Inkscape.


To complete this project, a student must implement at least several simple effects, propose and create a basic user interface for applying them to paths (Path Effects tool?). Some of the effects that you could start with are:
The work should be encapsulated in such a way that in theory, other vector graphics applications (such as Xara), could also use the work. However, for the scope of this project we only require demonstration of the capabilities in Inkscape.


* '''Filleting''' (corner rounding) is common in technical drawing.  While this is a fairly basic drafting task, it's currently not particularly easy to do in Inkscape except for certain cases such as round cornered rectangles.  This effect would apply rounding with a given radius to all or some sharp corners of a path. It should also permit creation of '''chamfers''' which are flattened edges at suitable angles.


* '''Fractalize''' is currently a Python effect but would make a great live path effect. It can be useful in <b>mapmaking</b>; maps involve lots of irregular shapes - coastlines, forest boundaries, rivers, etc. that could use fractalization with adjustable level. (As an added bonus, this could be implemented so that the level of fractalization depends on zoom, but preserving this behavior outside of Inkscape would require some smart scripting as explained in this paper: [http://www.svgopen.org/2004/papers/AdaptiveLoD/ Adaptive Level of Detail in SVG].)
== Scalable Vector Graphics (SVG) ==


<b>Mentor:</b>  Aaron Spike
=== SVG Font support ===


== Inkboard Portability ==
We need SVG Font support in order to be able to claim SVG Tiny support. While the occurrence of SVG fonts in the wild seems to be pretty low, we will benefit from this by being able to embed fonts and thus ensure rendering of text without converting it to paths.


Last year we had a successful project to integrate the SVG online whiteboard capability, called Inkboard, into Inkscape. Unfortunately, it does not work on Windows, so many users are missing out on this capability.
<b>Mentor:</b> ???


This work may involve [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/branches/INKBOARD_PEDRO/src/jabber_whiteboard/protocol/ formalizing and extending the Inkboard communication protocol] and [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/branches/INKBOARD_PEDRO/src/jabber_whiteboard/ working on the INKBOARD_PEDRO branch])
=== External Cascading Stylesheet (CSS) Support ===


<b>Mentor:</bTed
Inkscape currently has good support for inline CSS, and limited read-only support for an internal stylesheet in a <style> element, and no support for external stylesheets. Support for editing non-inline CSS would allow better expressiveness and adaptation, and smaller SVG files, and better support for SVG generated by other programs that use non-inline CSS.


== New Grids ==
<b>Mentor:</b> Peter Moulder


Inkscape currently has square grids that can be snapped to.  Extend this to allow other kinds of grids:  Perspective, hex, iso, etc.
=== Multi-page Support ===


This will involve modifying the grid code to support the ability to have multiple kinds of grids, implementing at least 3 new grids, and adding the UI elements to allow users to make use of them.
An often requested feature is for Inkscape to support multi-page editing. 
Currently, an Inkscape document is set to correspond to 1 printed page.  However, the next version of SVG specification (1.2) includes support for [http://jan.kollhof.net/projects/svg/motjuvie/present.xhtml multi-page documents], and lots of people would like to have this capability in Inkscape as well.


Requests in tracker:
This project would involve several steps: 1)  Add internal support for reading and writing SVG 1.2 <pageSet> and <page> elements. 2) When editing a pageSet, create the visual page frames for each <page>3) When exporting to Postscript, have it export each <page> as a separate page in the Postscript file.
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1591386&group_id=93438&atid=604309 Perspective Grid: 2 and 3 point with sample Perl script.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1005753&group_id=93438&atid=604309 Perspective Grid: 1, 2, and 3 point.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1418249&group_id=93438&atid=604309 Hex Grid.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1365504&group_id=93438&atid=604309 Isometric Grid.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=900270&group_id=93438&atid=604309 Isometric Grid.]


<b>Mentor:</b> TBD
(Another frequent request is support for a tabbed interface. To be clear a tabbed interface is quite a different request from this one and any such Tabbed interface would need to accomodate the requirement of single documents with multiple pages like those proposed in SVG and already existing in PDF, OpenDocument Draw, and many others.)


== User Interface for SVG Filters ==
=== User Interface for SVG Filters ===


Filters are a very important [http://www.w3.org/TR/SVG/filters.html SVG capability].
Filters are a very important [http://www.w3.org/TR/SVG/filters.html SVG capability].
Line 135: Line 109:
<b>Mentor:</b>  Ted Gould
<b>Mentor:</b>  Ted Gould


== Inkscape / GIMP Bitmap Editing Integration ==


Currently, you can embed raster/bitmap images into Inkscape drawings, but editing them is a bit of a hassle because Inkscape isn't really "aware" of external bitmap editing tools.
== General ==


This project would seek to correct this by modifying inkscape's image embedding code to interoperate more directly with external bitmap programs.  For instance, there would be an "open external editor" command that could be used when one or more bitmap images are selected.  Another idea would be to include some common bitmap modification commands from the external program, that can be run entirely within Inkscape.  A third idea is drag and drop of selections from the bitmap editor to Inkscape, and SVG selections from Inkscape to the bitmap tool.
=== 3D capability ===


As a proof of concept, the result should demonstrate this interoperability with GIMP and/or [http://www.gegl.org/ GeGL].  Note that the code should be developed such that in theory it should work with any bitmap editor, but we would only require demonstration of working with GIMP.
Inkscape is a 2D drawing tool. However, very often it is used to draw 3D objects. It would be very cool to have more support from the program for doing that, instead of just drawing everything manually. Nothing too fancy - we're not going to compete with Blender; but even simple things can go a long way. What's listed below is just basic ideas; feel free to develop upon them or offer something entirely different in your proposal.  


Also see: http://sourceforge.net/tracker/index.php?func=detail&aid=862655&group_id=93438&atid=604309
* A '''3D box tool''' would be able to:  


<b>Mentor:</b>  TBD
:*draw a 3D box;


== Adding bitmap capabilities to Inkscape ==
:*adjust any of its 3 dimensions by handles and numerically;


While the purpose of Inkscape is to be a vector editor, design in the real world requires dealing with bitmaps too. Inkscape can import the bitmaps, and have them as full canvas objects, but there is no significant bitmap operations in Inkscape. While there is no reason for Inkscape to replicate the functionality of The GIMP, it would be desirable to have a few simple operations available from Inkscape.
:*freely move the perspective vanishing point for each dimension;


This project will use the Inkscape extensions system to add a series of bitmap effects. The majority of the effects will be achieved through the integration of the ImageMagick bitmap handling libraries.  GIMP may be another source. These effects can then be run on bitmap graphics within Inkscape.
:*switch any dimension from a vanishing point to direction (point in infinity, lines are parallel) and back;


The work should be encapsulated in such a way that in theory, other vector graphics applications (such as Xara), could also use the work.  However, for the scope of this project we only require demonstration of the capabilities in Inkscape.
:*Allow subdivision of each face to create perspective grids;


== Text Tool Improvements ==
:*when more than one 3D box is selected and their perspective is compatible, drag their common vanishing points/directions updating all selected boxes;


Inkscape's text tool is handy, but still lacks many of the niceties that users would like.  This project would seek to address this by implementing various improvements that users have requested.
:*3D-rotate the entire selected 3D box (or several selected 3D boxes if they have a compatible perspective), thus moving all 3 directions/vanishing points in a natural way;


Some ideas for improvements:
:*remember the last-set directions/vanishing points and create new objects in the same perspective, so you can quickly and easily draw an entire 3D scene with many boxes.
* Make flowed text respect the default style of the text tool (a simple bugfix)
* When flowing a text which already contains line breaks, provide a way for the line breaks to be conserved
* When the style selected in the the Text and Font dialog is applied it erases any other style applied to some part of the text (like italics on some words, bold on others...), it would also be better to keep them where appropriate.
* Support [http://www.w3.org/TR/SVG11/text.html#TextDecorationProperties text-decoration] (underline, overline, line-through)
* Better respect different faces of fonts (Light, Book, Normal, Black etc.)
* Support justified text - might be some subset of those proposed at http://www.w3.org/TR/css3-text/; see also http://bowman.csse.monash.edu.au/~pmoulder/text-in-shape.tar.gz as a possible starting point.
* Search through the Inkscape RFE list for other text and font improvement ideas


See also: http://valessio.ul-jb.org/projetos/inkscape/inkscribus.htm
:In SVG, a 3D box will be represented as a group with a special extension attribute; the group would contain the 6 quadrilateral paths representing the sides of the box. Only the 3D box tool would treat this object as a whole; for all other tools it will be just a group, so you can select any of the paths, apply any style to it, delete it, etc. At the same time, the 3D tool would still be able to 3D-rotate and 3D-tweak the box while preserving any changed style and not restoring deleted sides (e.g. if you don't want to see the hidden sides, simply delete them as objects from the group).
: The extrude tool in Macromedia Freehand may also be of interest as a way of  creating the appearance of 3D.


<b>Mentor:</b> TBD
* '''3D guides''' can be a helpful addition to the 3D box tool. You would be able to create a new set of 3D guides from any 3D box and then use these guides for drawing with any tool that can snap to guides (e.g. the Pen tool). The guides would use different colors  for the three dimensions. Ideally the guides should remember which object they were created from and update when that object's perspective (the set of 3 vanishing points or directions) is edited in the 3D tool.


* '''Other primitives''': Sphere, Cylinder, Cone, Pyramid ...


== Color Adjustment Dialog ==
* '''Perspective transform tool''' like in the GIMP


Currently, it is possible to select, say, 12 objects in the drawing and set them to the same color/gradient/pattern.  This project would go a step further, allowing multiple objects of differing color to have aspects of their color (such as brightness/contrast, HSL, etc.) altered, and to operate on vector objects with different fill styles (flat, gradient, or pattern fills), and to bitmaps.
* '''Perspective grid tiling''': cloning an object to each field of a grid.


Note: in 0.45, we have a set of extension effects that do this. But they are clumsy and slow. We need this to be in the core of the program with a good interactive UI.  
This is a big and infinitely expandable area. We do not expect any single student to cover all of this in a single summer. You can propose a reasonably useful subset of this functionality as your 2007 GSoC project.


<b>Mentor:</b>  Bulia Byak
<b>Mentor:</b>  Bulia Byak


== SVG fonts support ==


We need SVG font support in order to be able to claim SVG Tiny support. While the occurrence of SVG fonts in the wild seems to be pretty low, we will benefit from this by being able to embed fonts and thus ensure rendering of text without converting it to paths.
=== Live Path Effects ===


<b>Mentor:</b>  ???
As explained on [[LivePathEffects|this wiki page]], Live Path Effects allow arbitrary path-changing effects to be applied to any path object. Inkscape will remember the original path before the transformation was applied, so you will be able to remove the effect, chain several effects on the same path, adjust their parameters, etc. All the effects metadata will be stored in Inkscape-only attributes. At the same time, the resulting visible path (with the effects applied) is saved using pure SVG elements and attributes and thus visible to all SVG renderers, thus upholding Inkscape's basic principle of operation: drawings must look exactly the same in Inkscape as in any SVG-compliant renderer.
 
This approach will allow us to make many of the effects currently implemeted as extensions (in the Effects menu) live and interactive. Path randomization, putting pattern along path, blends, envelopes, various distortions - all these can and should be live path effects, not the clunky, slow, and inconvenient Python scripts. Fortunately, Inkscape architecture makes creating live path effects relatively easy.
 
To complete this project, a student must implement at least several simple effects, propose and create a basic user interface for applying them to paths (Path Effects tool?). Some of the effects that you could start with are:
 
* '''Filleting''' (corner rounding) is common in technical drawing.  While this is a fairly basic drafting task, it's currently not particularly easy to do in Inkscape except for certain cases such as round cornered rectangles.  This effect would apply rounding with a given radius to all or some sharp corners of a path. It should also permit creation of '''chamfers''' which are flattened edges at suitable angles.
 
* '''Fractalize''' is currently a Python effect but would make a great live path effect. It can be useful in <b>mapmaking</b>; maps involve lots of irregular shapes - coastlines, forest boundaries, rivers, etc. that could use fractalization with adjustable level. (As an added bonus, this could be implemented so that the level of fractalization depends on zoom, but preserving this behavior outside of Inkscape would require some smart scripting as explained in this paper: [http://www.svgopen.org/2004/papers/AdaptiveLoD/ Adaptive Level of Detail in SVG].)
 
<b>Mentor:</b>  Aaron Spike
 
=== Inkboard Portability ===
 
Last year we had a successful project to integrate the SVG online whiteboard capability, called Inkboard, into Inkscape.  Unfortunately, it does not work on Windows, so many users are missing out on this capability.
 
This work may involve [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/branches/INKBOARD_PEDRO/src/jabber_whiteboard/protocol/ formalizing and extending the Inkboard communication protocol] and [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/branches/INKBOARD_PEDRO/src/jabber_whiteboard/ working on the INKBOARD_PEDRO branch])
 
<b>Mentor:</b>  Ted


=== New Grids ===


Inkscape currently has square grids that can be snapped to.  Extend this to allow other kinds of grids:  Perspective, hex, iso, etc.


== External Cascading Stylesheet (CSS) Support ==
This will involve modifying the grid code to support the ability to have multiple kinds of grids, implementing at least 3 new grids, and adding the UI elements to allow users to make use of them.
 
Requests in tracker:
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1591386&group_id=93438&atid=604309 Perspective Grid: 2 and 3 point with sample Perl script.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1005753&group_id=93438&atid=604309 Perspective Grid: 1, 2, and 3 point.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1418249&group_id=93438&atid=604309  Hex Grid.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=1365504&group_id=93438&atid=604309 Isometric Grid.]
*[http://sourceforge.net/tracker/index.php?func=detail&aid=900270&group_id=93438&atid=604309 Isometric Grid.]
 
<b>Mentor:</b>  TBD


Inkscape currently has good support for inline CSS, and limited read-only support for an internal stylesheet in a <style> element, and no support for external stylesheets.  Support for editing non-inline CSS would allow better expressiveness and adaptation, and smaller SVG files, and better support for SVG generated by other programs that use non-inline CSS.


<b>Mentor:</b> Peter Moulder
=== Text Tool Improvements ===


== Multi-page Support ==
Inkscape's text tool is handy, but still lacks many of the niceties that users would like.  This project would seek to address this by implementing various improvements that users have requested.


An often requested feature is for Inkscape to support multi-page editing. 
Some ideas for improvements:
Currently, an Inkscape document is set to correspond to 1 printed page. However, the next version of SVG specification (1.2) includes support for [http://jan.kollhof.net/projects/svg/motjuvie/present.xhtml multi-page documents], and lots of people would like to have this capability in Inkscape as well.
* Make flowed text respect the default style of the text tool (a simple bugfix)
* When flowing a text which already contains line breaks, provide a way for the line breaks to be conserved
* When the style selected in the the Text and Font dialog is applied it erases any other style applied to some part of the text (like italics on some words, bold on others...), it would also be better to keep them where appropriate.
* Support [http://www.w3.org/TR/SVG11/text.html#TextDecorationProperties text-decoration] (underline, overline, line-through)
* Better respect different faces of fonts (Light, Book, Normal, Black etc.)
* Support justified text - might be some subset of those proposed at http://www.w3.org/TR/css3-text/; see also http://bowman.csse.monash.edu.au/~pmoulder/text-in-shape.tar.gz as a possible starting point.
* Spellchecking.  Inkscape includes limited spellchecking support based on aspell but it is not enabled by default.  Spellchecking based on enchant could use a much wider range of spellchecking engines and be made more widely available and be good enough to show prominently and enable by default. 
* Search through the Inkscape Request for Enhancement (RFE) list for other text and font improvement ideas. 
 
See also: http://valessio.ul-jb.org/projetos/inkscape/inkscribus.htm


This project would involve several steps:  1)  Add internal support for reading and writing SVG 1.2 <pageSet> and <page> elements.  2) When editing a pageSet, create the visual page frames for each <page>.  3) When exporting to Postscript, have it export each <page> as a separate page in the Postscript file.
<b>Mentor:</b> TBD


(Another frequent request is support for a tabbed interface.  To be clear a tabbed interface is quite a different request from this one and any such Tabbed interface would need to accomodate the requirement of single documents with multiple pages like those proposed in SVG and already existing in PDF, OpenDocument Draw, and many others.)


== ccHost Import/Export ==
=== ccHost Import/Export ===


Allow exporting to, or importing from, a remote ccHost instance.
Allow exporting to, or importing from, a remote ccHost instance.
Line 211: Line 214:


[[LionKimbro]] can help someone spec out the capabilities, interfaces (both programmatic and GUI), and so on.  He's written a little on [[OpenClipArtLibraryIntegration]] already.  cell: 206.427.2545.
[[LionKimbro]] can help someone spec out the capabilities, interfaces (both programmatic and GUI), and so on.  He's written a little on [[OpenClipArtLibraryIntegration]] already.  cell: 206.427.2545.
=== Color Adjustment Dialog ===
Currently, it is possible to select, say, 12 objects in the drawing and set them to the same color/gradient/pattern.  This project would go a step further, allowing multiple objects of differing color to have aspects of their color (such as brightness/contrast, HSL, etc.) altered, and to operate on vector objects with different fill styles (flat, gradient, or pattern fills), and to bitmaps.
Note: in 0.45, we have a set of extension effects that do this. But they are clumsy and slow. We need this to be in the core of the program with a good interactive user interface.
<b>Mentor:</b>  Bulia Byak
== Your own original ideas ==
Original ideas are also welcome but students stand a better chance of getting selected by choosing from the suggested projects and where a mentor is available to supervise the work.  If in doubt contact the developers on the mailing lists. 


= Past Years =
= Past Years =

Revision as of 02:52, 12 March 2007

This year Inkscape is going to participate, yet again, in Google's Summer of Code (SoC) 2007. Help us come up with some solid places to innovate and push forward.

Student Applications

Project Ideas

File formats

Native Import of Encapsulated Poscript (EPS) or Adobe Portable Document Format (PDF)

While SVG is becoming a common format for exchanging data between graphics programs, EPS and PDF are still much more common. Inkscape's current EPS import is brittle, not as well maitained as we might like, and not available for all target platforms as it depends on 3rd party software. The goal is to give Inkscape native EPS or PDF import capability.

Where the code can be borrowed from:

  • For EPS: Scribus' EPS Import Library
  • For both: Ghostscript (though it may be too heavy for us)

The student needs to evaluate these (or other) possibilities, lay out a plan, and implement a native importer in Inkscape, either using an external lib to link to, or just importing the necessary code directly into Inkscape tree (as we did for Potrace). The end result will be Inkscape being able to correctly import a reasonable majority of EPS or PDF files in the wild (we can agree on a more formal conformance test if this idea interests anyone).

Mentor:  ???

Native Import/Export of Corel Draw (CDR) files

Corel Draw was and still is a very popular drawing application and many files exist in the Corel Draw format. The user interface of Corel Draw is more similar in many ways to Inkscape than other graphics software making Inkscape more attractive to Corel Draw artists. We are getting a lot of requests from users to support this format.

While CDR is not an open format, several open source implementations exist, from which you can borrow code:

  • Open source Xara LX can import and export CDR files.
  • sK1 is a Corel Draw lookalike vector editor, at early stages of development but claiming to be able to read CDR files.

A student for this project will need to plan the scope of the feature (we do not need to do all the fancy features, but basics need to be covered) and assemble, with the help of the mentor, a library of sample CDR files for testing.

Mentor: Bulia Byak

Raster Graphics

Inkscape / GIMP Bitmap Editing Integration

Currently, you can embed raster/bitmap images into Inkscape drawings, but editing them is a bit of a hassle because Inkscape isn't really "aware" of external bitmap editing tools.

This project would seek to correct this by modifying inkscape's image embedding code to interoperate more directly with external bitmap programs. For instance, there would be an "open external editor" command that could be used when one or more bitmap images are selected. Another idea would be to include some common bitmap modification commands from the external program, that can be run entirely within Inkscape. A third idea is drag and drop of selections from the bitmap editor to Inkscape, and SVG selections from Inkscape to the bitmap tool.

As a proof of concept, the result should demonstrate this interoperability with GIMP and/or GeGL. Note that the code should be developed such that in theory it should work with any bitmap editor, but we would only require demonstration of working with GIMP.

Also see: http://sourceforge.net/tracker/index.php?func=detail&aid=862655&group_id=93438&atid=604309

Mentor: TBD

Adding bitmap capabilities to Inkscape

While the purpose of Inkscape is to be a vector editor, design in the real world requires dealing with bitmaps too. Inkscape can import the bitmaps, and have them as full canvas objects, but there is no significant bitmap operations in Inkscape. While there is no reason for Inkscape to replicate the functionality of The GIMP, it would be desirable to have a few simple operations available from Inkscape.

This project will use the Inkscape extensions system to add a series of bitmap effects. The majority of the effects will be achieved through the integration of the ImageMagick bitmap handling libraries. GIMP may be another source. These effects can then be run on bitmap graphics within Inkscape.

The work should be encapsulated in such a way that in theory, other vector graphics applications (such as Xara), could also use the work. However, for the scope of this project we only require demonstration of the capabilities in Inkscape.


Scalable Vector Graphics (SVG)

SVG Font support

We need SVG Font support in order to be able to claim SVG Tiny support. While the occurrence of SVG fonts in the wild seems to be pretty low, we will benefit from this by being able to embed fonts and thus ensure rendering of text without converting it to paths.

Mentor:  ???

External Cascading Stylesheet (CSS) Support

Inkscape currently has good support for inline CSS, and limited read-only support for an internal stylesheet in a <style> element, and no support for external stylesheets. Support for editing non-inline CSS would allow better expressiveness and adaptation, and smaller SVG files, and better support for SVG generated by other programs that use non-inline CSS.

Mentor: Peter Moulder

Multi-page Support

An often requested feature is for Inkscape to support multi-page editing. Currently, an Inkscape document is set to correspond to 1 printed page. However, the next version of SVG specification (1.2) includes support for multi-page documents, and lots of people would like to have this capability in Inkscape as well.

This project would involve several steps: 1) Add internal support for reading and writing SVG 1.2 <pageSet> and <page> elements. 2) When editing a pageSet, create the visual page frames for each <page>. 3) When exporting to Postscript, have it export each <page> as a separate page in the Postscript file.

(Another frequent request is support for a tabbed interface. To be clear a tabbed interface is quite a different request from this one and any such Tabbed interface would need to accomodate the requirement of single documents with multiple pages like those proposed in SVG and already existing in PDF, OpenDocument Draw, and many others.)

User Interface for SVG Filters

Filters are a very important SVG capability.

Inkscape has basic support for filters in general thanks to a couple GSoC students' work last year, and more or less complete support for Gaussian Blur. What is needed: (1) adding support for more filters and making sure they work well in combination; (2) designing a UI that will be able to create, view, and modify arbitrarily complex filter stacks.

Mentor: Bulia Byak

Project Timeline:

  • Implement first effect. This involves building Inkscape, linking in ImageMagick and getting one effect written (6 weeks)
  • Implement remaining effects within ImageMagick (3 weeks)
  • Build a test suite for operations and complete all Doxygen documentation of code (3 weeks)

Mentor: Ted Gould


General

3D capability

Inkscape is a 2D drawing tool. However, very often it is used to draw 3D objects. It would be very cool to have more support from the program for doing that, instead of just drawing everything manually. Nothing too fancy - we're not going to compete with Blender; but even simple things can go a long way. What's listed below is just basic ideas; feel free to develop upon them or offer something entirely different in your proposal.

  • A 3D box tool would be able to:
  • draw a 3D box;
  • adjust any of its 3 dimensions by handles and numerically;
  • freely move the perspective vanishing point for each dimension;
  • switch any dimension from a vanishing point to direction (point in infinity, lines are parallel) and back;
  • Allow subdivision of each face to create perspective grids;
  • when more than one 3D box is selected and their perspective is compatible, drag their common vanishing points/directions updating all selected boxes;
  • 3D-rotate the entire selected 3D box (or several selected 3D boxes if they have a compatible perspective), thus moving all 3 directions/vanishing points in a natural way;
  • remember the last-set directions/vanishing points and create new objects in the same perspective, so you can quickly and easily draw an entire 3D scene with many boxes.
In SVG, a 3D box will be represented as a group with a special extension attribute; the group would contain the 6 quadrilateral paths representing the sides of the box. Only the 3D box tool would treat this object as a whole; for all other tools it will be just a group, so you can select any of the paths, apply any style to it, delete it, etc. At the same time, the 3D tool would still be able to 3D-rotate and 3D-tweak the box while preserving any changed style and not restoring deleted sides (e.g. if you don't want to see the hidden sides, simply delete them as objects from the group).
The extrude tool in Macromedia Freehand may also be of interest as a way of creating the appearance of 3D.
  • 3D guides can be a helpful addition to the 3D box tool. You would be able to create a new set of 3D guides from any 3D box and then use these guides for drawing with any tool that can snap to guides (e.g. the Pen tool). The guides would use different colors for the three dimensions. Ideally the guides should remember which object they were created from and update when that object's perspective (the set of 3 vanishing points or directions) is edited in the 3D tool.
  • Other primitives: Sphere, Cylinder, Cone, Pyramid ...
  • Perspective transform tool like in the GIMP
  • Perspective grid tiling: cloning an object to each field of a grid.

This is a big and infinitely expandable area. We do not expect any single student to cover all of this in a single summer. You can propose a reasonably useful subset of this functionality as your 2007 GSoC project.

Mentor: Bulia Byak


Live Path Effects

As explained on this wiki page, Live Path Effects allow arbitrary path-changing effects to be applied to any path object. Inkscape will remember the original path before the transformation was applied, so you will be able to remove the effect, chain several effects on the same path, adjust their parameters, etc. All the effects metadata will be stored in Inkscape-only attributes. At the same time, the resulting visible path (with the effects applied) is saved using pure SVG elements and attributes and thus visible to all SVG renderers, thus upholding Inkscape's basic principle of operation: drawings must look exactly the same in Inkscape as in any SVG-compliant renderer.

This approach will allow us to make many of the effects currently implemeted as extensions (in the Effects menu) live and interactive. Path randomization, putting pattern along path, blends, envelopes, various distortions - all these can and should be live path effects, not the clunky, slow, and inconvenient Python scripts. Fortunately, Inkscape architecture makes creating live path effects relatively easy.

To complete this project, a student must implement at least several simple effects, propose and create a basic user interface for applying them to paths (Path Effects tool?). Some of the effects that you could start with are:

  • Filleting (corner rounding) is common in technical drawing. While this is a fairly basic drafting task, it's currently not particularly easy to do in Inkscape except for certain cases such as round cornered rectangles. This effect would apply rounding with a given radius to all or some sharp corners of a path. It should also permit creation of chamfers which are flattened edges at suitable angles.
  • Fractalize is currently a Python effect but would make a great live path effect. It can be useful in mapmaking; maps involve lots of irregular shapes - coastlines, forest boundaries, rivers, etc. that could use fractalization with adjustable level. (As an added bonus, this could be implemented so that the level of fractalization depends on zoom, but preserving this behavior outside of Inkscape would require some smart scripting as explained in this paper: Adaptive Level of Detail in SVG.)

Mentor: Aaron Spike

Inkboard Portability

Last year we had a successful project to integrate the SVG online whiteboard capability, called Inkboard, into Inkscape. Unfortunately, it does not work on Windows, so many users are missing out on this capability.

This work may involve formalizing and extending the Inkboard communication protocol and working on the INKBOARD_PEDRO branch)

Mentor: Ted

New Grids

Inkscape currently has square grids that can be snapped to. Extend this to allow other kinds of grids: Perspective, hex, iso, etc.

This will involve modifying the grid code to support the ability to have multiple kinds of grids, implementing at least 3 new grids, and adding the UI elements to allow users to make use of them.

Requests in tracker:

Mentor: TBD


Text Tool Improvements

Inkscape's text tool is handy, but still lacks many of the niceties that users would like. This project would seek to address this by implementing various improvements that users have requested.

Some ideas for improvements:

  • Make flowed text respect the default style of the text tool (a simple bugfix)
  • When flowing a text which already contains line breaks, provide a way for the line breaks to be conserved
  • When the style selected in the the Text and Font dialog is applied it erases any other style applied to some part of the text (like italics on some words, bold on others...), it would also be better to keep them where appropriate.
  • Support text-decoration (underline, overline, line-through)
  • Better respect different faces of fonts (Light, Book, Normal, Black etc.)
  • Support justified text - might be some subset of those proposed at http://www.w3.org/TR/css3-text/; see also http://bowman.csse.monash.edu.au/~pmoulder/text-in-shape.tar.gz as a possible starting point.
  • Spellchecking. Inkscape includes limited spellchecking support based on aspell but it is not enabled by default. Spellchecking based on enchant could use a much wider range of spellchecking engines and be made more widely available and be good enough to show prominently and enable by default.
  • Search through the Inkscape Request for Enhancement (RFE) list for other text and font improvement ideas.

See also: http://valessio.ul-jb.org/projetos/inkscape/inkscribus.htm

Mentor: TBD


ccHost Import/Export

Allow exporting to, or importing from, a remote ccHost instance.

In particular, export to the OpenClipArtLibrary, and import from said library (with some search terms, tag words, and perhaps even browsing.)

LionKimbro can help someone spec out the capabilities, interfaces (both programmatic and GUI), and so on. He's written a little on OpenClipArtLibraryIntegration already. cell: 206.427.2545.

Color Adjustment Dialog

Currently, it is possible to select, say, 12 objects in the drawing and set them to the same color/gradient/pattern. This project would go a step further, allowing multiple objects of differing color to have aspects of their color (such as brightness/contrast, HSL, etc.) altered, and to operate on vector objects with different fill styles (flat, gradient, or pattern fills), and to bitmaps.

Note: in 0.45, we have a set of extension effects that do this. But they are clumsy and slow. We need this to be in the core of the program with a good interactive user interface.

Mentor: Bulia Byak

Your own original ideas

Original ideas are also welcome but students stand a better chance of getting selected by choosing from the suggested projects and where a mentor is available to supervise the work. If in doubt contact the developers on the mailing lists.


Past Years