venetiansnares said... The ability to scroll while in landscape would be nice
On which activity? on my phone I can scroll everywhere, regardless of the orientation.
Both lessons and reviews.
Oh, I see: never noticed that because on my phone, landscape is unusable and portrait contains everything. So I thought you were talking about the app itself.
Ok, I lied: I can't see :) I've checked with my phone and a 4.3 emulator and in landscape mode it scrolls fine. What's your android version and screen size? Does it happen even when using the native keyboard?
Al4ric said...
I'm sorry but either I'm blind (very likely) or I'm doing something wrong. Where is this ignore button? I cannot find it.
Lol, no, you are not blind: the button is simply in a position not completely obvious. It is a menu item that appears only after entering a wrong answer (i.e. when the text box is red). After using it a good deal, I think a menu item rather than an HTML button is the right choice on a mobile device: it is not too tempting (on large screens) and still easy to access (on small screens). Problem is to give a hint where you can find it (and I guess the message box that appears when entering the review screen the first time is not clear enough...)
Thank you, this clarifies the issue (and now I remember you already gave me your specs :) I'll check if I can reproduce the issue: problem is I tried with an emulator running JB 4.3 and pages scrolled fine. Even if I can fix that, however, that it would still be clumsy because you won't be able to see both the question and the answer. Next release supports a "fullscreen mode", similar to an ebook reader: I'd suggest to give it a try (it is not enabled by default). If that's not enough, I may try to remove some less important content. For instance the lessons navigation bar could be hidden when in landscape: it only contains a link to the dashboard..
Well, it was easier than expected, and the next release will have this feature (now that I'm using it, I can't do without it :) Check the menu because it is disabled by default. Besides, did you have a chance to try the experimental builds? Maybe the custom IME fixes the odd problem you reported...
Thanks for the fixes! As to the problems I reported earlier, the phone I had at the time was an endless source of frustration so I returned it. WK always worked fine on my old phone and still does, so that's what I'm using for now.
Satoshi said...
Just installed the new RC and it works great. Thanks for the app! Consider adding the option to automatically move to next item when the answer is correct. Like this: /t/WaniKani-Improve-222-—-faster-and-smarter-reviews/2858/1
Thanks to @Seiji's kind permission, here's a beta APK that has (among some other stuff) also this feature: https://www.dropbox.com/s/1281heomfivvasw/WaniKaniMobile-1.7.0pre0-wki0.apk Note that it is disabled by default. Let me know what you think about: I'm still unsure whether it's stable enough to release it next week, or not.
s84606 said...Thanks to @Seiji's kind permission, here's a beta APK that has (among some other stuff) also this feature: https://www.dropbox.com/s/1281heomfivvasw/WaniKaniMobile-1.7.0pre0-wki0.apk Note that it is disabled by default. Let me know what you think about: I'm still unsure whether it's stable enough to release it next week, or not.
Thanks for the update!
I just did around 40 reviews with this turned on and it worked perfectly. I'm using a Galaxy S4 on Android 4.2.2
Hooray! That last update fixed the “swype isn’t inserting spaces between words” and “anything I type with the swype IME keyboard gets called wrong” issues that I never got around to reporting!
If you’re still up for suggestions, I have another one.
Add the option to put the radicals and kanji in the reviews in the beginning. It can be all radicals and kanji like in this script or just from the current level like in the Wanikani customizer. Whatever you feel is better/easier to implement.
I rarely feel like doing or have the time to do many reviews on my phone but just doing those “level critical” ones would be immensely helpful.
Satoshi said...
If you're still up for suggestions, I have another one.
Add the option to put the radicals and kanji in the reviews in the beginning. It can be all radicals and kanji like in this script or just from the current level like in the Wanikani customizer. Whatever you feel is better/easier to implement.
Had a look at the scripts: it seems feasible, though I'll schedule this for the release after the next one. I think I'll choose the first one: it seems easier to integrate and @alucardeck is still active on the forum (I like to receive an explicit permission)
Is anyone else having issues with “compound” kana (e.g. にゅう) getting screwed up in reading reviews? When I try to type something like 「にゅう」 I end up with 「ゅう」 — which, of course, is wrong. I end up using Google Japanese Input to put those in. (The Ignore button has come in handy for that, and for the Chinese/Japanese kanji confusion that I fixed using another app from these forums.)
dgw said...
Is anyone else having issues with "compound" kana (e.g. にゅう) getting screwed up in reading reviews? When I try to type something like 「にゅう」 I end up with 「ゅう」 — which, of course, is wrong. I end up using Google Japanese Input to put those in. (The Ignore button has come in handy for that, and for the Chinese/Japanese kanji confusion that I fixed using another app from these forums.)
Sigh... my hope was to fix all these issues with the new IME... A few questions: * Does it always happen? * Are you using a Swipe keyboard, or any other keyboard that enters text "word by word"? If not, is the "n" displayed initally? * In the example above, you enter "nyuu"? Thanks!
s84606 said...Sigh... my hope was to fix all these issues with the new IME... A few questions: * Does it always happen?
Seems pretty consistent, unfortunately.
* Are you using a Swipe keyboard, or any other keyboard that enters text "word by word"? If not, is the "n" displayed initally?
I use SwiftKey. Initially, I was using the built-in IME, but I had an issue with it, activated the system IME, and haven't been able to figure out how to get the built-in one back. (Tried toggling the checkbox, to no avail.)
* In the example above, you enter "nyuu"?
Correct. I apparently have no reviews due, so testing character-by-character isn't possible right now. But I can say with no uncertainty that everything is fine until I type that final 'u'; that's when the initial 'に' disappears.
* Are you using a Swipe keyboard, or any other keyboard that enters text "word by word"? If not, is the "n" displayed initally?
I use SwiftKey. Initially, I was using the built-in IME, but I had an issue with it, activated the system IME, and haven't been able to figure out how to get the built-in one back. (Tried toggling the checkbox, to no avail.)
The new IME became the third input method, so I had to change that specific setting: now it is called "Reviews kbd". I suggest to keep "Custom IME", anyway, because that's the only input method that supports all the "interesting stuff", like Ignore button etc. The checkbox applies to lessons only.
* In the example above, you enter "nyuu"?
Correct. I apparently have no reviews due, so testing character-by-character isn't possible right now. But I can say with no uncertainty that everything is fine until I type that final 'u'; that's when the initial 'に' disappears.
I wonder if it's related to autocorrection: does it happen when using other keyboards too? What happens if, keeping the SwiftKey kbd, you enter "nyuu" when WK is asking for a meaning?
* Are you using a Swipe keyboard, or any other keyboard that enters text "word by word"? If not, is the "n" displayed initally?
I use SwiftKey. Initially, I was using the built-in IME, but I had an issue with it, activated the system IME, and haven't been able to figure out how to get the built-in one back. (Tried toggling the checkbox, to no avail.)
The new IME became the third input method, so I had to change that specific setting: now it is called "Reviews kbd". I suggest to keep "Custom IME", anyway, because that's the only input method that supports all the "interesting stuff", like Ignore button etc. The checkbox applies to lessons only.
Toggled the "Reviews kbd" setting from "Custom IME" to "Embedded Kbd" and back to "Custom IME"; my next review is in about 22 hours. -.-
* In the example above, you enter "nyuu"?
Correct. I apparently have no reviews due, so testing character-by-character isn't possible right now. But I can say with no uncertainty that everything is fine until I type that final 'u'; that's when the initial 'に' disappears.
I wonder if it's related to autocorrection: does it happen when using other keyboards too? What happens if, keeping the SwiftKey kbd, you enter "nyuu" when WK is asking for a meaning?
I did try it with the stock "Google Keyboard" and had the same problem. SwiftKey appears not to do anything strange if I enter "nyuu" in a non-kana field. It only completes when I hit space, anyway, so the completion functionality shouldn't be involved.
At the very least, I got the sequence of character transformations during my most recent review session:
dgw said...At the very least, I got the sequence of character transformations during my most recent review session:
n: n
y: ny
u: にゅ
u: ゅう
Good to know. This evening I'll build a test APK that prints some state information each time you enter a character. If you can install it temporarily and give me the logs, I'll try to understand what's going on. Thanks!
EDIT: Here is a test APK, which adds a "Log" menu item: https://www.dropbox.com/s/iycj45bb51fxesw/WaniKaniMobile-1.7.0pre1-imel0.apk When you encounter a "Reading" question, please type "nyuu", and touch the "Log" menu. This way the "next" button displays a message dialog instead of sending the answer to WK (so you risk nothing here). If you could send me the screenshot, I would really appreciate it. After that, you can touch the "Log" menu again (or simply start over) and the app will behave exactly as if that feature were not there. Thank you again!
I would just like to say thank you for this, the new version finally displays the ~ on my phone so I no longer have to guess the meanings/readings of word enders and pray I chose the right one. You are my hero.
Satoshi said...Add the option to put the radicals and kanji in the reviews in the beginning. It can be all radicals and kanji like in this script or just from the current level like in the Wanikani customizer. Whatever you feel is better/easier to implement.
I rarely feel like doing or have the time to do many reviews on my phone but just doing those "level critical" ones would be immensely helpful.
...and this is the APK that integrates the Wanikani Reorder script: https://www.dropbox.com/s/axapu3ha6yb0flz/WaniKaniMobile-1.7.0pre1-meters1.apk This APK also contains a feature that was frequently discussed on this forum: when reviewing you can enable japanese fonts even if you don't have a rooted device (yet the phone must still support japanese localization, otherwise the app won't be able to find the font file). To do that, touch the "JP fonts" menu: this will switch between default fonts and japanese fonts (and back).
s84606 said... ...and this is the APK that integrates the Wanikani Reorder script: https://www.dropbox.com/s/axapu3ha6yb0flz/WaniKaniMobile-1.7.0pre1-meters1.apk This APK also contains a feature that was frequently discussed on this forum: when reviewing you can enable japanese fonts even if you don't have a rooted device (yet the phone must still support japanese localization, otherwise the app won't be able to find the font file). To do that, touch the "JP fonts" menu: this will switch between default fonts and japanese fonts (and back).
All good changes, especially the reordering makes it more useful. I find it hard to do reviews effectively without the reorder.
You may want to include the IPAGothic font optionally (if possible, since IDK how this works) for the same reason people requested it on my Kanji Fix app... the default font in 4.1-4.3+ does seem a bit "cartoony". I can't speak for the earlier fonts. The only big drawback is that the font is 5MB in size.
Ascend said...You may want to include the IPAGothic font optionally (if possible, since IDK how this works) for the same reason people requested it on my Kanji Fix app... the default font in 4.1-4.3+ does seem a bit "cartoony". I can't speak for the earlier fonts. The only big drawback is that the font is 5MB in size.
Yes, I agree. In fact in a future release I think I'll give the possibility to download the font from a user supplied URL, so users can choose the font they like (even a font that does not permit redistribution).