On Thu, Jan 19, 2012 at 4:49 PM, HansBKK <[email protected]> wrote: > On Thursday, January 19, 2012 10:32:48 PM UTC+7, Differance wrote: >> > I'm simply questioning whether the idea/discussion of "templating" >> > should necessarily be confabulated with reducing inadvertent data-loss due >> > to >> > clone-war issues. >> So you can't tell me whether what I'm saying does that or not. > > > I believe it does, however within the context of reducing the danger of > clone-war data loss I would argue for a more general formulation of > "export-only" or "generating" where you use the term templating. > > Within the domain of > a. only generated/exported > b. only read/imported > c. only to those that can be updated either within Leo or externally (aka > "two-way" files)? > > I'm understanding your @template idea as fitting within "a". Is that > correct?
The distinction I'm pointing to is between files that are being dynamically created from parts of other files (templated), versus files that are simply being maintained as individual files in themselves (code being maintained). They could be imported or exported. They could be two-way. Certainly @file files are two-way, and would be in my scheme. I think I just assume two-way-ness as part of the problem, and figure that making templating separate from maintaining code in self-contained distinct files will make it easier to do things like coming up with good ways to handle clone wars and, later, collaboration and versioning, plus make it easier for users to understand what's going on. They are two distinct functions, it seems to me. > My second concern is with what I believe to be an unnecessarily strict > blanket rule > > >> >> keeping clones out of @file branches > > > When the "master source" file is externally modified, my use case > specifically requires one (and only one) instance of the cloned nodes to > remain in an @ <file> branch that allows importing - @shadow in the "b" case > above, optionally @file when "c" is allowed. > > Can that need be made to fit within your @templating scheme? It's not clear what purpose you're serving by that protocol. Can't say. I would ask what files you're trying to put together out of other files, and perhaps you'd have to have separate @file source files. Maybe that's what you're talking about as a "master source" file. >> I'm trying to see if the use case can be implemented by the app in a way >> that doesn't require users to understand clone war issues, that makes what's >> going on more transparent. > > I'm 100% behind that as a general goal for improvement, with helping further > that understanding via more clear documentation on the issue as an "in the > meantime" stop-gap. Maybe something will come of it . . . Seth -- 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.
