I wonder if there is a script for all the new items learned in say past couple of days? I love the current review feature, but don’t want to see all the items, just the new ones.
Would be much obliged and thankful.
Is there a script that can show stats about the word? As you can see on Jisho.org, for example - you can see the JLPT level, in which grade is it taught in Japan (even though I don’t think it’s as important), and how common the word is (there’s a list I remember I saw online, some time ago, and on Jisho there’s a “common word” mark (I remember there was a button that said if the word is within the Top 5k (?) most used word in newspapers, too.
Slightly different, but on Jisho you can see collocations of the word, it would be great if someone could word out a way to make it visible\linkable from WaniKani too.
I have a script on my old laptop that would auto-show the lesson info if I answered wrong.
I can’t find it now, can anyone help me find it?
Molans said... I have a script on my old laptop that would auto-show the lesson info if I answered wrong.Look here: /t/The-New-And-Improved-List-Of-API-and-Third-Party-Apps/7694/1
I can't find it now, can anyone help me find it?
Are there any scripts to lock up the descriptions unless you enter it wrong or get both the reading and the meaning correct. I tend to peek a little bit too much that it’s become a habit.
KSamo said... I wonder if there is a script for all the new items learned in say past couple of days? I love the current review feature, but don't want to see all the items, just the new ones.Try this /t/Userscript-Dashboard-Progress-Plus/8309/1 plus this /t/Userscript-Vocabulary-for-Dashboard-Panel-115/15905/1
Would be much obliged and thankful
Probably already been listed but the ability to have single word kanji that are vocabulary - say “we are looking for the other reading” instead of marking as wrong. Basically, what it already does when it is in the Kanji phase.
for example, as a kanji if I put “otoko”/“dan” in for 男 , but the Kanji is looking for the other reading, the text box would jiggle and say “that is the on reading, were looking for kin reading” (or vice versa). It does this already for kanji, but not at the vocabulary level. If I know both readings, I don’t care if I can identify if it is the on or kun reading.
hallus said... Probably already been listed but the ability to have single word kanji that are vocabulary - say "we are looking for the other reading" instead of marking as wrong. Basically, what it already does when it is in the Kanji phase.No, because that would be wrong. Words don't have readings. You get them right or wrong. Ultimately it won't matter if you know both readings and which one is the on or kun reading, because if you wanna say 'man' you better say おとこ. What you're proposing is an easy way out and will probably hurt your learning.
for example, as a kanji if I put "otoko"/"dan" in for 男 , but the Kanji is looking for the other reading, the text box would jiggle and say "that is the on reading, were looking for kin reading" (or vice versa). It does this already for kanji, but not at the vocabulary level. If I know both readings, I don't care if I can identify if it is the on or kun reading.
I would like a script that allows me to test myself on critical condition items, by revealing the reading and meaning when I hover.
Franken said... I would like a script that allows me to test myself on critical condition items, by revealing the reading and meaning when I hover.Are you familliar with JavaScript? You can adjust this /t/Userscript-Vocabulary-for-Dashboard-Panel-115/15905/1 for your needs changing Request URL and some parsing IF's.
Edit - @Mempo I reread what you wrote.
It is the easy way out, but that doesn’t necessarily make it a bad thing.
I find the diff between on and kun knowledge to be about as useful as knowing stroke order - all of us are taking the easy way out by not writing characters a billion times.
In other words- I just don’t care. In compounds, it obviously matters, but in single word vocabulary, I just don’t care.
For my purposes, I find knowing even more than one Japanese reading to be a waste of time, given that I am only trying to improve my ability to translate - Japanese to English (you know, that is the intended learning outcome of this program). HOWEVER, because of compounds, generally people should know more than one reading which is why I am saying that this should be implemented. I don’t actually think wanikani’s purpose at all is to teach English -> Japanese, so I’m not sure what makes you think that you need to know that man is best said as “Otoko” for the purposes of wanikani at least. In kaniwani, or English to JPN, then sure I guess, but I have literally no need to speak Japanese.
it doesn’t have to be a global setting. It would be nice to turn it on for myself.
I don’t know if this script already exists, I tried searching for it and couldn’t find it. I’d like to be able to see a more detailed SRS breakdown on my homepage (listing number of items in Apprentice 1, 2, 3, 4 and Guru 1, 2). Does it exist? Would it be difficult to knock up?
ありがとうございます!
Not sure that’s what you’re looking for, but here is what I use:
Yeah I saw that one, it’s not really what I’m looking for. That’s a breakdown by type of item rather than level of item. Thanks though!
Its possible, but would be slower. Probably not obnoxiously slow, but probably noticeable. Also would be different API calls than what my scripts currently doing, so not a quick addition. Plus, that’s a lot of info to show in a fairly small space. Not sure how pretty it would be.
http://wanikaniexplorer.com/ is a stand-alone site that will give a detailed breakdown of everything. Not exactly what you’re looking for either though. Gives a breakdown of everything and what level it is, but don’t think it gives a nice total.
Edit: Looks like that site may not work anymore… It says I’m level 3. Also says data was retrieved sometime in late 2015 (forget the exact date now)
Yeah, I don’t know anything about script writing so I don’t know how hard it would be, but I thought as the Reviews Timeline script shows the SRS level of each item it might be possible.
Regarding design, I just knocked this together (very roughly), but I don’t think it’s the ugliest thing in the world:
Ah. Thought you were talking about breaking each level into radical/kanji/vocab/totals like my script does, but expanding each of those into their respective levels, creating a 4x4 grid (plus titles)
Ah yes that would be too much! No, this is all I’m after.
This will give you an array of how many items are in each level (1-9). Take those, build your html, and shove it in there.
I stopped at this point because the amount of time it takes to get the information is pretty bad, and will only be worse the higher level you are. Review timeline (if I remember right) does some fancy work to only query what it needs. My notification script does something similar. So its possible to speed it up, but its a fair amount of work, which I unfortunately don’t really have time for. If you don’t care about the speed, or you want to try your hand at some scripting (or someone else wants to run with this), here ya go.
// ==UserScript==
// @name WK testing
// @namespace http://tampermonkey.net/
// @version 0.1
// @description try to take over the world!
// @author You
// @match https://www.wanikani.com/dashboard
// @grant none
// ==/UserScript==
(function() {
'use strict';
var apiKey = 'xxxxx'
var radicals, kanji, vocabulary;
var levelAmount = [];
$.getJSON('https://www.wanikani.com/api/user/'+ apiKey +'/radicals', function (data) {
radicals = data.requested_information;
$.getJSON('https://www.wanikani.com/api/user/'+ apiKey +'/kanji', function (data) {
kanji = data.requested_information;
$.getJSON('https://www.wanikani.com/api/user/'+ apiKey +'/vocabulary', function (data) {
vocabulary = data.requested_information;
for(var i=1; i<=9; i++){
var amount = 0;
amount = amount + jQuery.grep(jQuery.grep(radicals, function( n ) { return ( n.user_specific !== null ); }), function( n ) { return ( n.user_specific.srs_numeric == i ); }).length;
amount = amount + jQuery.grep(jQuery.grep(kanji, function( n ) { return ( n.user_specific !== null ); }), function( n ) { return ( n.user_specific.srs_numeric == i ); }).length;
amount = amount + jQuery.grep(jQuery.grep(vocabulary.general, function( n ) { return ( n.user_specific !== null ); }), function( n ) { return ( n.user_specific.srs_numeric == i ); }).length;
levelAmount.push(amount);
}
});
});
});
// Your code here...
})();
Cool, maybe I’ll try my hand at it at some point! Thanks