On Fri, Feb 26, 2016 at 9:23 AM, 'Terry Brown' via leo-editor < [email protected]> wrote:
Sorry to bring up the "inadmissible" ;-) solutions again, but todo.py > includes icons, of course, and a "go to next todo node" which seems to > cover similar ground to the finding nodes which have open / todo tags. > Yes. todo.py has been in my thoughts. I think it points the way to a new direction for Leo: more visible attributes. In my last post I implied that nodetags.py might make tags visible via icons. Still true, but an optional 'icon' keyword argument to c.cloneFindByPredicate is just too good to pass up. I'll do it today if I can. > > To digress (the real point of my response is the next para :-) I have > scripts which search across a long list of .leo files for open todo items > (using leosax for speed), and generate flattened lists (views) of the same > in various orders. They can now use c.cloneFindByPredicate. > Further, UNLs pointing into the (possibly unloaded) leo file containing > the real todo node are stored on the shadow todo items in the collected > lists and changes to attributes trigger loading of the target file and > change of the corresponding attribute on the real todo node. Cool. > Still think the "declutter" machinery might work for this - basically it > applies "beyond stylesheet" style / visualization changes to nodes, > currently it uses rules like this: > > # remove @clean etc. and use an icon > RULE ^@clean (.*) > REPLACE \1 > ICON file_icons/file_clean.png > RULE ^@auto (.*) > REPLACE \1 > ICON file_icons/file_auto.png > I think we may be converging on something really cool. > So all it needs is a different sort of RULE that looks into p.v.u, maybe a also variant that deals specifically with tags, seeing I'm guessing any generic rule for getting into p.v.u['path']['morepath']['list_of_strings'], which worth having, may be cumbersome of the specific case of tag driven icons. I don't have time to follow this in detail, but it's clear that p.v.u can handle whatever data we want to store. c.cloneFindByPredicate is only one way of creating "views". Otoh, I suspect that your RULE's are equivalent to predicate, perhaps more dynamic. I am quite sure that we are about to get something spectacular. Good work, Terry, Richard and all of us. 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.
