Skip to content
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

[keyboard kcm]: simplify / redesign the part where to choose layout (->VDG) #76

Open
star-buck opened this issue Feb 14, 2015 · 4 comments
Assignees

Comments

@star-buck
Copy link
Contributor

suggestion:

  • move choose layout TAB to the left, so its default visible
  • TICK the checkbox so that choosing other layouts is enabled default
@star-buck star-buck removed the POLISH label Dec 14, 2015
@star-buck star-buck changed the title [keyboard kcm layout]: simplify / redesign the part where to choose layout (->VDG) [keyboard kcm]: simplify / redesign the part where to choose layout (->VDG) Jan 11, 2016
@colomar
Copy link

colomar commented Mar 14, 2016

Definitely +1 for moving the layout tab to first position, since it is very likely to be more commonly used than the Hardware tab.
About the "Configure Layouts" checkbox: Is there any good reason why this checkbox even exists? If one does not add or remove any layouts, does even just checking the box alone change anything?
Unless the checkbox has an otherwise important function (and if it does, we should inform users about it), it should simply be removed and changing layouts should always be possible.

@colomar
Copy link

colomar commented Mar 14, 2016

Feedback from @mgraesslin is that the raison d'être for the checkbox might be that keymaps are only compiled if the checkbox is checked, so that it does not use resources for nothing if the user does not want to change keyboard layouts. If that is the case and cannot be changed, it should not be checked by default because it would mean a waste of resources for the vast majority of users that do not switch layouts.
From a user perspective, however, it would definitely be better if the system only compiled a keymap if multiple layouts were activated, making the checkbox obsolete.

The problem is that this is very old code so somebody would need to investigate what the checkbox actually does before we could make any decision about it.

@star-buck
Copy link
Contributor Author

then the task is: redesign keyboard KCM, not only that part.

@colomar
Copy link

colomar commented Mar 14, 2016

All the better :) Does that mean that we'll get developer time for implementing the redesign, too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants