I haven't yet found where in the code it causes own posts to appear violet (default post background color) in the right navscrollbar
The prev js I've been using since 3/2018 changed you posts, & the replies to you posts, pink, in body and in nav bar. Been heavily using that for navigation for a long time. Not having it threw me for a loop.
Carry on. Don't mind me.
o7
OK, I'm going with pic related color scheme for the time being, reserving colors that had meaning for 22 months. Pink not used at this time, to be available for highlighting yous and/or replies-to-yous if ever implemented. Yellow not used at this time since it has been muh color for Q posts.
/* * Create styles that determine how notables are highlighted / _createStyles() { $('head').append(<style id='${this.styleId}'> .thread div.post.${NotableHighlighter.NOTABLE_CLASS} { background-color: #e5ffcc; /* replace #FFFFCC YELLOW with #e5ffcc LIGHT GREEN */ } /* less specificity than notable so it has less preference */ div.post.${NotableHighlighter.NOMINATOR_CLASS} { background-color: #cee5b7; /* replace #FFCCE5 PINK with #cee5b7 a darker light green */ } div.post.reply .mentioned .${NotableHighlighter.NOMINATOR_CLASS} { color: #00CC00; /* BRIGHT GREEN TEXT */ font-weight: bold; font-size: 1.5em; } </style>); }
Yes, I confirm.
I'm the same anon who gave you the JS
https://pastebin.com/HTjaECNM
(combination of JS from multiple codefags) the functions of which you have been implementing one by one into Bakertools. (I change my ID frequently so as not to be too identifiable, since I'm a frequent presence on QR.)
I don't know how many anons have been using it – I presume a fair # of oldfags.
Pic 1 is what
the old comfy JS
https://pastebin.com/HTjaECNM
looks like.
The pink highlighting are OWN-POSTS and REPLIES-TO-OWN-POSTS.
It lacks your special functions to help the bakers.
Pic 2 is its yellow highlighting for Q posts that works on any 8kun board Q posts on.
P.S. You're absolutely right about UI design requirements to offer comfy options for colorbindfags. You have been educated correctly, kek. I liked the similar shades of green for my own use (not colorblind).
I'm a memefag very attuned to color nuances so it works well for me personally.
To best of my knowledge, light green hasn't been used for anything before. Not wedded to it, but it seemed to work OK after ruling out yellow and pink.
A point: Any custom JS that plays with colors looks really weird on a board that has a default theme different than Yotsuba-B or its derivatives. For example >>>/qrb/ has a default dark color scheme and I found that BO's theme choice was incompatible with my preferred custom JS so had to set Yotsuba-B theme when visiting there.
Just something interdasting to know. Not a requirement in any way shape or form.
~~has~~ had
Now testing Blacklist All Post Images
in Gen bread to find out what it does. I assumed it would make all the images in a post disappear but my assumption was incorrect.
Blacklist All Post Images button on a post makes that entire post disappear – image, text, not even a stub showing that something used to be there.
Other posts by that ID in that bread are still there.
The function applies to a single post in a single bread, and is not persistent across breads.
It's different from CM's Hide Post tool, which hides the post alright, but it honors one of CM's general options to "Show Stub" which only suppresses the text/graphics in a post but leaves the header portion intact so anon can see that a post is there but suppressed, the ID, date/time, post count, post # and any replies to that post.
Does it make sense to duplicate a function that already exists by default?
A clear explanation in the documentation would probably help.
Pics are examples of CM's hide post function.
-
Unhidden
-
After hide post
-
Ability to unhide the hidden post
-
The option that causes the post header to remain visible or disappear entirely (default)
Baker tools check boxes and nav options selected by user should persist across breads. Instead, they reinitialize every time a QResearch tab is opened.
-
Set baker tools options per pic 1
-
Copied URL and closed tab.
-
Opened new tab with saved URL.
-
Baker tools options have reset to initial values per pic 2.
Priority: low
We need to think through some use cases for the Bakertools JS.
Use by a baker has received a lot of attention.
What about ordinary users who want to read down a thread as the thread is forming, and comment or or notable posts as they go, and return to the spot where they were reading?
The Bread List plus the highlighting of posts nominated notable is very useful for quickly scanning past full breads to catch up on the news & notables.
In the previous JS that anon used for 22 months (posted above, https://pastebin.com/HTjaECNM), all the nav controls seemed to work off a single model, so that no matter how anon advanced through the bread, the nav controls would update to match the current position in the bread (similar to how CM's JS updates the post number in the URL). Anon could scroll down with browser scroll bar, scroll by clicking the Next You/YouReply nav, click next/prev Q, etc. and the right nav scrollbar would update accordingly. It didn't matter what kind of navigation was used, the navigation was unified and worked off a single model.
The bakertools JS doesn't do this.
For example if anon posts, the Own Posts nav updates the # of posts and CM's JS updates the bread view to the just-posted post. But if anon clicks Own Posts right arrow (advance one own post), the location in the bread changes to one post after the one previously viewed via this nav tool.
I'm not sure what behavior is most desirable. Here is a suggestion for consideration:
What if after posting, all the Bakertools nav tools update to match the current position in the bread, BUT a NEW BUTTON is added so I can return to where I was reading before posting a comment or notable nomination? The lack of "return to where I was after posting" is probably the most irritating and time-consuming feature of 8kun's native JS.
Think (model - view - controller) ??
The "hover over scrollbar to preview post" is fantastic. Huge timesaver.
You are awesome.
Magnifico !
❌ v0.7.1
Disable spam fader checked
Spam faded anyway
Pic
Tried toggling the control and spam gets unfaded, but after scrolling up/down the page spam is faded out again.
The main use for "Disable Spam Fader" is in breads with long duration, also in the Meme breads where there are typically many posts by the same ID.
☕ Low priority.
❌ v0.7.1
Disable spam fader checked
Spam faded anyway
Pic
Tried toggling the control and spam gets unfaded, but after scrolling up/down the page spam is faded out again.
The main use for "Disable Spam Fader" is in breads with long duration, also in the Meme breads where there are typically many posts by the same ID.
☕ Low priority.