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

Allow developers create custom main menu items from extensions. #365

Closed
ilich opened this issue Nov 20, 2015 · 9 comments
Closed

Allow developers create custom main menu items from extensions. #365

ilich opened this issue Nov 20, 2015 · 9 comments
Labels
api feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code ux User experience issues
Milestone

Comments

@ilich
Copy link

ilich commented Nov 20, 2015

Hello,

It would be nice to have a possibility to create custom menu items for extensions' commands, e.g. Edit -> Format Document. I think it should work similar to keybindings contribution point.

Sincerely,
Ilya

@bpasero bpasero added the feature-request Request for new features or functionality label Nov 20, 2015
@egamma egamma added the api label Nov 23, 2015
@beiluo
Copy link

beiluo commented Dec 4, 2015

+1

1 similar comment
@Thaina
Copy link

Thaina commented Dec 4, 2015

+1

@egamma egamma modified the milestone: Backlog Dec 10, 2015
@artas90
Copy link

artas90 commented Apr 7, 2016

Yes, mouse-less interface is good. But some functions are used rare. And it is better to have them in menu and do not guess how it is called in Command Palette.

@bpasero bpasero added the ux User experience issues label May 2, 2016
@brunnopleffken
Copy link
Contributor

I came here because of #6000

My point here as a VS Code (& others) user... Adobe Brackets does this (put everything in "Edit" or create new menu items for each extension), and the menus become SOOOO cluttered, with native features + extension features in the same menu makes it too long! I particularly hate this kind of solution that Adobe has taken.

I think a menu "Extensions" listing the installed extensions and submenus with the functions of each extension (like #6000 does) is an elegant solution.

@pawchen
Copy link

pawchen commented May 11, 2016

It seems to me that Notepad++ take the similar approach with @brunnopleffken proposed. I think it's more organized and discoverable than random places. I've seen people didn't know how to "activate" some extension for VS.

@Tyriar
Copy link
Member

Tyriar commented May 11, 2016

I would prefer if the menu entries were isolated in an Extensions menu as in #6000. The reasons being:

  • It makes it very clear which menu items belong to which extensions.
  • Prevents possible duplicate menu items from multiple extensions by forcing nesting.
  • Allowing menu items in the regular menu has the potential for abuse.

@smuuf
Copy link

smuuf commented Oct 19, 2016

Please, please, avoid the clutter made by many extensions extending menus at several places and create a new Extensions menu for extensions' menus, so our installed extensions can have menus. ❤️

@hanfengcan
Copy link

2 year now~

@Tyriar Tyriar added the *out-of-scope Posted issue is not in scope of VS Code label Dec 12, 2017
@vscodebot
Copy link

vscodebot bot commented Dec 12, 2017

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api feature-request Request for new features or functionality *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