We may have discussed .leo.ipynb files before. But I'm pretty sure this is a new Aha.
*The Aha* We could design a (json) file format for Leo that would "masquerade" as a jupyter notebook. This would instantly give us access to all of the "trust mechanisms" of the jupyter project! It would also give us all the *other* aspects of the jupyter project, including access to all the various kernels that jupyter provides. *The format of .leo.ipynb files* .ipynb files are json, so they naturally support nested data. It should be possible to design a format that: 1. Will load as a "vanilla" jupyter notebook. 2. Will *naturally *represent .leo files. In fact, the .ipynb file format is flexible. We could use as many .leo.ipynb file formats as we like. *Summary* .leo.ipynb files are not just a way to "play better with jupyter". .leo.ipynb files allow us to use jupyter's capabilities, including jupyter's trust mechanisms and kernels. .leo.ipynb files could also support a jupyter plugin for Leo. 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.
