Ok, I see, thank you. I'll try to reproduce this on an emulator, since it does not happen on my device. Should be a trivial fix..
jlel said...
Update: The app doesn't allow me to use the Swype keyboard that I have properly. Everytime I try to type any hiragana, it would give me the wrong hiragana. :(
Yes, unfortunately some keyboards do not interact well with the javascripts on the WK review page. I'd suggest trying the embedded keyboard (Settings/Embedded reviews kbd), which is designed in a way to avoid all such incompatibilities.
Ok, I see, thank you. I'll try to reproduce this on an emulator, since it does not happen on my device. Should be a trivial fix..
I really appreciate your quick responses, most devs for paid apps aren't nearly this diligent.
If you're taking suggestions, there's a couple of things that I'd like to see in the app:
LightFlow integration/support for notification LED
Average level time and current level time
Progress estimates (user toggles between defined intervals (ex: every 10 levels, 5 levels, or every 2 levels))/when you will reach X level based on average level time
How much you should be able to read, based upon this post
Version 1.5.1.pre0 is definately the best one do far. However from time to time it still happens that I cannot write in textbox. But this time it only at start. In previous versions it happened in the middle od writing. And a few times it happened with same “page”. For example I got to kanji D and textbox is not “accepting” any input from embeded keyboard, so I quit application and open it again. I go to kanji C and in D it is not working again. And sometimes it would start from D and stop working from start. But when I see D for the third time it works fine.
venetiansnares said...If you're taking suggestions, there's a couple of things that I'd like to see in the app:
LightFlow integration/support for notification LED
Average level time and current level time
Progress estimates (user toggles between defined intervals (ex: every 10 levels, 5 levels, or every 2 levels))/when you will reach X level based on average level time
How much you should be able to read, based upon this post
I like your suggestions, especially because they don't touch the integrated browser part, which at the moment is causing a lot of problems and I'd like to keep frozen. I'll put them into my todo list and implement them as soon as the rest of the app becomes stable again (and if I survive the next week, that seems challenging for non-WK related reasons :) Here is a release that should fix the time label bug: https://www.dropbox.com/s/c7oyv4875oicn6u/WaniKaniMobile-1.5.1pre1.apk I could not run the Nexus 10 emulator (it needs a lot of memory), but I believe it should be ok now.
Al4ric said...
Version 1.5.1.pre0 is definately the best one do far. However from time to time it still happens that I cannot write in textbox. But this time it only at start. In previous versions it happened in the middle od writing. And a few times it happened with same "page". For example I got to kanji D and textbox is not "accepting" any input from embeded keyboard, so I quit application and open it again. I go to kanji C and in D it is not working again. And sometimes it would start from D and stop working from start. But when I see D for the third time it works fine.
You know, lately I've been experimenting a bit and I wrote a minimalistic japanese IME: my idea is to bypass the javascript IME completely and send the resulting string directly to the answer box. I still have to integrate it with the WK javascripts, so I'm not even sure if it is feasable, but if you are interested in it, I can distribute early versions of it as they come available (~2 weeks, if everything goes well).
venetiansnares said...If you're taking suggestions, there's a couple of things that I'd like to see in the app:
LightFlow integration/support for notification LED
Average level time and current level time
Progress estimates (user toggles between defined intervals (ex: every 10 levels, 5 levels, or every 2 levels))/when you will reach X level based on average level time
How much you should be able to read, based upon this post
I like your suggestions, especially because they don't touch the integrated browser part, which at the moment is causing a lot of problems and I'd like to keep frozen. I'll put them into my todo list and implement them as soon as the rest of the app becomes stable again (and if I survive the next week, that seems challenging for non-WK related reasons :) Here is a release that should fix the time label bug: https://www.dropbox.com/s/c7oyv4875oicn6u/WaniKaniMobile-1.5.1pre1.apk I could not run the Nexus 10 emulator (it needs a lot of memory), but I believe it should be ok now.
Al4ric said...
Version 1.5.1.pre0 is definately the best one do far. However from time to time it still happens that I cannot write in textbox. But this time it only at start. In previous versions it happened in the middle od writing. And a few times it happened with same "page". For example I got to kanji D and textbox is not "accepting" any input from embeded keyboard, so I quit application and open it again. I go to kanji C and in D it is not working again. And sometimes it would start from D and stop working from start. But when I see D for the third time it works fine.
You know, lately I've been experimenting a bit and I wrote a minimalistic japanese IME: my idea is to bypass the javascript IME completely and send the resulting string directly to the answer box. I still have to integrate it with the WK javascripts, so I'm not even sure if it is feasable, but if you are interested in it, I can distribute early versions of it as they come available (~2 weeks, if everything goes well).
I think that this is more than feasible. Shouldn't it be possibly to integrate with WK JavaScript IME laterally? Iirc, WK's IME won't touch stuff that's already Japanese, so couldn't you just have the user use your proprietary IME to go from roman to Japanese and then send that right into WK's IME (which would accept it as is)? Please correct me if I'm wrong or over-simplifying anything :)
I can't imagine the N10 emu needing more than 2048MB of ram, since the device itself only has 2GB. I would think that the problem would lie in being able to display the resolution (since most people don't own 2560x1600 or better monitors).
I’m definately interested. If there is new version I can test it. Thank You very much for Your hard work. If there would be paid version I would gladly buy it.
venetiansnares said... I think that this is more than feasible. Shouldn't it be possibly to integrate with WK JavaScript IME laterally? Iirc, WK's IME won't touch stuff that's already Japanese, so couldn't you just have the user use your proprietary IME to go from roman to Japanese and then send that right into WK's IME (which would accept it as is)? Please correct me if I'm wrong or over-simplifying anything :)
Correct. Basically my idea is to place an Android TextView over the HTML text box, so you can use your favourite soft keyboard to type the answers. I have, however, three main concerns:
I must find the correct triggers: the textview should enable/disable kana translation, clear its contents, become green, red or shake when the text box does it. Probably in the initial prototype I'll make it disappear when the user enters the answer, and appear when a new question is displayed. This is simpler because I believe it can be done by watching the "currentItem" jStorage key;
I have no idea of the reasons behind the bug reported by @Al4ric, so if the text box stops accepting input, I'm not sure what will happen..
Of course, this code will be strongly dependent on undocumented features, so even an innocent bugfix or change made by Viet can make this mechanism suddently unusable for everybody, which is a real nightmare :)
I can't imagine the N10 emu needing more than 2048MB of ram, since the device itself only has 2GB. I would think that the problem would lie in being able to display the resolution (since most people don't own 2560x1600 or better monitors).
For some reason ADT says that emulating devices with more that 768M "can give problems on Windows", and these days I can't use Linux. I've tried using a smaller amount of RAM but it crashes...
Al4ric said...I'm definately interested. If there is new version I can test it. Thank You very much for Your hard work. If there would be paid version I would gladly buy it.
Good, thank you. I'll publish new APKs on this thread.
I didn’t see these bugs on the past few pages, so I figured I’d list them just in case they haven’t been reported:
If you start reviews from notification, the “Dashboard” link closes the app.
There is no way to return to your lessons after clicking the info button to view a missed kanji, since back closes the app instead of moving backwards in the browser. You have to close the app (using back) then select the Lesson notification again.
There is no “enter” key during lessons. It’s only an issue because I’ll have to hit the heart several times sometimes after being correct since most of the time there is no indicator a new lesson is loading (hopefully fixed by WK new lessons interface).
Otherwise, love the app, and thanks for linking to my font-fixing app!
Ascend said...
I didn't see these bugs on the past few pages, so I figured I'd list them just in case they haven't been reported:
If you start reviews from notification, the "Dashboard" link closes the app.
Thank you for pointing this out: I'll check it as soon as I've new reviews. Does it happen when the app is already open (and in background) or not?
There is no way to return to your lessons after clicking the info button to view a missed kanji, since back closes the app instead of moving backwards in the browser. You have to close the app (using back) then select the Lesson notification again.
Well, the code for the back button is there, but commented out :) The reason is that if you use it on the info page, the mini-review starts over, and asks for readings and meanings already answered correctly. I had half an idea to modify the info page, but at the beginning of september it seemed the new lessons module was almost done and I abandoned the idea...
There is no "enter" key during lessons. It's only an issue because I'll have to hit the heart several times sometimes after being correct since most of the time there is no indicator a new lesson is loading (hopefully fixed by WK new lessons interface).
The reason is that I could not find a simple way to implement it (the reviews and lessons page are very different). Probably now, after gaining some experience on how WK javascripts work, I could do a better job -- but again, due to reasons above I left it as it is.. This, however, should be easier than the one above and I may give a fresh attempt as soon as I have new lessons.
Walnut said...
Small request for a future version (Don't know if anyone's asked this yet)
A link to browse the forums would be awesome
Yes, it's a good idea. In my wildest dreams I'd like to add a new tab completely dedicated to the forum, which could also track threads and tell you when they have new posts, but I think that for the time being I'll just use the ordinary internal browser for doing that..
I have been using this a lot, but I can’t figure out one thing. How can I go back to a lesson after I clicked on more info button? Like let’s say I got the wrong answer for a lesson, and I click on more info, how do I get back to my lesson? It seems I need to go back to the homescreen and restart the lessons.
Ascend said...
I gave the experimental a shot. There's suddenly a random textbox in the top region, and no integrated keyboard (intentional?).
Thank you for the screenshot. This is really interesting. Actually, the textbox should have appeared exactly on top of the WK textbox: this means that I'm not translating the "HTML pixels" into "Android pixels" in the correct way. I'll have to add a background view to hide the HTML textbox, otherwise it will be too confusing. Hope to release these fixes later today.
EDIT: Just released. This new version should place the box at the right position (and fix a few bugs discovered in the meantime)
On the positive side, dashboard works again.
Good. This patch comes from the "next" branch of the repository, so it will be available on the production releases too.
petitcrabe said...
I have been using this a lot, but I can't figure out one thing. How can I go back to a lesson after I clicked on more info button? Like let's say I got the wrong answer for a lesson, and I click on more info, how do I get back to my lesson? It seems I need to go back to the homescreen and restart the lessons.
There's no other way :) The WK page is not a popup, it has no "close button", and the back button makes things worse (so I disabled it). I hope the new lessons modules will be implemented soon, so we can get rid of this problem.
This isn’t anything new so I’m not sure why I never reported it before, but my level graph is a little messed up. The placement of my level 10 marker is completely off (ie between level 8 and level 9). Not really sure how or why that happened, but I think it’s been like that since you added the graphs.
Ankotaro said...
This isn't anything new so I'm not sure why I never reported it before, but my level graph is a little messed up. The placement of my level 10 marker is completely off (ie between level 8 and level 9). Not really sure how or why that happened, but I think it's been like that since you added the graphs.
It depends on whether the marker is on the "reconstructed gray area" or not. From what you say (and from a screenshot you posted a while ago), we are in the former case. If so, the marker is placed where the first item of level 10 has been unlocked. Could you please download and check (or send me) the results of the {radicals, kanji, vocabulary}/9,10 call? Maybe there's a l10 item which appears as if it were unlocked before time.
Anyone else have a problem with wavedashes being invisible in reviews? I noticed it when I kept getting reviews for 間 wrong because they were actually 〜間. Saw it again later with 〜病, which doesn’t have a non-suffix counterpart in Vocab. Wavedashes do show in the Items tab, so I guess it’s really a problem with the browser. Does the app use the integrated Android browser no matter what? My primary browser is Chrome, and that does render the 〜 (at least on /dashboard), but iirc it had some kind of input issue when I tried to use it for reviews.
This is on a Verizon Galaxy S3, unrooted (locked bootloader so possibly unrootable).
petitcrabe said...
I have been using this a lot, but I can't figure out one thing. How can I go back to a lesson after I clicked on more info button? Like let's say I got the wrong answer for a lesson, and I click on more info, how do I get back to my lesson? It seems I need to go back to the homescreen and restart the lessons.
There's no other way :) The WK page is not a popup, it has no "close button", and the back button makes things worse (so I disabled it). I hope the new lessons modules will be implemented soon, so we can get rid of this problem.
Oh, thank you for answering. At least I know it's not my tablet or something like that.
protospork said...
Anyone else have a problem with wavedashes being invisible in reviews? I noticed it when I kept getting reviews for 間 wrong because they were actually 〜間. Saw it again later with 〜病, which doesn't have a non-suffix counterpart in Vocab. Wavedashes do show in the Items tab, so I guess it's really a problem with the browser.
Actually, on my phone it appears as a square box (which at least is not invisible). I'll check if I can replace it with an ordinary tilde. Problem is that those vocab words are not so frequent, so it can be a long time before I can test it.
Does the app use the integrated Android browser no matter what? My primary browser is Chrome, and that does render the 〜 (at least on /dashboard), but iirc it had some kind of input issue when I tried to use it for reviews.
Unfortunately, only the stock browser offers an API I can use. Of course the app can launch Chrome instead of the integrated browser, if you deselect the option, but you'll loose some features, since it becomes an external process on which I have no control.
petitcrabe said...
Oh, thank you for answering. At least I know it's not my tablet or something like that.
You know, maybe I found a workaround. Next time I've some lessons in the queue I'll test it and make it available on the store if it does the trick.