3 ms·
> Removes the “Translate Selection” button from the right-click menu. I don't want the Translate button to NEVER be there. I want it to be there if and only if
by CobrastanJorji 8mo ago
> Removes the “Translate Selection” button from the right-click menu.
I don't want the Translate button to NEVER be there. I want it to be there if and only if the selection is not in English.
- kps 8mo agoHow would it know?
- Zopieux 8mo agoHave you heard of machine learning?
- unselect5917 8mo agoIf you put machine learning into the loading of a right click menu, I want you to step on a Lego barefoot immediately afterward. Right click menus should be instant. No fade in. No animation. No spinner. And certainly not any machine learning calls.
- eviks 8mo agoHave you heard of async? You can get instant menu with a delayed menu item
- VVertigo 8mo agoThat is a recipe for pain too: menus shouldn't be morphing as the user is trying to choose an option.
- eviks 8mo agoSure, but this also has an easy solution - don't morph, have an inactive menu in place (with an indicator of wort work in progress) that activates when the work is done
- unselect5917 8mo agoThank you. There are sane, good ways to build UIs, and after 30 years of programming, my main complaint hasn't changed: "Stop doing what you're doing, and do what I want." Be like TRON, fight for the user. Not the developer. Not the developer's politics or opinions, and certainly not for the computer itself. The user's wants are the #1 priority in a human-computer interaction.
- kps 8mo agoSure. If I select the word “Gift”, how much work does it need to decide whether it's English? How much more context does it need, and where does it get it? What if it guesses wrong and doesn't show the translation button?