On Thu, 19 Sep 2013 15:04:18 -0700 (PDT) "Edward K. Ream" <[email protected]> wrote:
> On Thursday, September 19, 2013 12:12:52 PM UTC-5, Fidel N wrote: > > IMO, directives should also be attributes of a node. > > Sorry, but directives are inheritable, so directives are attributes of > *positions*, not nodes. > > This can cause problems from time to time. For instance, I like to > minimize directives by defining, say, @language rest in the ancestor node > of notes. But when I clone a node and move the clone out of the tree I > have to insert the @language rest in the node. Not a terrible problem: > when I'm done with the note node I just remove the @language rest. Although this is worth bearing in mind, I don't think it bears directly on the proposal. I.e. the proposed change wouldn't interact with the inheritance issues. The OP's proposal was to move '@edit', for example, from v.h to v.u['_attr'] or something like that, and render the node with an icon to show its @editness, rather than in the headline text. Either way, current or proposed, the @editness is stored on v. My thought was that directives aren't going to actually move out of v.h, but appearance wise they could be hidden at least part of the time, replaced with icons or whatever. Cheers -Terry > In short, nodes don't have any "intrinsic" directives, except for those > defined in the node itself. Thus, to determine the directives in effect at > position p, you call c.scanAllDirectives(p) > > HTH. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
