On Thu, Sep 14, 2017 at 12:02 PM, Offray Vladimir Luna Cárdenas < [email protected]> wrote:
Happy to see this direction. I think that the best approach to make Leo > > and Jupyter collaborate without one becoming the other. > I'd call it the only approach ;-) As I have said before, the idea is to go from files to services and for > that, I would use the Jupyter Kernel protocol to communicate with Leo, > > making nodes in Leo behave as Jupyter cells, which means that they can > > send calculations to the Jupyter Kernel and get results back that would > > be "output" nodes in Leo. I would start with the Jupyter Client > > documentation [1], making Leo behave as one of such clients. > > [1] http://jupyter-client.readthedocs.io/en/latest/ Thanks for an excellent high-level summary. 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.
