The idea is to fork the IPython/Jupyter code
<https://github.com/jupyter/notebook> and make it the basis of Leo as a web
app.
This has been a great thought experiment, regardless of what happens. It
has given rise to the following ideas:
1. Extend the vr plugin to handle pyplot scripts. A prototype is already
running.
2. Create a server that will showcase .leo files and that will allow users
to share .leo files.
This page <http://leoeditor.com/load-leo.html> could be called a
prototype, but much more work would be necessary.
3. Add features to Leo that would facilitate web development.
It's been useful to study the Jupyter code, for at least the following
reasons:
- The code uses a range of interesting technologies, including the Tornado
<http://www.tornadoweb.org/en/stable/>server.
- We can assume that the code is close to best practices.
- Little code is written in javascript. Most is in Python or .css or jinja2.
- Jupyter has an interesting security model, which allows sharing on sites
like this one <http://nb.bianp.net/sort/views/>.
- Jupyter allows lengthy computations to be run asynchronously.
*Summary*- Adding Leo's features to Jupyter notebooks would be a lot of
work for little gain.
- It is easy for Jupyter users to find and share Jupyter notebooks safely.
- We should investigate ways of having Leo users find and share .leo files
via the web.
Your comments, please.
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.
