On Monday, March 30, 2020 at 12:06:47 PM UTC-4, Thomas Passin wrote: > > > This thread is for discussion about how or whether Leo might be able to > play with Jupyter. > > I think there are basically four general ways that Leo could interact with > Leo. I'll put them in my next post. See what you think. >
There are at least four ways that Leo could be used with Jupyter: 1. **Import a Jupyter notebook into Leo**. A notebook could be viewed and rendered in Leo. It is not clear why this would be better than using a notebook viewer program, although Leo might make navigation between cells easier than with most other programs. Rendering these notebooks in Leo would be desirable for good readability. It could be done with a modification to Viewrendered 3, or something similar. 2. **Export a Leo tree to a Jupyter notebook**. If Leo could export a tree to a Jupyter-compatible notebook, then work that was done in Leo could be shared with others, and the well-developed software that already exists to view and author notebooks could be used with these Leo-originated notebooks. Exporting would play a role similar to creating Sphinx documents from a Leo tree - it would be a one-way sharing of the rendering and execution results with others. 3. **Combine importing and exporting**. 4. **Build a Jupyter front end client for Leo**. Presumably this would be in the form of a Leo plugin. This would have the advantage that the plugin could make use of Jupyter kernels developed for other languages. Leo would not need to re-invent that wheel. A Jupyter client would not necessarily duplicate everything provided by other clients, such as JupyterLab or the QTConsole. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/d387deab-4b78-4bb6-91a6-8fc3a8f9b353%40googlegroups.com.
