Skip to content

Rearrange annotation settings#857

Merged
killergerbah merged 6 commits intomainfrom
annotation-settings-rearrange
Jan 25, 2026
Merged

Rearrange annotation settings#857
killergerbah merged 6 commits intomainfrom
annotation-settings-rearrange

Conversation

@killergerbah
Copy link
Copy Markdown
Owner

Rearranged annotation settings mostly as discussed:

  • Moved "import from file" into the "import clipboard" dialog and renamed the dialog.
  • Rearranged the import/export and Anki cache sections so that they're below the "Annotation" section. The "colorize" setting felt more important, since it enables the word DB settings .
  • Renamed them to "local word database" and "Anki word database" respectively. "Cache" felt like an implementation detail that might not be palatable to layman users.
  • Changed wording of some helper text to (hopefully) be more clear.
  • Linked some helper text to the settings sections they refer to.
Screen.Recording.2026-01-22.at.8.58.17.AM.mov

@killergerbah killergerbah requested a review from ShanaryS January 22, 2026 00:04
Copy link
Copy Markdown
Collaborator

@ShanaryS ShanaryS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, the only reason I kept the Anki button at the top is to make it clear it applies to all tracks at once but it shouldn't be pressed often anyways.

I didn't see any changes to have the lemmas from the json calculated if missing, is that for a later PR?

@killergerbah
Copy link
Copy Markdown
Owner Author

the only reason I kept the Anki button at the top is to make it clear it applies to all tracks at once but it shouldn't be pressed often anyways.

Oh.. forgot about that. I'll move the buttons back up. Should be easy enough for the user should figure out that they need to enable stuff for the buttons to work.

I didn't see any changes to have the lemmas from the json calculated if missing, is that for a later PR?

I also didn't know that we wanted to do this.. if importing JSON, then most likely the words were exported with lemmas in the first place, is this something we expect to happen often?

@ShanaryS
Copy link
Copy Markdown
Collaborator

I also didn't know that we wanted to do this.. if importing JSON, then most likely the words were exported with lemmas in the first place, is this something we expect to happen often?

I was referring to this comment: #853 (comment)

By combing the clipboard and file import we can now parse any missing lemmas since the user can chose the track to parse with.

- Moved word DB buttons back to top
- Removed track selector from import dialog because local tokens are
  trackless
- Maturity + state inputs are displayed lazily, after previewing, since
  those options are not applied to 'import from file'
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Jan 25, 2026

Deploying asbplayer with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8787f01
Status: ✅  Deploy successful!
Preview URL: https://73e213ab.asbplayer.pages.dev
Branch Preview URL: https://annotation-settings-rearrang.asbplayer.pages.dev

View logs

@killergerbah
Copy link
Copy Markdown
Owner Author

@ShanaryS I've added the lemmatization but it will be done regardless of whether the record already has lemmas or not - I opted against adding an option for now since I thought it might be confusing given that the dialog already has a Yomitan API URL input, implying that parsing will be done.

Maybe we could add a checkbox to the effect of 'lemmatize only if record has no lemmas,' but this starts getting confusing since the behavior would only be affected in the case of "import from file" and not "import from clipboard." I guess this is the tradeoff with using the same dialog for two slightly different behaviors.

@killergerbah
Copy link
Copy Markdown
Owner Author

I also updated the dialog UI slightly:
image

image

- split clipboard string before tokenize bulk
- use Partial<DictionaryTokenRecord>
- lemmatize imported file records only if lemmas are missing
@killergerbah killergerbah requested a review from ShanaryS January 25, 2026 02:11
@killergerbah killergerbah merged commit e7f7198 into main Jan 25, 2026
2 checks passed
@killergerbah killergerbah added this to the Extension v1.14.0 milestone Jan 27, 2026
RonzyOnGIT pushed a commit to RonzyOnGIT/asbplayer that referenced this pull request Feb 2, 2026
* Rearrange annotation settings

* Address feedback + additional changes to import dialog

- Moved word DB buttons back to top
- Removed track selector from import dialog because local tokens are
  trackless
- Maturity + state inputs are displayed lazily, after previewing, since
  those options are not applied to 'import from file'

* Restore track selector as 'yomitan api URL' selector in import dialog

* Only lemmatize if imported record does not already have lemmas

* Address feedback

- split clipboard string before tokenize bulk
- use Partial<DictionaryTokenRecord>
- lemmatize imported file records only if lemmas are missing

* Fix keyboard shortcut tab not scrolling when navigated to from dictionary settings
RonzyOnGIT pushed a commit to RonzyOnGIT/asbplayer that referenced this pull request Feb 21, 2026
* Rearrange annotation settings

* Address feedback + additional changes to import dialog

- Moved word DB buttons back to top
- Removed track selector from import dialog because local tokens are
  trackless
- Maturity + state inputs are displayed lazily, after previewing, since
  those options are not applied to 'import from file'

* Restore track selector as 'yomitan api URL' selector in import dialog

* Only lemmatize if imported record does not already have lemmas

* Address feedback

- split clipboard string before tokenize bulk
- use Partial<DictionaryTokenRecord>
- lemmatize imported file records only if lemmas are missing

* Fix keyboard shortcut tab not scrolling when navigated to from dictionary settings
@killergerbah killergerbah deleted the annotation-settings-rearrange branch February 23, 2026 23:39
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

Successfully merging this pull request may close these issues.

2 participants