Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various Design Fixes and Improvements #1268

Closed
11 of 13 tasks
danielromlein opened this issue Sep 22, 2016 · 16 comments
Closed
11 of 13 tasks

Various Design Fixes and Improvements #1268

danielromlein opened this issue Sep 22, 2016 · 16 comments
Assignees

Comments

@danielromlein
Copy link
Contributor

danielromlein commented Sep 22, 2016

Issue details

  • Kubernetes logo not properly aligned with breadcrumb. Breadcrumb needs to be moved down 1px, and I think logo has to go up 1px.
    • alignment
  • When a second level of breadcrumb is added, the parent jumps up a pixel
    • jump
  • Breadcrumb should start with overview page (e.g. Workloads > Pods)
  • "Kubernetes" logo is too close to menu icon – should be 24px
    • screen shot 2016-09-21 at 8 19 10 pm
  • Divider between local & global actions should be 1px instead of 2px; 32px tall instead of 40px
    • Desired:
      screen shot 2016-09-21 at 8 33 45 pm
  • Some action buttons have insufficient right padding ("Create" is too tight; "Edit" is correct)
    padding
  • Increase space between action button icon and text by 2px
    • too-close-buttons
  • Selected Namespace shouldn’t be blue and have gray background.
    • screen shot 2016-09-16 at 2 51 37 pm
    • Selected should be blue; hover state should have gray background, as per the Material spec.
  • Namespace dropdown font should be Roboto Medium, not Roboto Mono Medium
  • Namespace dropdown should have 10px spacing between Namespace and bottom border (currently 7px)
    screen shot 2016-09-21 at 8 52 46 pm
  • [x] Cards should have 2px border radius

    corners
  • Cards should have 1px border of 0,0,0, .12
  • “Ingress” is currently the only singular nav item. Change to "Ingresses"
  • Titles of graphs: "history" is redundant in “CPU usage history”. I think we should change to "CPU / Memory Usage [or Utilization?]" or even just "CPU".
Environment
Dashboard version: 1.4.0
Operating system: OSX
Chrome and Firefox
@maciaszczykm maciaszczykm added kind/bug Categorizes issue or PR as related to a bug. area/styling and removed kind/bug Categorizes issue or PR as related to a bug. labels Sep 22, 2016
@floreks floreks self-assigned this Sep 22, 2016
@maciaszczykm
Copy link
Member

maciaszczykm commented Sep 22, 2016

@romlein I hope you don't have anything against putting checkboxes near items that need be completed :)

@floreks
Copy link
Member

floreks commented Sep 22, 2016

Cards should have 1px border of 0,0,0, .12

Is it border between title and content?

Cards should have 2px border radius

Is it blur radius or spread radius? Current value for box shadow is quite complex.
0 1px 3px 0 rgba(0, 0, 0, .2), 0 1px 1px 0 rgba(0, 0, 0, .14), 0 2px 1px -1px rgba(0, 0, 0, .12)

@floreks
Copy link
Member

floreks commented Sep 22, 2016

Breadcrumb should start with overview page (e.g. Workloads > Pods)

We've abandoned this idea at some point but I'm not sure why. We can add this again I think. @bryk @maciaszczykm what do you think?

Some action buttons have insufficient right padding ("Create" is too tight; "Edit" is correct)

Unfortunately this is default angular material behavior. When text is too long and takes too much space then padding is smaller. To fix that globally we'd need some kind of wrapper for md-button. Anyone has a better idea for that?

Selected Namespace shouldn’t be blue and have gray background.

Same as above. Not easy to fix and requires default angular material behavior override.

Titles of graphs: "history" is redundant in “CPU usage history”. I think we should change to "CPU / Memory Usage [or Utilization?]" or even just "CPU".

I don't have any strong opinions here. Simple CPU/Memory Usage sounds good to me. I'll change that once we agree on something.

@danielromlein
Copy link
Contributor Author

@maciaszczykm checkboxes are great! Sorry, I didn't know you could include those.

@floreks

Breadcrumb should start with overview page (e.g. Workloads > Pods)

