On Thu, Dec 26, 2013 at 11:58 AM, Terry Brown <[email protected]>wrote:
> On Thu, 26 Dec 2013 09:19:07 -0800 (PST) > "Edward K. Ream" <[email protected]> wrote: > > > Part I. Packing @auto and @auto-view nodes. > > Part II. Unpacking @auto and @auto-view nodes. > > It's not clear to me how hierarchy is or isn't represented. The question is not important for @auto nodes. A view is simply a list of nodes, cloned or not. The question *is* important for @auto-view nodes. Mostly, I can't answer it yet--it will depend on how @auto-view works. In both cases, however, the unl's contain information relating to hierarchy: a --> b --> c says that b is a child of a, and c is a child of b (unless we generalize the search algorithm) If we *don't* generalize the unl search algorithm, then a sort operation on unl's can be defined. For example, here is a sorted list of unl's a a --> b a --> b --> c e e --> f e --> g etc. It's kinda like outline order, but not exactly. Even if we *do* generalize the unl search algorithm, we could first "fix" (make static) the unl's so that no searching is required and then apply the sort algorithm. A sorted list of unl's will likely be needed in order to more easily reorganize the imported @auto tree. 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.
