On Wed, Oct 25, 2017 at 12:06 PM, Offray Vladimir Luna Cárdenas < [email protected]> wrote:
> > I have updated #561 to clarify the rationale behind this proposal and > include some links. Thanks for this. The link to the Jupyter messaging protocol <https://jupyter-client.readthedocs.io/en/latest/> was most helpful. As I understand it, you idea is quite simple. It has two parts: 1. Using the Jupyter kernel, we allow people *to do in Leo* what they might otherwise do in the Jupyter notebook itself. 2. After their work is done, we provide a way of writing *the work done in Leo* to a Jupyter notebook (.ipynb) file. This is similar, but not the same as, using Leo's existing .ipynb writer. Does this vision match yours? Here are some initial thoughts. #1 above is non-trivial. As I understand it, the most important part of the messaging protocol, as far as Leo is concerned, is the client - communicating with kernels <https://jupyter-client.readthedocs.io/en/latest/api/client.html> part. The execute, execute_interactive, complete, inspect and history messages have implications for users' work flow. Must Leo emulate Jupyter's QtConsole window directly in the body pane? Previous investigates indicate that that might be quite difficult, even given the source code for the console. Alternatively, the user could mark some body text (say @jupyter) as input to Jupyter. Leo would then direct the output to a "jupyter capable" vr-pane. But perhaps direct emulation of Jupyter's QtConsole in the body pane might be preferable, no matter what the implementation cost. 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.
