After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 668351 - Remove the Screen/Brightness and Lock panel
Remove the Screen/Brightness and Lock panel
Status: RESOLVED WONTFIX
Product: gnome-control-center
Classification: Core
Component: [obsolete] Screen
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-01-20 14:49 UTC by Christian Giordano
Modified: 2012-06-12 13:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Giordano 2012-01-20 14:49:29 UTC
The Screen and Lock panel currently has the following issues:

- ux-jargon: the difference between Personal and Hardware is not clear to the user. Especially if the main difference is that Personal is used for settings you change often. This is more a shell issue but until redesigned influences the panels organization.

- ux-discovery: the separation between Personal and Hardware visually is not particularly evident, or at least the representation doesn't convey the difference. The name "screen" conflicts with "display", especially in some languages which are translated in the same word.

- ux-minimalism: the Lock is not tightly related to the screen, it is more related to privacy/security. Looks at the moment a settings dump. The amount of settings panels should be kept at the minimum to make it easier for the user to browse the top level.

- ux-consistency: Lock is not strictly related to Screen, even less to Brightness.

(ref. https://spreadsheets.google.com/pub?key=tJxF8zTuLdEj9pUcxnLAemA&output=html)

Renaming it to "Brightness and Lock" would simply improve discoverability.

The solution I am proposing is to blur a little bit further the difference between Personal and the others while the shell is not redesigned.

- Brightness, which can easily be modified, in general, by labelled special keys, could join the Display setting which will provide the possibility to set a different brightness to each display.
- Dim, because strictly related to power saving, joins Power.
- Lock, because strictly related to authentication, joins user accounts login options. In the future, if a privacy panel will be available with general settings, a move there could be evaluated.

I think this option would improve ux-consistency and optimizing the 1st level navigation not only ux-minimalism but also ux-discovery.


Any opinion?
Comment 1 Allan Day 2012-01-20 17:24:45 UTC
The screen panel has been renamed to brightness and lock (bug 653015). Seems to fix the issues described here.

(In reply to comment #0)
...
> - Brightness, which can easily be modified, in general, by labelled special
> keys, could join the Display setting which will provide the possibility to set
> a different brightness to each display.
> - Dim, because strictly related to power saving, joins Power.
> - Lock, because strictly related to authentication, joins user accounts login
> options. In the future, if a privacy panel will be available with general
> settings, a move there could be evaluated.

Much of this is discussed in the comments of bug 653015.
Comment 2 Robert Ancell 2012-02-01 05:25:23 UTC
Allan, do you see the renaming as solving the all the issues listed by Christian?

In particular the major remaining issues seem to be:
- The icons for the two entries still look too similar (improved now the labels are distinct).
- Brightness and lock don't have a logical connection

From bug 653015 There seemed to be a consensus that lock should be moved into a security panel, when this occurs where do you see the brightness/dim/power off settings going?
Comment 3 Allan Day 2012-02-09 09:28:25 UTC
(In reply to comment #2)
> Allan, do you see the renaming as solving the all the issues listed by
> Christian?

Hey Robert, apologies for the slow response.

> In particular the major remaining issues seem to be:
> - The icons for the two entries still look too similar (improved now the labels
> are distinct).
> - Brightness and lock don't have a logical connection

These are somewhat related, since the connection between brightness and lock that we've pushed in the past was that they both involve the screen. It is 'screen lock' and 'screen brightness'.

I'm not convinced that those things go together either. ;)

> From bug 653015 There seemed to be a consensus that lock should be moved into a
> security panel, when this occurs where do you see the brightness/dim/power off
> settings going?

Having lock in a security panel might make sense, but it's hard to comment on that without seeing more details on what the security panel would contain. 

I don't see a good alternative location for brightness/dim/power off right now (I don't think displays is a good place for it).

My view is that we need to reappraise the system settings from the top down...
Comment 4 Christian Giordano 2012-05-23 13:58:59 UTC
Hi Allan, if we are gonna have a Security panel, which could nicely host the Lock. I think we should reconsider joining Screen and Displays.
Comment 5 Allan Day 2012-05-29 10:06:54 UTC
Upon reflection, I'm growing more in favour of this panel.

 * Blank screen and screen lock are functionally related - you can't lock the screen after it has been blanked.
 * The screen element of the lock will become its most prominent aspect once the new design [1] is implemented, meaning that people will associate the lock with the screen.
 * The lock isn't actually a security feature (and so shouldn't be transplanted to a new security panel), since you don't always need a password to unlock.

[1] https://live.gnome.org/GnomeOS/Design/Whiteboards/ScreenLock
Comment 6 Christian Giordano 2012-05-29 10:17:42 UTC
I agree lock alone is not necessary security, if it doesn't require a password. But adding password to the unlock is a security feature.
Comment 7 Bastien Nocera 2012-06-12 13:14:36 UTC
We're adding more things to the Screen panel instead. See bug 658660.