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

Support custom views in other locations #28662

Closed
1 task done
sandy081 opened this issue Jun 13, 2017 · 7 comments
Closed
1 task done

Support custom views in other locations #28662

sandy081 opened this issue Jun 13, 2017 · 7 comments
Assignees
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code tree-views Extension tree view issues

Comments

@sandy081
Copy link
Member

sandy081 commented Jun 13, 2017

Support custom views in other locations

  • Debug
@sandy081 sandy081 self-assigned this Jun 13, 2017
@sandy081 sandy081 added tree-views Extension tree view issues feature-request Request for new features or functionality labels Jun 13, 2017
@sandy081 sandy081 added this to the June 2017 milestone Jun 13, 2017
@sandy081 sandy081 modified the milestones: Backlog, June 2017 Jun 26, 2017
@eamodio
Copy link
Contributor

eamodio commented Sep 25, 2017

@sandy081 Any way to get this bumped up -- the GitLens view is just BEGGING to be on the SCM activity. Or is there some guidance on what would need to be done here if a PR would be accepted?

@sandy081
Copy link
Member Author

I would request @joaomoreno to reply since he owns SCM viewlet.

@joaomoreno
Copy link
Member

I'm not entirely convinced that this is the way to go... I would like to keep the SCM viewlet clean, though I do see that a Gitlens view is wrong in the File Explorer.

@ADTC
Copy link

ADTC commented Nov 27, 2017

I thought I could simply drag an extension's view into any activity I like. That would be ideal since I can fully control what goes where. But if it's something that's not acceptable, I'll settle with allowing developers to plug in their extension views into other activities.

Although, how about giving extensions the ability to add their own activities? That would be totally awesome and the best use of the wasted vertical space on the Activity Bar between the five built-in activities and the settings cog.

PS: Really want to see GitLens and Git History in the SCM activity (or with their own activities) so that my explorer activity focuses on just exploring.

@sandy081
Copy link
Member Author

Closing this as there are no plans to contribute views to SCM viewlet.

@sandy081 sandy081 removed this from the Backlog milestone Feb 14, 2018
@sandy081 sandy081 added the *out-of-scope Posted issue is not in scope of VS Code label Feb 14, 2018
@ADTC
Copy link

ADTC commented Feb 19, 2018

How about allowing extensions to create custom viewlets/activities? #1833

@sandy081
Copy link
Member Author

@ADTC above request is in plan - #43645

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code tree-views Extension tree view issues
Projects
None yet
Development

No branches or pull requests

4 participants