On Wed, 18 Jan 2012 17:00:32 -0500 Seth Johnson <[email protected]> wrote:
> First, I think you answered the question: no. But I'm still unclear > what a cross-file clone is. Is it a clone that's in the one leo file, > pointing at external file A, while within the @file branch for > external file B? I was going to say it's a clone which occurs in two @<file> derived files in the same Leo outline. But even occurring in only one @<file> and somewhere else in the outline (but not in an @<file>) can create confusion when the @<file> is modified externally. I suspect external modification is the real bugbear here. > If that's the case, it strikes me that part of the problem is that -- > I think -- the cross-file clone is already being treated like a > templating function -- isn't that what you'd mean by having a clone > for file A inside the @file branch for file B? > > I think templating in that pattern is different from cloning in the > sense Edward uses them. Exactly - Edward uses them for creating views, typically of code although they could be views of other kinds of data. That's what I think you're calling a codebase, although I think the term view is better. But it seems like others are trying to use them to generate output with repetitive elements, presumably because they're unaware of more appropriate tools for doing that, and Leo's clones seem to offer a solution to their problem. In response to your other post, I think providing templating tools in Leo would be a completely unrelated to clones. They'd be more like section references which could refer to content in a much broader range of places (vs. section references referring to content in the node's children). Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. 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.
