Could you post any pictures? I’m currently on a work PC so I don’t want to download anything 
2 Likes
@TheFlaminMunch I’ve updated the main post to include pictures 
I’ll eventually redo the main GIF when I can get it down to less than 4MB, it’s currently 18MB >.<
2 Likes
Woah that looks great!
2 Likes
This looks really nice. I will say that one thing that should be fixed if it can be is to try to allow some other scripts (maybe like common ones that people have) to be able to work with this script.
1 Like
@Tomy56739 thanks! Can you please give me some examples of some common scripts? I only use this and Jitai, I’ve not had any need for any others so didn’t even think to include compatibility 
I’ll also add that to Known deficiencies.
You should take a look at @jprspereira 's guide. The scripts recommended in section 7 are hugely popular because of the recommendation.
As the author of Item Inspector I request you provide compatibility for my script.
1 Like
Thanks for that link @prouleau I’ll review the list and see what ones I’ll include. It’ll be impossible to include all of them of course, and really I’ll probably just focus on the dashboard specific userscripts.
It was frustrating enough just to learn how to incorporate multiple files without using a webpack project, so I think it’ll take some time to go through example scripts to reverse engineer how to make mine compatible, so it may take some time and not be done quickly, but I’ll do what I can
1 Like
I think many of the dashboard scripts just append or prepend themselves to some div or section in the dashboard. As long as you don’t change the id or class of the dashboard html elements they should work fine. Scripts like the heatmap or my Item Inspector would fall in this category.
There are also the scripts like Dashboard Progress Plus that actively modify WK dashboard elements. Then there may be conflicts between their modifications and yours.
1 Like
Ah, then there’s a major problem there because my userscript is a literal rewrite of the dashboard. I generate my own dashboard HTML, use JS to remove the existing dashboard, then add my custom HTML to the page instead.
I thought about just modifying the original but it was far more work than writing my own. I’ll look at the IDs and elements that they’re using, because that might be simple enough, but yeah that could be interesting haha
1 Like
The insertion code for Item Inspector is here.
if (quiz.settings.position === undefined) {quiz.settings.position = 2};
let position = [".progress-and-forecast", '.progress-and-forecast', '.srs-progress', '.span12 .row', '.span12 .row:last-of-type',][quiz.settings.position];
if (quiz.settings.position == 0){
$(position).before(sectionContainer);
} else {
$(position).after(sectionContainer);
};
The user selects a position via a setting like this:
Then the script installs itself either after or before some HTML elements identified by classes. There is a pitfall. What happens if you support only the default position and the user changes for one you don’t support? Will he be stuck without being able to change back his position to the one that is supported? There may be one way out. The settings will be available from the dropdown menu even if the main script doesn’t inserts.
I know the heatmap also has the ability to let the user choose its position.
At least this code gives you positions that are likely to be used by scripts.
1 Like
@prouleau thanks for this, I’ve gotten a bit of energy to do some coding, so I’ve gone through the whole list in the link you gave, and I’m in the process of testing out what classes and such I need to add to accommodate almost all dashboard related userscripts
Simply put, I’m aiming to try and give all of those options IF possible without needing a massive overhaul of my code.
I’ll let you know when I’ve got an update to 1.1 for you to test if you have time today when it’s done?
1 Like
I am OK with doing a test. I don’t promise how fast it will be. It will depends on my availabilities.
Of course! No rush, I’ll be doing testing myself of course, but I figured it would help to have someone else run their eye over it at some point 
1 Like
Just adding some points to keep an eye on.
- Some dashboard scripts install themselves in the top bar. The classes I provided don’t account for this.
- Some scripts modify the reviews and lessons buttons to include popups to display information.
- Also the dropdown menu when you click the round icon on the top right corner is where almost all scripts insert their settings.
1 Like
Yeah the top bar is the part giving me trouble at the moment.
Thanks, though I’m excluding those ones since those buttons will won’t exist in this dashboard and some of the information is already available elsewhere on the dashboard. The shortcut navigation buttons are different because I’m just modifying the colours and text in them, not recreating them so things like the Lesson Hover Details and Level Duration 2.0 work fine as is.
Thank you, that one I did know but it’s good to have for those that don’t
1 Like
@prouleau I’ve made the updates so this is now v1.1 so feel free to update and have a look when you’re able and let me know what you think
I’ve also updated the main post to include a changelog and compatibilities.
5 Likes
I have done a little testing. First there are two things you may want to address.
Here:
And here:
Nest the good news. Item Inspector works fine. I have found a bug in Item Inspector that cause CSS not be correctly applied when the position settings is changed. This problem can be worked around by refreshing the browser. It will be fixed in the next version of Item Inspector which is due shortly…
I also found that Self-Study Quiz and Leech Training are working out of the box. They are arguably the two most important scripts not mentioned in your top post.
For Self Study Quiz this is a by-product of the settings installing correctly in the Wanikani dropdown menu. Leech Training inserts nicely in the top bar.
Another good point: if people want leeches instead of critical they may install Item Inspector and Leech Training and they will be OK.
Finally I have questions about your critical condition.
- What is the threshold for critical condition be listed on the dashboard?
- What is the correlation between your formula and the trouble in reviews an item cause?
Concerning point 2, I have in the Item Inspector top post a section titled Leech Value that explains how the metric correlates with trouble in reviews. People can interpret the numbers to gauge how much trouble an item gives them. I don’t find similar information in your top post and I can’t figure out this correlation from the formula alone.
I get that you consider troublesome any item older than three levels and still in Apprentice. I don’t see how that correlates with the formula. Why not coding that directly instead of having a formula? For example it is easy to set filters for this in Item Inspector and Self-Study Quiz. Here it is.
Then you can get the full power of Item Inspector and Self Study Quiz with your definition of critical items. You can also set the filters programmatically and have wkof.ItemData.get_items() return the items for you.
Thank you for testing this for me
For the undefined portion, I’m not sure where that’s coming from. I might have to force false data to see that because it’s not appearing for me at this stage. It’s supposed to show the next review time. Is there anything about it that you can shed light on, like if you’re in vacation mode or anything?
And the larger numbers, that’s fair I’ll see what styling fixes I can apply.
For point 1 there is no threshold for the number of critical items to be listed. It will list everything that fits within the parameters of a “critical item” until such time as there aren’t any more of them.
For point 2 the formula is primarily for sorting and the inner shadow. The idea was that say: I’m now level 10, so if I have a level 1 item that’s at SRS level 1 (Apprentice 1) then the inner shadow will be very dark to the point where the background may be almost black rather than purple, blue or pink for the item type. As for the use I get from it? Well it was more that I felt that items that old should at least be in guru by now, so I tend to use it as a tracker of what keeps going up to guru then back down to apprentice. I’ll try to reword that section in the top post to make it clearer.
The reason that the critical items section isn’t as clear cut as the rest is because it was the first piece of additional information I added via userscript, even before I had the idea of making a fully custom dashboard and I haven’t changed its base code since then. I have plans to overhaul it to resemble leech items more, and even make it optional to display via settings when I get around to adding some settings.
I didn’t understand leeches way back then, but I knew I wasn’t seeing items that I knew I wasn’t doing so well with. Now that I understand the available data better I can rework the formula to something more useful.
As for the usage of other userscripts to get this information, I could use them but I haven’t and don’t at this stage. The reality is that I never went looking for any and used this as an opportunity to learn how to create userscripts instead. Now that I know of other userscripts with similar setups, I’ll either modify the critical items to compliment them or I’ll remove it altogether.
1 Like
I have no reviews in the future. All my items are due to review right now because their review dates are all in the past. I am currently taking a break of reviews because I am busy scripting and I didn’t turned on vacation mode…
This is not my question. You have a formula. Which value the formula must take to get an item listed as opposed to a value that doesn’t get it listed? I didn’t see this information anywhere.
This is curious. Which software did you use to list your leeches back then?
The most commonly used formula for leeches will mark an item as a leech as soon as you fail a review. You need to get it right a number of times in a row to bring it out of leech status. The more you have failed an item, the longer it takes to bring it back. Look at the explanation on top post of the Item Inspector thread for details. The formula is given and explained.
I mean to say, the leech formula is very sensitive. You shouldn’t have items that you feel are in problems and don’t show up because, as I said, if you fail them they automatically get marked, even if there is only one failure.
Ah, it should show a title of ‘次の復習をなんでもない’ with 0’s for all the item types. Could you please do me a favour and turn on debugging mode (from the boolean toggle) and look at your console for the log “Generating future reviews HTML with the following data.”, open the object next to it, and show me the data in it? I would assume there would just be a list for the next 24 hours all with no items which is catered for in the code, so I’m wondering if there’s an undefined somewhere.
Oh, well every item gets tagged with a critical value. Quite literally ANY item that is in SRS level 1-4 (Apprentice) AND is 3 levels below your current level should show. The critical level itself is only used for the sorting and inner box shadow. I did update the main post so hopefully it makes more sense but I’ll see if I can refine it again.
That’s just it, I wasn’t using any software or userscript at all, just the original WaniKani dashboard. I was also a bit annoyed that I had to open a whole new page just to see all of the items as well haha. So I had two choices then, find something to help or make my own. I chose to make my own purely for the experience, and it grew from there into what I have today.
In essence, I built this dashboard for my own personal use as a one-stop-shop for installation and usage without needing to configure anything or install multiple scripts. In saying that, I had NO IDEA just how many decent options there were for things like leeches. Now that I know there are heaps, and that I’m comfortable with my ability in creating userscripts, I can look at options to add rather than packing them into my userscript