On Friday, February 19, 2016 at 9:20:30 AM UTC-6, Terry Brown wrote:
> I suspect that the views I create and use are a set of positions selected
> manually. The two cases where I most commonly use views (presented with the
> bookmarks plugin in my case) are leo debugging / coding, where I'll collect
> a set of nodes that form part of a call chain, but very often a gappy
> subset of the callchain, skipping links that just pass through the vars I'm
> following, and Django coding, where you want the python, javascript, css,
> and html that interact collected together rather than in their separate
> sub-subdirs.
>
> So there are views that can't be defined by a codable predicate.
>
Yes, that's exactly how I use clones to gather nodes. As you say, it's a
counter-example. However, one can imagine an attribute that "marks" those
nodes, and in that case there *is* a predicate that describes the nodes,
something like
p.has_leo_attribute(name-of-attribute)
And then the nodetags plugin could show just those nodes, for instance.
Furthermore, if we hoist the selected nodes, another predicate applies:
p.isDescendantOf(root_of_hoist) # doesn't exist yet.
or:
root_of_hoist.isAncestorOf(p)
In short, this discussion has immediate practical implications. I'll say
more asap in another thread.
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 https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
