[WIP] Keyboard creator

[willwade]

Proper PR from asterics own repo

Allows for adding a keyboard - by language code in frequency or alphabetical order #614

How to use.

Manage Grids ->More -> Generate Keyboard -> Displays Modal -> choose options. "Generate"

Keyboard now at bottom of grid list

[github-actions]

🎉 Beta deployment successful! 🎉

You can view the changes in the live preview environment here: https://gridbeta-github.asterics-foundation.org/willwade/keyboard-creator/pr

[willwade]

To-do

• When the language has a large number of characters (eg Chinese) - at least more than the current layout allows we hit a problem. I'm really not sure what to do at here.. Magically increase the rowxcol size?
• Not all languages support digits or frequency. We need to check that
• There needs to be some sanity checking about the UI placement. I feel it should somewhere else but not sure..

[github-actions]

🎉 Beta deployment successful! 🎉

You can view the changes in the live preview environment here: https://gridbeta-github.asterics-foundation.org/willwade/keyboard-creator/pr

[github-actions]

🎉 Beta deployment successful! 🎉

You can view the changes in the live preview environment here: https://gridbeta-github.asterics-foundation.org/willwade/keyboard-creator/pr

[arasaac-dga]

From our point of view, adding this option to create a keyboard could be confusing if there isn't an option to create a QWERTY keyboard within the same window (adapted to each language. For example, Spanish uses the ñ, but Catalan uses the ç), given that it's usually the most requested and used by our users. They'll go to create a keyboard and, upon creating it, they'll see that it has nothing to do with a QWERTY.

That is, there should also be an option to create standard QWERTY keyboards, which should already be created with a specific row and column configuration (disabling the row and column option) (as we have examples for various models) so that the keyboard can be created in seconds by simply pressing it.

There could even be QWERTY models with numbers above the letters or numbers on the right. We could start with templates with some keyboard models like the ones we've been using. Even if a thumbnail of the keyboard type is shown, it could be extended to other keyboards such as ScanKeyboard, Huffman, etc.

Additionally, options such as:

1. Create in uppercase (although there is an option to force uppercase in settings, it may be interesting to create it already in uppercase)
2. Add a space bar (for the two types of keyboards you propose, the space bar is not created, which is confusing). Additionally, our users are always wondering how to create the space bar, so adding it would make it easier for them.
3. In the case of Spanish, you may or may not want to add accented vowels. Normally, vowels with accents are not added on standard keyboards.
4. Add some punctuation marks (period, comma, question mark, exclamation mark, etc.). Perhaps just the basic ones.

As it stands now, it's an option our users won't use and can cause confusion by creating a keyboard that isn't what they're "thinking" or need.

In other words, it can be a good time-saving feature for users who start with blank communicators or models that don't have language-specific keyboards, but to be useful, it should offer all the options.

[ms-mialingvo]

@arasaac-dga Just as a reminder, we have discussed that feedback about a feature should happen in the issue (in this case #614 ) not in the PR :)

the issue is for discussing the implementation from the user's side (UI, testing environment) while the PR is for discussing the code changes and technical background

[github-actions]

🎉 Beta deployment successful! 🎉

You can view the changes in the live preview environment here: https://gridbeta-github.asterics-foundation.org/willwade/keyboard-creator/pr

[arasaac-dga]

Sorry, it's true.

[github-actions]

🎉 Beta deployment successful! 🎉

You can view the changes in the live preview environment here: https://gridbeta-github.asterics-foundation.org/willwade/keyboard-creator/pr