Menu entries are not grouped according to spec

Bug #429580 reported by David Siegel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Session Menu
Fix Released
Medium
Ted Gould

Bug Description

The current menu item grouping does not reflect the design decisions recorded in the spec (https://wiki.ubuntu.com/DesktopTeam/Specs/KarmicFusa#UI%20Changes).

Current layout:

---------------------------
| User's Full Name
| Set Status >
| About Me…
|----------------------
| Log Out…
| Lock Screen
| Switch User >
| Guest Session
|----------------------
| Suspend
| Hibernate…
| Restart…
| Shut Down…
------------------------

In the spec, we use horizontal dividers to separate three groups, roughly characterized as (1) status info/actions, (2) session actions, and (3) power state actions:

---------------------------
| User's Full Name
| Set Status >
| About Me…
|----------------------
| Log Out…
| Lock Screen
| Switch User >
| Guest Session
|----------------------
| Suspend
| Hibernate…
| Restart…
| Shut Down…
------------------------

To reflect the specification, *Log Out and Lock Screen should be grouped in the second group* (session actions) as shown.

Revision history for this message
David Siegel (djsiegel-deactivatedaccount) wrote :

Here is an updated bug description (a Launchpad bug is preventing me from editing the description):

The current menu item grouping does not reflect the design decisions recorded in the spec (https://wiki.ubuntu.com/DesktopTeam/Specs/KarmicFusa#UI%20Changes).

Current layout:

---------------------------
| User's Full Name
| STATUS >
| Lock Screen
|----------------------
| Guest Session
| New Session...
|----------------------
| Log Out
| Suspend
| Hibernate…
| Restart…
| Shut Down…
------------------------

In the spec, we use horizontal dividers to separate three groups, roughly characterized as (1) status info/actions, (2) session actions, and (3) power state actions:

---------------------------
| User's Full Name
| Set Status >
| About Me…
|----------------------
| Log Out…
| Lock Screen
| Switch User >
| Guest Session
|----------------------
| Suspend
| Hibernate…
| Restart…
| Shut Down…
------------------------

To reflect the specification,:
  1. Log Out and Lock Screen should be grouped in the second group (session actions) as shown.
  2. Remove "New Session..."

Changed in indicator-session:
assignee: nobody → Ted Gould (ted)
Revision history for this message
Ted Gould (ted) wrote :

Uhm, that's not what is currently in the code. The code currently is:

---------------------------
| User's Full Name
| Status >
| Lock Screen
|----------------------
| Guest Session
| New Session...
|----------------------
| Log Out...
| Suspend
| Hibernate
| Restart…
| Shut Down…
------------------------

So you're suggesting we add an "About Me..." in the first section move the lock screen into the second section and move "Log Out..." up a section?

Considering we're already beyond UI Freeze and Feature Freeze we'll need a reason why moving those items and adding the about me feature in would be important.

Revision history for this message
Ted Gould (ted) wrote :

Additionally, I would say the current ordering is:

Current Session
Switch Session
End Session

Revision history for this message
David Siegel (djsiegel-deactivatedaccount) wrote :

I think both groupings have merit, but the first is a bit easier to grok. I am happy leaving Log Out... where it is considering we are past UI freeze. We can omit "About Me" for the time being as well if it's too late (it has been in KarmicFUSA spec for weeks). But I really would like Lock Screen moved to the top of the middle section, and "New Session..." removed -- users do not think in terms of spawning sessions, they think in terms of people logging in.

Only one user:

----------
Lock Screen
Guest Session
----------

1 < #users < 7:

----------
Lock Screen
Guest Session
Switch User >
----------

7 <= #users:

----------
Lock Screen
Guest Session
Switch User...
----------

I think either section is good for "Log Out...", so we can leave it as-is at this point and improve it another time, if that makes things easier.

Ted Gould (ted)
Changed in indicator-session:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → ubuntu-9.10-beta-freeze
Ted Gould (ted)
Changed in indicator-session:
milestone: ubuntu-9.10-beta-freeze → 0.1.4
Ted Gould (ted)
Changed in indicator-session:
status: Confirmed → Fix Committed
Ted Gould (ted)
Changed in indicator-session:
status: Fix Committed → Fix Released
Revision history for this message
David Siegel (djsiegel-deactivatedaccount) wrote :

Ted, I am sorry, but the combination of a Launchpad bug preventing me from correcting typos in the bug description, and further confusion surrounding the organization of the session indicator menu in Karmic makes me feel that this is not fixed.

----------------
Full User Name
Set Status >
About Me...
----------------
Lock Screen
Guest Session
[Switch User > OR Switch User...]
Log Out...
----------------
Sleep
Hibernate
Restart...
Shut Down...
----------------

Above is the latest menu structure from the KarmicFUSA wiki page. Let's use the organization of the second section in the Karmic session indicator: Lock Screen, Guest Session, Switch User with submenu OR Switch User... OR no menu entry depending on the number of users, and finally Log Out....

Revision history for this message
Ted Gould (ted) wrote : Re: [Bug 429580] Re: Menu entries are not grouped according to spec

On Fri, 2009-09-18 at 17:58 +0000, David Siegel wrote:
> Above is the latest menu structure from the KarmicFUSA wiki page. Let's
> use the organization of the second section in the Karmic session
> indicator: Lock Screen, Guest Session, Switch User with submenu OR
> Switch User... OR no menu entry depending on the number of users, and
> finally Log Out....

Well, in comment #4 you wrote:

  "I am happy leaving Log Out... where it is considering we are past UI
freeze."

And yes, the submenu for switching user I didn't consider part of this
bug as it's being tracked in another.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.