> It's an interesting idea. MediaWiki's categories work this way. I imagine
> it's a fairly easy plugin to write. The plugin would need a formatter so
> that (for example) [[tag:SomeTag]] would be ignored by the wikifier. And
> possibly eat surrounding new lines to reduce unwanted whitespace. And a
> hijack of story.saveTiddler to parse the contents of the tiddler and produce
> a list of tags.
AutoTaggerPlugin already does the latter part, i.e., hijacking
story.saveTiddler() and parsing the contents to add tags, so it would
be relatively simple to implement as another feature of that plugin.
However, I'm just not sold on the idea of embedding a special syntax
to surround tiddler content. There are several concerns:
* An 'inline tag' syntax wouldn't actually result in some kind of
corresponding *formatting* of that content. Instead, the result would
look like normal text, but perform a 'side-effect' of setting a tag.
This is unlike other TW syntax that is generally used to format the
content it surrounds.
* The inline tag syntax would have to be something that *never* occurs
in normal content, otherwise inadvertent tagging would occur.
* Tagging that is specified inline could be very hard to spot when
buried within a large block of content (especially if it looks similar
to other kinds of TW wiki formatting syntax), making it difficult to
locate and review or remove a tags from that tiddler without carefully
reading through the tiddler's entire source definition.
* I suppose that AutoTaggerPlugin could remove the inline syntax when
it scans and adds the tags, so that subsequent edits of the tiddler
would show the tags in the usual tag input field and the actual
tiddler source would contain normal text. However, this means that
interaction with the tags input field would still be an integral part
of editing a tiddler, so the use of inline tag specification becomes
just a one-time minor convenience.
Given the concerns noted above, I just don't see where there is a
great advantage to using a special inline syntax to enter tags when
the normal tag input field would still need to be present. Even so,
if you can make a strong case for how this feature would result in a
significant improvement in user interaction during editing, and can
suggest a suitably distinct syntax, I'm willing to add it as an
*optional* feature to AutoTaggerPlugin.
-e