On Tue, Feb 6, 2018 at 5:53 AM, vitalije <[email protected]> wrote:
An alternative might be to use interprocess communication between python >> and electron. This might be a client server architecture, or something >> else. >> > > IMHO this is the way to go inter-process communication between regular > python process and electron application. Embedding python into node, (IMHO) > would bring too many complications and gain very little. Using ordinary > python installation for running background process and exposing Leo API > would allow usage of all python libraries including extensions written in C. > Many thanks for these remarks. I think they are spot on. In fact, I trust Leo API could be exposed in a single plugin. In that case > electron application can spawn python process to open Leo using nullGui > with enabled plugin for exposing Leo API. The rest of development would go > in electron app. > This seems like a plan. Our first task will be to run all unit tests in the nullGui. And just for fun (an experiment) we can do a substantial test of node-python: 1. Create a hello-world electron app. 2. Hook up node-python. 3. Run all Leo's unit tests and see what appears in the console. For me, #1 might take the most time, and will likely be the most valuable. *Summary* Running unit tests early in development is a crucial first step, just as it was when developing the console gui. We might get a prototype up and running in a matter of days! Edward -- 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.
