Namely: https://ankiweb.net/shared/info/1645629943
Does anyone have any ideas for how I can improve this? Also any bugs/bugfixes...
Does anyone have any ideas for how I can improve this? Also any bugs/bugfixes...
The layout is fine; clear and functional.
frony0 Wrote:I noticed the odd grading too, it was indeed an overflow bug. Fixed now (at some point along the line for intervals greater than 180, I turned the score from float to int inadvertently, rounding it down to 0). Thanks for pointing that outNever mind, I just thought field confusion was a more plausible cause for the grading bug than an overflow. If it was an overflow issue after all there's no problem at all
As for choosing the field, right now it's chosen by using the first field to contain "testing_field" in any case, which is by default "kanji". It seems a little overboard to add a whole preferences screen and database, so should I just add an intermediary screen to choose the settings?
An intermediate field selection screen would still be useful if the correct field can't be autodetected, though.Daichi Wrote:Whenever I run it, it leaves empty little anki windows floating around the screen. (They look like screwed up Anki progress bar windows.) I can only remove these by closing Anki.Hmm, I'm not getting that, but then I'm on linux. I moved the progress windows a bit later, because there was a delay between them closing and the window opening, but I'll try closing the progress windows a little earlier, maybe that'll fix it.
Daichi Wrote:When you sort by score, you might wanna order from strong to not seen. Showing all the kanji you have never seen first doesn't seem as useful.I meant to do that actually, but forgot... Sorry!
Daichi Wrote:When sorting by grade, you might wanna have the Non-Jouyou be at the bottom, instead of the top.Fair enough. That was the order I found the lists in when I copied them from the JP plugin. Done anyway
Daichi Wrote:On the output window, at the top it shows Weak[color gradients] Strong, but it looks fine on html export.I think that was a typo, though again, I don't see that (different html engines maybe). Hopefully fixed
Daichi Wrote:This is what my sorted kanji grid looks like. This is much more useful than the Kanji Stats that the Japanese plugin spits out. (One of the problems I have with that is you can't restricted it to one field on your card, so it gets a bunch of Kanji on the card that are for reference not review.)No problem!
Thanks for your contribution.
The seen cards in this collection contain:
1536 total unique kanji.
Old jouyou: 1368 of 1940 (70.5%).
New jouyou: 59 of 196 (30.1%).
Jinmeiyou (regular): 63 of 641 (9.8%).
Jinmeiyou (variant): 0 of 145 (0.0%).
46 non-jouyou kanji.
Jouyou levels:
Grade 1: 80 of 80 (100.0%).
Grade 2: 153 of 160 (95.6%).
Grade 3: 186 of 200 (93.0%).
Grade 4: 181 of 200 (90.5%).
Grade 5: 160 of 185 (86.5%).
Grade 6: 143 of 181 (79.0%).
JuniorHS: 465 of 934 (49.8%).ryuudou Wrote:Yes all of those things are true. Sure.It turns out the problem was because although the "kanji" field is the first in the notetype editor, it's not in the database, so another field was being chosen instead. I've added a "match exactly" field option (still case insensitive though), so you can type the field name exactly and have it search for that.
<Link>
Daichi Wrote:frony0, go right ahead and use my grid as a sample.I added "sort by frequency" while fixing ryoudou's problem, but I'm not sure about external frequency lists... That would probably involve adding another dialog, and a lot more lines of code not to mention runtime. But I have a skeleton idea already of how to do it if you think it's worth it...
Couple other suggestions. Sort by frequency options. Frequency seen in your own cards, and also by an external frequency list, maybe so you can sort by newspaper frequency data or something you collected yourself.
Maybe more stats could be useful. If you look at the Japanese plugin it lists all sorts of good info.
<code>
And at the bottom it goes on to list what kanji from each grade are missing from your collection.
frony0 Wrote:Thank you very much!ryuudou Wrote:Yes all of those things are true. Sure.It turns out the problem was because although the "kanji" field is the first in the notetype editor, it's not in the database, so another field was being chosen instead. I've added a "match exactly" field option (still case insensitive though), so you can type the field name exactly and have it search for that.
<Link>
ryuudou Wrote:No not at all! I just didn't take into account that the order they appear in the editor and the order in the code could be different. My faultfrony0 Wrote:Thank you very much!ryuudou Wrote:Yes all of those things are true. Sure.It turns out the problem was because although the "kanji" field is the first in the notetype editor, it's not in the database, so another field was being chosen instead. I've added a "match exactly" field option (still case insensitive though), so you can type the field name exactly and have it search for that.
<Link>
Since you mentioned database was it an issue with my deck..?