elliot.white wrote:This is my first attempt at an extension and also the first python program I have written over 20 lines so forgive my naivety.
Nothing to forgive here
- many thanks for writing the extension and sharing it!
In hindsight - Python 2.5.1 is quite old (considering that Python 3.x has been out for quote some time), and most systems probably by now have Python 2.7 (or at least 2.6) installed. I just wanted to give you feedback about my tests (there might have been a chance that you'd just know what the syntax error with 2.5.1 is about, and how to avoid it).
The extensions shipping with Inkscape have been updated and tested to work with Python 2.6, so one can assume that Python 2.6
would be the agreed min. Python version supported (though this is not stated as requirement anywhere). Up to you
elliot.white wrote:I created the Laser Tools group thinking that I would over time produce more extensions, but if you have a suggested group I would gladly put it there.
About the menu name, not sure how to tackle this one - maybe a discussion in a separate topic here in the forum, or on the mailing list (inkscape-devel
) to brain-storm about proposals, with the goal to add some hints/information to the pages in the Inkscape wiki about extensions?
If you think the extension is beyond BETA (nearing release candidate status
) - please consider adding it to the list in the wiki (the Inkscape project doesn't yet have a real extensions repository like e.g. the GIMP has - the best we can do for now is keeping the list updated and add new ones there): Extension repository - Inkscape Wiki
In this comment
(another topic about a new extension) I tried to describe the current options (externally hosted vs. bundled) and how to submit it to get your extension bundled with Inkscape (if you aim for that).
elliot.white wrote:This is the first BETA version so any bug fixes/comments would be welcome
BTW - two tiny notes on the INX file (boxmaker.inx):
- File type declaration: Before 0.47 was released, all extensions shipping with Inkscape got updated to be «now propper XML files with a namespace and all validate against the new inkscape.extension.rng RelaxNG schema.» Maybe you consider changing the first line of your INX file from to
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
- Permissions: with several extensions which have been developed on Windows, I noticed that the INX file (as well as the README file) does have the executable flag set when unpacking the archive (on a unix- or linux-based platform):
this is not needed for the INX file - if at all, only the *.py files need to be executable. The INX files are plain-text XML files, read&write permissions are sufficent for those. Not sure though if and how these file permissions can be set on Windows
Code: Select all
LeWitt:BoxMaker suv$ ls -lFG *
-rwxr-xr-x 1 suv staff 2491 Oct 9 13:00 README.txt*
-rwxr-xr-x 1 suv staff 2351 Oct 7 10:33 boxmaker.inx*
-rwxr-xr-x 1 suv staff 7638 Oct 9 00:06 boxmaker.py*