As with all of these I'm totally open to being to persuaded otherwise if there's a good reason.

Some action buttons have insufficient right padding ("Create" is too tight; "Edit" is correct)

Ah ok, that's unfortunate. No I don't have any ideas.

Simple CPU/Memory Usage sounds good to me

Cool, let's wait for @bryk to weigh in.

Is it border between title and content?

No, I was referring to the border all the way around the card. Since the divider between title and content is #ddd, that would work for the border all the way around as well I think.

Cards should have 2px border radius

That's referring to the rounding of the corners of the card itself – not the shadow.

@floreks
Copy link
Member

floreks commented Sep 22, 2016

Current state (with border changed from #ddd to rgba(0,0,0,.12)):

Card
zrzut ekranu z 2016-09-22 15-40-19

Logo & breadcrumbs
zrzut ekranu z 2016-09-22 15-40-23

Logo & breadcrumbs (2 levels)
zrzut ekranu z 2016-09-22 15-40-34

Overall
zrzut ekranu z 2016-09-22 15-41-26

@bryk
Copy link
Contributor

bryk commented Sep 27, 2016

Breadcrumb should start with overview page (e.g. Workloads > Pods)

We've abandoned this idea at some point but I'm not sure why. We can add this again I think. @bryk @maciaszczykm what do you think?

This was at the time of menu with workloads only. This can be reintroduced.

@bryk
Copy link
Contributor

bryk commented Sep 27, 2016

Simple CPU/Memory Usage sounds good to me

Cool, let's wait for @bryk to weigh in.

I'd go with CPU/Memory or CPU usage/Memory usage. I've been commenting about this before.

@bryk
Copy link
Contributor

bryk commented Sep 27, 2016

Some action buttons have insufficient right padding ("Create" is too tight; "Edit" is correct)

Hmm.. This looks like a bug. I'll take a look.

@danielromlein
Copy link
Contributor Author

danielromlein commented Nov 22, 2016

@bryk where do we stand with these remaining changes? It'd be nice to wrap these up.
Still to be done:

  • Rename CPU & Memory graphs
  • Start breadcrumb with overview page (e.g. Workloads > Pods)
  • Fix padding issue where some action buttons have insufficient right padding ("Create" is too tight; "Edit" is correct)
  • Selected Namespace shouldn’t be blue and have gray background.

@bryk
Copy link
Contributor

bryk commented Nov 23, 2016

Rename CPU & Memory graphs

This is done already.

Start breadcrumb with overview page (e.g. Workloads > Pods)

I'll take care of this.

bryk added a commit to bryk/dashboard that referenced this issue Nov 23, 2016
maciaszczykm pushed a commit that referenced this issue Nov 24, 2016
* Update breadcrumbs to show ast 3 states for entire app

Re #1268

* Fix compilation error

* Add missing tests for nav items
@bryk
Copy link
Contributor

bryk commented Nov 28, 2016

Fix padding issue where some action buttons have insufficient right padding ("Create" is too tight; "Edit" is correct)

This is harder than expected, as the behavior is built into the library we use...

But all other comments are done :)

@maciaszczykm
Copy link
Member

But all other comments are done :)

Can we close it then?

@danielromlein
Copy link
Contributor Author

If the button padding is too hard to correct for this release we can punt that, but I would like to see the following fixed:

Selected Namespace shouldn’t be blue and have gray background.

Thoughts on how difficult that would be @maciaszczykm?

@maciaszczykm
Copy link
Member

maciaszczykm commented Mar 15, 2017

@danielromlein As @floreks already noticed it's hard to implement. We use Angular Material select component (https://material.angularjs.org/latest/demo/select) and unfortunately it's not working as described in Material Design docs (https://material.io/guidelines/components/buttons.html#buttons-dropdown-buttons). We would need to override standard behavior, which is not good for us. We can make issue on Angular Material repsitory, maybe they'll be willing to fix it.

@maciaszczykm
Copy link
Member

Opened issue in Angular Material repo, will track it from #1730. Closing this issue.

@danielromlein
Copy link
Contributor Author

@maciaszczykm sounds good! Thank you for taking care of that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants