desktop-packages team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

Pat, we've been working with design (Patricia) to get actual design
documents for the tablet greeter.  Up until now, their guidelines have
been "just copy what the desktop does" because they didn't have cycles
for tablet stuff.  Now, obviously, tablet and convergence matters more
and they are working on visual specs as we speak.

But they haven't finished yet.  And I'm loathe to make a redesign in
advance of that.

But the issue with real names makes immediate sense.  We'll need to (1)
update the script that creates the phablet user to set Ubuntu, (2) fix
liblighdmqt to return the actual real name, and (3) probably add a hack
in unity8 to display "Ubuntu" for a system with a single "phablet" user
for the upgrade case.

I'll start on it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1536714

Title:
  Fix the user login experience on the greeter

Status in The Avila project:
  New
Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu RTM:
  New

Bug description:
  The current UX for tablets or when converged with a mouse attached is
  a bit of a placeholder showing the default phablet user.

  We need to support two modes of the greeter that scales according to
  the available input devices. The first one is one that works across
  mobile and tablet devices in non-mouse connected / touch-centric
  state. Unlocking with no mouse connected would be exactly as it is
  today on the phone, which displays the Infographic until you touch the
  screen, and then you get a message that says "swipe to unlock" If you
  don't have a pin code set, the screen unlocks. if you have a pincode
  set, the touch pincode-entry pad appears.

  If a mouse is connected, however, you get the more "desktop-friendly"
  greeter with the infographic, user-name and password entry field (just
  like what we have today) on tablet.  If the user taps or clicks into
  the password edit box, the OSK is popped up (unless an external
  keyboard is also attached). If no password or pincode has been set,
  then instead of the password entry field, you would instead have a
  "login" button that clears the greeter.

  On a tablet with mouse connected and no pincode set, the user could
  either swipe away the greeter or tap on the login button. If the user
  has a password/pincode set and attempts to swipe away the greeter, we
  should put up a hint message asking the user to enter their
  password/pincode to continue.

  This incremental enhancement to recognize the mouse is more consistent
  with convergence because tablets are mobile devices, and if no mouse
  is attached, we should follow a touch-centric approach. In a mouse-
  connected state, we can assume the user will be favoring that device.

  ===============

  Immediate problem: "phablet" name on the greeter login list. A bigger
  refactoring of the greeter for bigger screens will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1536714/+subscriptions