On Thursday, January 19, 2012 5:57:02 AM UTC+7, Terry wrote: > 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.
On Thursday, January 19, 2012 5:00:32 AM UTC+7, Differance wrote: > 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? > Then: make templating something different from clones under @file. Indeed, it strikes me you don't want any clones under @file. But you could implement, and handle distinctly, something like an @template thingie, where you can paste any clones you please, and the purpose of that is to make an external file built out of those pieces, which can dynamically change. Plus, you can have a way of specifying the order of priority processing issues (presently called "clone wars"), maybe a variety of selectable algorithms, associated with @template branches. -------------------- I'm not clear about just how generally the term "templating" applies to all non-coding use cases. >From my experience with HTML, it would refer to the repetitive "site chrome" elements wrapping around the variable content. However say I'm using Leo to manage a large amount of content for a given topic domain, like an encyclopedia. A relatively small proportion of the content needs to be output in more than one place, e.g. an article on the Bangladeshi spotted deer should be available both in the "D" and the "B" volumes. Is that templating? Certainly not related to programming, but IMO it's an appropriate use of cloning - as long as I am careful with my data (and Leo assists me as much as the developers think appropriate). On Thursday, January 19, 2012 3:50:30 AM UTC+7, Terry wrote: > Maybe there's no way to stop people shooting themselves in the foot > with a tool as complex and versatile as Leo - I just think that with > clones they sometimes don't know the gun's loaded until it's too late. Very well put. I recognize that it may be some time before Leo helps protect relatively inexperienced users from making clone-war mistakes. In the meantime I believe some additional clarity in the official docs will at least improve the odds they will be forewarned to tread carefully. -- 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/-/TJ9kxC7-tmQJ. 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.
