Hi,
spencerone@??? wrote:
> > Alan:
> > I published a 1st draft of the rationale of our design proposal for the
> > greeter at:
> >
> > https://tails.boum.org/blueprint/greeter_revamp_UI/design_rationale_phase1
> >
>
> Holy shit, this is a ton of work; kick-ass, G! Thanks for this!!
>
Thanks!
> > I made a few changes:
> >
> > - I added a "more info" (aka help) link that was missing.
> > - I moved the reassuring text in the appropriate section "Settings"
> > - I moved Language above Storage as I think we decided
> >
>
> I dig the first two changes. The Language location change, which seems
> to be based on ticket #9922[0], doesn't seem to have a link to the
> discussion/logic that its built on, is there one?
>
I though we agreed on that:
https://mailman.boum.org/pipermail/tails-ux/2015-March/000303.html
> This[1] discussion details some thoughts on the placement of the
> 'Language' section. The summary of language auto-detect on the first
> iteration is:
>
> • Auto-detect language preference every session, deemphasizing the
> 'Language' section in 'Settings'.
>
That makes sense, but...
> The summary of *no* language auto-detect on the first iteration is:
>
> • Present the guided configuration step for 'Language'[2] every session
> unless saved, deemphasizing the 'Language' section in 'Settings'.
>
I don't agree on that (and I though it was clear). That is because one
*need* to set at least the keyboard layout to be able to type its
passphrase. Be there a saved language of not, it is logical to be
first ask to review the language before reading about typing
something with the wrong keyboard. Sorry for the misunderstanding.
> Also, this[3] comparison shows the two options side-by-side displayed
> with the understanding that we are placing the 'Language' section on top
> of the 'Storage' section because we aren't including a language
> auto-detect in this first phase.
>
> However, with all of this said, I think we should have the 'Language'
> section ordered after the 'Settings' section, since all people using
> this would have no issue locating the 'Language' section on the first
> screen, at least I am having trouble envisioning a case where they
> would.
>
I definately think the left one is better in all cases for the reason
explained above.
> > Also a few questions:
> >
> > - may I have the source of Tails.Greeter with the explanations?
> >
>
> Yes, I did zip it for you previously, I think, but in case I screwed
> that up, here[4].
>
That's not what I'm asking for. I'd like the source of the
Tails.Greeter.png I attach to this email.
> > - should we have icons for the ActionBar buttons?
> >
>
> No. Mainly because it is hard to effectively visualize 'Restart',
> 'Tour', and 'Start Tails' into iconic representations of their concepts.
> Considering 'Start Tails', the 'Play' and 'Computer' icons are not as
> precise as they cold be, which really leaves the standard stand-by I/O
> icon such as on a Mac.
>
> However, if we do include icons on our buttons, I encourage only
> settling on icons that only have the one meaning. For example, the
> 'Play' icon works because it is like saying "Run", which is what
> programs tend to do, but also doesn't work because it means "Play", like
> a video, and therefore isn't as precise of an iconic representation as
> it could be; this icon wouldn't make the cut.
>
I don't really want icons, just wanted to know why there were none.
Would you please add this to the blueprint?
> > - do we want to display both the "Configure Encrypted Storage" button
> > and the unlock box?
> >
>
> Yes, if the threat model *can* be defended against by displaying these
> two options side-by-side. Doing so also lessens development time,
> enhances the user experience, and reduces the likelihood of bugs by not
> having to create different states of the greeter for varying storage
> settings.
>
> However, if there *is* a technical way to accurately discover existing
> storage, then displaying both buttons side-by-side might not be
> effective to that extent, though doing so would still provide the
> development and usability benefits touched on above.
>
Currently there is, even though we though about removing it in the
future.
Cheers.
%20link%20that%20was%20missing.%0A>%20>%20>%20-%20I%20moved%20the%20reassuring%20text%20in%20the%20appropriate%20section%20%22Settings%22%0A>%20>%20>%20-%20I%20moved%20Language%20above%20Storage%20as%20I%20think%20we%20decided%0A>%20>%20>%20%0A>%20>%20%0A>%20>%20I%20dig%20the%20first%20two%20changes.%20%20The%20Language%20location%20change,%20which%20seems%20%0A>%20>%20to%20be%20based%20on%20ticket%20#9922%5B0%5D,%20doesn't%20seem%20to%20have%20a%20link%20to%20the%20%0A>%20>%20discussion/logic%20that%20its%20built%20on,%20is%20there%20one?%0A>%20>%20%0A>%20I%20though%20we%20agreed%20on%20that:%0A>%20https://mailman.boum.org/pipermail/tails-ux/2015-March/000303.html%0A>%20%0A>%20>%20This%5B1%5D%20discussion%20details%20some%20thoughts%20on%20the%20placement%20of%20the%20%0A>%20>%20'Language'%20section.%20%20The%20summary%20of%20language%20auto-detect%20on%20the%20first%20%0A>%20>%20iteration%20is:%0A>%20>%20%0A>%20>%20%E2%80%A2%20Auto-detect%20language%20preference%20every%20session,%20deemphasizing%20the%0A>%20>%20'Language'%20section%20in%20'Settings'.%0A>%20>%20%0A>%20That%20makes%20sense,%20but...%0A>%20%0A>%20>%20The%20summary%20of%20*no*%20language%20auto-detect%20on%20the%20first%20iteration%20is:%0A>%20>%20%0A>%20>%20%E2%80%A2%20Present%20the%20guided%20configuration%20step%20for%20'Language'%5B2%5D%20every%20session%0A>%20>%20unless%20saved,%20deemphasizing%20the%20'Language'%20section%20in%20'Settings'.%0A>%20>%20%0A>%20I%20don't%20agree%20on%20that%20(and%20I%20though%20it%20was%20clear).%20That%20is%20because%20one%0A>%20*need*%20to%20set%20at%20least%20the%20keyboard%20layout%20to%20be%20able%20to%20type%20its%0A>%20passphrase.%20Be%20there%20a%20saved%20language%20of%20not,%20it%20is%20logical%20to%20be%0A>%20first%20ask%20to%20review%20the%20language%20before%20reading%20about%20typing%0A>%20something%20with%20the%20wrong%20keyboard.%20Sorry%20for%20the%20misunderstanding.%0A>%20%0A>%20>%20Also,%20this%5B3%5D%20comparison%20shows%20the%20two%20options%20side-by-side%20displayed%20%0A>%20>%20with%20the%20understanding%20that%20we%20are%20placing%20the%20'Language'%20section%20on%20top%20%0A>%20>%20of%20the%20'Storage'%20section%20because%20we%20aren't%20including%20a%20language%20%0A>%20>%20auto-detect%20in%20this%20first%20phase.%0A>%20>%20%0A>%20>%20However,%20with%20all%20of%20this%20said,%20I%20think%20we%20should%20have%20the%20'Language'%20%0A>%20>%20section%20ordered%20after%20the%20'Settings'%20section,%20since%20all%20people%20using%20%0A>%20>%20this%20would%20have%20no%20issue%20locating%20the%20'Language'%20section%20on%20the%20first%20%0A>%20>%20screen,%20at%20least%20I%20am%20having%20trouble%20envisioning%20a%20case%20where%20they%20%0A>%20>%20would.%0A>%20>%20%0A>%20I%20definately%20think%20the%20left%20one%20is%20better%20in%20all%20cases%20for%20the%20reason%0A>%20explained%20above.%0A>%20%0A>%20>%20>%20Also%20a%20few%20questions:%0A>%20>%20>%20%0A>%20>%20>%20-%20may%20I%20have%20the%20source%20of%20Tails.Greeter%20with%20the%20explanations?%0A>%20>%20>%20%0A>%20>%20%0A>%20>%20Yes,%20I%20did%20zip%20it%20for%20you%20previously,%20I%20think,%20but%20in%20case%20I%20screwed%20%0A>%20>%20that%20up,%20here%5B4%5D.%0A>%20>%20%0A>%20That's%20not%20what%20I'm%20asking%20for.%20I'd%20like%20the%20source%20of%20the%0A>%20Tails.Greeter.png%20I%20attach%20to%20this%20email.%0A>%20%0A>%20>%20>%20-%20should%20we%20have%20icons%20for%20the%20ActionBar%20buttons?%0A>%20>%20>%20%0A>%20>%20%0A>%20>%20No.%20%20Mainly%20because%20it%20is%20hard%20to%20effectively%20visualize%20'Restart',%20%0A>%20>%20'Tour',%20and%20'Start%20Tails'%20into%20iconic%20representations%20of%20their%20concepts.%20%0A>%20>%20%20%20Considering%20'Start%20Tails',%20the%20'Play'%20and%20'Computer'%20icons%20are%20not%20as%20%0A>%20>%20precise%20as%20they%20cold%20be,%20which%20really%20leaves%20the%20standard%20stand-by%20I/O%20%0A>%20>%20icon%20such%20as%20on%20a%20Mac.%0A>%20>%20%0A>%20>%20However,%20if%20we%20do%20include%20icons%20on%20our%20buttons,%20I%20encourage%20only%20%0A>%20>%20settling%20on%20icons%20that%20only%20have%20the%20one%20meaning.%20%20For%20example,%20the%20%0A>%20>%20'Play'%20icon%20works%20because%20it%20is%20like%20saying%20%22Run%22,%20which%20is%20what%20%0A>%20>%20programs%20tend%20to%20do,%20but%20also%20doesn't%20work%20because%20it%20means%20%22Play%22,%20like%20%0A>%20>%20a%20video,%20and%20therefore%20isn't%20as%20precise%20of%20an%20iconic%20representation%20as%20%0A>%20>%20it%20could%20be;%20this%20icon%20wouldn't%20make%20the%20cut.%0A>%20>%20%0A>%20I%20don't%20really%20want%20icons,%20just%20wanted%20to%20know%20why%20there%20were%20none.%0A>%20Would%20you%20please%20add%20this%20to%20the%20blueprint?%0A>%20%0A>%20>%20>%20-%20do%20we%20want%20to%20display%20both%20the%20%22Configure%20Encrypted%20Storage%22%20button%0A>%20>%20>%20and%20the%20unlock%20box?%0A>%20>%20>%20%0A>%20>%20%0A>%20>%20Yes,%20if%20the%20threat%20model%20*can*%20be%20defended%20against%20by%20displaying%20these%20%0A>%20>%20two%20options%20side-by-side.%20%20Doing%20so%20also%20lessens%20development%20time,%20%0A>%20>%20enhances%20the%20user%20experience,%20and%20reduces%20the%20likelihood%20of%20bugs%20by%20not%20%0A>%20>%20having%20to%20create%20different%20states%20of%20the%20greeter%20for%20varying%20storage%20%0A>%20>%20settings.%0A>%20>%20%0A>%20>%20However,%20if%20there%20*is*%20a%20technical%20way%20to%20accurately%20discover%20existing%20%0A>%20>%20storage,%20then%20displaying%20both%20buttons%20side-by-side%20might%20not%20be%20%0A>%20>%20effective%20to%20that%20extent,%20though%20doing%20so%20would%20still%20provide%20the%20%0A>%20>%20development%20and%20usability%20benefits%20touched%20on%20above.%0A>%20>%0A>%20Currently%20there%20is,%20even%20though%20we%20though%20about%20removing%20it%20in%20the%0A>%20future.%0A>%20%0A>%20Cheers.%0A>%20 "Responder a esta mensaxe")