Hi,
On Tue, 16 Sep 2014 10:18:25 +0000 sajolida@??? wrote:
> Alan wrote:
> > We could have only one list with languages and consider that
> > changing the specific keyboard layout and locale is somehow an
> > advanced option. I'm not convinced it's better but that could be an
> > option.
>
> If I understand your proposal correctly, the idea here would be to
> have only the language on the first screen and then automatically
> select a keyboard depending on this. For example, if I select German
> as language it will automatically configure German keyboard.
>
Yes.
> Personally, I would start by removing the locale list and leave the
> keyboard like this. The use of this one is definitely quite more
> obscure that "language" and "keyboard".
>
"Locale" could be renamed "region" or "country" or something like that.
It as also useful, e.g. when we'll have our custom clock applet it will
be used to fetch the right timezone for a french speaking person in
Canada. But anyway I think we already dropped what's useless so now it
we want to simplify more we need to drop useful things. It's a matter
of: is it useful enough for the complexity it adds to the UI?
> And also, since the keyboard is used to typed in the persistence
> passphrase, I think it should be possible to change it from the first
> screen (maybe using another popup widget or something). I don't know
> how to type my passphrase on other keyboard layouts!
>
> But maybe I'm insisting on having the keyboard on the first screen
> only because I use this myself every day.
>
> Can we try to brainstorm a bit and maybe find important groups of
> users for which selecting the language won't give them a valuable
> keyboard layout by default? Maybe French speaker in Canada? Do they
> use the French keyboard?
>
There's a swiss keyboard different from the French and German one, but
that would be possible to guess from language + region (locale).
Selecting the keyboard alone is mostly useful for users that are
traveling as Lunar highlighted.
> >> http://git.tails.boum.org/tails/plain/wiki/src/blueprint/greeter_revamp_UI/greeter-1st-screen-persistence-1.png?h=web/layered-persistence-config
> >>
> >> http://git.tails.boum.org/tails/plain/wiki/src/blueprint/greeter_revamp_UI/greeter-1st-screen-persistence-2.png?h=web/layered-persistence-config
> >
> > With the original proposal I imagined that typing something in the
> > password box would automatically move the slider to enable
> > persistence.
>
> I like this idea as well. It would fix the problem that I raised in my
> previous answer to tchou about having a visual feedback on whether
> persistence is enabled or not.
>
So do we agree on that?
> > These new mockups implies that to enable persistence one
> > has first to click on the slider (or focus it with the keyboard)
> > then type the password. I'm not totally convinced *but* if there is
> > an agreement it's easier for new users I find it an acceptable
> > compromise
>
> Nah, I think that we should drop this idea and try to simplify other
> things on that screen like the localization options.
>
OK
Cheers
.%20I%20don't%20know%0A>%20>%20how%20to%20type%20my%20passphrase%20on%20other%20keyboard%20layouts!%0A>%20>%20%0A>%20>%20But%20maybe%20I'm%20insisting%20on%20having%20the%20keyboard%20on%20the%20first%20screen%0A>%20>%20only%20because%20I%20use%20this%20myself%20every%20day.%0A>%20>%20%0A>%20>%20Can%20we%20try%20to%20brainstorm%20a%20bit%20and%20maybe%20find%20important%20groups%20of%0A>%20>%20users%20for%20which%20selecting%20the%20language%20won't%20give%20them%20a%20valuable%0A>%20>%20keyboard%20layout%20by%20default?%20Maybe%20French%20speaker%20in%20Canada?%20Do%20they%0A>%20>%20use%20the%20French%20keyboard?%0A>%20>%20%0A>%20There's%20a%20swiss%20keyboard%20different%20from%20the%20French%20and%20German%20one,%20but%0A>%20that%20would%20be%20possible%20to%20guess%20from%20language%20+%20region%20(locale).%0A>%20Selecting%20the%20keyboard%20alone%20is%20mostly%20useful%20for%20users%20that%20are%0A>%20traveling%20as%20Lunar%20highlighted.%0A>%20%0A>%20>%20>>%20http://git.tails.boum.org/tails/plain/wiki/src/blueprint/greeter_revamp_UI/greeter-1st-screen-persistence-1.png?h=web/layered-persistence-config%0A>%20>%20>>%0A>%20>%20>>%20http://git.tails.boum.org/tails/plain/wiki/src/blueprint/greeter_revamp_UI/greeter-1st-screen-persistence-2.png?h=web/layered-persistence-config%0A>%20>%20>%20%20%0A>%20>%20>%20With%20the%20original%20proposal%20I%20imagined%20that%20typing%20something%20in%20the%0A>%20>%20>%20password%20box%20would%20automatically%20move%20the%20slider%20to%20enable%0A>%20>%20>%20persistence.%0A>%20>%20%0A>%20>%20I%20like%20this%20idea%20as%20well.%20It%20would%20fix%20the%20problem%20that%20I%20raised%20in%20my%0A>%20>%20previous%20answer%20to%20tchou%20about%20having%20a%20visual%20feedback%20on%20whether%0A>%20>%20persistence%20is%20enabled%20or%20not.%0A>%20>%20%0A>%20So%20do%20we%20agree%20on%20that?%0A>%20%0A>%20>%20>%20These%20new%20mockups%20implies%20that%20to%20enable%20persistence%20one%0A>%20>%20>%20has%20first%20to%20click%20on%20the%20slider%20(or%20focus%20it%20with%20the%20keyboard)%0A>%20>%20>%20then%20type%20the%20password.%20I'm%20not%20totally%20convinced%20*but*%20if%20there%20is%0A>%20>%20>%20an%20agreement%20it's%20easier%20for%20new%20users%20I%20find%20it%20an%20acceptable%0A>%20>%20>%20compromise%0A>%20>%20%0A>%20>%20Nah,%20I%20think%20that%20we%20should%20drop%20this%20idea%20and%20try%20to%20simplify%20other%0A>%20>%20things%20on%20that%20screen%20like%20the%20localization%20options.%0A>%20>%20%0A>%20OK%0A>%20%0A>%20Cheers%0A>%20%0A>%20 "Nachricht beantworten")
