Object-oriented extension development with play-SVG
Hello developers,
I'm writing to announce the recent re-release of play-svg, a set of python libraries aimed at generative and geometry-based coding for creating SVG files: https://github.com/cosmo-guffa/play-svg, with some minimal documention here: http://cosmo-guffa.github.io/play-svg/ . It includes some Inkscape extensions for plotting various geometric objects as well as many more scripts demonstrating its use. Currently the extensions are undocumented, though most of them are pretty self-explanatory in live preview mode.
My project went defunct in 2009 when the pyxml libraries got canned. I recently decided to dust the project off and get it back up and running. I noticed the Inkscape community implemented the use of lxml and so I decided to do so as well.
I'm realizing that having to install the libraries before using the extensions is an impediment to their use. However, I think that they could serve as a valuable resource for extension developers who want to strip out a lot of the lower-level coding that goes on. Particularly, I've implemented object-oriented creation of paths with some useful helper functions and created an object-oriented interface to creating all svg elements.
What I'm wondering is, would it benefit the project to include play-svg and its extensions in Inkscape ? If so, how could they best integrate ? I would like to preserve the ability to import the libraries in stand-alone scripts for those who have already installed Inkscape. What could I do for the project to make it as high-calibre as the Inkscape software itself ? Your feedback would be greatly appreciated :)
Sincerely, ~Cosmo
Thanks for recovering your old code Cosmo,
On Mon, 2013-07-01 at 16:10 -0400, Cosmo Guffa wrote:
What could I do for the project to make it as high-calibre as the Inkscape software itself ?
I would put your exalted generic object-oriented code into a or the generic python library that python ships. Allowing other extensions to take advantage of your generic work and reducing your own code base liability.
Martin,
participants (2)
-
Cosmo Guffa
-
Martin Owens