This is in reply to Plausible's post [1] and I would appreciate some
feedback as to whether or not you would want to see an implementation
for this, too... and if so, which variant.
> Tried a bunch of other tagging plugins
> and now I'm using Tobias's TagSearchPlugin.
> (Tobias: this is neat, though
> making 10 tag tiddlers each itself tagged e.g.
> 'Topic' is more convoluted than
> if one could have 1 tiddler 'Topic'
> with a list of ten tags in it...
> I bet I'm overlooking the pros of your system.)
For a while now, we're able to not just use tags as mere pointers but
also to promote them to first class citizens ...a design tenet of
which I made extensive use in tbGTD [2]. They're a good starting point
if not only to get a list of tiddlers pointing to them.
On the other hand, it is true that your TiddlyWiki were more compact
if your categories in one way or the other only had a reference to the
corresponding category values. So here are some variants for achieving
this.
Variant A) Using a section...
tiddler 'action'
!Tags
#future
#queued
#next
#waiting
#done
...possibly wrapped like this if you didn't want to have them on
display:
/%
!Tags
...
!EndTags
%/
Variant B) Using some field, e.g.
tiddler 'action' {tags:"#future #queued #next #waiting #done")
Variant 3) Save sections in your TagSearchConfig named like the
category that you want to use and put the corresponding values into
that section ...triggered by another parameter, e.g.
cats:TagSearchConfig. Using slices somewhat is not an option as they
must not contain empty spaces, whereas your category titles just
might ...although, one might replace them with underscores and thus
make that work too.
I would tend to prefer 3) ...however, all three alternatives are not
overly difficult to implement, so that might be a welcome addition
giving you the flexibility to only promote tags to first class
citizens when you really want to.
Benefits of all three variants would be that you were able to...
#sort your category values the way you want
#leave out some, perhaps because they're not that important
All three would require you to store categories as a bracketedList
[3].
I would, however, see this as an [either<>or] approach. Thus, if you
devise such a section or field then it will be used; otherwise the
tiddlers tagging to the category tiddler will be used.
Variant 4) would be to allow for all three alternatives, whereas...
cats:@Tags -> lookup section 'Tags' in the category tiddler
cats:%tags -> lookup field 'tags' in the category tiddler
cats:TagSearchConfig -> look for a section corresponding to the
category title in that tiddler
default: Use tiddlers tagging to the category
On the other hand, there would be no known relation between a 'topic'
tiddler and the individual topics, unless other plugins would (be able
to) use the same lookup mechanism as it were implemented for
TagSearch.
So, either this is some form of 'poor man's tagging' or it is a neat
enhacement to bind tags to categories for when you have no desires to
promote your tags to first class citizens. Your call.
Cheers, Tobias.
[1] http://groups.google.com/group/tiddlywiki/msg/ff68dafd4fa2213c
[2] http://tbgtd.tiddlyspot.com
[3] 'foo [[bar baz]] "mumble grotz" fronk'
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" 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/tiddlywiki?hl=en.
