View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016783||Scribus||Scripter||public||2022-04-21 18:05||2022-04-22 07:23|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Summary||0016783: Please making Scripter2 available for use as soon as possible|
|Description||I know Scripter2 is Scribus' new architecture for Scripting.It has been released for many years and I can find introduction on Scribus' offical wiki,even there is an old documentation exists on the web (https://scribus-scripter.readthedocs.org/en/latest/).I think Scripter2 could be easier to hand on for developers switched from InDesign scripting.Unfortunately I can't find a way to access this new feature via existing Scribus releases.So please making Scripter2 available for use as soon as possible, and I can help porting existing Python scripts to the new Scripter.|
|Tags||No tags attached.|
>> I know Scripter2 is Scribus' new architecture for Scripting
Well it was rather an attempt of a new architecture. This experiment was started during Qt4 times. I don't remember exactly why, but that code could not be ported to Qt5 and we have no man power to port it to Qt5... or Qt6. Currently that code is not in a state of running.
afaik, the current scripter is based on code that is very old, unmaintained since it has been published, only used by scribus and no other project, and is very hard to read and understand.
i've tried a few solutions for replacing that part of the code (and modernize the scripter API) and settled on pybind11 which is an amazing piece of software.
i produced a proof of concept, but there is one big issue left: running a script that uses pyqt5 (or pyside2) two times leads to a crash. (there is a ticket for it on github)
||p.s.: now that i think about it: i'm not sure if it's the scripter or the original scripter2 that depends on that obscure piece of software.|