Hello Edward & Thomas, Looking forward how this re-design will evolve.
[email protected] schrieb am Freitag, 18. Oktober 2024 um 17:00:31 UTC+2: I think that a good approach would be to come up with several use-cases or scenarios of how someone would actually use a hybrid Leo-IPython system. It's no different that the case of Jupyter or sage. I stopped supporting Jupyter notebooks in VR3 for the reason that I couldn't come up with one, at least one that wouldn't take a huge amount of work. In the case of Jupyter notebooks, it's obvious that the input and output blocks could become Leo nodes, and Leo would bring a superior way to work with, view, and and handle those nodes. There are two things that stand in the way: 1) code in each Jupyter input node has access to the variables computed by earlier nodes, and 2) the inline display of graphics. There is also trickiness that about recomputing when the code changes. I can live with the graphics by viewing the notebook with VR3, and I have made fairly extensive notebook-style outlines including code-generated graphics that way. Passing variables from one node to the next would require a serious rethink of how VR3 operates. Since Jupyter is in some sense an elaborate extension of IPython similar points should apply. I don't know about Sage but it too probably fits into that kind of picture. IPython clients communicate with a server process, isn't that right? I know it's that way with Jupyter. I don't know why there couldn't be a Leo client, but it wouldn't be VR3 (and there is no reason why it should be). I have checked the Jupyter documentation - and - have found the following links, which I believe will answer the question & help in the design process: - Jupyter > Projects > Architecture - Projects Overview - https://docs.jupyter.org/en/stable/projects/architecture/content-architecture.html#projects-overview - Jupyter > Projects > IPython - https://docs.jupyter.org/en/stable/projects/ipython_projects.html - Jupyter > Projects > Core Building Blocks - https://docs.jupyter.org/en/stable/projects/core.html - -> Jupyter Client - -> https://jupyter-client.readthedocs.io/en/latest/ Again, the most important starting point is to think through how a Leo client would work from the user's point of view. Once that is understood, we can come to grips with how to make it work. Trying to make something work before understanding a way or ways to make use of IPython support isn't likely to lead to helpful results, in my view. With kind regards, Viktor -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3e4c1fe9-5ca0-461c-8855-4a7217d79aa5n%40googlegroups.com.
