Leo Notebooks are easy to imagine, but they would never gain traction because Jupyter is too widespread already.
On Monday, March 30, 2020 at 12:13:04 PM UTC-4, Thomas Passin wrote: > On Monday, March 30, 2020 at 12:08:15 PM UTC-4, Thomas Passin wrote: >> >> 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: >> > [snip] > > Since Leo outlines consist of a graph of nodes, it seems likely that the nodes could be mapped to Jupyter cells in some manner. The nodes in a subtree could be rendered, for example by Viewrendered3 or a similar but specialized plugin. There is no reason to try to duplicate Jupyter Notebook capabilities as Leo outlines, because Leo-format notebooks would never gain traction. Jupyter notebooks are already too widespread. The questions are: what benefit could be gotten by interfacing Leo and Jupyter, and how complicated would it be? -- 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/3ff81d41-1c39-48fd-a1a6-d67ed5e61df0%40googlegroups.com.
