-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full-width layout #155
Comments
You can already do a full width layout currently, by simply increasing the key size in the settings. If your key grid size overflows your screen size, the columns on the right should be minimized. Your proposals above all require non-square, and relative key sizing. Outside of the complication of having to hard-code these specific relative sizes, I doubt doing so would actually increase tapping speed in any way. Having keyboards fill screen widths doesn't seem like a parameter that would be beneficial in any way to tapping speed. |
I think this should be an option since the current keyboard does take up a lot of the screen. For example, sometimes I can't see the input field on Duolingo because the green Check button has been pushed up and now covers it. |
I think that if we could have it had a more rectangular shape it would be more comfortable. I also think that we can find a layout which has the spacebar at the center. |
You can create these layouts, the only requirement is that its a grid, and that the key sizes are square. |
Thank you. Then I will give it a try. Can we keep this thread open for when I'll come back with a draft? |
Sure. |
I was going to comment the same thing! Messagease is only comfortable for me at full width, as the width of the kb matches my muscle memory for the width of the screen. Currently the height of keys at a full width size takes up more the half my screen. |
If you'd like to create "wider" layouts (currently we are a 4x4 grid, but 5x3 is entirely possible), feel free. But I don't want to add the complication of having non-square key sizes. |
I start by say "Thank you!": finally someone got back the idea of not using a QWERTY layout on mobile.
** Describe the feature request below **
![senza titolo-f000256](https://user-images.githubusercontent.com/30182251/232306984-d592ebd4-ddcd-4d3f-8451-8e319bc7bdb3.png)
Right now the keyboard only takes a portion of the horizontal width of the screen:
I'm thinking about how you could better manage the space to make typing easier keeping this style of tap+slide writing. I think we could add an option to the "Position" section to fill all the horizontal space with the keyboard.
I have two proposals:
In this way it could be needed to relocate the right-to-left swipes of the leftmost keys, but I see lots of other places where they could be placed in any language layout. But the buttons are bigger! So the action could be performed anyway starting from the top or the center of such keys.
I prefer this second proposal and I think we could mix this with another change: removing the "Settings" button from the keyboard, because ideally it should never be needed from the moment the user chooses a final layout:
![proposal2 1](https://user-images.githubusercontent.com/30182251/232305870-c928768d-1ed0-4489-8c0e-a38455467359.png)
Or we could simply use that position for another function.
The last one is the layout I would prefer, but it could clash with the sliding pointer function of the spacebar (#59), unless we think it could work anyway while being used vertically.
The text was updated successfully, but these errors were encountered: