On Tuesday, February 11, 2014 1:20:27 AM UTC-6, nakedmind wrote:
> what if the outline structure of an @auto node is saved as attributes of the @auto node. That is, instead of saving the sentinels in the external file (as what @file does), save the sentinel information as attributes of the parent node. There might be two passes when reading in an external file via @auto. The first pass reads in the file in the usual @auto way. The second pass uses information stored in parent node to rearrange the nodes generated by the first pass. This is what the new auto code does, but instead of using attributes on the @auto node the code creates an @auto-view tree. The advantage of an explicit tree of information is that it could be shared between Leo users. My next post will summarize the strengths and weakness of @file, @shadow and @auto. As will be seen, @file is the clear winner because it retains *all* outline structure. @shadow and @auto cannot hope to do as well, no matter how clever we try to be. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
