If one wants to develop a desktop app, then having the two processes (Python process + webruntime) is annoying. Some issues:
You probably don't want to show a window for the Python process. But then you are missing any Python logging / tracebacks, unless you somehow send these back to the webruntime.
If either process is killed, the other should die as well. We've built things to make this work, but its hard, and not bulletproof.
It can be confusing in some cases that the main app is not the thing that provides the window.
You cannot "pin applications to the taskbar", because the process associated with the window is not one of which the executable should be started ...
I'm playing with the idea of defining some sort of API to access the system, which can be exposed via Python or Electron / whatever. Then (Flexx) apps can be created and deployed using Electron or a Gecko-like runtime.
If one wants to develop a desktop app, then having the two processes (Python process + webruntime) is annoying. Some issues:
I'm playing with the idea of defining some sort of API to access the system, which can be exposed via Python or Electron / whatever. Then (Flexx) apps can be created and deployed using Electron or a Gecko-like runtime.