Right now, users must manually put in both their keyboard layout and their locale.
However, most locales have a keyboard layout they are most likely to use. We can easily use this fact to implement smarter default values for drop down menus. When a user selects their locale, we can automatically infer what their keyboard layout is most likely to be and set the drop downs in the locale window to default to that. This can also easily be done in reverse.
This can be done in one of two ways. Either:
A) Intelligently try to figure out what sane defaults would look like based on names and labels alone. This would have a lot of false positives and negatives, but may take up less space on disk.
B) define a simple key-value pair system, in JSON. This makes processing very fast (O(1)), but takes up a lot of memory and disk space.
Right now, users must manually put in both their keyboard layout and their locale.
However, most locales have a keyboard layout they are most likely to use. We can easily use this fact to implement smarter default values for drop down menus. When a user selects their locale, we can automatically infer what their keyboard layout is most likely to be and set the drop downs in the locale window to default to that. This can also easily be done in reverse.
This can be done in one of two ways. Either:
A) Intelligently try to figure out what sane defaults would look like based on names and labels alone. This would have a lot of false positives and negatives, but may take up less space on disk.
B) define a simple key-value pair system, in JSON. This makes processing very fast (O(1)), but takes up a lot of memory and disk space.