On Thu, Jan 19, 2012 at 7:11 AM, Seth Johnson <[email protected]> wrote: > On Thu, Jan 19, 2012 at 6:30 AM, HansBKK <[email protected]> wrote: >> 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. > > > I suspect the problems derive from mixing functions. Putting clones > in @file branches is actually something fundamentally different. I > suspect this might resolve the clone wars, but it also should make it > possible for the app to not let users make mistakes -- no bullets nor > dangerous weapons, since clones aren't in @file branches, and are only > in @template branches.
. . . or in regular views, grouped under regular headers. 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.
