On Sat, Mar 7, 2009 at 1:17 AM, edgimar <[email protected]> wrote: > > > By "recursive loops", I suppose you mean that the "imported" .leo file > might > > contain @leo nodes. > > I mean, for example, in a.leo we have "@leo b.leo", and in b.leo we > have "@leo a.leo". > (or a->b->c->a, etc...)
We agree. > > > More importantly, imo, there would have to be ways of "unifying" @<file> > > nodes that are intended to refer to the same external file. Such nodes > > should become clones. The problem is, how is that to be done? Leo has > no > > real mechanism to do "cross-file" clones. Furthermore, the so called > hidden > > machinery in, iirrc, @thin nodes, must be merged somehow. > But I'm fuzzy on how the tree structure / node relationships are stored. Leo represents nodes as one or more vnodes sharing a common tnode. > Whatever the case, you would need, for each @leo file, a complete new set > of > data structures for storing node-relationships and text blocks for that > file. Correct. Reading an @leo node would be similar to doing a copy/paste of the included @leo file. I think the challenge would be to know how to deal with the > case when someone wants to clone a node across .leo file boundaries. > Initially, the easiest might be just to forbid clones across .leo > files, but maybe there is some way to do this...? Cross-file clones are conceivable because the gnx's of their vnodes would create a unique, immutable identity. I say 'conceivable': there may be problems that are not apparent now. > > > Rather than having @leo physically importing nodes, I would prefer that > @leo > > simply opens another outline. This would still be useful, and it would > > avoids deep complexity. > > One of the advantages of the 'non-trivial' implementation, as I see > it, would be the ability to search through all of the nodes, including > the nodes of @leo subtrees. If it simply opened another outline, this > would not be possible. True. However, I am still uneasy with the proposal. In replying to your statements, I get, maybe for the first time ever, the impression that perhaps non-trivial @leo nodes might be feasible. But I am in no particular hurry to experiment just now: the list of way-too-long-delayed projects is way-too-long :-) Having said this, a plugin exploring this topic might be interesting. 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 -~----------~----~----~----~------~----~------~--~---
