> To me tags are a fundamental feature of tiddlywiki and there are a > range of plugins that address these. I am keen to see native support > for extended tag manipulations so they can be used generically. Such > as with FET, tagsplorer, etc.. in the core.
I'm interested in incorporating some of the functionality of FET and tagsplorer in the core, particularly exposing filtering, sorting, listing and templating as wiki macros and interactive user interfaces. By that I mean that you ought to be able to write wiki text to, say: 1) pick out all tiddlers from the last seven days that are tagged 'alpha' and 'beta' but not 'gamma' 2) remove any tiddlers that contain the word "beta" 3) sort them by date 4) push the first 10 of the resulting tiddlers through a given template tiddler that includes <<view>> macros to display the matching tiddlers in an arbitrary format The interactive user interface would look a bit like the rule editing facilities of email clients, with picklists and '+' buttons to control the filters, sorting and templating. > Allow for Multiple named tag lines ! This sounds like the ability to create custom fields that have the same behaviour as the built in 'tags' field, which has various special behaviours associated with it. I've been thinking along similar lines, but right now, TiddlyWiki5 treats tags specially in much the same way as classic TiddlyWiki. > Allow all tag lines to be referred to at once in search and other > tools, however permit the scope to be limited to a particular tag line > or set of tag lines as required. A tag line could be a specially > tagged tiddler. That makes sense. > Thus the system could have a tagline for system config, excludelists > etc... > Then one could create an object tag line and have tags for task, > contact, video etc.. > Have a status tag line for open closed hold etc.. > of for Subject, or Genealogy relationship etc... I wonder if some of these use cases are equivalent to introducing name spaces to tags, so that behind the scenes we tag things as "system:Config" or "system:Stylesheet", and perhaps only by default giving the user access to tags that have no namespace. > If you edit a tag line the available tags (already used) would only > come from those already used in that tag line not in all tag lines. > That is the native behavior will allow you to use large number of tags > arranged into functional groups. Quite true, the scoping would be useful for simplifying the user interface. > I will keep it as simple as possible so stop now, but does any one see > where this is leading ?, the potential advantage of this approach or a > substantial mistake in this suggestion ? It definitely makes sense. I'm interested in namespace support as an alternative, too. Cheers Jeremy > TonyM > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" 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/tiddlywikidev?hl=en. > > -- Jeremy Ruston mailto:[email protected] http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
