Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve navigation for Restudy kanji #339

Open
fabd opened this issue May 20, 2024 · 0 comments
Open

Improve navigation for Restudy kanji #339

fabd opened this issue May 20, 2024 · 0 comments

Comments

@fabd
Copy link
Owner

fabd commented May 20, 2024

Suggestion from Pedro

When I am restudying the red kanjis, something a little odd happens. Let's say you have the kanji #500 on red, and you add it to the "learned list": instead of it moving to the next one on list, let's say, #513, it goes back to the first one of the list, the first you've left unlearned (for example, #94). Sometimes this bothers me a little, since I want to clear some kanji off the list (for example, the easier ones that I've forgotten), but I want to leave the real hard ones there so I can restudy them later. The suggestion would be making arrows for the "restudying kanji", so one could go back and forth on them, as one can do with kanji on normal RTK order - or make some kind of similar thing to it. Or you could just make them go to the next kanji on the list, instead of rolling back to the first one.

Possible implementations:

  • some kind of popup /expand with all the restudy kanji one can navigate to directly (complex)
    • main concern is not having yet another SQL pulling all restudy kanji on every Study page load
      • restudy list may be cached (session) but then it needs to be synced whenever any are cleared from the list or added
  • go to the next kanji on the list, instead of rolling back to the first one. (easy)
@fabd fabd pinned this issue May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant