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

Pt#147640893 - redesign vm details #831

Closed

Conversation

AllenBW
Copy link
Member

@AllenBW AllenBW commented Jun 30, 2017

https://www.pivotaltracker.com/story/show/147640893

Brings service details closer to the mock mentioned in the pt.

In ops rows occasionally link to other views, this task was NOT done as part of this pr.

RBAC implemented where applicable.

There are a few icons/tiny images yet to do on this pr, but wanted to get the bulk of this out there

Da gooooooodddzzzzzzzz

vmdetails

shout out to @jntullo for api 🛍 ⛑

Odds and end this fixes:

  • fixes color names app_colors rather than colors
  • scroll overflow for detail rows whose content extends space
  • ensures vm-details error feedback is meaningful
  • updates filters (formatBytes) to provide additional precision
  • other minor stuff, check commit messages

@AllenBW AllenBW added this to the Sprint 64 Ending Jul 3, 2017 milestone Jun 30, 2017
@chriskacerguis chriskacerguis self-assigned this Jun 30, 2017
@chriskacerguis
Copy link
Contributor

@ManageIQ/core-ux for your review

/cc @Loicavenel

chriskacerguis
chriskacerguis previously approved these changes Jun 30, 2017
@chriskacerguis
Copy link
Contributor

@AllenBW this is good 🍣

@chriskacerguis
Copy link
Contributor

@AllenBW can you please address the travis fail?

@AllenBW
Copy link
Member Author

AllenBW commented Jun 30, 2017

Yeah that's odd, not failing locally 🤔

@AllenBW
Copy link
Member Author

AllenBW commented Jun 30, 2017

@chriskacerguis yeah that should feel better 🌮 😋

@miq-bot
Copy link
Member

miq-bot commented Jun 30, 2017

Checked commits AllenBW/manageiq-ui-service@90bfae4~...dc4febc with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
0 files checked, 0 offenses detected
Everything looks fine. 🏆

@chriskacerguis
Copy link
Contributor

@ManageIQ/core-ux for your review

/cc @Loicavenel

@Loicavenel
Copy link

First comment is about Smart Tags.. at Service level it is different... we should remain consistent..

@AllenBW
Copy link
Member Author

AllenBW commented Jul 6, 2017

@Loicavenel Dont quite follow, a different level?

@Loicavenel
Copy link

@AllenBW the way we represent Tags at Service level (blue boxes) is different at the VM level (a table)

@AllenBW
Copy link
Member Author

AllenBW commented Jul 6, 2017

Ah @Loicavenel the inconsistency below:
screen shot 2017-07-06 at 10 12 30 am

A few comments on the comment:

  • no unifying ux guidance has been provided, this pr follows outstanding guidance
  • parity, this pattern matches opsui

@Loicavenel
Copy link

@AllenBW yes, this is what I am talking about.. So, we introduced this blue box concept (I like it) which does not exist in OpsUI (Or I never saw it) but in VMS, we do as Ops UI.... This is inconsistent for me... Now, I understand this require some guidance

@serenamarie125
Copy link

These mocks were provided a ways back, and had no input from PM. Let's discuss

@serenamarie125
Copy link

I think that this goes back to the thought that we were introducing new elements into the SUI that would be later brought into the Ops UI. This is not the only place that we are showing tags this way in the SUI. If i remember right, chris hale or josh worked on a component with colleen on this a ways back.

@beanh66
Copy link

beanh66 commented Jul 6, 2017

@serenamarie125 Correct, Josh and I worked on a common design pattern for Tags that we were looking to first implement throughout the SUI and add follow up stories to implement in the Ops UI. The design can be found HERE on the design repo under the Common Components section.

@Loicavenel
Copy link

@serenamarie125 this was my point we should use the same pattern for all SUI when is about Tags :)

@AllenBW
Copy link
Member Author

AllenBW commented Jul 7, 2017

So we have a meet setup to talk about the tags, thinking adjusting falls outta scope of the original ask of this pr, which was to make vm-details look like the mocks we presently had.

Given ☝️ @Loicavenel @serenamarie125 @chriskacerguis, I propose we merge this and do the additional work in a future pr.

@chriskacerguis
Copy link
Contributor

@serenamarie125 @Loicavenel so, I setup a meeting to discuss, regardless of the outcome of that meeting it would be a separate PR to address the look / feel of the tags. Can we agree that this can go in (as it does fit the current UX design) and once we have consensus we will address the tag look and feel?

/cc @chessbyte

@Loicavenel
Copy link

@chriskacerguis Ok, can we have a screenshot from other type of VM... Windows on wmware, Amazon instance for example

@chriskacerguis
Copy link
Contributor

@allewbw could you help with that?

@AllenBW
Copy link
Member Author

AllenBW commented Jul 7, 2017

yeah! i'll get on that monday... 5 prs in a day is enough for me 😩 🤘

@AllenBW
Copy link
Member Author

AllenBW commented Jul 10, 2017

Here are a few more fotos of different provider types, (all i have in my db) @chriskacerguis @Loicavenel
screen shot 2017-07-10 at 9 29 41 am
screen shot 2017-07-10 at 9 29 47 am
screen shot 2017-07-10 at 9 30 38 am
screen shot 2017-07-10 at 9 30 58 am
screen shot 2017-07-10 at 9 28 46 am
screen shot 2017-07-10 at 9 28 37 am

@miq-bot
Copy link
Member

miq-bot commented Jul 12, 2017

This pull request is not mergeable. Please rebase and repush.

@chriskacerguis
Copy link
Contributor

Added new UX to the story. Closing this PR.

@AllenBW
Copy link
Member Author

AllenBW commented Jul 13, 2017

le sigh. 831, I will not forget you

@AllenBW AllenBW deleted the PT/#147640893-redesign-vm-details branch October 19, 2017 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants