-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Functionality #2
Comments
Works in Chrome properly for me. Doesn't work in FF, thanks for reporting. The tag index isn't small, its size depends on the amount of posts and pages visited by you on your booru, because that's how it collects and stores tag data. Regarding your functionality and to avoid making a separate issue, I recommend you implementing keyboard controls in your script. You know, when you want to work really fast and streamlined, keyboard is the way, not mouse. Assign hotkeys to going back/forward a post as well as switching between important input fields. Maybe like on http://booru.org/login . Make submit button larger, perhaps fields too, aiming mouse takes time. On a subjective note, I would have renamed your userscript to something other than "Mass editor" because it is in no way a batch editor. Something like "Quick editor" or stuff like that, but that's me. |
I think I fixed the Chrome and Firefox issue, for some reason it failed to use part of the prototype.jp library embedded in booru pages. Had to |
One can't really debug with Firefox, rarely Firefox will have a pop-up saying something like "there is a problem with this script: end script, dubug, cancel" then after clicking "dubug" it will give information. Also using inspect element you can read the errors. Maybe use some JavaScript verification page online. Usually the problem is that it either works or it doesn't, sometime it half works, and it is hard to get info on the problem. Thus, I make changes a little at a time. And yeah hotkeys are a good idea, such as using left and right arrows to navigate the pages. |
Correction on what I said before: the pagination fix does work on Google Chrome at http://*.booru.org/index.php?page=post&s=list&tags=all (although it does look a tiny bit strange with the spacing, but that is non-issue). I am testing it on Google Chrome and Firefox and it all seems to be working well so far except some things Google Chrome:
|
Yeah, it sometimes fails to load the tag database, which is also why the autocompletion sometimes doesn't work. I dunno what's causing this, maybe something about the time at which scripts loads (document-body/idle/etc). Another thing to note, since the state of localStorage is captured once the page load, if you open several tabs and start editing tags in all of them, it will show old results until refresh, since it can't know about changes done in other tabs. About the tag index seen on the account page, it will show some tags even if there are currently no images of this tag on the booru, again because it's a client-side replica of the server. However if you navigate to the tag page, it will see that there are no images and remove the tag from cache. |
I added the function to batch-remove the tagme tag from all posts that have it (can be found under Account options). It's quite slow though because Booru limits the rate at which you can make editing requests and if you make them too fast they'll just fail so I had to slow it down without guarantees. Also made better formatting of tags shown on list and post pages, does not replace _ in tags with spaces anymore, instead show them as they're stored in the database. This is because booru failed to properly show tags with multiple _ in a row or tags consisting entirely of _. |
If it does work then it's great! However, I see a few problems with it. Also check out my updated work on improving the
&id=
parts on Firefox! My work has overlapped with yours in a few regards; for example, I too edited the "Statistics" section; my edits of that area are better though.Also, the tag index at account options is small but useful :)
The text was updated successfully, but these errors were encountered: