I understand. My thinking was that if you decide to move ahead, the IPython (and more generally Jupyter) developers have gone through the careful process (and pain) of designing an integrated, extensible system (tornado, zmq, json, javascript) that may be of use in a more general context. This might give the project a head start instead of having to discover a workable system based on lower-level components.
On Wednesday, January 14, 2015 at 8:50:10 AM UTC-7, Edward K. Ream wrote: > > On Wed, Jan 14, 2015 at 7:43 AM, Brad <[email protected] <javascript:>> > wrote: > >> Can any of the lessons learned and infrastructure from the IPython >> notebook and project Jupyter (https://jupyter.org/ - private >> <https://jupyter.org/>) be of use? >> > > Excellent question. > > I hadn't known about jupyter until just now, but it's derived from > IPython so let's pretend for the moment that similar remarks apply to both. > > I've thought about this question recently. Here are my present thoughts. > > IPython is quite different from Leo. The IPython notebook can and does > write .nb files in a "private" format. Yes, .nb files can be shared, but > the goal of notebooks isn't to create files but to use IPython. > > The collaboration model for IPython and Leo are different. Presumably, > one would not use git on .nb files, though I suppose one could. > > In short, studying IPython's code would be useful *if* we knew we wanted > wLeo, but the success of IPython's notebook does not mean that wLeo is > useful. > > 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]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
