@Felix: " I'm guessing here Thomas is using the term "leoBridge" 
interchangeably with "leoserver". - correct me if I'm wrong."
Yes, I was unclear in my own mind which one does what, but I knew that 
leoserver opens leoBridge.

Basically, what I want to do is to work on a Leo outline that lives in 
computer A, and I want to sometimes work on it on Computer B without having 
to copy the outline to and from a privileged directory.  At first, I 
pictured the outline open in Computer A, and Leo in Computer B seeing the 
same thing, like an echo.  But then I thought why not have Leo/A be a null 
gui?  Or maybe Leo/A isn't actually needed?

On Wednesday, March 9, 2022 at 8:29:18 PM UTC-5 Félix wrote:

> Hi :)
>
> Here are my thoughts after reading this thread so far, *(English is not 
> my first language so i may still be confused about what is suggested in the 
> setup Thomas is describing)*
>
> > There is no need to duplicate leointeg's logic because Leo *itself* is 
> available remotely. Perhaps the remote Leo needs only two new commands:
>
> leointeg does not do what leo's core does. it only gives what it asked 
> from leoserver to it's "vscode-GUI-api-interfaces". (leojs does though, but 
> still in early beta) 
>
> & I'm guessing here Thomas is using the term "leoBridge" interchangeably 
> with "leoserver". - correct me if I'm wrong.
>
> >1: get a remote outline by name and
> >2: save the remote outline (possibly with another name)
>
> Hmmm. that's already what leoserver does. (*unless the meaning of 
> 'remote' is opposite of what I see it as)* In my mind, the new functions 
> it would need are rather: 
> 1-get a leo file over the wire as a string in a json package, (sent from 
> local clients filesystem to the remote server's) almost akin to a 'paste as 
> root node'
> 2- maybe a "copy root node" (whole outline) - to mirror #1 in opposite 
> direction to save modifications.
>
> Please correct me and/or comment on what I just layed out as my 
> understanding of this subject. :)
>
> Hey btw: Thanks to Thomas for bringing this up now at this point in time, 
> because the thing about this subject, is that i'm considering needing those 
> two functionalities for combining leojs as a new front end for the whole 
> 'leointeg' setup. 
>
> in the meantime, those last few days I'm still working on the nav tab and 
> functionality, and trying to get that going before Edward's 6.6 final 
> deadline !  hehe! :P
>
> Félix
>
> On Wednesday, March 9, 2022 at 2:16:19 PM UTC-5 Edward K. Ream wrote:
>
>> On Wednesday, March 9, 2022 at 11:18:15 AM UTC-6 Edward K. Ream wrote:
>>
>> ...Perhaps the remote Leo needs only two new commands:
>>>
>>
>>> 1: get a remote outline by name and
>>> 2: save the remote outline (possibly with another name)
>>>
>>
>> And maybe commands to list and change the remote working directory. 
>> However, some kind of shell could do this without 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/baa9b965-99a5-461e-b0c2-5ecc42d0a9fen%40googlegroups.com.

Reply via email to