[email protected] schrieb am Sonntag, 31. Januar 2021 um 15:15:13 UTC+1: > Viktor, could you say more about the workflow you are thinking of? For > myself so far, I am happy to keep Leo open in its own app outside a > browser. And I would prefer to avoid running a server on my system to > mediate between Leo and the browser. However, without a server, it's not > really practical to store the Leo outlines on your computer in a way that > you can retrieve using other browsers or programs. (yes, you can use > LocalStorage, but that can only be accessed by the browser that created it, > IIUC. And yes, you can do it if you are willing, say, to use an in-browser > java app, but I don't like that way, either.) >
The closest figure I can provide for my envisioned workflow comes from Jupyter project, describing the 'Jupyter Notebook Interface' [1]. Just exchange 'Notebook' with 'Leo Outline' in every box - and - 'Kernel' with 'Leo'. This is a first, very quick answer from my side. - I'll investigate further on my side as well, where the analogy breaks for Leo ... With kind regards, Viktor --- [1] https://jupyter.readthedocs.io/en/latest/projects/architecture/content-architecture.html#the-jupyter-notebook-interface -- 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/4bc7795a-82bf-4531-a3a8-aee2063143d6n%40googlegroups.com.
