On Sun, Jul 5, 2009 at 5:36 PM, Edward K. Ream<[email protected]> wrote:
> The best guide, I think, is the picture that brought the unified nodes world > into being several years ago. The picture is of a hand holding seeds. The > fingers are positions; the seeds are nodes. The outline is the hand and the > seeds. We must have both at all times. I've read this before, but admittedly I just don't get it :-). > I hope this clarifies the essence of the situation, namely that in the > one-node world, just as in the present world, the fundamental code in > leoNodes.py must be based primarily on positions, not (v)nodes. Yes, I get it now. Positions are needed for operations that need to know something about the parent to disambiguate which clone we are talking about here. Thanks for clearing this up. However, I still think most of the methods in position could be in node as well (i.e. they are operations that apply equally well to any cloned version). Just to illustrate the issue, some examples: p. at* is* set* clear* copy* .h .b -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
