Difference between revisions of "Updating your Extension for 1.0"

From Inkscape Wiki
Jump to navigation Jump to search
(move documentation)
Tags: Replaced Visual edit
 
(13 intermediate revisions by 5 users not shown)
Line 1: Line 1:
This is a preliminary and incomplete list of actions to take for updating Python extensions for Inkscape 1.0:
This was a preliminary and incomplete list of actions to take for updating Python extensions for Inkscape 1.0. It has been moved to the [https://inkscape.gitlab.io/extensions/documentation/authors/update1.0.html extensions repository documentation].
 
== Updating *.inx files ==
 
=== Remove dependency listings ===
 
Remove the dependency listings for the following modules:
 
* bezmisc.py
* coloreffect.py
* cspsubdiv.py
* cubicsuperpath.py
* ffgeom.py
* inkex.py (removal not strictly required)
* pathmodifier.py
* simplepath.py
* simplestyle.py
* simpletransform.py
* more?
 
This change is backwards compatible (as long as the user has a fully functioning Inkscape installation).
Not removing these will result in the extension not being available in Inkscape 1.0 or higher.
 
 
=== Changes to parameter definitions ===
 
There are also some updates to the parameter definitions in .inx files. While these are intended to be backwards compatible to 0.92, you may wish to review the changes as documented in [https://gitlab.com/inkscape/inkscape/merge_requests/808 MR#808].
 
They include:
 
* '''Underscores''' in inx parameter tags and attributes for translation '''can be dropped''' entirely. Use <code>translatable="no"</code> to make an item (e.g.e a unit name) untranslatable.
* <code>boolean</code> can be renamed to <code>bool</code>
* <code><param type="enum" /></code> is deprecated, instead use optiongroups for dropdown selections (comboboxes) and radio buttons (e.g. <code><param type="optiongroup" appearance="combo" /></code>, or <code><param type="optiongroup" appearance="radio" /></code>).
* Appearance value <code>minimal</code> is deprecated
* Choosing files / folders with <code><param type="path" /></code> (these return the path as a string to the Python script):
** Files:
*** Choose a file, with file type restriction (optional): <code><param name="param_file" type="path" mode="file" filetypes="png,jpg" gui-text="A file:">my/path/to/file.png</param></code>
*** Choose multiple files (file type restriction possible, too): <code><param name="param_files" type="path" mode="files" gui-text="Multiple files:">my/path/to/file.png</param></code>
*** Create a new file: <code><param name="param_file_new" type="path" mode="file_new" filetypes="png" gui-text="A new file:">my/path/to/file.png</param></code>
** Folders:
*** Choose a folder: <code><param name="param_folder" type="path" mode="folder" gui-text="A folder:">my/path/</param></code>
*** Choose multiple folders: <code><param name="param_folders" type="path" mode="folders" gui-text="Folders:">my/path/</param></code>
*** Create a new folder: <code><param name="param_folder_new" type="path" mode="folder_new"  filetypes="png" gui-text="A new folder:">my/path/</param></code>
* Color choosers: make them more compact with <code>appearance="colorbutton"</code> for parameters of type <code>color</code>
* Multiline text entry fields are available with <code>appearance="multiline"</code> for parameters of type <code>string</code>
* The following new widgets (static, do not need to be read in by the .py file's option parser anymore):
** <code>label</code>: (<code><label>Some text</label></code>), replaces parameters of type <code>description</code> (which never really were parameters in the actual sense), optionally with <code>appearance="header"</code>.
** <code>hbox</code>/<code>vbox</code>: for layouting purposes (allow to pack child widgets into horizontally/vertically oriented boxes)
** <code><spacer/></code>/<code><separator/></code>: which add a variable space or separating line between child widgets.
** <code><image>my_image.svg</image></code>: which allows to display an image in the extension UI
 
Example file with many of the new features (click on Expand on the right to show):
 
<div class="mw-collapsible mw-collapsed" style="overflow:auto;">
 
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<inkscape-extension xmlns="http://www.inkscape.org/namespace/inkscape/extension">
    <name>Layout Demo</name>
    <id>org.inkscape.test.layout_demo</id>
    <dependency type="executable" location="extensions">pathmodifier.py</dependency>
 
    <hbox>
        <vbox>
            <label appearance="header">Multiple vboxes packed into an hbox</label>
            <hbox>
                <vbox>
                    <label>Vertical stack</label>
                    <param name="param_bool" type="bool" gui-text="Boolean">true</param>
                    <param name="param_int" type="int" gui-text="Int:" >12345</param>
                    <param name="param_float" type="float" gui-text="Float:">1.2345</param>
                    <param name="param_color" type="color" appearance="colorbutton" gui-text="Color:">0x12345678</param>
                </vbox>
                <spacer />
                <vbox>
                    <label>Vertical stack with separators</label>
                    <param name="param_string" type="string" gui-text="Single line string:">a string value</param>
                    <separator></separator>
                    <param name="param_string_empty" type="string" gui-text="Empty single line:"></param>
                    <separator></separator>
                    <param name="param_string_multiline" type="string" appearance="multiline" gui-text="Multiline string:">a\nmultiline\nstring\nvalue</param>
                </vbox>
                <spacer />
                <vbox>
                    <label>Vertical stack with spacers</label>
                    <param name="param_file_new" type="path" mode="file_new"  filetypes="png" gui-text="A new file:">my/path/to/file.png</param>
                    <spacer />
                    <param name="param_file" type="path" mode="file" filetypes="png,jpg" gui-text="A file:">my/path/to/file.png</param>
                    <spacer />
                    <param name="param_files" type="path" mode="files" gui-text="Multiple files:">my/path/to/file.png</param>
                    <spacer />
                   
                </vbox>
                <spacer />
                <vbox>
                    <label>Vertical stack with expanding spacer</label>
                    <spacer size="expand"/>
                    <param name="param_folder" type="path" mode="folder" gui-text="A folder:">my/path/</param>
                    <param name="param_folders" type="path" mode="folders" gui-text="Folders:">my/path/to/file.png</param>
                    <param name="param_folder_new" type="path" mode="folder_new" gui-text="A new folder:">my/path/</param>
                </vbox>
                <spacer />
                <vbox>
                  <label appearance="header">An image!</label>
                  <image>ink_icon.svg</image>
                  <spacer />
                  <label appearance="header" indent="1">Indented header</label>
                  <spacer />
                  <label>For details please refer to</label>
                  <label appearance="url" indent="1">https://clickable.url</label>
                </vbox>
            </hbox>
        </vbox>
    </hbox>
 
    <effect needs-live-preview="false">
        <object-type>all</object-type>
        <effects-menu>
            <submenu _name="Test"/>
        </effects-menu>
    </effect>
    <script>
        <command reldir="extensions" interpreter="python">do_nothing.py</command>
    </script>
</inkscape-extension>
</pre>
</div>
 
== Updating *.py files ==
 
=== Collecting the options of the extension ===
 
# Instead of <code>inkex.Effect.OptionParser.add_option</code>, your extension should now use <code>inkex.Effect.arg_parser.add_argument</code>.
# The 'type' option now works with variables instead of strings. Use <code>int</code> instead of <code>"int"</code> (same for float,...).
# The 'inkbool' type is now <code>inkex.inkbool</code>.
# <code>action="store"</code> can be removed.
 
These changes are not backwards compatible. The old options will still work, but are deprecated and should no longer be used when you develop your extension for Inkscape 1.0 or higher.
 
=== Replace specific functions ===
 
# <code>pathmodifier.zsort()</code> is now <code>inkex.zsort()</code> (more info: https://gitlab.com/inkscape/extensions/issues/24).
 
Lots more, someone needs to flesh this out.
 
=== Test run your extension ===
 
Many functions, when run, will still work, but they will give you a deprecation warning, with instructions what to replace them by.
 
E.g. <code>inkex.Effect.selected</code> is replaced by <code>inkex.Effect.svg.selected</code> - however, most replacements do not follow this naming scheme translation.
 
These changes are not backwards compatible.
 
=== Python 3 / Python 2 compatibility ===
 
Test your extension with both Python 2 and Python 3. With the updated extensions, Inkscape does no longer require Python 2, so some users will probably be using Python 3, and may no longer have Python 2 installed on their system. See [[Extension_Interpreters]] for how to set the Python version for your extension (for testing).
 
== Getting your extension added to Inkscape's stock extensions ==
 
Inkscape now has a [https://gitlab.com/inkscape/extensions separate repository for its Python extensions], which is included into Inkscape proper by using a Git submodule.
 
=== Writing tests ===
 
Previously Inkscape didn't require any unit testing for code. You should now write test code, if you expect your module to be included into the Inkscape extensions repository and included in the shipped Inkscape release. In this case, a test suite file should be made in the tests directory for your extension. It should test each aspect of your extension and exercise all assumptions.
 
If you are writing a standalone extension that users will install themselves, there is no strict requirement for tests. But having them will greatly improve your code and your ability to upgrade the code later. You can have tests in your own folders and use the extension's setup.py as a harness to run them (a setup.py file is also useful for installing your python code as a non-inkscape related python module, which might be useful too). See Python documentation for creating packages.
 
=== Documenting your extension ===
 
TODO
 
== API documentation ==
 
The [https://inkscape.gitlab.io/extensions/documentation/ inkex API documentation] collects the inline documentation comments into a single document.
 
== Submitting your extension for inclusion ==
 
Visit https://gitlab.com/inkscape/extensions, fork the repository, and create a merge request on GitLab.
 
[[Category:Extensions]]
[[Category:Extensions]]

Latest revision as of 19:02, 3 March 2022

This was a preliminary and incomplete list of actions to take for updating Python extensions for Inkscape 1.0. It has been moved to the extensions repository documentation.

Retrieved from "https://wiki.inkscape.org/wiki/index.php?title=Updating_your_Extension_for_1.0&oldid=120963"