Version 1.3.1 is available. You may download it at the link at the beginning of the top post.
Hell yeah!! Thanks! : )
Version 1.3.2 is now released. Download it at the link at the beginning of the top post.
This version implements table state memory. This is when you refresh your dashboard or when you go do lessons or reviews, upon returning to the dashboard you will find the table in the same state as it was. Previously the state of the table was reinitialized.
Version 1.3.3 is now released. Download it at the link at the beginning of the top post.
This fixes a minor bug introduced with version 1.3.2. Now when you click the save button in the settings panel it will reset your table position at the beginning. Clicking the cancel button leaves the table position unchanged.
Version 1.3.4 is now released. Download it at the link at the beginning of the top post.
This is a new features release.
The number of tooltip elements is increased from four to six.
You may now specify the sort order, Ascending or Descending for sort criteria.
New information is now available for table data and tooltip.
A new setting allows to select the position of Item Inspector on the dashboard. Big thanks to @Kumirei who showed me how to do it.
@inspectatoro you may now place Item Inspector at the bottom of the screen as you asked.
There is a minor incompatibility with the Leaderboard script. If you select Below panels and you have Leaderboard Item Inspector will install between Leaderboard and the panels.
There is also an incompatibility between Item Inspector and Heatmap Beta 3.0.7.
- If both Heatmap and Item Inspector are positioned at the Bottom position Heatmap will crash.
- Also, if you have Remove Useless Panels and you Position Item Inspector at the Bottom position, Heatmap will crash if positioned Below panels.
These bugs do not affect the current Heatmap V2 so if you are not participating in the BETA there is no problem.
thanks for putting me on the spot again PRouleau.
Version 1.4.0 is out. Download it at the link at the beginning of the top post.
This version adds an item exporter. You click on a button and the items in the current table are copied to the clipboard. You can then paste them in the software of your choice. The items will be listed in the same order as they appear in the table. This copies just the items and not any other data in the table.
The new button:
There are also settings that go with this:
Some radicals have no unicode characters to represent them. They are displayed as images in the tables. These images can’t be exported. These items are exported as latins characters, for example the cleat radical is exported as ‘cleat’. For some applications like word clouds this may ruin the look. You have the option to exclude these radicals from the export.
You also have the option of exporting items one by line or all bundled in a single paragraph.
Finally you may set a limit to the number of exported items. Some tables are large and you may want just the first x items. If the limit is 0 then the whole table will be exported.
@ekg this feature was developed for you. The intent is to give you an easy way to export items so you can make word clouds out of them. The idea is you put items in the clipboard and you paste them in your cloud making software. Let me know how it works for you. If you encounter issues I will try to resolve them.
You’re spoiling me! 有り難うございます!
I wasn’t planning on doing a new cloud so soon, gotta work on those leeches first, but, I can of course give this feature a test run later today! ^>^ I’ll report back my findings then…gotta do lessons first… >_>
So, now that I’m done with the lessons for today, I’ve been trying out your new feature on the Item Inspector. It works like a charm! ^>^
As for making the word cloud, however, I do need to also get the counts for each item correct or you just get a cloud with equal emphasis for all items. That’s not what I did for my word clouds, but I manually repeated all items according to their leech value.
I’m still gonna use this way of extracting the items though, because it’s clearly superior. And it gives me a great overview to do my leech studies with as well! ^>^ (just going through them all, which I really like)
So thanks again for adding this neat new feature!
Version 1.4.1 is out. Download it at the link at the beginning of the top post.
According to @ekg comment, the ability to repeat an exported item according to a numerical value has been added to support proper word clouds. It is in the settings.
@ekg please confirm this is working as is needed.
The top post has been updated and reorganized to reflect the new features added since the original release of Item Inspector.
I just got this idea for a neat feature (at least I thought so), which would allow you to compare a list of leeches taken from the Item Inspector (with or without their leech values, not sure what’s possible here), and then put them against a different leech-list made at a later date - thus exposing which leeches are still on there and which are completely new ones.
(if leech values can be retained, then it would show which leeches are moving up or down the list).
Not sure how any of those things could be accomplished or if they are possible at all to do. But since you said you were working on the script, I figured I might as well put the idea out there.
I really do feel this script has transformed how I approach leeches already, so kudos for making it! ^>^
If you can already pull lists of leeches out (at least, I assume so, because word cloud) then maybe make a spreadsheet and dump the list into that? You could do a compare function to see what both lists share? Would also mean you could save a leech record.
Not as easy as if the script did that for you, but it would work ^-^
I do have Excel…now, knowing how to use it properly, I do not! ;;>_>
Ask, and Google shall provide, hehe
I see…I might wanna have a look into this, in other words. Not sure if I’ll be able to bend it to my will, but I’m gonna check it out. Can’t expect @prouleau to do all the hard work here!
This is a neat idea. The difficulty is a browser does not have access to a lot of local storage so keeping an history within the script is out of question. We have to bring the data out of the script and give the work to an external software. An export to a spreadsheet as @Joeni suggested is the way to go.
I can do a quick simple export function when I am done with the next Item Inspector version I am working on. I can make it so that spreadsheet comparisons will be simple.
You are a darling! I’m pretty helpless around these things, so any help is welcome. It’s not a priority right now either, since I wanted to give my recent studies a chance to take effect (well, I already see movement on the Item Inspector-list, so I know something is working. ^>^)