On Fri, Mar 7, 2014 at 11:39 AM, Matthew Paul Thomas <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sebastien Bacher wrote on 06/03/14 18:08: >> >> Le 06/03/2014 19:02, Marc Deslauriers a écrit : >>> >>> Wouldn't a better design be to have the lock screen in the >>> user's session? That way each user can have their own lock >>> screen, and it can access the user's data without any security >>> issue and difficulty in transferring data between different >>> security contexts... >> >> That' what we have been doing so far (on desktop), it has those >> advantages but also issues: >> >> - you get 2 codebases to maintain >> >> - you can't do user switching on the lock screen, so you need to >> to support bouncing users between those >> >> - design suggested the user experience is more confusing (mostly >> because you have similar screens with small difference and it's >> not obvious why that) >> >> ... > > I think that's because this was considered mainly as a visual design > problem: "these two screens look roughly the same, let's make them > exactly the same". > > But they behave very differently: music should keep playing at the > lock screen but not the greeter, the camera and mic should keep > recording at the lock screen but not the greeter, Touch apps may allow > limited access at the lock screen but not the greeter, your preferred > keyboard layout should persist at the lock screen but not the greeter, > screen magnification should persist at the lock screen but not the > greeter, and so on. > > Things that behave different should look different, which leads to the > conclusion that the lock screen shouldn't look like the greeter after all. >
That's interesting. With the lock screen as part of the session, we would not need to surface information up to the greeter. @Matthew: Is anyone assigned to the lockscreen work for the phone/tablet right now? Thomas > (This reminds me of the logic "snap decision dialogs look roughly like > notification bubbles, let's implement them in the notification > system", which has led to similar poor containment, e.g. Unity8 having > to contain knowledge about the format of SIM PINs.) > > - -- > mpt > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.14 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlMZodsACgkQ6PUxNfU6eco2MwCgqXka223UGmasgrFZYLqYnwtR > 2IMAoKzEHt30qCNneCvQigng2kfCWgjD > =BCKY > -----END PGP SIGNATURE----- > > -- > Mailing list: https://launchpad.net/~ubuntu-phone > Post to : [email protected] > Unsubscribe : https://launchpad.net/~ubuntu-phone > More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
