So one idea talked about here is to run the IDE as a separate, possibly browser based process. I propose an inversion of this, run Leo as the separate process, (Leobridge++), then leave all the fiddly UI bits (like completions), to what ever editor you're using as a graphical front end.
Some of the work being done in VScode caused me to have the realization that such an integration may not be as hard as we thought it might be. Think of it this way, editors are built to work on files, well let Leo be the file system! All you need is a tree-like browser in your editor to get at the "files", ie Leo's nodes. Emacs, Vim, VScode all have tree-like file browsers, they just need to be "re-plumbed" to get Leo to open the selected node as if it were a file, (then save any edits back to Leo). It may even be possible to have that plumbing be very dumb, just ship the outline navigation commands to Leo and have it send the resulting outline tree to the editor to "paint" rather that duplicate all the outline handling code in the editor. Tom -- 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.
