After reading several posts by Edward about clones and refresh-from-disk command dangers, I've come to the conclusion that I may be using clones incorrectly, or at least having unrealistic expectations for them. One of the features of Leo that attracted me in the first place was the ability to use clones to write data once and see/use it in multiple ways and places. However, after destroying a file that contained cloned nodes because my administrative assistant refreshed her copy of the file from disk, I figured that I need a different strategy.
Edward's comments about using clones to help with work flow makes sense in that context, but it's not what I'm wanting the clones to do. Are my expectations unreasonable? Here's my scenario: Suppose I have a node with information about some file such that right-click>open URL opens the file for printing or whatever... That information link (node) needs to appear in more than one place in the file (the outline) so I cloned the node and had it appear in those other contexts (all within the same plain text file). This actually worked for us for a while until recently when I made a lot of changes to the structure of the file and asked her to refresh the file inside of her Leo file. Ever since then, all the cloned nodes disappeared and the file became essentially useless. 1) Should clones be able to work for this? If not, what other strategy might work? 2) What other strategy should I consider for us to work on and use the same shared file? (No, we can't really use any kind of CVS system. It was all I could do to teach her the basics of using Leo, much less that...) Suggestions appreciated! Best regards, Rob............... -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
