{"action":"created","issue":{"url":"https://api.github.com/repos/Jermolene/TiddlyWiki5/issues/1223","labels_url":"https://api.github.com/repos/Jermolene/TiddlyWiki5/issues/1223/labels{/name}","comments_url":"https://api.github.com/repos/Jermolene/TiddlyWiki5/issues/1223/comments","events_url":"https://api.github.com/repos/Jermolene/TiddlyWiki5/issues/1223/events","html_url":"https://github.com/Jermolene/TiddlyWiki5/issues/1223","id":51806865,"number":1223,"title":"Suggested new behavior for tag dropdown list","user":{"login":"twMat","id":4534056,"avatar_url":"https://avatars.githubusercontent.com/u/4534056?v=3","gravatar_id":"","url":"https://api.github.com/users/twMat","html_url":"https://github.com/twMat","followers_url":"https://api.github.com/users/twMat/followers","following_url":"https://api.github.com/users/twMat/following{/other_user}","gists_url":"https://api.github.com/users/twMat/gists{/gist_id}","starred_url":"https://api.github.com/users/twMat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/twMat/subscriptions","organizations_url":"https://api.github.com/users/twMat/orgs","repos_url":"https://api.github.com/users/twMat/repos","events_url":"https://api.github.com/users/twMat/events{/privacy}","received_events_url":"https://api.github.com/users/twMat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2014-12-12T13:39:52Z","updated_at":"2015-01-21T13:46:57Z","closed_at":null,"body":"tw.com\r\ncreate a new tiddler \r\nbegin typing a new tag with string \"$:/tags\"\r\nin dropdown tag list, a few suggestions are seen.. but I was expecting to see all [SystemTags](http://tiddlywiki.com/#SystemTags). I'm guessing shadow tags are not seen.\r\n\r\n* I suggest that an exception to show all shadowtags/tiddlers beginning with *$:/tags*\r\n* what actually *is* supposed to show in the dropdown? Typing in \"jer\" in tag field seems the result in a more general search, i.e including searching tiddler content\r\n* ...or maybe not: typing in \"jer\" I was expecting to see tag JeremyRuston but it only shows tag TiddlyWiki. This tiddler references JeremyRuston. However, JeremyRuston is also referenced in e.g tiddler Jermolene but Jermolene does not appear in the dropdown.\r\n\r\nUnless I misunderstand something, I would say this ought to be dealt with as soon as possible. Here is my suggestions for how it should behave:\r\n\r\nI presume one key use for tags is as a way to categorize tiddlers. As such one typically does not want more categories than necessary. For this reason, the system should help the user to avoid introducing unnecessary new tags. (Example: If intending to create a new tag \"Jeremy\" it is of value to learn about existing tags \"jeremy\", \"JeremyRuston\"... )\r\n\r\nFor these reasons, my first proposal is that the dropdown should show the following, and in this order:\r\n1. tags with names starting with the typed string\r\n2. tiddlertitles, that are *not* also tags, with names starting with the typed string\r\n3. tags with names containing, but not starting, with the string\r\n4. tiddlertitles, that are *not* also tags, containing, but not starting with, the string\r\n5. tiddlertitles for tiddlers merely referencing the string in text, fields etc. (If these even should be suggested at all... but ok, they do have *some* relationship with the tag-to-be).\r\n\r\nIt may seem irrational to put in \"(2) tiddler titles that are *not* tags\" so *early* in a tag suggestions list - but in practice, they are a) very likely to be appropriate if they do start with the typed string and b) it is, again, of value to tag with something that already exists (regardless if a pure tag or a tiddlertitle). Number (3) is IMO a less likely 'search' than (2) \r\n\r\nThe above is my primary suggestion for behaviors. The following is something I would also like to see but is perhaps not as urgent:\r\n\r\nBecause tab pills have a rather small font size, I would prefer a *clearer* way to differentiate between tags that are tiddler titles and pure tags (which name are in *italics* in the tag pill). Again, the aim is to keep the number of tags small (and maybe there are other reasons?). For example;\r\n* if a tiddlertitle and pure tag are 'similar', it makes sense to choose the title (because this connects the current tiddler with an actual other tiddler) and maybe you can even delete the pure tag.\r\n* ...or vice versa; you may wish to use tags purely for categories and not as tiddlers. Take the ToC macro as used on tw.com for example: In closed state, you cannot tell if a ToC entry contains text or if it merely serves as a categorizer. On tw.com under tab *Contents*, compare e.g *HelloThere* with *Customise Tiddlywiki*. A visitor checking out *Customize TiddlyWiki* may wrongly conclude that the top level is merely a category name. ToC is autogenerated from tags so there is benefit in being helped with consistently choosing \r\n\r\nSo can we have some further way to (automatically) differentiate between pure tags and tiddlertitle-tags?\r\n\r\nThank you!"},"comment":{"url":"https://api.github.com/repos/Jermolene/TiddlyWiki5/issues/comments/70839109","html_url":"https://github.com/Jermolene/TiddlyWiki5/issues/1223#issuecomment-70839109","issue_url":"https://api.github.com/repos/Jermolene/TiddlyWiki5/issues/1223","id":70839109,"user":{"login":"twMat","id":4534056,"avatar_url":"https://avatars.githubusercontent.com/u/4534056?v=3","gravatar_id":"","url":"https://api.github.com/users/twMat","html_url":"https://github.com/twMat","followers_url":"https://api.github.com/users/twMat/followers","following_url":"https://api.github.com/users/twMat/following{/other_user}","gists_url":"https://api.github.com/users/twMat/gists{/gist_id}","starred_url":"https://api.github.com/users/twMat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/twMat/subscriptions","organizations_url":"https://api.github.com/users/twMat/orgs","repos_url":"https://api.github.com/users/twMat/repos","events_url":"https://api.github.com/users/twMat/events{/privacy}","received_events_url":"https://api.github.com/users/twMat/received_events","type":"User","site_admin":false},"created_at":"2015-01-21T13:46:57Z","updated_at":"2015-01-21T13:46:57Z","body":">Personally, I think any system-tiddler should never be up top, because it's an internal feature. \r\n\r\nThing is, when you *use* a system title as a tag, it becomes \"yours\". It is no longer an anonymous name of a system tiddler, but it's not your fault it happened to still be titled like one such. I wish we could treat user used system tags differently from other system tags in the displays.\r\n\r\n>I'd want to see content tags first, even though that generic sorting puts $ before a. I would rather like to see all non-ascii characters behind alpha-numeric ones, if only for the starting character.\r\n\r\nCreated #1402 \r\n\r\n\r\nThe slow loading of all titles in the popup\r\n>[...] Possibly, tiddlers should only be shown when a search term (longer than x) has been entered.\r\n\r\nHow about this: We use your distinction and physical separation between tags and non-tags! Load one at a time. The user gets to see the tags while the non-tags are still being rendered. It is likely that if there are very few tags, then it is a new TW and there are also few non-tag titles meaning it would be fast to load that list too.\r\n\r\n...there's probably still the freezing though, when you can't type. Still better to look at a list while frozen than nothing.\r\n\r\nCould typing interrupt the filtering? This is desirable because typing means you want another (filtered) list anyway.\r\n\r\nI also notice that the delay occurs for each new tag that I want to add. Maybe the originally rendered list could be kept in memory so it won't have to be calculated again?\r\n\r\nOr maybe there is a point in workflow that could be taken advantage of; it is reasonable to expect that tagging is common, so maybe the list could be rendered whenever you go into tiddler edit mode, at least for new tiddlers. I would guess people don't create tags as the first thing they do but instead title or text. Would it be possible to calculate tag list while he's busy typing title or must, as indicated in a simple test I just did, everything in TW freeze?\r\n\r\n>>posting as separate issues\r\n>Please, consider this option more often! It's not good at all if issues get bloated up like that. They should be small and actionable, not entire topics! When you write an issue, rather than \"suggested new behavior for tag dropdown list\" it would ideally be titled with the precise behavior you want. And if that is multiple things, it's multiple, independently, cross-referenced issues.\r\n\r\nI definitely understand your point and I think this is one reason why people are not comfortable using github. I wish all threads were initially discussions, unless otherwise specified, but that one could tag or select individual posts as \"small and actionable\" and have these filtered out separately. We miss out on potential stuff due to such infrastructure limitations. For instance, I probably belong more on the google boards but I think that some of the things having come from my participation in github over the past 2 (3?) months would not have come about if I limited myself to the boards. But... just maybe I should switch back actually.\r\n"}}