Tag ($:/tags/ViewTemplate) allowed to "disregard" some tag-children

[TW_Tones]

Looking at this example really makes me think the correct term is delisted not unlisted. However you are listing it, all be it via a special view.

• delist suggests its listed and you are stoping it to be listed.
• unlist suggests its permanently removed from the list.

Although I have not participated 100% in this conversation (sorry) I would favor a field in any tag field called delist-filter where in the logic can determin when and if to delist something. For example what it we wanted to hide the subtitle on tag tiddlers, we may place a filter;
-[all[current]is[tag]then[$:/tags/ViewTemplate/Subtitle]] in the tag tiddler $:/tags/ViewTemplate this would delist only $:/tags/ViewTemplate/Subtitle on $:/tags/ViewTemplate

• Critical here is its almost trivial to be drawn to $:/tags/ViewTemplate if something so tagged is not being displayed, and here we find it is delisted only of tag tiddlers.

If this method (or another) was implimented it would be trivial to add something to the tag pill to inform the user of the fact there is a delist filter present. For example to my reimagin tags solution. One would only need to click on the tag pill to be informed a delist filter is present.

There is another way to do this and I will give it some thought. the idea in the above example is to add the delist-filter to $:/tags/ViewTemplate/Subtitle and have a fieldname of $:/tags/ViewTemplate/

• We can then see which tag the current tiddler is delisted from (allowing multiple) and the conditions it is delisted.

I love this form of colaboration folks

[Springer]

@TW_Tones

I would favor a field in any tag field called delist-filter where in the logic can determin when and if to delist something. For example what it we wanted to hide the subtitle on tag tiddlers, we may place a filter;

This is exciting, and really a logical step up from my proof-of-concept. And one nice thing about it is that a list is indeed the simplest kind of filter run, so expanding in this direction would only amplify the list-based approach, without detracting from it.

@TW_Tones

it would be trivial to add something to the tag pill to inform the user of the fact there is a delist filter present.

Right. That’s currently something I have implemented in both the tags-wrapper area and in tagpill dropdowns (for the simple list), and it shouldn’t be hard to catch the filter-based delist just as well.

I think finding the right metaphor for disregard or unlist or delist is important. I am indeed worried about any word that would imply an outright cancel because the tag claim is still present at the tiddler end, and that fact still needs to be trackable. For a while I liked the metaphor suspended (as in getting suspended without pay from one’s job) but I worry that it may not be as cross-culturally obvious.

Thanks for the input.

[Springer]

@Yaisog

<$list filter="[enlist{!!unlist}]">
	

@Yaisog, I don’t think this is quite enough. We want to display (in the tag pill) only the tiddlers that “claim” the tag, and none that don’t.

The unlist field (or disregard or de-list or whatever) could (over time) include some values that do not correspond to tiddlers that claim the tag. Those should not be in the tagpill.

I’m looking for the equivalent of [enlist{!!disregard-list}] :filter[<currentTiddler>tag<thisTag>] (which behaves fine in my wiki)…

But we would need a different formulation, if your elegant javascript version doesn’t “see” the tiddler-side tag … [<thisTag>listed[tags]] feels like it should work (and does work by itself, but not as a :filter run… )

[Yaisog]

@Springer

I don’t think this is quite enough

Right, I didn’t think of that.

<$list filter="[enlist{!!unlist}tag:raw<currentTiddler>]">

This should work, since tag:raw[] ignores the unlist list. The same filter expression needs to go into the <% if statement. I’ll update my code above.
This is another way to do it:

<$list filter="[tag:raw<currentTiddler>] -[tag<currentTiddler>]">

[Springer]

@Yaisog

tag:raw[] ignores the unlist list.

Ah, right. Sorry I was losing track of that detail!

[TW_Tones]

@Springer

I think finding the right metaphor for disregard or unlist or delist is important.

I agree, I love naming competitions, word smithing, and like in flags a good choice at the beginning lasts forever.

My thoughts are although tags generate lists that is a simplification. in reality it remains a tag list, from which you are hiding a tag from the list.

perhaps it could be hide-tag(s) or a variation like exclude-tags. after all the titles are excluded from those identified as tags.

your choice here

[tw-FRed]

@Springer

I think finding the right metaphor for disregard or unlist or delist is important. I am indeed worried about any word that would imply an outright cancel because the tag claim is still present at the tiddler end, and that fact still needs to be trackable.

What about “masking”? In graphics software, “masking” is used to make some parts of the image immune to current tool.

Fred