On Mon, Jan 18, 2010 at 10:46 AM, Kent Tenney <[email protected]> wrote: > To clarify: > > You are describing a file format which uses Leo sentinels, but > very lightweight ones?
Yes. > In my mind @auto = no sentinels, so when you mention @auto files > with sentinels, I first think of a new directive ... > > @lite myfile.py Possible. It would not be any different behind the scenes than @auto, so we might as well think only of @auto. Yes, this is a change of viewpoint. In the past, I have ruled out sentinels in external @auto files. Now, I think they could be useful, provided the user agrees. But as you say, the user should "agree" by using a per-file mechanism, @lite or @auto/@auto-sent. In my mind, however, the important unanswered questions are: 1. Would the @view scheme really work, and would it be comfortable to use? 2. What kinds of sentinels would be required in @auto trees to give all of Leo's present features. 3. How robust would the @auto read/write code be in the presence of those sentinels. > but that's not the case because what you are describing is entirely > optional, no change to @auto behavior, just providing access to > markup which can enhance the clonability of an @auto file ... I suppose you could say that @view would enhance the clonability of nodes in @auto external files. I would prefer to think of the idea as a way to do without (permanent) clones in @auto trees. The distinction between temporary and permanent clones is close to the heart of the matter. Leo's heavyweight sentinels result in permanent clones. @leo-view sentinels, because they identify views rather than nodes, are less important. In turn, children of @view nodes need not be identified explicitly using heavy-weight sentinels. Edward P.S. I might start out by experimenting with the new lite sentinels to see well they work in practice. EKR -- 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.
