spencerone@???:
> Alan,
>
> On 01/23/2015 08:30, Alan wrote:
>> Hi!
>>
>> I implemented a first prototype. Please have a look at
>> https://labs.riseup.net/code/issues/7550#note-9
Woh! Big up!
> My first thoughts are about the use of the color blue. If the color
> blue is used to highlight selections, such as in the Language selection
> of Arabic in greeter1.png, it clashes with its use as a hyperlink
> indicator, such as in the highlight of 'more info', and its use as an
> alternative path indicator, such as in the highlight of the 'Guided'
> button, in all three greeter.pngs. Also, should we be using TAILS
> purple here?
Well, all those three usages of the blue color are inherited from the
default GNOME libraries. See
https://developer.gnome.org/hig/stable/ui-elements.html.en.
We proposed to have the "Guided" button in blue to make it sticking out
a bit more for new comers. It reuses the blue as color for "suggested"
button in the GNOME HIG.
Also note that this same blue color is used in other interface elements
in the HIG such as progress bar, activated switches, etc.
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.
Regarding the "Guided" button, maybe it would be clearer if it was
called "Guided setup" (as in earlier mockups I think). I'm all for
removing words but not too many :)
> My next thoughts are about the use of the dotted line in the
> depressed/active states of buttons. If the dotted line is an indicator
> in addition to the inner drop shadow, such as in the active state of the
> 'Basic' button in greeter1.png and the 'Advanced' button in
> greeter2.png, then it would be beneficial to include it in every screen
> in which buttons are depressed/active, such as the depressed/active
> states of the 'Basic' and 'Keyboard' buttons in greeter3.png.
I think that the dotted line in the first image is either a glitch or
some temporary state because it doesn't happen on the second image.
Again Alan probably reused the default behavior of GNOME buttons here.
> My next thoughts are about the 'Search' field. In the Keyboard Language
> widget that appears during the active state of the 'Keyboard' button,
> there is a 'Search' field, though the scroll bar slider seems to
> indicate only a couple of options are hidden below, negating the value
> of the 'Search' field's presence. If this language list is truncated
> for prototyping purposes, then ignore this.
Yes, the list of keyboard is much longer and having a quick search is
really useful when you start Tails every day or several times a day and
need to configure a keyboard.
Alan, I'm myself concerned about the width of this popup. Remember that
some keyboard description has super long such as
"Arabic (Morocco) - Berber (Morocco, Tifinagh alternative phonetic)"
Sic!
So we need to take this into consideration and probably have a much
wider popup across the main window. Sorry for your nice alignment :)
> Though, if there is a
> 'Search' field for one language list, such as in the widget that appears
> during the active state of the 'Keyboard' button in greeter3.png, then
> it seems logical to include it in the other, such as in the Language
> selection of TAILS in both greeter1.png and greeter3.png.
That makes sense, but on the other hand this would add an extra widget
to the screen so maybe we can find something better.
In the current Greeter we have something different that could be reused
here. The predefined list of 7 or so languages ends up with an
"Others..." item. Then we could have a popup similar to the one for the
keyboard selection, including the search widget when "Others..." is
clicked. But then I'm not sure how this extra language would be made
visible on the original widget once selected...
> My next thoughts are about the use of trademark symbols. In
> greeter2.png, regarding Windows™, Microsoft™, and Windows®, in addition
> to the conflicting use of the symbols, they have no legal significance.
> With the exception of Microsoft, which has no secondary meaning in our
> society, they do, however, in the case of Windows, help to clarify to
> people that we are referring to the OS and not an actual window.
> Though, with the assisted text "Looks like Microsoft Windows", which
> might intend to read "Look", not "Looks", I think enough context is
> established to justify dropping the symbols all together.
+1
> My last thought, without getting into the IA, is about the main
> navigation of the greeter. With the addition of the 'Close' 'X', the
> top right corner seems a bit crowded. I am not sure of a [re]solution
> just yet, but, as we move forward with the broader IA structure, it
> should come to the light.
I think that we don't need the 'X' in the top right corner. Maybe it was
tricky for Alan to implement a prototype without it but it should
definitely be removed as it does make sense in the context of the Greeter.
PS: I will send more comments as well later on...
--
sajolida
%20At%0A>%20least%20for%20the%20selection%20list%20and%20hyperlink.%0A>%20%0A>%20Regarding%20the%20%22Guided%22%20button,%20maybe%20it%20would%20be%20clearer%20if%20it%20was%0A>%20called%20%22Guided%20setup%22%20(as%20in%20earlier%20mockups%20I%20think).%20I'm%20all%20for%0A>%20removing%20words%20but%20not%20too%20many%20:)%0A>%20%0A>%20>%20My%20next%20thoughts%20are%20about%20the%20use%20of%20the%20dotted%20line%20in%20the%0A>%20>%20depressed/active%20states%20of%20buttons.%20If%20the%20dotted%20line%20is%20an%20indicator%0A>%20>%20in%20addition%20to%20the%20inner%20drop%20shadow,%20such%20as%20in%20the%20active%20state%20of%20the%0A>%20>%20'Basic'%20button%20in%20greeter1.png%20and%20the%20'Advanced'%20button%20in%0A>%20>%20greeter2.png,%20then%20it%20would%20be%20beneficial%20to%20include%20it%20in%20every%20screen%0A>%20>%20in%20which%20buttons%20are%20depressed/active,%20such%20as%20the%20depressed/active%0A>%20>%20states%20of%20the%20'Basic'%20and%20'Keyboard'%20buttons%20in%20greeter3.png.%0A>%20%0A>%20I%20think%20that%20the%20dotted%20line%20in%20the%20first%20image%20is%20either%20a%20glitch%20or%0A>%20some%20temporary%20state%20because%20it%20doesn't%20happen%20on%20the%20second%20image.%0A>%20Again%20Alan%20probably%20reused%20the%20default%20behavior%20of%20GNOME%20buttons%20here.%0A>%20%0A>%20>%20My%20next%20thoughts%20are%20about%20the%20'Search'%20field.%20In%20the%20Keyboard%20Language%0A>%20>%20widget%20that%20appears%20during%20the%20active%20state%20of%20the%20'Keyboard'%20button,%0A>%20>%20there%20is%20a%20'Search'%20field,%20though%20the%20scroll%20bar%20slider%20seems%20to%0A>%20>%20indicate%20only%20a%20couple%20of%20options%20are%20hidden%20below,%20negating%20the%20value%0A>%20>%20of%20the%20'Search'%20field's%20presence.%20%20If%20this%20language%20list%20is%20truncated%0A>%20>%20for%20prototyping%20purposes,%20then%20ignore%20this.%0A>%20%0A>%20Yes,%20the%20list%20of%20keyboard%20is%20much%20longer%20and%20having%20a%20quick%20search%20is%0A>%20really%20useful%20when%20you%20start%20Tails%20every%20day%20or%20several%20times%20a%20day%20and%0A>%20need%20to%20configure%20a%20keyboard.%0A>%20%0A>%20Alan,%20I'm%20myself%20concerned%20about%20the%20width%20of%20this%20popup.%20Remember%20that%0A>%20some%20keyboard%20description%20has%20super%20long%20such%20as%0A>%20%0A>%20%22Arabic%20(Morocco)%20-%20Berber%20(Morocco,%20Tifinagh%20alternative%20phonetic)%22%0A>%20%0A>%20Sic!%0A>%20%0A>%20So%20we%20need%20to%20take%20this%20into%20consideration%20and%20probably%20have%20a%20much%0A>%20wider%20popup%20across%20the%20main%20window.%20Sorry%20for%20your%20nice%20alignment%20:)%0A>%20%0A>%20>%20Though,%20if%20there%20is%20a%0A>%20>%20'Search'%20field%20for%20one%20language%20list,%20such%20as%20in%20the%20widget%20that%20appears%0A>%20>%20during%20the%20active%20state%20of%20the%20'Keyboard'%20button%20in%20greeter3.png,%20then%0A>%20>%20it%20seems%20logical%20to%20include%20it%20in%20the%20other,%20such%20as%20in%20the%20Language%0A>%20>%20selection%20of%20TAILS%20in%20both%20greeter1.png%20and%20greeter3.png.%0A>%20%0A>%20That%20makes%20sense,%20but%20on%20the%20other%20hand%20this%20would%20add%20an%20extra%20widget%0A>%20to%20the%20screen%20so%20maybe%20we%20can%20find%20something%20better.%0A>%20%0A>%20In%20the%20current%20Greeter%20we%20have%20something%20different%20that%20could%20be%20reused%0A>%20here.%20The%20predefined%20list%20of%207%20or%20so%20languages%20ends%20up%20with%20an%0A>%20%22Others...%22%20item.%20Then%20we%20could%20have%20a%20popup%20similar%20to%20the%20one%20for%20the%0A>%20keyboard%20selection,%20including%20the%20search%20widget%20when%20%22Others...%22%20is%0A>%20clicked.%20But%20then%20I'm%20not%20sure%20how%20this%20extra%20language%20would%20be%20made%0A>%20visible%20on%20the%20original%20widget%20once%20selected...%0A>%20%0A>%20>%20My%20next%20thoughts%20are%20about%20the%20use%20of%20trademark%20symbols.%20%20In%0A>%20>%20greeter2.png,%20%20regarding%20Windows%E2%84%A2,%20Microsoft%E2%84%A2,%20and%20Windows%C2%AE,%20in%20addition%0A>%20>%20to%20the%20conflicting%20use%20of%20the%20symbols,%20they%20have%20no%20legal%20significance.%0A>%20>%20With%20the%20exception%20of%20Microsoft,%20which%20has%20no%20secondary%20meaning%20in%20our%0A>%20>%20society,%20they%20do,%20however,%20in%20the%20case%20of%20Windows,%20help%20to%20clarify%20to%0A>%20>%20people%20that%20we%20are%20referring%20to%20the%20OS%20and%20not%20an%20actual%20window.%20%0A>%20>%20Though,%20with%20the%20assisted%20text%20%22Looks%20like%20Microsoft%20Windows%22,%20which%0A>%20>%20might%20intend%20to%20read%20%22Look%22,%20not%20%22Looks%22,%20I%20think%20enough%20context%20is%0A>%20>%20established%20to%20justify%20dropping%20the%20symbols%20all%20together.%0A>%20%0A>%20+1%0A>%20%0A>%20>%20My%20last%20thought,%20without%20getting%20into%20the%20IA,%20is%20about%20the%20main%0A>%20>%20navigation%20of%20the%20greeter.%20%20With%20the%20addition%20of%20the%20'Close'%20'X',%20the%0A>%20>%20top%20right%20corner%20seems%20a%20bit%20crowded.%20%20I%20am%20not%20sure%20of%20a%20%5Bre%5Dsolution%0A>%20>%20just%20yet,%20but,%20as%20we%20move%20forward%20with%20the%20broader%20IA%20structure,%20it%0A>%20>%20should%20come%20to%20the%20light.%0A>%20%0A>%20I%20think%20that%20we%20don't%20need%20the%20'X'%20in%20the%20top%20right%20corner.%20Maybe%20it%20was%0A>%20tricky%20for%20Alan%20to%20implement%20a%20prototype%20without%20it%20but%20it%20should%0A>%20definitely%20be%20removed%20as%20it%20does%20make%20sense%20in%20the%20context%20of%20the%20Greeter.%0A>%20%0A>%20PS:%20I%20will%20send%20more%20comments%20as%20well%20later%20on...%0A>%20%0A>%20--%20%0A>%20sajolida%0A>%20%0A>%20 "Répondre à ce message")