Hmm, it’s still not showing up on the menu. I have the latest Google Play version. Do I need to install the script separately or anything?
Sometimes you need to open menu more than once. For me it usually works for second time. For example: item is red I press menu and it is not present I press it again to close menu and again to show it. Second time menu appears it has more items (one of them is “ignore”) .
Al4ric said... Sometimes you need to open menu more than once. For me it usually works for second time. For example: item is red I press menu and it is not present I press it again to close menu and again to show it. Second time menu appears it has more items (one of them is "ignore") .You know, I noticed the same behaviour with the dashboard menu, which is static: the first time it is opened, the fourth item is not shown. At first I thought it was a problem with the emulator, since it does not happen on my phone. Later today I'll prepare an APK, which:
- Moves the ignore item at the top
- Removes the "export", which I believe is useless in that context
The latest version works. Nothing else to add 
Satoshi said... The latest version works. Nothing else to add :)Feel free to ask more features: people love the ones you requested ;)
Al4ric said... Sometimes you need to open menu more than once. For me it usually works for second time. For example: item is red I press menu and it is not present I press it again to close menu and again to show it. Second time menu appears it has more items (one of them is "ignore") .Ok, here's the fix for this problem:
https://www.dropbox.com/s/gbbny0xu4y8gw1x/WaniKaniMobile-1.8.0pre3.apk
Besides it also has a more modern look, with the cute menu icons I lovingly hand-picked or gimp'd (I'm especially proud of the JP fonts icon :D).
I'd also like to know about its usability when doing reviews in full-screen mode on devices that have no hardware menu button.
s84606 said...Feel free to ask more features: people love the ones you requested ;)I don't think I can think of much else...
Oh yeah, you could expand the "other" stats a bit. Add a "percent learned" and learned/total to every jlpt and joyo level. Learned meaning having a kanji at guru and above.
For example:
N5
Master 1
Enlightened 2
Burned 76
79/79
100% learned
Or something similar
Also maybe a number of total jlpt kanji learned/total kanji (in the jlpt or joyo) for the jlpt and joyo.
Example:
Joyo Progress
G1
G2
G3
G4
G5
G6
S
2000/2136
93.6% learned
As for features, when the client side lessons get implemented tomorrow you could make a reordering script for the lessons to put radicals in the front if you want.
Satoshi said...Oh yeah, you could expand the "other" stats a bit. Add a "percent learned" and learned/total to every jlpt and joyo level. Learned meaning having a kanji at guru and above.Good point. I'll add this to what is described in:
https://github.com/WaniKani/Android-Notification/issues/3
I bet in a couple of days someone will come up with a userscript. As soon as it is available, I'll embed it.
As for features, when the client side lessons get implemented tomorrow you could make a reordering script for the lessons to put radicals in the front if you want.
Ok… new lessons module is out. I have no lessons available, so I can’t check. The review module, at least, seems to work fine.
Is it ok for you all too, or do I have to distribute an emergency patch ?
I just did a handful of lessons and it seemed to work fine, other than a cosmetic issue with the last answer overlaying the “do you want to stop here or do more lessons?” splash screen.
protospork said... I just did a handful of lessons and it seemed to work fine, other than a cosmetic issue with the last answer overlaying the "do you want to stop here or do more lessons?" splash screen.Good, thank you. This is the build I'll release in a few days, which fixes this specific behaviour:
https://www.dropbox.com/s/j2quhpy2ntid5wq/WaniKaniMobile-1.8.0rc1.apk
A small request again. Can you make links from the forums open up in an external browser when clicked on in the internal browser of the app?
I was browsing the forums and wanted to download the new version that you just posted from my phone but when I tried to open it I got an error. And this happens with every link.
Satoshi said…Good point. Here’s the last APK you need to download by cut&paste:
A small request again. Can you make links from the forums open up in an external browser when clicked on in the internal browser of the app?
I was browsing the forums and wanted to download the new version that you just posted from my phone but when I tried to open it I got an error. And this happens with every link.
https://www.dropbox.com/s/ufsr8kxpzyvlrhc/WaniKaniMobile-1.8.0rc2.apk
BTW this fixes @Seiji’s script too (the button disappeared after the last WK update)
Wow you really are fast. If you were the programmer on Wanikani it would be out of beta a year ago XD
Satoshi said... Wow you really are fast. If you were the programmer on Wanikani it would be out of beta a year ago XDnot necessarily, but s84606 is pretty awesome
btw, the new stats page is very nice!
I wanna thank you for making this.
I am so happy that this works on my Kindle Fire x3 thank you very much!
Satoshi said... Wow you really are fast. If you were the programmer on Wanikani it would be out of beta a year ago XD
SamusAranX said...Lol, don't make blush :) Working on a platform with so many users would ruin my sleep...not necessarily, but s84606 is pretty awesome
Demonskid said... I wanna thank you for making this.Glad to head this, welcome aboard. Hope you'll enjoy this site!
I am so happy that this works on my Kindle Fire x3 thank you very much!
Something you changed in the most recent store release re-broke Swype keyboard input for me, in both languages. In English, it’s gone back to not inserting spaces between words, and in Japanese I can no longer Swype at all, it just inputs the last character I touched. I’m using the ‘custom IME’ option, which worked before, but I also tried the other options (and restarted the app in between) with no return to the old behavior.
I do like the in-place kanji fix, though.
protospork said... Something you changed in the most recent store release re-broke Swype keyboard input for me, in both languages. In English, it's gone back to not inserting spaces between words, and in Japanese I can no longer Swype at all, it just inputs the last character I touched. I'm using the 'custom IME' option, which worked before, but I also tried the other options (and restarted the app in between) with no return to the old behavior.Makes sense: I changed the behaviour of the textbox to skip suggestions and autocorrection when in japanese. Thought it could be useful. It wasn’t.I do like the in-place kanji fix, though.
Here’s an APK that restores the old behaviour:
https://www.dropbox.com/s/wuiaie4epz6anzh/WaniKaniMobile-1.8.1rc0.apk
Could you please try it? If it works for you, I’ll push it on google play.
And… out of curiosity, when entering japanese words, doesn’t the autocorrection get into the way?
EDIT: Apparently some JB users appreciated the change. Could you please try this instead?
https://www.dropbox.com/s/5j6ejn5fhxu5mik/WaniKaniMobile-1.8.1rc1.apk
The difference is that the behaviour is configurable (default is pre 1.8.0)
Tried RC1, kanji input works great; english input still seems to ignore spaces, which isn’t a huge problem since the review system does as well. Thanks.
And… out of curiosity, when entering japanese words, doesn’t the autocorrection get into the way?The way Swype’s JP keyboard works, hiragana is input first, and the autosuggestions are all kanji forms. Which I guess is a form of cheating if you actually look at those.
protospork said...The way Swype's JP keyboard works, hiragana is input first, and the autosuggestions are all kanji forms. Which I guess is a form of cheating if you actually look at those.Ahh.. I see, so you use the JP keyboard. I did not suspect that. The idea of this patch was to allow people to use the US (or any other language) keyboard. Unless I receive other complaints, I'll switch to default=true then (nothing changes for you, anyhow, since the current value has been set).
Then I'd like to understand why autospace is disabled. It is, as you say, a less important issue, but it puzzles me, since I can't see what changed since rel1.7.
BTW is there anyone else who noticed a similar behaviour?