On Fri, Mar 11, 2022 at 1:54 PM [email protected] <[email protected]> wrote:
> It seems to me that this is the simplest thing that could possibly work: > > Write a new Leo method: openFileViaServer(host_address, file_path) > > 1. The command on the remote computer sends an open file request to a > leoserver instance on the host machine. > 2. The server sends back the requested outline, wrapped in a server data > package. > 3. The remote Leo instance unpacks the outline and creates a new commander > for it. > > Saving the file would require another, complementary save command. > Actually, since I'm thinking here of only sending an outline, I suppose > that any file server would do. We don't really need to open the outline on > the host machine. But why not use leoserver, since it is at hand? > > With this technique, an open instance of Leo on the host machine wouldn't > know that the file is being edited on the remote. For my limited use case, > that is probably OK since I presumably wouldn't be changing the outline on > both machines at the same time. If the same outline were open in a Leo > instance on the host computer, then it would notice when the file on disk > has been changed and put up the usual dialog asking if it should reload the > outline. This is just how things work with leointeg (or used to - maybe > Felix has changed it by now). I think that's acceptable. > Yes, this is what I was thinking when I wrote my initial reply. That is, we want the desktop version of Leo to be the "client". 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/CAMF8tS2xNOerd%3DZaHZyFGpzuLz0Cock9DxAvNmBKRxrhBdsOQQ%40mail.gmail.com.
