my work on the new scripter was/is in this github repository:
https://github.com/aoloe/scribus-plugin-scripterthe most interesting information source is
https://github.com/aoloe/scribus-plugin-scripter/issues/3as you can read in the (currently) last comment of mine, i'm right now testing a new approach using pybind11.
my tentatives can be followed here:
https://github.com/aoloe/cpp-pybind11-playgroundit still looks a bit wild but i'm close to get a prototype that could be used for building a new scripter.
and, with a bit of luck, that repository will transform in a nice manual on how to embed a python interpreter inside of a c++ application.
(imo, this is something that is not well documented, and every project is creating its own solution)
the reason why i'm trying a new approach is this issue:
https://github.com/aoloe/scribus-plugin-scripter/issues/7(we cannot get signals and slot to cross the c++ -> python boundary)
combined with the issue 3 linked above -- which states that the technology used by the scripter created by henning is not supported anymore (and have never really been supported) -- i prefer restarting from scratch, get much inspiration from the wonderful previous new scripter (really, it looks like a very clever solution... even if i could not understand everything!), and produce a new scripter with a very similar API as the so called scripter 2.
i hope to have my tentatives finished by the end of next week and then i could need work with defining the API and porting the code from the scripter 1 and 2 to the scripter 3
ah, please, forget as soon as possible the name scripter 3... if it gets into scribus, it should simply be the new scripter or the pybind11 scripter : - )
To cut a long story short: it's saturday evening, time to party!