Hi, On 21/06/19 11:53 a. m., Edward K. Ream wrote: > There might be a third way: some kind of client/server interaction > between Leo and pyzo/yoton. > > Yoton, pyzo's communication infrastructure, is worth learning and > playing with on its own. Communication between Leo and other programs > will likely be a big part of Leo's future. > > > Scripts run in an external environment can't be Leonine. They could > be given access to c, g and p, but they could not control Leo without > heroic measures. > > Not a gotcha. Most people use scripts for purposes unrelated to Leo! > Pyzo allows scripts to run in the background. Leo could (and should) > do this too. Such *Leonine background scripts* would not be able to > control Leo either.
Happy to see this "Leo as a service" exploration. I have advocate for it since... well years... particularly to have an interactive outlining experience (at that time I compared interacting with the external world via files, versus interacting with it via services). But I think now is the time when such idea is coming more naturally here. Maybe a Yoton playful prototype that connects Leo with IPython or something like that will be soon on the horizon. Congrats about 6.1 and the happy prototypes from this year. Cheers, Offray -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/af8d03c0-d1b5-6e65-7fb6-470dc2bb9d11%40riseup.net. For more options, visit https://groups.google.com/d/optout.
