On Sun, Mar 15, 2009 at 10:00 AM, Edward K. Ream <[email protected]> wrote: > > > On Sat, Mar 14, 2009 at 12:23 PM, Ville M. Vainio <[email protected]> > wrote: >> >> On Sat, Mar 14, 2009 at 6:14 PM, Terry Brown <[email protected]> >> wrote: >> >> > vnodes aren't positions though. Durable vnode ids are working for >> > backlinks.py. Vnodes persist until they're specifically destroyed, the >> > "interesting" part is that they can occur at more than one position. >> >> If you are using vnode id's alone, it's not all that different from >> using tnodes that are pointed to by some vnodes. >> >> However, if you are using vnode path (archived position), you can: >> >> - Trace the full vnode path and find the exact position >> - If that fails, just pick up any position that points at the same vnode >> - If that fails, the node is deleted. > > Important note: Ever since the "unified node" world, positions are "fully > expanded". That is, p.stack contains the entire set of ancestor vnodes for > that position. Thus, a position now contains *all* information that could > possibly be archived. >> >> >> While we are at it, perhaps it might also make sense to move >> headstrings to tnodes? > > It may not be perfectly obvious, but head strings are already part of > tnodes.
My interest here was in the xml of the .leo file (not Leo's data model) and the requirement to correlate a tnode to a vnode to determine the head string. I know the correlation can be done, but IMO the value of the XML would be increased if the head string were an attribute of the tnode. > Again, this change was part of the unified node world. Indeed, > when tnodes are separate from vnodes, v.t._bodyString and v.t._headString > contain the body and head text, respectively. When tnodes are part of the > vnode (g.unified_nodes is True), then v.t == v always, and both the body and > head text are part of the vnode. For details, see vnode.__init__ and > tnode.__init__ > > Edward > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
