Summary: | New colors KCM needs far too many mouse clicks to save changes after changing a color | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Jonathan Marten <jjm> |
Component: | kcm_colors | Assignee: | Matthew Woehlke <mwoehlke.floss> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cfeck, jpwhiting, kollix, nate, olivier, simonandric5, thomas.pfeiffer |
Priority: | NOR | Flags: | olivier:
Usability+
|
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jonathan Marten
2016-10-08 19:29:34 UTC
Agreed. During this redesign, the "Current" (unsaved) color scheme setting got lost. The "current" was to be removed. The VDG wanted to have a scheme creator and a scheme picker, which are 2 different usercases. They are now split. I add the VDG in the thread. As Olivier said, this change was made on purpose, to have a clearer separation between selecting and editing color schemes. Yes, that makes this particular use-case less efficient. No, we won't change that fundamental system back. Ideas for how to make the scheme editing simpler without sacrificing the clear separation between selecting and editing a theme (so no, no unsaved "current" theme) are still welcome, however. Take the point about having a separation of the scheme editor, but the fundamental problem is still the number of clicks now required. Unless, of course, the intention is to discourage users from changing individual colours and instead concentrate on predefined schemes only, but that would be a restriction of what was previously possible and there may well be adverse feedback from users. The current setup could be kept but the number of clicks still reduced by the scheme editor dialoge knowing whether it is being called from System Settings or standalone (by a command line option if necessary), and in the former case having buttons "Upload", "OK" and "Cancel" instead of the current ones. "OK" would save back the settings to the current scheme (the one that was selected in systemsettings when "Edit Scheme" was clicked) without any further interaction needed. When started standalone the editor would have the buttons and operation as now. Another click could be eliminated by the editor remembering the tab that was last used and selecting the same one when started again (currently the "Options" tab is always initially selected). Also, the parent KCM could remember the selected scheme while the editor dialog was open and not clear the list selection after it is closed. If all of these were implemented then the sequence to change a single colour would be reduced to: 1. Assuming that the current colour scheme is selected in the list, click Edit Scheme. 1½. In the dialogue that appears, select the Colours tab if necessary - only the first time 2. Click the colour button for the item to change, the colour picker opens. 3. Pick a colour by whatever means is wanted, then OK. 4. Click OK to close the editor dialogue. 5. Click Apply; the desktop colour scheme changes. This reduces the number of clicks from ten down to five. @Jonathan: You have a point here. We are actually not done. The first step was to split the edition from the selection. Now the edition dialog should not look like this anymore, but more like a sdk tool where you can really choose everything on the main page, actually see the changes on the fly etc. The buttons should disappear and have a tool bar + menu bar where you can have "save", "save as", ... This is still to be done: maybe we merged it too early, but I'm sure that otherwise, the work wouldn't have been merged anytime soon. So yes: there is still work to do on this, and mockups or other ideas are welcome :) *** Bug 374139 has been marked as a duplicate of this bug. *** With the latest QML version of the KCM, a few of the steps have been cut out, which mostly leaves us with Bug 411317 and the fact that there's no "Save" button, just "Save As". Let;s use this bug report to track that specifically. Actually, my mistake: there's now an "Apply" button which does that. Even fewer clicks! I think we can call this fixed. |