I would try just running a normal basic core extension in the shell.
For example:
org.inkscape.color.randomize.noprefs
( assuming you have used it once in the gui and exited inkscape cleanly - it appears under Extensions>Colour>Randomise )
If it doesn't work - then you know that yours won't either. It is possible for some user made extensions ( well mine anyway ) to fail if they have code that exports ( with open ) etc.
I'm not sure the criteria for that failure though as I have not tested things.
Before Inkscape 1.2, there were verbs ( which required triggering the gui ) and actions. Verbs required --batch-process or --with-gui to function. All filters / extensions were verbs.
So I think it is a hangover from the relatively new move to actions only.
Is it possible to run a extension through the Inkscape shell?
I have written an extension to load an image as SVG make some changes and export it as a PDF file.
This needs to be done for example100 thousand files. Running the extension through the GUI consumes a lot time to complete.
After going through the MAN page of Inkscape, I noticed that --shell command can be used for memory & speed optimizations.
But I'm unable to find out how to run the extension from the shell.
Thanks
I think it's related to this:
https://gitlab.com/inkscape/inkscape/-/issues/3631
@inklinea Thank you for pointing me to this.
Is there any work around for this? Or do we have to wait until it's fixed in the upcoming releases?
@inklinea Thank you for pointing me to this.
Is there any work around for this? Or do we have to wait until it's fixed in the upcoming releases?
I would try just running a normal basic core extension in the shell.
For example:
org.inkscape.color.randomize.noprefs
( assuming you have used it once in the gui and exited inkscape cleanly - it appears under Extensions>Colour>Randomise )
If it doesn't work - then you know that yours won't either. It is possible for some user made extensions ( well mine anyway ) to fail if they have code that exports ( with open ) etc.
I'm not sure the criteria for that failure though as I have not tested things.
Before Inkscape 1.2, there were verbs ( which required triggering the gui ) and actions. Verbs required --batch-process or --with-gui to function. All filters / extensions were verbs.
So I think it is a hangover from the relatively new move to actions only.
I've not tested in 1.3 yet
Thanks for this, even my extension doesn't work that way. Hope it will be fixed in the upcoming releases.