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]
> > 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. > A Jupyter server handles just one kind of cell - those that want code executed. The server executes that code and sends it back to the client. The client figures out how to display and persist it. A server runs a "kernel", and different kernels can handle different languages. If you want Python, you use a Python kernel. If you want R, you use an R kernel. -- 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/00ad3d9f-d28a-4461-b62f-3f9335944515%40googlegroups.com.
