On Monday, March 30, 2020 at 1:04:12 PM UTC-4, Edward K. Ream wrote: > > On Mon, Mar 30, 2020 at 11:08 AM Thomas Passin wrote: > > > There are at least four ways that Leo could be used with Jupyter: > > All four look like the hard way. I tried the hard way several times last > year and I'm not eager for more :-) > > I am interested in a Jupyter plugin for Leo *only *if it leverages > another project's bridge code. Bokeh *might* provide the necessary > leverage. See this page > <https://docs.bokeh.org/en/latest/docs/user_guide/jupyter.html>. I'll be > investigating this topic next. >
Well, here's the thing. How would someone use a Jupyter Notebook with Leo? 1. To look at someone else's notebook. A notebook viewer would do this job at least as well as Leo. 2. To create a notebook in Leo for someone else to look at. It they don't need to be able to execute the code, we could probably serialize VR3's output to a notebook as things stand. No server needed. 3. To let someone else view and execute the code. We could probably still serialize VR3 subtrees to do this, but it would be harder. Note that if we create the notebook, we don't have to understand or execute the %-magic expressions. They are a convenience, not an essential. Once it's been executed and the notebook saved, it's a tricky question whether or not we could use it again in Leo. For that, we would need a much better importer than we have now. 4. To be able to execute code in some language we don't support, like R or Stata, but Jupyter has a kernel for. It would probably be easier to get VR3 working with this other language instead. 5. To be able to execute the code in someone else's notebook. To do this, we would need to be able to handle the %-magic expressions. Obviously that could be done, but I fancy it will take a lot of doing. 6. To work collaboratively with others. This is one benefit of using a Jupyter server, but it would be the hardest to achieve in Leo. And I don't think many of us need to do in very often. Feel free to add to this list, but so far I don't see a strong reason why better import/export wouldn't be enough for almost all needs. -- 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/82cf0079-294f-4fa0-9c25-00d57cd3e06b%40googlegroups.com.
