On Jan 27, 6:07 pm, "Edward K. Ream" <[email protected]> wrote:
> On Wed, Jan 27, 2010 at 8:56 AM, Edward K. Ream <[email protected]> wrote:
>
> >> Every  time a clone node is moved, Leo can evaluate if it becomes an 
> >> external
> >> clone node and if it does and the clone entity has more than one
> >> external clone nodes,
>
> > I absolutely refuse to do this, and I will not accept a plugin that
> > attempts to do this.
>
> I want to say a few more words about this.  The reason I can reject
> this idea so quickly is it implies far-reaching changes to Leo that
> are not needed, and that are not at all pretty.
>
> One could say that the essence of the proposal  is that it would
> change v.isCloned.  Here it is:
>
>     def isCloned (self):
>         return len(self.parents) > 1
>
> Not only is this extremely simple and fast, more importantly, being a
> clone is thus a property *only* of Leo's nodes.  We simply can not
> allow what is now an intrinsic property of data to become an extrinsic
> property of the outlines overall structure.

I understand this, and see no reason why it should change.

> For example, *every* Leo command would have implications for
> cloned-ness.  Changing @thin to @@thin would have global implications.
>  I am not going there.

This is a good point. However, it is relevant only for @file like
commands that affect the internal/external state of a clone node. I do
not think that changes like @this to @@thin (i.e. change from external
to internal) are done often to justify throwing this idea. Also, the
implication of such change (assuming it is not something like @file to
@shadow, which is of no interest from our perspective) is scanning the
sub-tree for clone nodes and incrementing or decrementing their clone
entity's external count. This is probably quite fast (and, I believe,
rarely done).

> Happily, we can devise much simpler approaches to dealing with
> read-time problems.
>
> Edward

Anything simple is good.

Gil

-- 
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.

Reply via email to