On 01 Aug 2015, at 22:45, Peter Uhnák <i.uhnak@gmail.com> wrote:
On Sat, Aug 1, 2015 at 10:10 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Le 1/8/15 13:54, Esteban Lorenzano a écrit :
On 01 Aug 2015, at 13:25, Franck Warlouzet <franck.warlouzet@hotmail.fr <mailto:franck.warlouzet@hotmail.fr>> wrote:
Hello,
Yes it looks a little bit 'lite' but we did not want to have 2 buttons with the same look but two different kinds of actions. Hierarchy button changes the window itself and variable and scoped open a new menu or window.
but they are buttons, then they should look like one. also⦠âVariablesâ (button or whatever) there just do not make sense (since is a âclassâ related action)⦠it increases confusion instead solving a problem. we need a better general approach for those actions, maybe a toolbar or something like that⦠but as it is now it does not work.
Yes we know. Now there is a difference between a button popping something and one just acting on the default browser.
But does there need to be a distinction?
If I DON'T know what the button does, then distinction, unless it is well known, will not help me, because I will not know what the distinction means.
And if I DO know what it does, then I don't care about the distinction anymore.
So if you want to visualize it, then it must be something that is well known. For example "Print ..." (dotdotdot) means "Clicking on this will not print immediately, but will open a new window with some more stuff.", or the V triangle down signifies that it will open a dropdown menu.
And even with these minor UI/UX details, most people don't even realize it's there and will just memorize and internalize the process,
+1000 is complete non-sense to change form of buttons just because they trigger a different action. basically, all rules of UI design are against it. Every year we have same discussion, and every year I point to the same readings: - âdonât make me thinkâ. https://en.wikipedia.org/wiki/Don%27t_Make_Me_Think <https://en.wikipedia.org/wiki/Don't_Make_Me_Think> - the mac UI design guidelines. https://developer.apple.com/library/mac/documentation/UserExperience/Concept... <https://developer.apple.com/library/mac/documentation/UserExperience/Concept...> there are many papers, research, etc. around this but well⦠here is a *very* simplified summary of principles: http://web.cs.wpi.edu/~matt/courses/cs563/talks/smartin/int_design.html <http://web.cs.wpi.edu/~matt/courses/cs563/talks/smartin/int_design.html> And even more simplified: Coherence (same metaphor), organisation (same layout), uniqueness (same elements) So, a button is a button. If we present them as links, then ALL buttons should be a link. If they are âold-styleâ buttons, then ALL buttons should be old style. Esteban
Peter