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

Horizontal panel separator look bogus #2300

Closed
jrieken opened this issue Jan 26, 2016 · 14 comments
Closed

Horizontal panel separator look bogus #2300

jrieken opened this issue Jan 26, 2016 · 14 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug ux User experience issues verified Verification succeeded
Milestone

Comments

@jrieken
Copy link
Member

jrieken commented Jan 26, 2016

I don't understand why it uses the status bar background color and that it even changes when debugging. It should use a more similar style as the sidebar does (background et al) and not look like an editor

screen shot 2016-01-26 at 11 41 49

@jrieken jrieken added the bug Issue identified by VS Code Team member as probable bug label Jan 26, 2016
@isidorn
Copy link
Contributor

isidorn commented Jan 26, 2016

As designed, please comment on the issue here #1876 where the current design is explained and it also links to other issues where this is discussed

@isidorn isidorn closed this as completed Jan 26, 2016
@jrieken
Copy link
Member Author

jrieken commented Jan 26, 2016

disagree - we should discuss this in the team

@jrieken jrieken reopened this Jan 26, 2016
@isidorn
Copy link
Contributor

isidorn commented Jan 26, 2016

Setting to jan for discussion

@isidorn isidorn added this to the Jan 2016 milestone Jan 26, 2016
@jrieken
Copy link
Member Author

jrieken commented Jan 26, 2016

@bgashler1, @stevencl fyi

...like the way you used colour in option 2 to indicate whether content in the panel is 'live' or 'hot' as you called it...

While that makes sense for the debug panel is doesn't for the output view. Take git which runs constantly and produces output all the time. Now depending on the debug status that is shown as 'hot' or not which is misleading.

I think it should use the title color of viewlets because it's just another part and it should also use their background color because it is a non-editable part.

@stevencl
Copy link
Member

We discussed this quite a bit before deciding to proceed with the design as it is. We understand the concern you have raised but we aren't sure how significant the consequences are. Is there something about the colour that you think will cause the user to misinterpret the output they are reading and cause them to take an incorrect action?

One thing I wonder about is whether or not the blue colour might be interpreted as indicating that focus is inside the panel. Now that we are doing this work to indicate focus, this might be another reason to rethink this design.

The main aim remains the same - we need to ensure that the horizontal panel can be distinguished from an editor.

@bpasero bpasero added the ux User experience issues label Jan 27, 2016
@bpasero bpasero modified the milestones: Feb 2016, Jan 2016 Jan 27, 2016
@jrieken
Copy link
Member Author

jrieken commented Jan 27, 2016

We usually don't use strong contour lines but separation by extensive backgrounds (see sidebar & editor). That's why I am irritated by the harsh line being drawn between editor and bottom panel. I would suggest to continue using the background stylings to separate editable from non-editable (primary/secondary) content.

I didn't think of focus indication but you do make a point there

screen shot 2016-01-27 at 11 06 04

@stevencl
Copy link
Member

Yes, we will revisit this.

@isidorn
Copy link
Contributor

isidorn commented Jan 27, 2016

Giving to Brad so he is aware of feedback.
Once we collect all the feedback we can revisit what exactly to do here.

@isidorn isidorn assigned bgashler1 and unassigned isidorn Jan 27, 2016
@bgashler1
Copy link
Contributor

Thanks everyone for taking a good look at this. Are we targeting the February milestone to update this?
_EDIT:_ Just noticed we are. Ok, I'll be working on some new design proposals starting after end game week based off the feedback and this discussion.

@jrieken
Copy link
Member Author

jrieken commented Jan 27, 2016

awesome

@jrieken
Copy link
Member Author

jrieken commented Jan 27, 2016

Btw my choice of color are shown here: #1875 (comment)

@bgashler1
Copy link
Contributor

@jrieken, how does this look to you? It's gray now, so it's not misleading—in the case that a user is looking at Git output. It's also lightweight and gracefully avoids becoming a viewlett.
image

.monaco-workbench>.part.panel>.title { border-color: rgba(127, 127, 127, 0.34902); }

FYI - @stevencl

@bgashler1
Copy link
Contributor

I can push this change if you're happy with it.

@isidorn
Copy link
Contributor

isidorn commented Feb 24, 2016

@bgashler1 we will discuss this during the standup and if we decide to do it I can push it. Thanks

@bgashler1 bgashler1 added the verified Verification succeeded label Mar 18, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug ux User experience issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants