Inkscape Wiki - User contributions [en]

Source Directory Structure Screaming Architecture

2018-03-29T10:07:13Z

Christoffer:

{{DevDiscussion}}

Another idea concerning the the directory structure for Inkscape's source code. [[User:Christoffer|Christoffer]] ([[User talk:Christoffer|talk]]) 09:43, 29 March 2018 (UTC)

*src
**plugins
***dbus
**entities
***xml
****manipulations
**core
***svg
****manipulations
****transformations
****filters
****rendering
***object (??? not sure what to name this but "object" is too generic)
****containers
****shapes
***util
****numeric
****color
**entrypoints
***gtk3gui
***commandline
***future interfaces
**dataproviders
***file
***http (could go in "entrypoints" instead depending on how http is used, as data provider or as some kind of API to create/modify SVG files)
**libraries
***2geom
***libavoid
***libcola
***libcroco
***libdepixelize
***potrace
***etc.

Source Directory Structure Screaming Architecture

2018-03-29T09:43:02Z

Christoffer: Created page with " {{DevDiscussion}} Another idea concerning the the directory structure for Inkscape's source code. ~~~~ *src **plugins ***dbus **core ***svg ****manipulations ****transforma..."

{{DevDiscussion}}

Another idea concerning the the directory structure for Inkscape's source code. [[User:Christoffer|Christoffer]] ([[User talk:Christoffer|talk]]) 09:43, 29 March 2018 (UTC)

*src
**plugins
***dbus
**core
***svg
****manipulations
****transformations
****filters
****rendering
***xml
****manipulations
***object (??? not sure what to name this but "object" is too generic)
****containers
****shapes
***util
****numeric
****color
**entrypoints
***gtk3gui
***commandline
***future interfaces
**dataproviders
***file
***http (could go in "entrypoints" instead depending on how http is used, as data provider or as some kind of API to create/modify SVG files)
**libraries
***2geom
***libavoid
***libcola
***libcroco
***libdepixelize
***potrace
***etc.

Roadmap

2015-03-31T06:48:40Z

Christoffer: Added strikethrough over doxygen bullet points as that is fixed already at (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)

This is a working document showing specific near-term tasks needed for achieving the numbered milestones. It is '''not a wishlist''' of features to be included in future releases. Because people often work on whatever they feel like, only the current and current+1 releases should be taken seriously. Beyond that is mainly conjectural.

''See [[OldRoadmap]] for milestones that have already been achieved.''

=== Inkscape 0.91 ===

0.91 will be a longer cycle focused on refactoring and new features.

* (DONE) <del>Merge GSoC 2010 work</del>
* (DONE) <del>Evaluate changing the numbering scheme to a date-based one, or setting more realistic goals for major (1.0, 2.0) releases</del>
* (DONE) <del>Port renderer to Cairo (Krzysztof - GSoC 2010)</del>
* (DONE) <del>Completely remove libnr</del>

=== Inkscape 0.92 ~ Infrastructure Focus ===

=== Inkscape 0.93 ~ Maintenance Focus ===

=== Inkscape 0.94 ~ Feature Focus ===

=== Inkscape 0.95 ~ Stability Focus ===

=== Inkscape 1.0 ~ Documentation Focus ===

=== Milestone [Future] ===

=== Random Ideas / Requests / Needs ===

Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.

===== Maintenance =====
* C++11. Initially focus on widely supported C++11 features, then later adopt remaining features as they become widespread.
* Better modularization
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
** Switch to using libgdl as a regular dependency
** Break libavoid out to its own library
** Break libcola out to its own library
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Break libvpsc out to its own library
* Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
* Refactor out "Sodipodi" history
** SPItem, SPObject and other variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers).
* Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)
* Split backend / GUI frontend
* Split out less well maintained extensions to an 'extras' package

===== Infrastructure =====
* Replace VCS.
* Replace Automake Build System.
* Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)
* make msi Windows install multilingual
* Decide which Unit testing framework to use ([http://inkscape.13.x6.nabble.com/Unit-testing-td4967386.html Discussion july 2013 didn't get much traction])
** Greatly expand Unit test framework.
** Set up workflow (passing tests, test coverage, code review) for getting code into trunk.
* <s>Set up autogeneration of Inkscape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
** <s>Put it publicly somewhere on the inkscape domain for "official" access.</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
* Improved mailing list archive
** Move existing archive to inkscape.org or add an archive mirror at inkscape.org ("official" inkscape information is spread out wide between different domains), this would be an improvement.
* inkscape: We need postmaster@inkscape.org and abuse@inkscape.org set up. Maybe as part of a mailing list refresh?

===== New features / Improvements to existing features =====
* Improve support for CMYK/spot colors
* Multi-page documents and parent/child document references
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
* <strike>Using the above mechanism, make flowed text SVG-compliant.</strike>
* Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* Flip y-coordinate to match SVG.
* Hardware acceleration: make use of modern GPUs to speed up rendering.
* Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.
* Mesh gradient support
* CSS support
* Javascript support
* Animation support.
** frame-by-frame interpolations?
** SMIL?
** Javascripts?
** Something else?
* D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)
* Evaluate pdf exporter to join features from scribus Export
** Improved export for printing industry ([http://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/trinity-c6dc9287-cda7-4d8d-9a49-3201dd64f2d1-1412200320248%403capp-gmx-bs01/#msg32887957 Mailing list thread from October 2014])
* Take a holistic approach to UI design ([http://sourceforge.net/p/inkscape/mailman/message/33080043/ Original email])
*# Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.
*# Look around, see how other project solves these things, figure out what's good/applicable for Inkscape (like designing particular custom widgets that are less pixel-hungry etc.).
*# Design some sort of HIG (Human interface guidelines?) for Inkscape
*# Use it to redesign existing dialogs/docks.
*# Preserve dialog layouts between sessions
* For animation and css, a functionality to remove ALL transformations from an SVG
* PDF cleanup function - ungroup everything, remove all unnecessary clipping and masking
* Improved performance
** Start up empty
** Opening an existing file
** Working with large files
** Working with files with lots of filters
* Better marker support
* Object navigator (like in ponyscape)
* New plugin / extension system
** Easy to create
** Powerful enough to do LPEs
* Inkscape for Android
* CAD drawing functionality
* More file format import compatibility
** TopDraw
* OCR of bitmap traces
* Rewrite / reintroduce 3D box.
** 3-dimensional grid, perspective deformed, with snapping

===== Documentation =====
* Introduce new tutorials
* Split tutorials and other content from the main executable, to enable them to be updated independently of our main release process
* Better translations - keep track of % translations for all languages. Drive to 95% on all major languages.

===== Community =====

[[Category:Developer Documentation]]

Roadmap

2014-11-29T19:46:19Z

Christoffer: Added item about Sodipodi history

This is a working document showing specific near-term tasks needed for achieving the numbered milestones. It is '''not a wishlist''' of features to be included in future releases. Because people often work on whatever they feel like, only the current and current+1 releases should be taken seriously. Beyond that is mainly conjectural.

''See [[OldRoadmap]] for milestones that have already been achieved.''

=== Inkscape 0.91 ===

0.91 will be a longer cycle focused on refactoring and new features.

* (DONE) <del>Merge GSoC 2010 work</del>
* (DONE) <del>Evaluate changing the numbering scheme to a date-based one, or setting more realistic goals for major (1.0, 2.0) releases</del>
* (DONE) <del>Port renderer to Cairo (Krzysztof - GSoC 2010)</del>
* (DONE) <del>Completely remove libnr</del>

=== Inkscape 0.92 ===

=== Inkscape 0.93 ===

=== Inkscape 0.94 ===

=== Inkscape 0.9x ===

=== Inkscape 1.0 ===

=== Inkscape 1.x ===

=== Milestone [Future] ===

=== Random Ideas / Requests / Needs ===

Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.

===== Maintenance =====
* C++11. Initially focus on widely supported C++11 features, then later adopt remaining features as they become widespread.
* Better modularization
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
** Switch to using libgdl as a regular dependency
** Break libavoid out to its own library
** Break libcola out to its own library
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Break libvpsc out to its own library
* Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
* Refactor out "Sodipodi" history
** SPItem, SPObject and other variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers).

===== Infrastructure =====
* Replace VCS.
* Replace Automake Build System.
* Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)
* make msi Windows install multilingual
* Decide which Unit testing framework to use ([http://inkscape.13.x6.nabble.com/Unit-testing-td4967386.html Discussion july 2013 didn't get much traction])
** Greatly expand Unit test framework.
** Set up workflow (passing tests, test coverage, code review) for getting code into trunk.
* Set up autogeneration of Inkcape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])
** Put it publically somewhere on the inkscape domain for "official" access.
* Improved mailing list archive
** Move existing archive to inkscape.org or add an archive mirror at inkscape.org ("official" inkscape information is spread out wide between different domains), this would be an improvement.

===== New features / Improvements to existing features =====
* Multi-page documents and parent/child document references
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
* <strike>Using the above mechanism, make flowed text SVG-compliant.</strike>
* Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* Flip y-coordinate to match SVG.
* Hardware acceleration: make use of modern GPUs to speed up rendering.
* Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.
* CSS support
* Animation support.
* D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)
* Evaluate pdf exporter to join features from scribus Export
** Improved export for printing industry ([http://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/trinity-c6dc9287-cda7-4d8d-9a49-3201dd64f2d1-1412200320248%403capp-gmx-bs01/#msg32887957 Mailing list thread from October 2014])
* Take a holistic approach to UI design ([http://sourceforge.net/p/inkscape/mailman/message/33080043/ Original email])
*# Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.
*# Look around, see how other project solves these things, figure out what's good/applicable for Inkscape (like designing particular custom widgets that are less pixel-hungry etc.).
*# Design some sort of HIG (Human interface guidelines?) for Inkscape
*# Use it to redesign existing dialogs/docks.

===== Documentation =====
===== Community =====

[[Category:Developer Documentation]]

Roadmap

2014-11-29T10:40:20Z

Christoffer: Removed the category "others"

This is a working document showing specific near-term tasks needed for achieving the numbered milestones. It is '''not a wishlist''' of features to be included in future releases. Because people often work on whatever they feel like, only the current and current+1 releases should be taken seriously. Beyond that is mainly conjectural.

''See [[OldRoadmap]] for milestones that have already been achieved.''

=== Inkscape 0.91 ===

0.91 will be a longer cycle focused on refactoring and new features.

* (DONE) <del>Merge GSoC 2010 work</del>
* (DONE) <del>Evaluate changing the numbering scheme to a date-based one, or setting more realistic goals for major (1.0, 2.0) releases</del>
* (DONE) <del>Port renderer to Cairo (Krzysztof - GSoC 2010)</del>
* (DONE) <del>Completely remove libnr</del>

=== Inkscape 0.92 ===

=== Inkscape 0.93 ===

=== Inkscape 0.94 ===

=== Inkscape 0.9x ===

=== Inkscape 1.0 ===

=== Inkscape 1.x ===

=== Milestone [Future] ===

=== Random Ideas / Requests / Needs ===

Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.

===== Maintenance =====
* C++11. Initially focus on widely supported C++11 features, then later adopt remaining features as they become widespread.
* Better modularization
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
** Switch to using libgdl as a regular dependency
** Break libavoid out to its own library
** Break libcola out to its own library
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Break libvpsc out to its own library
* Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.

===== Infrastructure =====
* Replace VCS.
* Replace Automake Build System.
* Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)
* make msi Windows install multilingual
* Decide which Unit testing framework to use ([http://inkscape.13.x6.nabble.com/Unit-testing-td4967386.html Discussion july 2013 didn't get much traction])
** Greatly expand Unit test framework.
** Set up workflow (passing tests, test coverage, code review) for getting code into trunk.
* Set up autogeneration of Inkcape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])
** Put it publically somewhere on the inkscape domain for "official" access.
* Improved mailing list archive
** Move existing archive to inkscape.org or add an archive mirror at inkscape.org ("official" inkscape information is spread out wide between different domains), this would be an improvement.

===== New features / Improvements to existing features =====
* Multi-page documents and parent/child document references
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
* <strike>Using the above mechanism, make flowed text SVG-compliant.</strike>
* Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* Flip y-coordinate to match SVG.
* Hardware acceleration: make use of modern GPUs to speed up rendering.
* Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.
* CSS support
* Animation support.
* D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)
* Evaluate pdf exporter to join features from scribus Export
** Improved export for printing industry ([http://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/trinity-c6dc9287-cda7-4d8d-9a49-3201dd64f2d1-1412200320248%403capp-gmx-bs01/#msg32887957 Mailing list thread from October 2014])
* Take a holistic approach to UI design ([http://sourceforge.net/p/inkscape/mailman/message/33080043/ Original email])
*# Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.
*# Look around, see how other project solves these things, figure out what's good/applicable for Inkscape (like designing particular custom widgets that are less pixel-hungry etc.).
*# Design some sort of HIG (Human interface guidelines?) for Inkscape
*# Use it to redesign existing dialogs/docks.

===== Documentation =====
===== Community =====

[[Category:Developer Documentation]]

Roadmap

2014-11-29T10:38:33Z

Christoffer: Added clarification concerning PDF export feature as I see it.

This is a working document showing specific near-term tasks needed for achieving the numbered milestones. It is '''not a wishlist''' of features to be included in future releases. Because people often work on whatever they feel like, only the current and current+1 releases should be taken seriously. Beyond that is mainly conjectural.

''See [[OldRoadmap]] for milestones that have already been achieved.''

=== Inkscape 0.91 ===

0.91 will be a longer cycle focused on refactoring and new features.

* (DONE) <del>Merge GSoC 2010 work</del>
* (DONE) <del>Evaluate changing the numbering scheme to a date-based one, or setting more realistic goals for major (1.0, 2.0) releases</del>
* (DONE) <del>Port renderer to Cairo (Krzysztof - GSoC 2010)</del>
* (DONE) <del>Completely remove libnr</del>

=== Inkscape 0.92 ===

=== Inkscape 0.93 ===

=== Inkscape 0.94 ===

=== Inkscape 0.9x ===

=== Inkscape 1.0 ===

=== Inkscape 1.x ===

=== Milestone [Future] ===

=== Random Ideas / Requests / Needs ===

Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.

===== Maintenance =====
* C++11. Initially focus on widely supported C++11 features, then later adopt remaining features as they become widespread.
* Better modularization
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
** Switch to using libgdl as a regular dependency
** Break libavoid out to its own library
** Break libcola out to its own library
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Break libvpsc out to its own library
* Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.

===== Infrastructure =====
* Replace VCS.
* Replace Automake Build System.
* Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)
* make msi Windows install multilingual
* Decide which Unit testing framework to use ([http://inkscape.13.x6.nabble.com/Unit-testing-td4967386.html Discussion july 2013 didn't get much traction])
** Greatly expand Unit test framework.
** Set up workflow (passing tests, test coverage, code review) for getting code into trunk.
* Set up autogeneration of Inkcape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])
** Put it publically somewhere on the inkscape domain for "official" access.
* Improved mailing list archive
** Move existing archive to inkscape.org or add an archive mirror at inkscape.org ("official" inkscape information is spread out wide between different domains), this would be an improvement.

===== New features / Improvements to existing features =====
* Multi-page documents and parent/child document references
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
* <strike>Using the above mechanism, make flowed text SVG-compliant.</strike>
* Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* Flip y-coordinate to match SVG.
* Hardware acceleration: make use of modern GPUs to speed up rendering.
* Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.
* CSS support
* Animation support.
* D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)

===== Documentation =====
===== Community =====
===== Others =====
* Evaluate pdf exporter to join features from scribus Export
** Improved export for printing industry ([http://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/trinity-c6dc9287-cda7-4d8d-9a49-3201dd64f2d1-1412200320248%403capp-gmx-bs01/#msg32887957 Mailing list thread from October 2014])

* Take a holistic approach to UI design ([http://sourceforge.net/p/inkscape/mailman/message/33080043/ Original email])
*# Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.
*# Look around, see how other project solves these things, figure out what's good/applicable for Inkscape (like designing particular custom widgets that are less pixel-hungry etc.).
*# Design some sort of HIG (Human interface guidelines?) for Inkscape
*# Use it to redesign existing dialogs/docks.
[[Category:Developer Documentation]]

Roadmap

2014-11-29T10:16:45Z

Christoffer: Added infrastructure item about mailing list archive

Roadmap

2014-11-26T18:49:02Z

Christoffer: Added note about doxygen online access.

Roadmap

2014-11-26T18:38:06Z

Christoffer: Added Alexandre's idea about a holistic approach to Inkscape UI

Roadmap

2014-11-26T18:30:55Z

Christoffer: Added some categories to the unordered list of roadmap items.

Roadmap

2014-11-24T13:43:29Z

Christoffer: Added "decision item" concerning unit testing framework and added item concerning workflow to get code into trunk.

Python modules for extensions

2013-05-15T15:19:09Z

Christoffer:

[[Category:Extensions]]

== inkex.py ==

This module encapsulates the basic behavior of a script extension, allowing the author to concentrate on manipulating the SVG data. The module provides an '''class Effect()'''. inkex.py was originally designed to provide the Effect (filter) extension type, but has been used for Input/Output extensions simply by overriding additional class methods.

=== Methods ===
*effect(): override with document processing code.
*affect(): actuate the script.
*xpathSingle(path): an xpath wrapper to return a single node.
*uniqueId(old_id, make_new_id = True): return an id that is unique in the document given a proposed id.

=== Properties ===

*document: DOM document
*selected: a list of nodes that were selected in inkscape
*doc_ids: all of the ids used in the document
*options: options passed to the script

== simplestyle.py ==
Provides methods for dealing with css data embeded in SVG's style="" atribute

*parseStyle(string): Create a dictionary from the value of an inline style attribute
*formatStyle(dict): Format an inline style attribute from a dictionary
*isColor(c): Determine if its a color we can use. If not, leave it unchanged.
*parseColor(c): Creates a rgb int array
*formatColoria(a): int array to #rrggbb
*formatColorfa(a): float array to #rrggbb
*formatColor3i(r,g,b): 3 ints to #rrggbb
*formatColor3f(r,g,b): 3 floats to #rrggbb

*svgcolors: a dictionary defining legal color names and corresponding color values

== simplepath.py ==
Provides functions to round trip svg path d="" attribute data and a simple path format mimicing that datastructure. additional functions for scaling translating and rotating path data.

== cubicsuperpath.py ==
An alternative path representation. access both handles of a node at once. loses a paths open/closed identity.

== simpletransform.py ==

Provides code to easily transform objects.

*parseTransform
:Takes a string such as <tt>rotate(10)</tt> and produces a transformation matrix. If you also supply an initial matrix, the new one will be composed with the old one.
:Available commands: <tt>translate, scale, rotate, skewX, skewY, matrix</tt>. Other examples:
::matrix = parseTransform('rotate(10)')
::matrix = parseTransform('skewY(10)')
::matrix = parseTransform('translate(10 10)')
::matrix = parseTransform(' rotate(10)')
::matrix = parseTransform('translate(700,210) rotate(-30)')

== pturtle.py ==

Provides turtle graphics primitives with svg path data output

== beziermisc.py ==
Utility functions for working with bezier curves

== cspsubdiv.py ==
Decompose a path into polylines

== ff*.py ==

an obscure set of tools for dealing with musical scales.