Jeremy, I second the multiple tag idea, and I will give my use case ideas below
> >> * I'd love multiple tag fields, ie for different types of tags because: >> - it would simplify filtering a lot (I think). >> - it would "allow" users to tag *plugins *freely without mutilating the >> original tags >> - and the obvious, it would allow you to generally separate between tag >> types >> I get the impression a "multiple tag fields" feature is more suitable for >> core than as a plugin becaue it is such an integral feature. I've seen >> requests for this but there hasn't really been any solution. Tobias did >> create TagSearch <http://tobibeer.tiddlyspace.com/#TagSearch> plugin >> and, wonderful as it is, it seems to be a circumvention to make the best of >> what is possible. I can't comment on how to code this but interface wise - >> if you allow me to be a tad too intricate for this bullet list - tag fields >> (eg. in searches) could perhaps be on the form "tiddler.tags3.contain..." >> (for tag field 3), and the default field could perhaps be reached both via >> "tags1" and "tags". A plugin might be the more appropriate way to give >> aliases (eg "Prioritytags", "Systemtags" etc). In edit view, adding a tag >> field could be with a simple [+] (with label "add tag field") close to the >> default single tag field. Well, you get it. Sorry if this bullet point is >> too intricate and if I'm using the wrong lingo in my layman descriptions. >> > > Interesting. It sounds as though you are envisaging multiple fields on a > tiddler each with the behaviour of the existing 'tags' field, and the > ability to specify which tags field is used for a given operation. I think > that's possible but I'd be keen to make sure that I understand your > intended use cases better: can you give me a few examples of operations > that would be easier to accomplish with this feature? > Use cases: In a to do list: a field for priority tags (urgent), a field for context tags (@home, @work), a field for project tags (Car renovation, learning and growth), etc In an inventory: a field for topic tags (books, DVDs, etc), a field for location tags (top file drawer, under the sofa cushion, etc), etc Recipes: a field for ingredient tags (bacon), a field for recipe type (side dishes, beverages) Music inventory: a field for artist tags, genre tags, etc. History: a field for people, for ideas, for movements, for time periods, for events, etc I would say that most tiddlers would have a small number of tags, no matter how many custom tag fields you add to edittemplate. So I don't think the viewtemplate would need to change. It would just show all tags for that tiddler. But yes it would be very very helpful to be able to create custom tag fields for the edittemplate as needed. I would argue that it should be a plugin, in order to keep 5 simple to look at for new users, and that we who monkey around with it could create TiddlyWiki 5 adaptations designed for particular uses such as the above. But personally for myself, if it were core that would be fine by me. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
