Chipping in as someone that wrote the (first version) of ipython plugin - there is no way Leo could compete with the current state of Jupyter notebooks. There is deep integration with VS Code, so you get the "full" editing experience from there. There would be tons of work, and probably little benefit compared to "main" Jupyter notebook experience
On Sun, Oct 20, 2024 at 9:17 PM Edward K. Ream <edream...@gmail.com> wrote: > On Sun, Oct 20, 2024 at 8:08 AM Thomas Passin <tbp100...@gmail.com> wrote: > > I think you may be a little hasty here. >> > ... > >> Sage, now, it may look like a shell but it can benefit a lot from >> notebook-like features: >> > > A quick look at IPython's code shows that trying to extract features from > the IPython codebase is a truly terrible idea. > > Every aspect of IPython is bound to the repl. For example, IPython uses > live objects throughout, which means that IPython can offer superior code > completion. But it's not possible to extract IPython's code completion > without extracting the repl! And even if it were possible, the extracted > code could change at the next IPython/Jupyter release. > > It's time to reject this fantasy! > > 1. After our Sage user goes through various math steps and maybe generates >> some graphics, now what? He wants to save that work and be able to look at >> it and pick it up again later! And in the saved work, who wants to save >> the false starts and the syntax errors? >> > > The workaround is to redo the valid steps in another notebook. There may > be automatic ways of doing that. > > A Leo node differs from a console shell in these ways: you can put the >> cursor out of sequence and do editing, you can highlight a block and do >> something with it, you can do something (like recalculate) with the entire >> node, and you can save and restore it. >> > > That's the Siren song. > > So here's the user wanting to do Sage. Type *@language sage* at the top. >> Just like CTRL-B sends the node or a marked part of it to be run as a >> script, the user can do something similar with lines of Sage code. The node >> acts much like, but not exactly the same, as a sage console, or the Jupyter >> Notebook version. Static graphics will be easy to deal with - get Sage to >> save the graphic to a file and Qt can insert that graphic with a cursor. >> The graphic can be persisted at that location by having the Sage handler >> insert an *@image <path>* line; during reload or re-display, the node's >> code re-inserts the graphic the same way it was originally inserted. Of >> course, the user doesn't need to know about that. A bonus is that the >> user could insert any image by manually typing in an *@image* line. >> Another bonus is that VR3 already understands the *@image* directive. >> >> This scenario uses Sage to produce a persistable, editable, rerunable >> version of the Sage console. >> > > Imo, this scenario is infeasible and unwise. I am definitely no longer > tempted by Sirens. > > 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 leo-editor+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS0ayX9nR7WnwhFZk76J2o%3D%3D-boE7ZBjrthH5TK2JqPG-A%40mail.gmail.com > <https://groups.google.com/d/msgid/leo-editor/CAMF8tS0ayX9nR7WnwhFZk76J2o%3D%3D-boE7ZBjrthH5TK2JqPG-A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAPuzRuOPRyRCQZ3kYUO%2BFYLrsQQgA3C6qED4Psz_v55AtaO5ag%40mail.gmail.com.
