search

cplaverty / KeitaiWaniKani

Third-party WaniKani companion iOS app
MIT License
38 stars 15 forks source link

Feature Request: Auto Keyboard Choosing #42

Open UInt2048 opened 5 years ago

UInt2048 commented 5 years ago

In 4.0, with the introduction of native reviewing, can there be a setting to automatically choose one keyboard for English and another for Japanese?

Mercieral commented 5 years ago

Personally IMO, this seems like a bad idea and the app should be trying to prevent the user from using the iOS Japanese keyboard. The Japanese keyboard makes cheating way too easy because you can type the hiragana and know if you're right/wrong just by seeing if the suggested kanji matches befores submitting...

chrisjwelly commented 5 years ago

I agree with @Mercieral . I had experienced practising with the Japanese keyboard on KaniWani and I always noticed I get Kanji suggestions from the keyboard, which is bad for learning.

Perhaps it would be good if we could have a custom keyboard, where the suggestions are disabled. I'm not sure how feasible this is for iOS though.

Mercieral commented 5 years ago

Agreed. There have been several times where I've felt that using an actual kana keyboard or something like it would be really useful for practice, but I ended up using the suggestions too much which is a big no-no.

I could see something like a kana "keyboard" on a view that's really just a bunch of buttons injecting text into a field working, but it would be pretty difficult I'd imagine.

Although this does bring up a good point that @cplaverty is going to have to consider when implementing native lessons/reviews, regarding having to implement a native romanji -> kana converter like the one that's done by WK in the webview currently.

cplaverty commented 5 years ago

I thought that I might look to port wanakana to swift for the romaji to kana conversion. Or at least start there.

And I’m not opposed to doing keyboard switching provided the kanji suggestions can be disabled or hidden somehow. Implementing a custom keyboard is certainly an option, but I’ve no idea how much work that would be.

Mercieral commented 5 years ago

I didn't realize WK had the converter JS logic in a public repo. That's pretty awesome.

I'm wondering if some of these settings would hide those suggestions...?

UInt2048 commented 4 years ago

I'm wondering if some of these settings would hide those suggestions...?

Just one is needed - turning off correction (auto-correct)

This can be done programmatically/dynamically, too.