Re: [Tails-ux] [Tails-dev] Greeter mockups

Delete this message

Reply to this message
Autor: BitingBird
Data:  
Dla: Tails user experience & user interface design
Temat: Re: [Tails-ux] [Tails-dev] Greeter mockups
sajolida@??? a écrit :
> BitingBird wrote:
>> sajolida@??? a écrit :
>>> We're doing a last round of comments and polishing before moving on to
>>> implementation of phase 1.
>>
>> Some remarks: why does the first screen "start" button have a "play"
>> icon, while all other screens have a computer?
>
> Tchou proposed a computer logo for Start. Then Alan and I preferred the
> play logo. I might have left a version of each to leave this open to
> discussion.
>
> Which one do you think is better and why?


I prefer the play icon, it's quite known and easy to understand.
>
>> Did some japanese speaker check the ideograms on the 2 "languages"
>> icons, to make sure they are real ideograms ?
>

[...]
So after some wikipedia research, it seems to be
https://en.wikipedia.org/wiki/Su_(kana) and
https://en.wikipedia.org/wiki/Nu_%28kana%29 so... real characters,
except I didn't find versions with the things on top of the ideograms.
Let's say it's good enough, except if somebody tells us they're wrong :)
>
> Here again we have two versions because we haven't made a clear decision
> yet. I prefer the first icon on the first screen because it is less high
> and fits better on top of the selection list.
>
> Which one do you think is better and why?


I prefer the second one, because it presents 2 types of writing, like a
choice, but I see that the format of the first one is better. So, no
strong opinion in either direction.
>
>> Why did you keep weird sliders, while it's the thing that everybody
>> finds confusing, and we checked that Gnome says checkboxes are OK ?
>
> Those switches are described in the GNOME Human Interface Guideles [4]
> list this:
>
> « Switches should be used for controlling services or hardware that have
> a clear on/off logic. They are particularly appropriate when those
> services or hardware do not activate immediately (ie. there is a delay
> between the switch being operated and it having an effect), or when they
> affect the operation of the application in a significant way. »
>
> I think that this applies quite well to "Windows camouflage" and "Mac
> address spoofing". And I trust GNOME for them to be fine.
>
> [4]: https://developer.gnome.org/hig/stable/switches.html.en


Well, checkboxes seem to work also[1], for on/off questions, which are
our concern. And plenty of users reported problems with the switches
(*I* never get what they're on, that's for sure)[2]. Seriously, if you
see "on", does it mean it is "on", or you have to click to make it "on"?

[1]
https://developer.gnome.org/hig-book/unstable/menus-design.html.en#menu-item-type-check
: "Use a check box menu item only when it is obvious from the label what
the set and unset states mean. This usually means that the two states
are logical or natural opposites, such as "on" and "off"."

[2] https://tails.boum.org/blueprint/greeter_revamp_UI/feedback_on_0.X/

The only place that is concerned is the advanced options page
(https://tails.boum.org/blueprint/greeter_revamp_UI/greeter-advanced-screen.png),
for those who want to give input :)
>
>> In the advanced setup, I think the persistence configuration is not
>> implemented yet ?
>
> That's right. The same applies for the timezone configuration in the
> first screen and other things. But we wanted to design the screens with
> all the features that we are already planning on having. Even if they
> will be implemented with less features at first. Does that make sense?
>

Makes perfect sense, I just wanted to be sure :)

Cheers,

BitingBird