Just a quick note: remember that there is the “suggested-action” button which needs a particular hilight (it’s green in the new theme, blue Adwaita). Something to consider while talkin about focus in the headerbar
Consider that, from a “functional” point of view, a pressed button is not selected (for which state we chose the orange). At this time, when a button is actually selected, it gets a orange border
I like the current way.
It might’ve been posted here already but I like what this blog says about the orange:
It’s important for UX that keyboard navigation focus state “pops” because it can jump all over the place when you for example press tab.
This also provides an explanation for how nautilus looks: The “hero item” in Nautilus is the selected item in the left sidebar. You can argue that the folder in the pathbar is the same item, so it also deserves to be orange.
The hero item in tweaks for example is the current category you’re on.
I fully agree! I also think that we should use dark(er) for buttons. It might seem like a controversial post, but I was merely pointing out the inconsistencys.
A quibble: The next section of that article describes blue as “the Ubuntu selected state colour”, as distinct from orange. I don’t know what “hero item” actually meant in that context, but it suggests that a selected item wasn’t one.
Thanks for the clarification! I was on mobile, I honestly didn’t read that far
I actually really like blue as the general “selection” color. I liked it on Ubuntu Phone and in Adwaita. However, I’m unsure what the current stance on it is, since it has changed a bit in the past few weeks and I’m not following the design discussions too closely.
I also like the “new” blue from the latest color scheme; it feels warm and “homely”.
I wonder whether that darker blue is a problem with dark backgrounds
It seems that the black bottom line is rendered bad on some screens
Now the path-bar is still under rework, so maybe this won’t be a problem anymore, but this might be useful to know as well
This is replacing it with $slate (#5D5D5D)
I actually thought that we were reverting to this:
I don’t think the current design is working IMHO
since the button design is not consistent and has problems on the dark back, I stepped back again and overlooked some design and stuff we need to adopt (because of Gnome and so on). This is an overview of possible designs, after choosing what we like and what’s working I can work on defined mockups with the chosen design.
I also could not try all sorts of designs. Simply combine!
First the flat button design: (Not perfect visible on the PNG)
The four states are flat, hover, clicked and focused (like when hitting tab).
The first row is like it is now, the dark is hardly visible. So the second row has the same color for hover and clicked, with an inner-shadow to make it look clicked. Row 3 and 4 are also with an orange border for feedback.
We should consider this as a working and visual better solution. Also, the jump from white hover to dark clicked is less consistent.
Like always, breadcrumbs say hello.
The actual design is like also mads said not working (but was worth a shot!).
Like the connected buttons, they should be connected somehow and they should have a similar look.
Like the address bar in a browser, I don’t mind if it is not completely flat - they have a certain meaning and task and IS an address bar in a way. And with the white clicked button design from above it’s more consistent.
1: Flat, same backcolor, but repeating the Gnome surrounding buttons style
2: Like 1 but the clicked buttons also get’s an inner-shadow like on the other buttons.
3: Like 2, but only bottom line for focus and maybe little thinner like it is now because of the double feedback.
4: Only the clicked buttons feedback with the inner-shadow.
5: Flat with bottom border only, but then they need a separation between.
This kind of design is also adaptable to the power off window - with 4 or 1 border (focus and clicked):
Or the Software Center:
I don’t have time for perfect mockups (like squircle and colors, visual them in your mind^^) but this way around we’re adapting the Gnome style buttons and combining them with a better visuality like we have it now and the orange focus border(s) we use. And this brings more consistency and better usability thru the system (on dark back).
The buttons on white are still very different, but that’s also part of the deal when having a dark background. I tried also the inner-shadow effect, but this is a thing to try, mockups are not enough to see if it’s working. The orange color is also just a focus color - people will get used to it when using.
And yes, it is also a little compromise - maybe there is another consistent and working way. But to be consistend we need to make compromises here and there. Maybe it’s working in the live system too.
Overall - do you think this is a good way for you all?
Inner-shadow in connected buttons - or flat with a border only?
Let’s try to speed things up a bit to get faster decisions.
More stuff later… Stefan
Nice work Steffan
Short reply here: I like 1,3 or 5
Would you suggest another Hangout session?
Awesome work Stefan!
Flat button design: I like 2 and 3. The second option might be less visible in some screens though.
Breadcrumbs: 3 and 5
Summing it up, for squared items I prefer borders, while I prefer the bottom border only in rectangular shapes.
- flat button: 1 since the design of 3 doesn’t have a way to show “selected” status of a pressed-in button.
- breadcrumbs: 3, although I would prefer the pressed in state to be the same color as flat button 1. Since a pressed in flat button and breadcrumb is in the same z-axis, they should have the same color shade imo.
Thanks for your input, I’m not sure if the always pressed status is working everywhere in a nice looking way, but only for clicking (like in power off) it should be fine. We’ll find out^^
I sum it up to this for now based on your answers and including my favorites (hope this is right):
I’m out for today, hope we’ll get all feedbacks until tomorrow.
I like as well your proposal summary Way better for the click state than the orange-jumping-on-you that we did
The colors are subtiles and working well IMHO and the line shape brings consistency. However, I wonder how that will work for application buttons: we will have a square around focused buttons, which will be different in the Shell, like the Power Off dialog, any thoughts on this?
Can you give me a quick example/screenshot - not sure if I understand exactly what you mean. Are we limited to a certain design on some buttons?
I’m just talking about any GTK Button in any application for instance. The well-known paradigm for having focus (via keyboard navigation, tab tab…) is normally to have a selection border (orange in our case, blue for upstream).
Note that it’s the same for textbox and other widgets.
Having some buttons focus (like the Shell ones) representing differently may look inconsistent?
Another obvios construction site for me is the top bar and the dock, I also want you oppinion to force decicions:
I like the bar and dock in window mode (color and opacity, also the inner shadow is better, too strong on the top), only I still miss the shadow for the whole bar - this looks a little weird because the dock receives a shadow from the top bar.
The main problem is the max-window state - because the top bar is melting together with the headerbard and this has no meaning but visual confusing.
I put together some screenshots with mockups to get feedback, hope you can see enough to make decisions:
Like it is now, only with a shadow for the whole bar for separation. The inner-shadow on the dock is too strong (because its a screenshot)
Like it is now, but no shadows at all, only black separation lines. (too thin on the mockup)
Shadow for separation, the bar and dock are still quite the same opacity like in window mode - maybe a little less for an opacity for a fancy transition effect. This design is also less heavy then the actual.
Like #3 but now shadows, only black separation lines (too thin on the mockup).
Let’s try the poll tool: