I’m glad I can say I’m not one of those 25%. I make sure to at least change one variable name so it’s not a wholesale copy =D
Seriously, though, how can one just copy the code and call it a day? Well, maybe if it’s function, but even then it’s best to understand what it’s doing. Otherwise it’s like taking someone’s English translation of a Japanese sentence at face value, without understanding how they came to that translation.
If you listen to the podcast they talk about this. TL;DR most people use StavkOverflow to understand concepts/workflows and then adapt snippets to their needs.
@ChristopherFritz addressed this earlier in the thread…possible yes… probably not a priority
This was his first publicly posted script and he finally produced something to share after much ‘encouragement’ from some of us that thought it would be useful… for now unless you code this yourself, don’t see it happening right away
I use both and it’s worked fine! Because the kanji and vocab cards are separately organized, there’s not space for them to overlap. Like both scripts aren’t active on the same cards even when enabled.
Would it be possible to limit results to 5 or so pieces of vocab? I seem to be in the minority because I don’t care if they’re leeches, but on the more common kanji, the text box often moves out of sight.
addendum: I also have the problem of the script needing to reload fairly often and cutting off parts of what I’m typing. luckily double check script is to the rescue, but it’d be nice to not have to worry about it.
I’ve published an updated version of the script. I think updating it is as simple as clicking the button on the script install page.
I don’t have any fancy configuration menu, but there are now a couple of options in the code that can be modified.
In TamperMonkey, you can click on the TamperMonkey icon and open the Dashboard. From there, select “WaniKani Kanji Review Vocabulary List” to open the code. The configuration options are near the top of the code:
// Limit number of vocabulary words to be shown. Must be an integer.
const MAX_VOCABULARY_TO_SHOW = 100
// Show locked vocabulary words. Must be true or false.
const SHOW_LOCKED_VOCABULARY = true
These options address the following:
Update the script and change the following option to false:
const SHOW_LOCKED_VOCABULARY = false
That will hide that pesky wall of locked items. May you burn these kanji before you unlock all their vocabulary =D
(Sorry for taking so long to reply! I wanted to do a proper configuration menu, but I just haven’t made the time to learn how.)
Update the script and change the following option to 5 (or whatever your preferred max number of vocabulary words is):
const MAX_VOCABULARY_TO_SHOW = 5
I honestly can’t tell you which five it will show, but I assume it will be the first five vocabulary listed on WaniKani page for the kanji.
(If I do any future updates, user-specific configuration setting values will be lost, and will need to be manually set again.)
Congratulations on publishing the most interesting userscript I’ve seen yet. I’m no academic, but I feel certain that there is potential for a doctoral thesis involving how the brain functions with and without this script. There is something particularly fascinating about providing this specific kind of context.
I’ve no question whatsoever that installing this script will improve my accuracy immediately. Even Japanese natives discuss how much harder it is to read (and remember) kanji in isolation.
My goal with WK has always been to learn to read and write Japanese, not to memorize kanji. Personally, I’ve little interest in the etymology of individual characters, 書道, or whatever, and real-world reading will always be in context anyway.
And yet …
Somehow I’m too squeamish to actually try it, but I’m not completely clear in my own mind why.
Fortunately, there are people here far smarter than me with brilliant ideas:
With this change, I’d install it without a moment’s hesitation.
I’m not sure, but I think my squeamishness is related to writing/production.
There are so many gradations of meaning in written Japanese that depend on selecting the correct character in your IME.
Always seeing context (effectively reading prompts) feels like a cheat somehow. I worry that I’ll answer correctly more often, but not program my brain to see and understand important differences.
I feel the same way about reordering scripts that always test reading first. I honestly appreciate that WK seems to randomize whether I’ll see meaning or reading questions first. It definitely feels like I’m exercising different neural pathways when the first question for an item goes in a different direction.
You’ve consistently written “TaperMonkey” rather than “TamperMonkey” throughout.
Somehow I feel like this is Penn and Teller forcing me to focus on something utterly unimportant while all the interesting stuff is going on elsewhere…
This script really helps in cases where I draw a blank on the meaning and/or reading of a kanji when seeing it in isolation.
…It’s just a darn shame I can only use it on WK on desktop. This and the ConfusionGuesser scripts are ones I desperately wish I could use on mobile apps like Tsukurame, since I use a mobile app to do pretty much all of my reviews (if I waited until I got home from work to do my daily reviews, I’d be stuck with like over 100-200 reviews on some days, lol.)
What I like to do on the Flaming Durtles app is have the reviews reverse sorted by type, so all vocabulary come first. Then when I’m down to only kanji (and radicals), I can opt to switch over to desktop browser.
I don’t know if Tsukurame has sorting, or if you’d even want to use sorting if available, but it’s worth considering.