💾 Archived View for bbs.geminispace.org › u › skyjake › 406 captured on 2023-11-14 at 10:54:07. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Re: "Longer input text fields"
@satch Now that you mention it, I wouldn't mind an expanded input prompt with a larger size myself. The default dialog font that is used in Lagrange can be a bit tiny for actually composing a longer piece of text.
Maybe a nice solution would be for the Zoom In/Out keys to work in the input prompt to resize the dialog and the font.
@lufte Delegating to another app that does the job better is usually a great choice, however with Gemini in particular there is that maximum length limitation that is difficult to enforce in the external text editor...
May 17 · 6 months ago
🐵 cquenelle · 2023-05-18 at 05:04:
My thoughts are that if the client can auto size in a fluid way, then it’s not good to try to make the server be in charge of it. I didn’t remember or notice that Lagrange handles this smoothly until @satch mentioned it.
♊️ shtirlic · May 21 at 04:32:
It would be great to have shortcut/button to expand the input area to half the page/full page.
🐵 cquenelle · May 25 at 05:50:
@shtirlic This is more of a client thing, for me that's Lagrange. If there was a "big-input" button, the type-in panel could get bigger and the insert-line-break key could change from "shift enter" to "enter".
@cquenelle One option for that would be to repurpose the Titan upload UI for a "big input" mode. It might motivate me to improve the in-app text editing capabilities. 🙂
@cquenelle @skyjake I really like this idea of having the line break key change from enter to shift+enter when the user switches to big input mode. It would be very convenient.
Longer input text fields — I'm not proposing a spec update or anything like that, yet (as that seems unlikely). This is just more of a question. Is there anything that can be to tell a browser that an input field is long and should be displayed like a textarea preferably? For a search box or for simple question/answer type inputs the current input is appropriate. But for longer fields, such a when posting on Bubble, it should be displayed more like the tweet box on Twitter. The other solution...