On Monday, December 19, 2011 1:57:01 PM UTC+7, Matt Wilkie wrote: > > > Something like this could be useful when using Leo as a tool to study and > deconstruct data from Elsewhere. > ** Preeee*cise*ly ** what I'm currently doing with Leo My "B" branch, contains a "parallel" tree, starting out with a different top-level node and clones of those branches I haven't touched yet. When I want to create an edited version of a given node in the branch, I have to create new parent nodes all the way back to the root; this allows me to replace the "A" branch's nodes with mine freely once they and mine are fellow siblings of the "B" parent.
The @nosent output of the B branch is "diffable" against the original @shadow output from the A branch, only so long as I keep the two structures relatively parallel. I have found however that I end up refactoring, reorganizing the structure, or the text too much to continue doing this for long, but the node's clone marks make it pretty easy to see which of B's nodes are mine vs the originals from A. > Nodes or trees in outline A would be read-only, but still cloneable, while > outline B, containing clones from A, could be a full-fledged Leo citizen. > Not sure what you mean by this. What I'm looking for is the ability to somehow flag all clone-instances of a given node as protected from editing within Leo. That's all that makes sense to me anyway, and my understanding is that - both from the POV of storage and that of Leo's code - there is only one node in both locations so that's all that would be possible. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/_ske5Y7WnHMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
