On Thursday, March 24, 2016 at 3:15:18 PM UTC-5, Offray Vladimir Luna Cárdenas wrote:
For me the best scenario is having the structuring capabilities of Leo and > the interactivity of IPython at the **same** time, instead of writing in > Leo, then exporting it and then rendering it in Jupyter. > That would be very cool. > I imagine Leo nodes as markdown/IPython code that can be rendered inside > Leo with the help of QtWebToolkit, so we have the rendering capabilities of > the web/notebook without the constrains of "flat file" thinking. > Today we have a prototype of running Jupyter inside Leo in a QWebView. A new (easy!) render command would: - Create a working/hidden .ipynb file from a Leo node or tree. - Load it as a Jupyter notebook *inside* Leo. Is this the kind of thing you were thinking of? This doesn't try to outdo IPython, this tries to empower it by providing it > with Leo's outlining, DOM and scripting capabilities. > Exactly. We aren't competing with IPython/Jupyter. We are enhancing each other. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
