I may have missed it but are there any plans to integrate have a QtWebKit
frame inside Leo itself which could render the ipython/jupyter notebook?
That way you'd never have to leave Leo.
On Thursday, March 24, 2016 at 9:13:56 AM UTC-4, Edward K. Ream wrote:
>
> On Wednesday, March 23, 2016 at 3:55:18 PM UTC-5, Edward K. Ream wrote:
>
> *> Jupyter is Leo's long-sought rendering engine!*
>
> > Folks, this is an Aha on a par with "webs are outlines in disguise"
>
> This post explains why yesterday *might* turn out to be the second most
> important day in Leo's history. More likely, export-jupyter-notebook will
> turn out to be just another cool feature :-)
>
> A day or so ago I remarked to Rebecca that for Leo to become truly popular
> (hundreds of downloads a day), some "young hotshot" would have to talk up
> Leo. Presumably he or she would be a well-connected "star" of some kind.
>
> Better integration with Jupyter notebooks makes that scenario more likely.
> One can imagine an eminent scientist using Leo to create at least the
> documentation part ('markdown' nodes) of Jupyter notebooks.
>
> It is actually quite clumsy to edit markdown nodes on the Jupyter web page:
>
> - Change the node type from 'Markdown' to 'Raw NBConvert'.
> - Make the changes.
> - Change the note type back to 'Markdown'.
> - Re-render the cell by clicking on the 'run cell, select below' icon.
>
> Editing the node in Leo and exporting the entire .ipynb file might be
> automated to be faster than this.
>
> Furthermore, generating html headers automatically in Leo, *based on
> outline level*, is a huge advantage. Just as with the rst3 command, one
> can reorganize a tree of markdown nodes *without* changing html headers.
> And of course, the tree instantly shows document structure, something that
> is *impossible* in Jupyter notebooks.
>
>
>
> *Summary*Leo could become wildly popular not because of what Jupyter
> integration can do for *Leo's* users, but because of what Jupyter
> integration can do for *IPython/Jupyter* users.
>
> Having said that, Jupyter offers a huge amount to Leo, including superior
> rendering. Imo, we must make it as easy as possible to render Leo outlines
> using Jupyter. The export-jupyter-notebook command is the foundation for
> these efforts.
>
> Finally, Leo's viewrendered pane treats markdown as reStructuredText.
> Supporting markdown fully suddenly has very high priority.
>
> 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.
