I sort of implemented tags in my rpg.leo project - basically a series of buttons that interacted with the nav pane to search for hashtags, which were simply part of headlines.

It worked, it was simple, and to be honest, I don't think that Leo really needs them. I'm sure there is some functionality that I'm missing out on, though. Perhaps for those who don't wish to maintain lists of clones, or for sorting into groups based on common tags. Perhaps even a view-rendered extension that would render a clickable tag cloud of an entire outline?

-->Jake

On 5/24/2013 11:38 AM, Terry Brown wrote:
Does leo need tags for nodes?

Interface wise I see something similar to the the bookmarks.py
interface, shown in the attached, colored strings indicating the tags a
node has, probably a bit smaller.  Various commands and clicks for
adding or removing tags and navigating through the nodes with a
particular tag, or set of tags.

This would be useful for all sorts of things, but Leo, being Leo,
already has features that overlap functionality wise.  You could
collect clones of all the nodes you want to identify with a particular
tag, under a single parent node, which becomes the tag proxy thing.

You can do something similar with the backlinks.py plugin which provides
unrestricted node linking, just link all the nodes which need a
particular tag to a particular node.

But I'm guessing only a tag centric UI component will give the quick
and easy use you'd want from a tagging system.  Data wise I guess tags
could be a simple list of string, p.v.u['_tags'], with Leo maintaining
an index of tag to node list mappings.

Any thoughts / other software's approaches to look at?

Cheers -Terry


--
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?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to