=> Re: "A UX suggestion" | In: s/farkle
I had the same thought (using QWEASD for the selection). I wonder if the keyboard autocorrect/spellchecker would interfere with it, though.
2024-07-23 · 6 months ago
=> 👺 daruma · 2024-07-23 at 15:48:
In html, you can have a field being 'number' field and then your number keyboard shows up instead of the normal keyboard when you touch it in mobile. I am not sure gemini is equiped with a 'type' of input?
=> 🕹️ skyjake [...] · 2024-07-23 at 16:02:
@daruma Gemini has no mechanism for specifying what kind of input is expected, except for the human-readable prompt.
However, a client could provide a configuration setting for choosing a specialized keyboard for a given URL, for manually switching virtual keyboards.
=> 🍀 gritty [mod] · 2024-07-23 at 16:41:
this may be doable. a simple translation upon input could be an "easy" fix
=> 🚀 stack [OP] · 2024-07-23 at 16:45:
qweasd makes more sense spacially, but 'a' is already in use...
=> 🍀 gritty [mod] · 2024-07-23 at 16:50:
That's fair, but qwerty is already mapped to the right numbers on (most?) android phones. I'll think on it. the earliest I can work on anything would be Friday.
As I am silly enough to use a Dvorak keyboard on my phone, this won’t be of much use to me…
=> 🌒 s/farkle
A UX suggestion — I usually play on my Android phone, and the keyboard pops up with qwerty, not numbers, requiring an extra keystroke every time. I'd love to be able to use 'qwerty' mapped to 123456 positions. it's a little or unorthodox, but would improve the power user experience.
=> 💬 stack · 8 comments · 2024-07-23 · 6 months ago This content has been proxied by September (ba2dc).Proxy Information
text/gemini; charset=utf-8