On Tuesday, March 31, 2020 at 11:44:23 AM UTC-4, tfer wrote: > > There is another option we could consider, rather than full juypter stuff, > just add an Ipython console tab to the log pane. Though not as sexy as > Juypter, it has most of its guts, is embed-able, and has a qt-console > version. >
The thing is, I don't see the point of working with Jupyter/ipython in Leo unless we can actually make use of Leo's strengths. Otherwise, Jupyter notebooks are very good, highly developed, and have many features (like their kernels for other languages and widgets) that we will never be able to duplicate in Leo. Leo is especially good at at navigation, viewing, and and modification of the outline, and I don't want to give that up. The whole point of thinking about getting Leo to play with Jupyter would be to be potentially share notebooks with Jupyter users. Otherwise, we can just make Leo notebooks using VR3 or some similar plugin - I think I'd be happy with that - and we get all the advantages of Leo and the notebook-style approach. And it would be a lot easier in terms of development effort. That's my thinking, anyway. -- 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/46d88cbf-e363-4208-8f45-158dbee17ddd%40googlegroups.com.
