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

Commanding UX #1136

Closed
stevencl opened this issue Dec 9, 2015 · 3 comments
Closed

Commanding UX #1136

stevencl opened this issue Dec 9, 2015 · 3 comments
Assignees
Labels
*out-of-scope Posted issue is not in scope of VS Code ux User experience issues
Milestone

Comments

@stevencl
Copy link
Member

stevencl commented Dec 9, 2015

We need to explore ways we can provide access to commands that are global in scope. For example, the start debug icon is only visible in the debug viewlet but should be available regardless of context.

This should also handle the current UX for the likes of git checkout where we have a label in the status bar that shortcuts to the git checkout command in the command palette.

@stevencl stevencl added the UX label Dec 9, 2015
@stevencl stevencl self-assigned this Dec 9, 2015
@stevencl stevencl added ux User experience issues and removed UX labels Dec 9, 2015
@egamma egamma modified the milestone: Backlog Dec 10, 2015
@stevencl
Copy link
Member Author

stevencl commented Aug 9, 2016

We also need to consider ways in which we communicate whether or not a command is valid. Consider extension actions showing up in the command palette for example.

Also, can we get clear guidance on when to show commands, how overflow should work, how many commands we show on a viewlet, appropriate use of context menus, how to arrange and order main menu commands etc.

Some of this just needs an overhaul (i.e., the View menu is getting pretty big), others need some design guidelines.

Also see #10308

@bpasero
Copy link
Member

bpasero commented Nov 16, 2017

@stevencl should we close this, it seems very generic and should maybe have more specific actionable issues?

@bpasero bpasero removed the workbench label Nov 16, 2017
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Nov 20, 2017
@vscodebot
Copy link

vscodebot bot commented Nov 20, 2017

This feature request will not be considered in the next 6-12 months roadmap and has been closed to keep the number of issues we have to maintain manageable. See also our issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Nov 20, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*out-of-scope Posted issue is not in scope of VS Code ux User experience issues
Projects
None yet
Development

No branches or pull requests

4 participants