Allow modifying system keys row via kbdgen descriptor

[waelsaad]

Hi :), I understand this a bit of a change but there is so much code you can end up getting rid of by changing the system keys to be driven from the yaml / json file like the rest of the keys, I don't understand why that decision was initially made to have manual implementation for the system keys.

It would give so much control over this last row and in many cases you can reduce the number of rows to be similar to the native english keyboard.

Also then we could easily apply the alternative overlay keys to any of the keys placed in the last row.

I hope it can be seroiusly considered.

[waelsaad]

Thank you.

[waelsaad]

FYI, also another reason for this is there are like 6 or 7 characters in this language that are not in uppercase/lower case they are just a single case let's say lower for the sake of argument and if I'd include them in a traditional row, it doesn't seem right when clicking the shift button. They are charecters not symbols that are required to be included next to the rest of the alphabets not in the symbols area.

The point is if these were on the last row, they should not be impacted by the shift button.

[snomos]

6-7 letters? That is quite a lot, it won't fit on the system row if also shift, space etc are to be kept there. I would suggest to put them on an extra top row (fourth, fifth, depending on where you start), and duplicate them on the shifted layer, to give the impression that nothing happens when shifted.

[waelsaad]

Yes, at the moment I am using an additional row for 2 or 3 characters and placing the rest of additional characters in the overlay laternative of these keys as just a means to access them so the UI looks neat.

I also did exactly as you suggested ofcourse to place the same characters in lower and uppercase but still there is a slight UI change and doesn't look right because when you press shift on these characters they will look slightly smaller, I think I understand why but my point is as mentioned above goes back to the original purpose of this issue which is if we had at least couple of these characters placed in the system row and they were driven dynamically they wouldn't be impacted by the shift key.

By the way I appreciate all the responses and the effort. I hope this library will keep on being enhanced and also one more point is to minimize / group all the constants that are sort of eveywhere in the code and make them a bit more modular if possible.