Hi,
spencerone@??? wrote:
> Attached is a visual exploration of what the Check & Go greeter screen
> could look like.
Thanks! Your proposals are much clearer to me with this drawing.
> In short, it attempts to consolidate as much of the existing flow
> fragmentation as possible. There is a more detailed explanation on the
> document itself.
>
> I hope it addresses the existing decisions as you intended, if not, we
> can figure it out together :)
>
At first view, it seems to me that even though it doesn't address all
the existing "decisions" (actually more directions or guidelines we
agreed on) it looks possible to refine your design to address most of
them. So I'm up for discussing it deeper. If feels a bit like going
back to another design iteration to me but if we find a way to address
tchou's and your concerns about the current proposed design then I
think it's worth it.
Tchou and sajolida, could you please comment spencerone's proposal ASAP?
Tchou, do you think it goes in the direction of addression the issues
you have identified with previous proposals?
Spencerone, is it possible th have an editable version of your mockups
so that I can propose modifications graphically?
Please find below some detailled comment on the things I think we
should modify/refine if we go that way:
- it looks great overall.
- having to click an edit button to make setting editable looks useless
and painful to me. Consider an user that starts Tails for the 1st
time. She gets the defaults settings, adn before editing anything,
she'll have to click an edit button. Why not to make the settings
editable straight form the summary screen, e.g. with a Popover [1]
as on my current proposal[2]? That doesn't prevent us from showing a
"Guided" button as on my current proposal[2]. If a setting is edited,
we could then show a "Save" button.
- I think that the Storage section should go above the Settings
section. An user that has an encrypted storage area indeed needs to
access this section at each boot.
- is there a good reason not to use icons as we have in current
proposal?
- we wanted to have direct access to the languages, thus the left
languages list in my current proposal [2]. Yours doesn't address that
currently. However, given the big number of languages we now support,
I'm not sure that this goal is still valid. It may very well be
better to have a dropdown (e.g. a Popover) with a search area.
- I don't understand the "Specify the files that will be stored in the
encrypted storage folder" part. Anyway please note that including the
Persistence creation in the greeter won't probably be part of the 1st
iteration of the revamp.
Cheers
[1].
https://developer.gnome.org/hig/stable/popovers.html.en
[2].
https://labs.riseup.net/code/attachments/download/650/greeter3.png
%0A>%20>%20%0A>%20At%20first%20view,%20it%20seems%20to%20me%20that%20even%20though%20it%20doesn't%20address%20all%0A>%20the%20existing%20%22decisions%22%20(actually%20more%20directions%20or%20guidelines%20we%0A>%20agreed%20on)%20it%20looks%20possible%20to%20refine%20your%20design%20to%20address%20most%20of%0A>%20them.%20So%20I'm%20up%20for%20discussing%20it%20deeper.%20If%20feels%20a%20bit%20like%20going%0A>%20back%20to%20another%20design%20iteration%20to%20me%20but%20if%20we%20find%20a%20way%20to%20address%0A>%20tchou's%20and%20your%20concerns%20about%20the%20current%20proposed%20design%20then%20I%0A>%20think%20it's%20worth%20it.%0A>%20%0A>%20Tchou%20and%20sajolida,%20could%20you%20please%20comment%20spencerone's%20proposal%20ASAP?%0A>%20%0A>%20Tchou,%20do%20you%20think%20it%20goes%20in%20the%20direction%20of%20addression%20the%20issues%0A>%20you%20have%20identified%20with%20previous%20proposals?%0A>%20%0A>%20Spencerone,%20is%20it%20possible%20th%20have%20an%20editable%20version%20of%20your%20mockups%0A>%20so%20that%20I%20can%20propose%20modifications%20graphically?%0A>%20%0A>%20Please%20find%20below%20some%20detailled%20comment%20on%20the%20things%20I%20think%20we%0A>%20should%20modify/refine%20if%20we%20go%20that%20way:%0A>%20%0A>%20-%20it%20looks%20great%20overall.%0A>%20-%20having%20to%20click%20an%20edit%20button%20to%20make%20setting%20editable%20looks%20useless%0A>%20%20%20and%20painful%20to%20me.%20Consider%20an%20user%20that%20starts%20Tails%20for%20the%201st%0A>%20%20%20time.%20She%20gets%20the%20defaults%20settings,%20adn%20before%20editing%20anything,%0A>%20%20%20she'll%20have%20to%20click%20an%20edit%20button.%20Why%20not%20to%20make%20the%20settings%0A>%20%20%20editable%20straight%20form%20the%20summary%20screen,%20e.g.%20with%20a%20Popover%20%5B1%5D%0A>%20%20%20as%20on%20my%20current%20proposal%5B2%5D?%20That%20doesn't%20prevent%20us%20from%20showing%20a%0A>%20%20%20%22Guided%22%20button%20as%20on%20my%20current%20proposal%5B2%5D.%20If%20a%20setting%20is%20edited,%0A>%20%20%20we%20could%20then%20show%20a%20%22Save%22%20button.%0A>%20-%20I%20think%20that%20the%20Storage%20section%20should%20go%20above%20the%20Settings%0A>%20%20%20section.%20An%20user%20that%20has%20an%20encrypted%20storage%20area%20indeed%20needs%20to%0A>%20%20%20access%20this%20section%20at%20each%20boot.%0A>%20-%20is%20there%20a%20good%20reason%20not%20to%20use%20icons%20as%20we%20have%20in%20current%0A>%20%20%20proposal?%0A>%20-%20we%20wanted%20to%20have%20direct%20access%20to%20the%20languages,%20thus%20the%20left%0A>%20%20%20languages%20list%20in%20my%20current%20proposal%20%5B2%5D.%20Yours%20doesn't%20address%20that%0A>%20%20%20currently.%20However,%20given%20the%20big%20number%20of%20languages%20we%20now%20support,%0A>%20%20%20I'm%20not%20sure%20that%20this%20goal%20is%20still%20valid.%20It%20may%20very%20well%20be%0A>%20%20%20better%20to%20have%20a%20dropdown%20(e.g.%20a%20Popover)%20with%20a%20search%20area.%0A>%20-%20I%20don't%20understand%20the%20%22Specify%20the%20files%20that%20will%20be%20stored%20in%20the%0A>%20%20%20encrypted%20storage%20folder%22%20part.%20Anyway%20please%20note%20that%20including%20the%0A>%20%20%20Persistence%20creation%20in%20the%20greeter%20won't%20probably%20be%20part%20of%20the%201st%0A>%20%20%20iteration%20of%20the%20revamp.%0A>%20%0A>%20Cheers%0A>%20%0A>%20%5B1%5D.%20https://developer.gnome.org/hig/stable/popovers.html.en%0A>%20%5B2%5D.%20https://labs.riseup.net/code/attachments/download/650/greeter3.png%0A>%20%0A>%20 "Reply to this message")
