On Thu, 14 Sep 2017 10:42:06 -0500 "Edward K. Ream" <[email protected]> wrote:
> I'm always a big fan of this kind of rapid prototyping. I know from > writing the jupyter importer that jupyter notebooks are just json > files. So the first question that comes to mind is whether using the > jupyter api is really easier than writing json "by hand". Having > said that, perhaps you are thinking that using the jupyter api in the > prototype is an essential part of the prototype. Right - my thought is that we want to be able to execute any Jupyter cell, be it in Python or javascript or R or Go or whatever. And making that happen, from software installation to invocation to exposing variables across environments, should be Jupyter's problem, not ours. In that context, I don't see that Leo needs to parse notebook JSON. It needs to make Jupyter read and manipulate notebooks, and having done that, I'm sure it can get/set the source part of cells and get/display the result part of cells. Cheers -Terry -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
