No touch tags - or flags on tiddlers without editing or changing the tiddler

[TW_Tones]

@nemo

uh… the overuse of “flag” I find detracts from clarity here. “flag” is being overloaded with multiple uses - that one of them is prefixed with “review-” doesn’t really help the overload to me.

The point being a flag is an indicator, as a tag is an indicator of membership of a set. As I said this is a “working title” however the destinction is essential, I dont know how you would do without.

• In this example it is not that I prefixed flag with review-, but that I suffixed review with -flag to call out that title as being a flag. Just as one may tagname-tag. It is used here more to keep clarity in examples and the discussion, not what you would nessasarily implement.

@nemo

I wonder if the whole new “flag” terminology is needed though. Why not just have the existing tag tid have a “tagging” field?

This is an idea worth investigating including @Springer’s idea of blending into the tag concept.

@Springer

And that solution — helpful as it was! — did actually modify the template tiddlers by toggling the presence of the $:/tags/ViewTemplate tag. So if I removed and then re-added the tag to the subtitle view template, the tiddler would be a non-shadow… even if the toggling restored exactly its original shadow contents.

Exactly what I would like to address.

@Springer

to partially override (virtually exclude tiddlers from) the $:/tags/ViewTemplate tag.

I have spent a lot of time in this realm of “problems” enabling exceptions, I have more often that not maintained the $:/tags/ViewTemplate and within that made my code selective. Thus avoiding core changes except the $:/tags/ViewTemplate tag itself.

• Have we made this topic into two rather than one focused issue directly related to the topic?

Here is an example of how I may use my concept of a flag.

Using no touch flags I can create a few flags including “Story, ViewTemplate, Edit Template” and flag the shadow tiddlers involved in each of these, in the order they appear, in the process involved in each of these tiddlywiki “processes” so new and expert users alike can “follow the trail” of tiddlers used in such processes, but reviewing the tiddlers that share a flag. One or more flags on the same tiddler are permissable.

• These flags (the tiddlers defining the flag) can be imported to any wiki (with flags support) and guide the wiki user without touching (modifying) any system tiddler.

I actualy have quitre a deep understanding of these tiddlywiki structures such as "Story, ViewTemplate, Edit Template and cascades etc… However it can still demand a high cognative load to follow such paths searching for how something has being done or to modify it. As a result I would like a flag solution to support this.

• Ultimatly it should be in the core so it is a common mechanisium we can all use.

Whatever the outcome of this conversation I expect I will make a demo and seek support and comment from you all. I have maintained an open mind on all your feedback, but to be honest I have not yet found a reason to deviate far from the original concept. I hope an example / demonstration will prove this to many of you.

A resent trigger to revisit the flags concept Edit tiddler shortcut - #12 by TW_Tones