On Jul 4, 3:51 pm, "Edward K. Ream" <[email protected]> wrote:
> In short, it is the (careful!) combination of positions and (v)nodes > that will make the one-node world work. Let me emphasize that imo very little code will actually have to change in the one-node world. I expect only p.clone and a few low- level vnode methods will change, at least at first. The situation will be similar to the transition to the "unified node" world, way back in Leo 4.0, iirc. That is, the code will still be filled with references to p.v.t and v.t, but these will simply be synonyms for p.v and v respectively. Ditto for tnode iterators, etc. Later, after we are absolutely sure that the one-node world is rock solid, I'll clean away the cruft. But the essence of the situation is that, relatively speaking, *almost no code* will have to change to make the one-node world a reality. In this sense, the recent discussion of the relative merits of positions vs. vnodes should be moot. The relationship between positions and vnodes will remain *exactly* as it was before. If this isn't so, the entire one-node project would become risky. But I expect the project to "just work". We shall see... 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 -~----------~----~----~----~------~----~------~--~---
