hide tag buttons

[tobibeer]

Consider configurability for hiding tags from tiddler tag buttons as explained here...

Hide Tag Buttons @ tb5

Proposal for $:/core/ui/ViewTemplate/tags:

title: $:/core/ui/ViewTemplate/tags

<div class="tc-tags-wrapper">
<$list filter="[all[current]tags[]]-[list[$:/config/Hide/TagButtons!!text]]+[sort[title]]"
template="$:/core/ui/TagTemplate"
storyview="pop"/>
</div>

[Spangenhelm]

Hi tobias i see what you can do but i don't really know when i would need it..

[tobibeer]

It allows to use things like system tags, e.g. $:/tags/foo, that trigger some behavior but which you do NOT want to show up in a tiddlers taglist in view-mode.

This is one way to have a defined spot for declaring any tags as hidden from view-mode.

[pmario]

As I wrote elsewhere, I'd prefer a "readers only mode" that hides stuff from the user.

IMO "excludeXX" flags will cause the same problems as with TWc. ... So I'm not really happy with an option like this.

[tobibeer]

Using excludeFoo was and is a conscious choice and it didn't come out of a vacuum in TWc. I never experienced it as problematic. Actually, not seeing it used was problematic for me... as it made it harder to focus on actual content. So, I'm glad we're having that $: now.

Showing things that are of no interest to a visitor is just as problematic as hiding it can be in other regards. Of course, we are only talking about hiding things from view-mode, not edit-mode.

Read-only mode is a different issue and surely just as important. However, I am a reader, too, of my own wikis... and I don't like to be forced to switch to some reading mode to get a distraction free ui... or, failing that, to tweak the core ui in every single wiki, never getting updates on those components ...owed to not having what could easily be standard functionality... and would benefit from a standard solution rather than a bazillion different, much less intuitive, individual customizations.

[twMat]

+1 for Tobias suggestion.

Also the tw-coder has visual preferences that differ between coding (edit mode) and using or viewing the output. We readily accept a lot of other things that differ between edit and view modes like formatting and CSS. These could really be considered purely aesthetic just like the desire to hide certain tags from view mode.

That said, I do think it would make sense to introduce a "readers only mode" (perhaps called Presentation mode ?). For instance, most public sites include a lot of stuff only for visitors like logos, background images, footers etc. These are likely just disturbing for the desginer in view mode. And vice versa, the typical sidebars are very unsuitable to show for a non-tw audience, not to mention a thing like the edit button (OMG, I broke the website!) I think a global "Presentation mode" is a good idea to. Possibly as a theme but IMO it is fundamental enough to be included by default. It would encourage people to use TW in more public contexts. Currently, most public TWs look like... well not websites. (Start separate issue? More for google boards?)

BTW, if individual tags were really individual fields, would this mean they were individually "manipulable" and possible to apply CSS onto in a more direct way?

[tobibeer]

Start separate issue? More for google boards?

Surely... that is, if you can't find an existing issue on the topic.

BTW, if individual tags were really individual fields, would this mean they were individually "manipulable" and possible to apply CSS onto in a more direct way?

Not following. How would a tag be a field? Do you want to give tags artificial fieldnames, like tag-1, tag-2, tag-3... and then: Why? This just complicates things for reasons I do not grasp.

You can already style tiddlers by their tags, it is existing functionality. What is not existing is doing the same based on the presence of a user-defined field.

[twMat]

What I mean is if one could apply CSS to individual tags if they were fields. Today we can change the appearence of a tag(-pill) in terms of color and we can apply an icon. However, my question was merely because I'm curious and it was not a suggestion.

[tobibeer]

What I mean is if one could apply CSS to individual tags if they were fields.

Hi Mat, I think I understand. Try to be more precise in using the terminology we have. In TiddlyWiki, a tag is but a reference in any tiddler's tags field and nothing else!

If you want to be able to style a(n individual or all) tiddlers where there is some (tag-like) reference in some (list-)field other than the tags field then that is another issue. But that is not a tag, it's a reference in a field, in a special field designed to only hold tiddler titles, not any field.

[twMat]

( @tobibeer Just a thank you for correcting my possible errors. Very important that I use the correct terminology! I'm not sure your interpretation of what I meant is the same as what I did mean but it is too much of a side note from the OP so let's leave it.)

[pmario]

@tobibeer ... should be a PR?