On Tue, 6 Feb 2018 03:53:36 -0800 (PST) vitalije <[email protected]> wrote:
> IMHO this is the way to go inter-process communication between > regular python process and electron application. +1 But I'm not familiar with Electron, so I'm not clear what it brings to the table. Leo already is a desktop app., using Python (which we prefer over javascript ;-) and Qt, which is still richer and more versatile than any off the shelf GUI / widget set I've seen for javascript. Electron's big win seems to be allowing people who like to develop in javascript / html / css to build cross platform desktop apps. easily. Of course we need to pick some JS framework, but it seems to me the biggest criteria is how easily it lets us build a Leo UI - menus, tree widget, text editor with syntax highlighting, etc. I would think we want something "modern", Angular, React, Vue are the only ones I know, and of those I've only played briefly with React, and those are more frameworks than GUI toolkits, although there are GUI toolkits for each. To me the big win from Leo with a browser interface is Leo running over a network, i.e. everywhere - of course we'd support running the browser interface locally, but that's seems like a small part of the task and not one that should select Electron if Electron is mostly about running local desktop apps. written in javascript / html / css. But to repeat my opening comment: I'm not familiar with Electron. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
