Hi, Nice to see this theme become alive again, as Jupyter interactive alike experiences combining with Leo outiling alike experience have been discussed before. We could have interactive emergent computing. I have been a log advocate of them and it was the reason I prototyped Grafoscopio[1], after long trying to get such experience using Python based technologies and dealing with a lot of incidental complexity.
[1] https://mutabit.com/grafoscopio/en.html At some point I suggested Leo interacting with Jupyter and other projects not by importing and exporting files from/to them, but by establishing bridges (similar to Pyzo, AFAIK) that let Leo talk with such programs and import results as "@output" cells/nodes. Maybe the vr3 is the missing piece that would allow such interactive outlining computing. I'm having problems these days running Leo on my Manjaro Linux. There is any screenshot to share about how Leo + vr3 plugin looks like, for example, in the context of scientific computing (lets say combining a calculation, an equation, some Markdown/ReST, and a plot?). Cheers, Offray On 31/03/20 6:24 a. m., Edward K. Ream wrote: > Thomas, this post is an indirect response to some of your recent > remarks. There is some chance I understand them now ;-) > > When I awoke this morning I saw that Leo + vr3 looks to be /superior > /to Jupyter! vr3 adds all essential features of Jupyter notebooks and > cells, while retaining Leo's unique features: > > 1. Interleaved @language directives is /way /better than the clumsy > dropdown menu in Jupyter that selects the default view. > > 2. vr3 is aware of outline structure. > > 3. Leo + vr3 naturally retains all of Leo's superior organizational > abilities. > > 4. In the (unlikely?) event that people want to use both Leo and > jupyter, Leo can already import/export with jupyter. > > *No jupyter bridge needed* > > This page > <https://docs.bokeh.org/en/latest/docs/user_guide/jupyter.html> > discusses using bokeh with jupyter. I'm not sure what this page is > getting at, but the page appears moot. > > I had been thinking of resuscitating #1386 > <https://github.com/leo-editor/leo-editor/issues/1386>, but that issue > looks like it can remain a "Won'tDo". > > *Summary* > > Thomas's vr3 plugin makes every Leo node work like an /enhanced/ > jupyter cell. > > All comments welcome. > > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/7d2b9eac-6baa-4cb3-b22c-e1a22163219b%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/7d2b9eac-6baa-4cb3-b22c-e1a22163219b%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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/c1cd7592-9e64-2778-afdc-6151957dbb96%40riseup.net.
