Kanji learning progress review improvements

[GoogleCodeExporter]

- Show kanji details on kanji click
- Ability to view multiple jlpt levels, can be done with ranged seekbar 
http://range-seek-bar.googlecode.com/files/screenshot3.png or with simple 
checkboxes
- Sorting by stroke order, reading etc
- Tip at the top should be hideable, maybe better use an alert with a checkbox 
"don't show again", or an actionbar action "help"
- Not only JLPT, but Jouyou, Heisig etc, probably better use same ui logic as 
in word search (Advanced search settings)

Original issue reported on code.google.com by kazufuku...@gmail.com on 9 Dec 2014 at 9:57

[GoogleCodeExporter]

Sure, this makes sense. Just regarding the "sorting" requirement - can you 
please post a small story on why this feature is important to you? I'm just 
curious; also, I wish to see some justification of a feature before I implement 
it.

Original comment by martin.v...@gmail.com on 17 Dec 2014 at 4:12

[GoogleCodeExporter]

Implemented 1. and 4.

Original comment by martin.v...@gmail.com on 17 Dec 2014 at 8:23

[GoogleCodeExporter]

Sorting will help to locate concrete kanji in the big grid. 機 will be 
somewhere at the end of grid if I sort by stroke count. 会 will be at the 
beginning if I sort by by kunyomi. Maybe I'm bad at kanji with しょう onyomi 
and I will see solid block of red kanji if I sort. BTW which is default 
sorting? it looks random.

Original comment by kazufuku...@gmail.com on 17 Dec 2014 at 8:29

[GoogleCodeExporter]

Implemented 2. and 5., sorting will be implemented in next version

Original comment by martin.v...@gmail.com on 18 Dec 2014 at 9:18

[GoogleCodeExporter]

Just thinking: if a kanji has multiple readings, which one should I pick for 
sorting? I may pick a random one, or all, but there is no good strategy to 
group e.g. kanjis with the しょう onyomi... Let us think about this more.
Meanwhile, I will implement the occurence- and stroke- based ordering.

Original comment by martin.v...@gmail.com on 28 Dec 2014 at 10:14

[GoogleCodeExporter]

Original comment by martin.v...@gmail.com on 28 Dec 2014 at 11:29

• Changed state: Fixed

[GoogleCodeExporter]

I think the only way is to separate onyomi and kunyomi and use first, usually 
the most used reading.

Original comment by kazufuku...@gmail.com on 31 Dec 2014 at 11:54