On Tue, Mar 31, 2020 at 1:03 PM Thomas Passin <[email protected]> wrote:
I don't see the point of working with Jupyter/ipython in Leo unless we can > actually make use of Leo's strengths. > I agree. Last year we reached consensus that embedding Leo into emacs or vim is a bad idea. Similar logic applies here. Otherwise, Jupyter notebooks are very good, highly developed, and have many > features (like their kernels for other languages and widgets) that we will > never be able to duplicate in Leo. Leo is especially good at at > navigation, viewing, and and modification of the outline, and I don't want > to give that up. > Yes. You and I have been discussing vr3 architecture privately recently. Let's make sure future discussions are here on leo-editor. vr3 looks to be just what is needed. The whole point of thinking about getting Leo to play with Jupyter would be > to be potentially share notebooks with Jupyter users. > I agree. > Otherwise, we can just make Leo notebooks using VR3 or some similar plugin > - I think I'd be happy with that - and we get all the advantages of Leo and > the notebook-style approach. And it would be a lot easier in terms of > development effort. > Imo, vr3 will offer very substantial advantages over jupyter. So now people will have a happy choice: use Jupyter or Leo, whichever best suits their needs. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0x0W%3DuNQyTJHm0SVh0v4uXUxMMXd6Ny4vdEhBj6c9gNw%40mail.gmail.com.
