rugk / unicodify

✍️ A browser add-on (Firefox, Chrome, Thunderbird) that allows you to autocorrect common text sequences and convert text characters to a look like a special font.
https://addons.mozilla.org/firefox/addon/unicodify-text-transformer/?utm_source=github.com&utm_medium=git&utm_content=repo-about-description&utm_campaign=github
Other
11 stars 2 forks source link

Option for nested context menu #44

Closed rugk closed 11 months ago

rugk commented 3 years ago

Background

As explained in https://github.com/rugk/unicodify/issues/25#issuecomment-843961953:

We could always create a nested menu, but that would of course be harder for the user to use and we would then not be able to show all the options in a single screenshot.

https://github.com/rugk/unicodify/issues/25#issuecomment-844418604:

I’m getting lost in that many options, actually, already…

Proposed solution

I should be able to enable a nested context menu, where the different transformations are somewhat of being grouped together…

Alternatives

Maybe some thing of ”highlight top most used 5 ones” at the top or sort the entries by what was last used etc. If you’d want that, please open a new issue, however.

Additional context

N/A

tdulcet commented 3 years ago

OK, I do not think your “Proposed solution” is what you meant, so maybe we could structure the nested context menu something like this:

I am not sure if you wanted all the items in nested menus or if you wanted more than one level of nesting. I am also not sure how this would work with the live preview option. Anyway, this will likely require a significant refactoring of the text transformation feature, similar to #17.

rugk commented 3 years ago

OK, I do not think your “Proposed solution” is what you meant

Oh sorry, I had a syntax error here (cough cough caused by this add-on #14), which commented a bigger part. Corrected now.

am also not sure how this would work with the live preview option.

Hmm, just do not live-preview the categories should be enough, should not it? :thinking: Though it may look strange if some things are previewed and some are not. :thinking: Anyway… taht’s an implementation detail/UX thing that can be found out when implementing it and looking/comparing how it looks. I could also imagine it does sth. like not changing the top-level entries like “Superscript” to a live preview only, but still always forces to add the description, so one knows what is done there.

But thanks for making a list of all options! It’s a good proposal that could be implemented later on…