We have faced many issues where user is complaining about the wrong keyboard is getting selected which is resulting in some keys not working properly. So with this I am just trying to address that issue. This will also make sure that user is changing keyboard layout in his knowledge.
Additionally this also results in less loading of data in memory. I am not sure about how significant that is. We can give user option in UI to enable editing it easily. > On 15-Dec-2015, at 2:35 PM, Stephan Seitz > <s.se...@secretresearchfacility.com> wrote: > > Thank's for pointing to that PR. > > Do you think it's useful to cut the keyboard selector? > > As long as there's no wayu changing the keyboard setting after an > instance has been provisioned, the average user would need to fiddle > with API calls. > > Additionally, the keyboard doesn't necessary have to be consistent > inside the instance, so a drop down is really handy. > > > Am Dienstag, den 15.12.2015, 04:53 +0000 schrieb Anshul Gangwar: >> There is already a PR requested some 4 months back addressing some of these >> issues. With that patch one has to add only key mappings to support new >> languages. >> >> https://github.com/apache/cloudstack/pull/669 > >
