--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ed2a1734-702e-4771-9b5c-69a331079c91%40googlegroups.com.
This is the list under https://groups.google.com/forum/#!tags/tiddlywiki. It is a mess.
discussion - aren't most posts "discussions"discusson - spelling error!done - why is this needed?edit-text-widget - too specific?evaluation - ???filters - just use "filter"?find - ???forumuse - ???goodUSEofTAGS - ???html5 - just use "html"?information - too generic?legokit - ???lpfs - too specific?muuri-touch - too project specific?operator - as in "filter"??organise - ???paragraphs - ???period-rule - ???
search - (vs "find")
tips - there's LOTS of things that could be considered "tips"... too generic?translcusion - spelling error!type - is this about use of the "type" field?usage - isn't everything "usage"?
As far as I can tell, that is a list of the tags that are currently in use. There does not appear to be a means to remove items from the list (see illustration below). I think the only way we can remove items from the list would be to remove the corresponding tags from any posts.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddl...@googlegroups.com.
OK... which tags should stay and which should go?I've marked up a few that I think can go... but I'm not going to remove them until I get some feedback...
find - use "search"forumuse - ???goodUSEofTAGS - ???html5 - use "html"information - too genericlpfs - too specificmuuri-touch - project specificorganise - ???paragraphs - ???period-rule - ???table - use "tables"
On Friday, December 27, 2019 at 3:39:16 AM UTC-8, TiddlyTweeter wrote:This is the list under https://groups.google.com/forum/#!tags/tiddlywiki. It is a mess.OK... which tags should stay and which should go?I've marked up a few that I think can go... but I'm not going to remove them until I get some feedback...
discussion - aren't most posts "discussions"discusson - spelling error!done - why is this needed?edit-text-widget - too specific?evaluation - ???filters - just use "filter"?
muuri-touch - too project specific?operator - as in "filter"??organise - ???paragraphs - ???period-rule - ???
translcusion - spelling error!type - is this about use of the "type" field?usage - isn't everything "usage"?
Compare:filters, tables, tags, variables, fields, fonts, widgets, pluginsvs.filter, table, tag, variable, field, font, widget, pluginI think I prefer the plurals, since they seem to refer to collections of multiple posts rather than single posts
But either way will do, as long as we don't have BOTH.
-e
It showed me that the tags on a post appear in alphabetic order. This effectively creates a bit of a sorted index by bracketing all other tags. By using the gGroups search capabilities, it's easy to filter out various combinations.
Of course, tags are not strictly needed to do this since the search covers both the tag values and the appearance of that value with the text areas of a thread and its enclosed posts. As a result it's relatively easy to created "noWords" that are adequate Search targets. I doubt this method would ever be shared, but it is effective.
Hans.
action
activate
announcement
backtick
Bob
BobEXE
bug
bulk
codemirror
css
date
design
discussion
docs
done
edit-text-widget
editor
evaluation
favicon
feature-request
field
filter
filters
find
font
forumuse
GitHub
goodUSEofTAGS
GoogleGroup
html
html5
import
information
keybindings
keyboard-widget
language
legokit
lpfs
macro
maths
Before I remove the above tags, I'd like some confirmation from others that they concur.
Eric Shulman wrote:Before I remove the above tags, I'd like some confirmation from others that they concur.My view is that IF you get no explicit feedback use your own instinct.
To me that is really beginning to make sense. I'll sit on it day and comment further.
One thing to consider is how many times a particular tag has actually been used to tag posts.I don't know of a way to get all the tag counts in one screen, but you can view the list of tags:
announcement (60)
bug (30)
css (39)
question (60)
resource (49)
saving (34)
singlefile (26)
template (12)
theme (11)
tutorial (28)
widget (25)
Please review the list and make suggestions for tags that could be removed (and why).
BobGitHubGoogleGroupTWCTiddlyMap
action - delete as redundant, it is too widecodemirror - THIS one is interesting. Should every plugin have a tag? I think not. Suggest delete.datedesigndocs - This one was added by me at some point. Might be better to replace it with "documentation". I think it is USEFUL, to highlight new attempts to document TWeditorevaluation - of what? We are always evaluating stuff. Redundant. Delete.favicon - I think I added that? Seems okay. Its an aspect of TW that is defined, though minor. Keep.feature-requestfieldfiltersfonthtml - What isn't html? Sems far too wide to be useful.importkeybindings - Not useful to keepkeyboard-widget - Not useful to keeplanguagelegokit - I am pretty sure I added that. It is not really needed. Can be removed.
macromathsmobilenewbienodejsofftopicpackageplugin
quirkregexsearchserver
snippetssortsvgtablestags
tiddlyservertiddlyspottipstransclusiontypeupdateutc - far too specific. time/date covers it?variablesvim - delete, it is too specific.whitespacewikitext-e
I am sure it could be thinned more. But this is what I think to remove 9 more items.
action - delete as redundant, it is too wide
codemirror - THIS one is interesting. Should every plugin have a tag? I think not. Suggest delete.
evaluation - of what? We are always evaluating stuff. Redundant. Delete.
html - What isn't html? Sems far too wide to be useful.
keybindings - Not useful to keepkeyboard-widget - Not useful to keep
legokit - I am pretty sure I added that. It is not really needed. Can be removed.
utc - far too specific. time/date covers it?
vim - delete, it is too specific.
Eric Shulman asked:
Please review the list and make suggestions for tags that could be removed (and why).
BobGitHubGoogleGroupTWCTiddlyMap
datedesign - NOT SURE. It is certainly functional. But "css" might be better at tag level. Design of what: code? presentation?
docs - This one was added by me at some point. Might be better to replace it with "documentation". I think it is USEFUL, to highlight new attempts to document TWeditor
favicon - I think I added that? Seems okay. Its an aspect of TW that is defined, though minor. Keep.feature-requestfieldfiltersfont
importlanguagemacro
mathsmobilenewbienodejsofftopic
package - slightly tricky. But we aren't really doing "packages". So it seems redundant.pluginquirk - likely I created that. I doubt anyone would reference "quirks". Delete.
regexsearchserversnippetssortsvgtablestagstiddlyservertiddlyspot
tips - this was me. Can go. It was a nice idea at the time. But can be done though a title just as well.transclusiontype - this is ambiguous as is. Likely means "content-type"? Not worth keeping without demand for it.updatevariableswhitespace - not clear enough. This may be about pragma? But not helpful alone. Delete.wikitext