Man, talk about throwing a battleship at a tugboat's problem.<p>This is why we get hot new editors that take a gig of RAM to do what a 40 year old editor can do with a dozen megs.<p>If I were to touch a Python GUI app again, I'd probably just use Kivy. <a href="http://kivy.org/#home" rel="nofollow">http://kivy.org/#home</a>
PyOtherSide exists and is maintained<p><a href="https://github.com/thp/pyotherside" rel="nofollow">https://github.com/thp/pyotherside</a>
As the post claims, PySide is a dead project. But PyOtherSide isn't. And, being a Qt frontend, it works really well with most platforms. It would be interesting to see how Electron stacks up against this.
Maybe Brython would have been a better alternative than setting up a whole server...<p><a href="http://www.brython.info/" rel="nofollow">http://www.brython.info/</a>
This seems like a backwards approach - if you want to write Python for Electron you should probably wrap Pepper API in Python, AFAIK Electron supports Pepper plugins because it supports Flash.<p>So compile Python as a Chrome plugin and use Pepper to communicate with DOM.
An alternative to wrapping things in node might be to
use the chrome embedded bindings for python:<p><a href="https://code.google.com/p/cefpython/" rel="nofollow">https://code.google.com/p/cefpython/</a><p>This has the advantage to not have to start a web server -- just make python objects visible directly in JS.
It seems like building around uwsgi, for example, might be easier than interfacing over zmq; and the approach of of using electron to interface with a standalone Python web server is difficult to distinguish from simply opening a browser.
This is what I was hoping Atom would be more like when they released the text-editor. This takes some of the load from the DOM itself. However, I wouldn't limit it just to Python, but anything that can run a web server. There's text editors written in Go who could benefit from having Atom Shell on top of them as one example. There's plenty of use cases out there.
I experimented with this by using python-shell [1], but it in the end it just felt too hacky, and it decided it was best to embrace js instead.<p>[1] <a href="https://github.com/extrabacon/python-shell" rel="nofollow">https://github.com/extrabacon/python-shell</a>
I wonder if Phantompy could be extended to work with Electron as well.
<a href="https://github.com/niwinz/phantompy" rel="nofollow">https://github.com/niwinz/phantompy</a>
So you're running a Chrome window on top of V8/Node.js, and at the same time starting up a WSGI server just to serve your Python application in that browser window.<p>If that doesn't sound completely batshit insane to you, you have a problem. Or you're a Node.js developer.
For me it's not the best approach with server/html.<p>By design too many points of failure for desktop app, too many wrappers.
The gist is clear: it works, it's easier and faster to do, but ...