It would be easier to develop directly a specific app which would handle .sif files instead.
And better on a tablet than on a phone, with a Bluetooth mouse, because of usability, ouch…
This is more realistic and would make miracles!
I did some tests on my side with pybind11, starting from studio::App class but no matter what I tried it failed.
The type of the singleton returned by the Instance() is not the same type as the private App() constructor…
We definitely need scripting features…
Yes. My (future) intention is to use libsynfig and libsynfigapp with a new Android GUI app.
Tablets, of course. Phone would be too much limited IMO.
I already did some successful tests a year ago, with SWIG, that allow us to provide multiple languages, if wanted. But I prefer to cleanup some stuff before doing it, in order to provide an API relatively stable.
Something else that could be nice is to provide an OSC compability once the api would be available.
This could permit to use a phone or a tablet as a provider of touch control for the parameters in Synfig.
There are configurable GUI possibilities with OpenStageControl for example or even with external input with PureData.
One click on a layer/parameter and a slider, color selector, switch appearing on the companion phone/tablet.
Also instead of using right-click and a cascade of sub-menus, a circular menu in the style of Fly-Pie could be more intuitive for productivity.