I have worked on the TVPaint-integration. So far I have the workfiles-tool working.
It took me a while to find an approach that was stable and not too difficult :-).
The working is based on a python-wrapper around the tvpaint-app that uses the socketserver-module(py).
With tvp-plugins that are made with the TVPaint-SDK, it is possible to talk to the pythonwrapper.
The wrapper starts tvpaint in a subprocess and keeps listening for commands(like "open the workfile gui"), until the shutdown command is given from tvpaint when it closes..
The whole module(called "python-tvpaint") that contains the wrapper/launcher, also has functions to talk back to tvpaint. (but for now, only when the given plugin is listening..)
It is possible to keep tvpaint accepting commands in a separate thread, but this can crash tvpaint very easily. I have to explore this some more..
Demo of using the workfiles-tool from within TVPaint:

Now proceeding with Load & Creation-functionality,
to be continued...
I have worked on the TVPaint-integration. So far I have the workfiles-tool working.
It took me a while to find an approach that was stable and not too difficult :-).
The working is based on a python-wrapper around the tvpaint-app that uses the
socketserver-module(py).With tvp-plugins that are made with the TVPaint-SDK, it is possible to talk to the pythonwrapper.
The wrapper starts tvpaint in a subprocess and keeps listening for commands(like "open the workfile gui"), until the
shutdowncommand is given from tvpaint when it closes..The whole module(called "python-tvpaint") that contains the wrapper/launcher, also has functions to talk back to tvpaint. (but for now, only when the given plugin is listening..)
It is possible to keep tvpaint accepting commands in a separate thread, but this can crash tvpaint very easily. I have to explore this some more..
Demo of using the workfiles-tool from within TVPaint:

Now proceeding with Load & Creation-functionality,
to be continued...