On Thu, Jan 19, 2012 at 9:49 AM, Edward K. Ream <[email protected]> wrote: > On Wed, Jan 18, 2012 at 4:14 PM, Seth Johnson <[email protected]> > wrote: > >> You can group clones without regard for what external files they're >> in, willy-nilly, so long as what you're doing is creating views into a >> codebase, wherein files are maintained independently, and never making >> one a clone within another (which is a different purpose). >> >> True? > > Almost. The pattern in leoPy.leo is safe: all views reside either in > leoProjects.txt, the *first* @<file> node in the outline, or in the > outline itself. > > This will be safe, because if you modify any node in an external file, > that modification will "win": the value in the external file will > change the value in leoProjects.txt. Ditto for clones in leoPy.leo > itself, because Leo reads leoPy.leo before any @<file> node.
Okay, if you have the druthers, consider my reply to your subsequent message in relation to this. If views are disallowed within @file branches, then users would not have to remember a pattern like this, right? Here, perhaps the views you currently have in the first @file node would be in a @template node, and either just the separation of templating from @files might all by itself (miraculously if this were true) eliminate the need for users to follow a protocol based on deep understanding, or the @template node might have a feature where the user has to designate how clone wars would be handled. 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.
