Difference between revisions of "INX extension descriptor format"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
How an extension must work and how to write an INX file. | How an extension must work and how to write an INX file. | ||
== About the Inkscape Extension Interface == | == About the Inkscape Extension Interface == | ||
Line 8: | Line 6: | ||
After the extension program work it writes the modified SVG to the default output, the Inkscape get this and update the SVG for the user. | After the extension program work it writes the modified SVG to the default output, the Inkscape get this and update the SVG for the user. | ||
== How to Write an INX File == | == How to Write an INX File == |
Revision as of 16:32, 16 November 2006
How an extension must work and how to write an INX file.
About the Inkscape Extension Interface
The inkscape call a program with some arguments and as the last argumet it tells to the extension program where is the temporay SVG file to do the work. The temporay SVG file represents the actual state of the working SVG.
After the extension program work it writes the modified SVG to the default output, the Inkscape get this and update the SVG for the user.
How to Write an INX File
Example:
<inkscape-extension> <_name>{Friendly Extension Name}</_name> <id>{org.domain.sub-domain.extension-name}</id> <dependency type="executable" location="[extensions|{location}]">program.ext</dependency> <param name="{argumentName}" type="[int|float|string]" min="{number}" max="{number}" _gui-text="{Friendly Argument Name}">{default value}</param> <effect> <object-type>[all|{element type}]</object-type> <effects-menu> <submenu _name="{Extension Group Name}"/> </effects-menu> </effect> <script> <command reldir="extensions" interpreter="[python|perl|bash|{some other}]">program.ext</command> </script> </inkscape-extension>