It would be nice if the tag completion sorted by usage, so that, say, trying to tag 'dark_skin' with just 'dark', it wouldn't lead off with 'dark_hair' and 'dark_eyes' first.
Posted under General
CodeKyuubi said:
It would be nice if the tag completion sorted by usage, so that, say, trying to tag 'dark_skin' with just 'dark', it wouldn't lead off with 'dark_hair' and 'dark_eyes' first.
It sort of already does, as dark_hair -> black_hair has a count of 490K and dark_eyes -> black_eyes has a count of 71K, both which are greater than dark skin at just 65K. That's the order that Danbooru returns the data, so that's currently the order things are shown in.
Would your idea be to instead show all of the aliases last in the autocomplete popup?
BrokenEagle98 said:
It sort of already does, as dark_hair -> black_hair has a count of 490K and dark_eyes -> black_eyes has a count of 71K, both which are greater than dark skin at just 65K. That's the order that Danbooru returns the data, so that's currently the order things are shown in.
Would your idea be to instead show all of the aliases last in the autocomplete popup?
My bad, I meant sorted by personal usage, like it does with Danbooru's old autocompletion extension, or is that infeasible to program? And yeah I think it would be useful in my experience to move aliases beyond non-aliases.
CodeKyuubi said:
My bad, I meant sorted by personal usage, like it does with Danbooru's old autocompletion extension, or is that infeasible to program? And yeah I think it would be useful in my experience to move aliases beyond non-aliases.
I just looked into that, and it should be doable.
So here's what I'm thinking the order should be:
1. Used tags sorted by usage
2. Unused tags sorted by post count
3. Aliased tags sorted by post count
Note: Limited to 10 tags as per the current setup.
For #1, there are a couple ways that usage could be sorted. It could be by most frequent. It could also be by most recent. I'm leaning more towards the latter, as with the former you could have just been tagging one thing in abundance, so when you switch it up to something else you'd be forced to continually use the order mandated by your previous usage. Unless there's a convincing need to go with frequency method, or perhaps even a different method altogether, I'll just plan on going with the recent usage method.
Propagate the tag down all the way to the first letter. For instance, the tag girls_und_panzer doesn't show up until you type "gi", but if you were to select that tag, then it would now show up at the top of the "g" listing.
Have each used tag have an expiration so that stale tags don't continue to be propagated to the list. I'm thinking maybe a day for this. Whenever a tag gets used, the expiration will get renewed, but after a day of no use the system will in a sense reset itself.
The expiration period could always be extended after a trial period, but I don't want to expand too far initially then have to wait a period of time for things to reset themselves.
Pushed Version 16 which added a user choice mechanism to the autocomplete. Whenever a user selects a data item with Tab or Enter, that choice will appear at the top of results for at least the next 24 hour period. Reusing that same choice renews that period. Chosen items will appear in the most recently used order first. Beyond that, all aliased tags are pushed to the bottom of the list unless they are also a chosen item.
Updated
Pushed Version 17 which modifies the choice mechanism to account for usage. I've been experimenting this last week for something that wasn't as jittery as Version 16, and eventually settled on using an incremental count with a decrementing power function backoff.
The new schema works as such:
I found that the above works pretty well through simulation and also testing. Since some may want to adjust the values or turn off the choice schema altogether, I'll be working on a user interface for this script, and hopefully deliver something by next week.
Updated
Something seems broken.
https://i.imgur.com/lRSq8V5.png
Some words are staying at the top despite a different word having been spelled.
CodeKyuubi said:
Something seems broken.
https://i.imgur.com/lRSq8V5.png
Some words are staying at the top despite a different word having been spelled.
It's related to forum #149962 and it's been brought up in issue #3854
Pushed Version 18 which adds a settings menu available on the same page as the Danbooru settings (My Account >> Settings) under Userscript Menus. The specific settings for this script are under the tab IndexedAutocomplete. The settings "should" instantly reflect in all other open tags with the latest version of the script running.
Updated
Pushed Version 19 which adds styles and groupings for the various tag autocomplete sources.
By default, the autocomplete highlighting is turned on. The program adds CSS classes that facilitate this, which can be overridden by the user.
.iac-user-choice - The user selected data.iac-tag-highlight - All tag sources.iac-tag-exact - The exact source.iac-tag-prefix - The prefix source.iac-tag-alias - The alias source.iac-tag-corrct - The fuzzy source, i.e. misspellingsThe following is the current CSS code used:
.iac-user-choice a {
font-weight: bold;
}
.iac-tag-alias a {
font-style: italic;
}
.iac-tag-highlight {
margin-top: -5px;
}
.iac-tag-highlight > div::before {
content: "●";
padding-right: 4px;
font-weight: bold;
font-size: 150%;
}
.iac-tag-exact > div::before {
color: #EEE;
}
.iac-tag-prefix > div::before {
color: hotpink;
}
.iac-tag-alias > div::before {
color: gold;
}
.iac-tag-correct > div::before {
color: cyan;
}If the highlight option is turned off, then the classes will no longer be added, however the ability to style by source is still available with the HTML data fields, e.g. using [data-autocomplete-source="exact"] as the CSS selector. Replace "exact" with all of the other sources to address them.
By default, source sorting is turned on. The default order is exact, prefix, alias, correct. This order can be modified.
If this option is turned off, then the weighted sorting scheme by Danbooru will be used.
sort_weight = source_weight x post_count
The current source weights are:
At some point in the future, I may facilitate the ability to alter the weights and/or the equation as an alternate means to sort the data.
Pushed Version 20 which facilitates using an alternate weighting scheme for tag sources. Note that if the source grouping added in Version 19 is enabled, then this option will have no effect.
The default source weights are the same as those noted in the previous post. Valid values are any number between 0 and 1. Three different scaling functions are available to control how much of an effect that the post count has on the sort weight.
tag_weight = source_weight * post_counttag_weight = source_weight * Sqrt( post_count )tag_weight = source_weight * Log( post_count )The scaler really only functions when two sources have different weights. Sources with the same weight will be grouped purely by post count.
Square root has a medium effect at reducing the weight of the post count, whereas logarithmic has a huge effect.
Updated
Pushed Version 21 which primarily adds autocomplete to the new bulk update request form.
.iac-tag-bur > div::before{
color: #000;
}
.iac-tag-highlight .tag-type-400:link {
color: #888;
}
.iac-tag-highlight .tag-type-400:hover {
color: #ccc;
}Besides that, there was some issues with the artist autocomplete which were also fixed.
Updated
Pushed Version 22 which adds a program/cache data editor to the menu. This is being prototyped on this script before rolling it out to the other applicable scripts. Currently, values can be looked at and/or deleted. Also, the cache data is editable whereas the program data is not, as there is currently no centralized mechanism for validating all program data.
So basically, this adds the scalpel approach besides the already existing hammer approach, i.e. purge cache data / factory reset.
Updated
Pushed Version 23 which primarily integrates the new library code that was finalized today. This is coming out as a major version since a large majority of the code was changed while updating to the new library version and standardizing all of the affected userscripts.
Additionally, all of the menus were standardized, and fully working cache editors were incorporated. Also, a new control was added under cache settings which shows the size of all the userscript data amongst all of the various data storage.
Updated
Pushed Version 24 which adds an "already used" mechanic to the tag edit box, highlighting any lines with already used tags yellow. The program uses a CSS class for this, and the following shows its default setting.
.iac-already-used {
background-color: #FFFFAA;
}Besides the above, there have been several other additions:
Updated
Pushed Version 25 which adds metatags to the tag autocomplete for both query and edit inputs. For metatags with autocomplete themselves (order, status, rating, locked, child, parent, filetype, disapproval), once those tags have been selected it will automatically activate the autocomplete for them. The following is the CSS class and default setting for these.
.iac-tag-metatag > div::before{
color: #000;
}
.iac-tag-highlight .tag-type-500:link {
color: #000;
}
.iac-tag-highlight .tag-type-500:hover {
color: #444;
}The order for these can be set in the settings menu. Additionally, they can also be disabled there.
Besides the above, there have been several other additions/fixes:
Pushed Version 26 which primarily includes an update to the library code plus a few fixes:
Pushed Version 27 which adds several new additional features:
[[some_tag|insert text]]Updated
Pushed Version 28 which primarily updates the text autocomplete feature, along with a major code refactor.
tag - Includes the underscores.normal - Does not include the underscore.pipe - Normal mode with a pipe "|" at the end.[[Arthur Pendragon (Fate)|]] -> Arthur Pendragoncustom - Allows user to enter the display text.[[arthur_pendragon_(fate)|Saber-chan]] -> Saber-chanlowercaseuppercasetitlecase - First letter of tag/wiki capitalized.propercase - First letter of each word capitalized.exceptcase - Propercase except for "a", "an", "of", "the", "is".romancase - Romancase and capitalize all letters in Roman numerals.list Shows all of the available program/data keys.refresh Refreshes all of the available keys.