And another useful custom CSS edit. More tags on the screen line by line in
the block!
.tc-block-tags-dropdown{
white-space: normal;
min-width: 620px !important;
}
.tc-block-tags-dropdown a {
display: inline-block !important;
padding: 4px 4px 4px 4px !important;
}
воскресенье, 11 июля 2021 г. в 00:54:02 UTC+3, Mike Andyl:
> To remove unnecessary tags from *tag-picker* that already exist, find two
> filters *nonSystemTagsFilter* & *systemTagsFilter *in
> $:/core/macros/tag-picker and add this to them at the end:
> *-[all[current]tags[]]*
> суббота, 10 июля 2021 г. в 01:49:47 UTC+3, TW Tones:
>
>> Miket,
>>
>> Good questions we should collect answers to, the fact is Tags are such a
>> useful concept that we can "run away with them" and overuse them. These
>> questions of yours indicate you seem to be in a common phase we all pass
>> through with tiddlywiki.
>>
>> However it exposes something us "seasoned" tiddlywiki enthusiasts learn.
>> An *over reliance* on tags causes something we sometimes refer to as
>> "tag pollution" or "tag saturation". Fortunately there are plenty of
>> strategies we can adopt.
>>
>> Let me pass on a little from my experience of more than a decade with
>> tiddlywiki and three decades with Information technology.
>>
>> - Personally I came across this tag pollution very early in my
>> tiddlywiki journey, the result is I have a special approach now that
>> serves
>> me well, my approach is to use as few tags as possible leaving the "tags
>> space" as "empty as possible". I tend to reserve tags for system
>> functions
>> (behind the scenes eg system tags etc...) or "ad hoc" use.
>> - I achieve this by "moving tags into fields" whereever possible.
>> - An example would be rather than have a tag to indicate a task, I
>> have a field called *object-type with a value of task* (and other
>> values), to indicate a *status of a task* rather than a status tag
>> *have
>> a status field*.
>> - When moving from a tag to a field we get to craft the way they
>> behave differently, for example in the aforementioned *object-type
>> and status fields* we can ensure a given tiddler only has one value
>> at a time, so we do not need to put the effort into removing a tag. Just
>> change the field value.
>> - Of course like tags sometimes we want more than one value at a time
>> on a specific tiddler, I use tags initially, they make this easy, however
>> as you start to have too many tags, new tags simply "pollute the tag
>> space
>> further".
>> - I may not want to change what plugins and other tools use tags for
>> but I can control what I do with ones I create.
>> - Using the listops, list and other operators we can manage fields
>> that contain multiple values.
>> - I tend to avoid spaces in the names of such values so space
>> delimited is sufficient but you can make use of the [[title with
>> spaces]]
>> methods and look at enlist and other operators.
>> - The alt-tags (gen tags) plugin allows you to make use of
>> multiple-tags fields if you want.
>> - The trick is tags are a form of generic indicators, you can quickly
>> use to achieve an outcome, but with experience you discover on moving
>> them
>> into a field that there are different organisational methods you can
>> easily
>> enforce when using a field. For example you can ensure a tiddler belongs
>> only to one category or one or more subjects.
>> - Fields can
>> - Exist but contain nothing see [has[fieldname]] (field exists and
>> has value) and [[has:field[fieldname]] (field exists with or without
>> a
>> value)
>> - Thus the existence of a field can itself be a condition or
>> switch
>> - Contain wiki text or transclusions
>> - be managed with common suffixes or prefixes eg; anything-link
>> else-link
>>
>> Finally;
>>
>> - In coming versions the limitations of field naming are to be
>> removed and we expect a lot of innovation ultimately occurring around
>> this.
>> - Eventually one becomes aware of the subtle qualities of different
>> ways to define either a tag or field. So lets say I decided to give many
>> tiddlers a "domain" eg work/personal/health/family I may decide a given
>> tiddler should only belong to one domain, then I would use a field with a
>> single value.
>>
>> Regards
>> Tones
>> On Saturday, 10 July 2021 at 07:10:15 UTC+10 miket...@gmail.com wrote:
>>
>>> Now the usual view is very inconvenient when you have a lot of tags and
>>> need to scroll and scroll down the page. Plus, the selected tags are still
>>> on the list and continue to distract.
>>>
>>> This raises two questions?
>>>
>>> 1. How can I make the selection of tags more compact so that I don't
>>> have to scroll down the page?
>>>
>>> 2. And how to mark tags that are already assigned. Ideally remove from
>>> the list, but it's probably difficult. Maybe you can at least change the
>>> color to a less noticeable?
>>>
>>> Any ideas?
>>>
>>> Nice option with checkboxes here
>>> https://i.imgur.com/gxJm0Tw.jpg
>>> http://zemox.tiddlyspot.com/
>>>
>>> But I didn't understand how he did it, I installed his plugins and
>>> nothing changed.
>>
>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/747268b5-9c1e-4baa-a6ae-549437e6663an%40googlegroups.com.
