Re: [Tails-ux] Greeter: 1st screen and quick setup

spencerone@???:
> Sajolida,
>
>> I'm ready to discuss a better "Guided" button but I'm not sure that we
>> want to diverge from the way the GNOME widget look like that early :) At
>> least for the selection list and hyperlink.
>
> Yes, I understand :) The thing about guides is that they work but only
> until they don't. I still think that we should follow an agreed upon
> set of guidelines, e.g., GNOME HIG, until the experience calls for a
> different [re]solution.
>
> My reasoning is: not only are we predicting the unpredictable, i.e.,
> what other people want/need, we are also teaching people how to learn,
> as that is the nature of designing for others. So the greeter IA should
> be the most suitable for that, no worries if it doesn't align to
> standards, because that's not typically what defines the best
> experience, as it is is only a snapshot of what has worked in the past,
> not what's needed in the present.

I could agree with that to some extend, but I'm also against reinventing
the wheel and in favor of reusing well-proven solutions :)

>> Yes, the list of keyboard is much longer
>
> Why? How common is it for a person to type in a different language than
> is read? If very, then can we combine the languages [read and key] into
> a single space, though still independently functional?

The same language could be spoken in several countries with different
keyboards. For example the French keyboard in France is AZERTY but the
French keyboard in Switzerland is QWERTY (go figure!). Other people
prefer having an interface in English (without translation) but use
their usual keyboard mapping.

But we were considered preselecting the most common value of the
keyboard based on the language when changed.

--
sajolida