Wishlist: sync nodes to a common repository

On Wed, Jul 13, 2011 at 10:09 AM, Largo84 <email address hidden> wrote:
> Recent discussions here about clones and templates got me thinking
> about possible mechanisms to do more in that area with Leo.

My apologies for the delay in responding.

> The goal:

[Snip]

This seems reasonable. The "repository" becomes the "master" data: the data in the .leo files is, to use an old Leo term, "derived" from the master data.

> Current status:

I think your summary is accurate enough.

> Envision solution:
> There are three capabilities that Leo would need that don't exist
> now that could make this possible:
> 1) A procedure to copy a full path-to-node to the clipboard

Easily done. Naturally, any path can break. In this case the path could break in at least two ways: if the clone repository moved, or if you move the .leo file to a different machine with a different repository path. Both of these could cause problems, but let's assume that you can live with the potential problems.

> 2) A persistent @template-path that is distinct from the
> current @path, but operates in the same way down through its
> respective tree.

Easy.

> 3) Some headline directive (say @t) and a procedure to sync a
> remote copy back to the original.

Easy enough.

> I would be interested to know if this capability is desirable and
> possible.

I think this approach has merit. Certainly, it has no global impact on Leo. Synced nodes are simple ordinary nodes as far as Leo is concerned. They could be cloned as well, probably without any ill effects.

relevant to the SQL thread here?
cross-referencing https://groups.google.com/forum/#!topic/leo-editor/-wBPSW1Dkyo