I wouldn't object. You can usually view HTML versions of Jupyter notebooks in VR3 anyway. Jupyter is so evolved by now that it would be a losing battle to try to support all its capabilities, but outside of Jupyter. You can make your own (non-Jupyter but something like) notebooks to some extent with VR3, and I have found capability that useful.
On Friday, August 12, 2022 at 8:02:11 AM UTC-4 Edward K. Ream wrote: > Don't panic: support for .leojs files (see #442 > <https://github.com/leo-editor/leo-editor/issues/442>) will remain. > > The present importer for (special-format!) .json files is dangerously > incorrect. It must either be rewritten or retired. I much prefer the latter > option. Reading (and round-tripping) a *full* file format requires > low-level outline operations that could corrupt the original outline. Imo, > the risks far outweigh the rewards, which are likely to be nil :-) > > At one time, I thought importing jupyter notebooks (.ipynb files) might > allow Leo to evolve into an outline-oriented jupyter editor. Nothing ever > came of the idea. Testing that round-tripping .ipynb files works seems like > a waste of time. Without those tests, the .ipynb writer might corrupt > jupyter notebooks! > > *Summary* > > The .json and .ipynb importers/writers are dangerous. The .json importer > might corrupt Leo's outlines; the .ipynb writer might corrupt jupyter > notebooks. Imo, it's time to retire them all. > > 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/9823e600-0020-4121-91ee-3f3bfc18cf00n%40googlegroups.com.
