-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
Improve first run experience #98614
Comments
Outline is not a Breadcrumbs alternative. Those are two highly important distinctive features. It's shouldn't be anywhere hidden by default. #49923 shows how many users not just need Outline on screen, but also completely dedicated, so always on screen and maximized as possible. So instead of 3 it's better to revert #93764. It has poor usability. 1 is also has huge popularity and very important. |
Also assignign to myself since I will have time this and next week to look into this.
Ideas from @misolori and me which we discussed on Slack:
|
Here are two ideas for how to improve the discoverability. Global view menuThis would add an ellipsis icon to all global viewlets and surface the view menu. This is the same menu you get when you right-click in the sidebar. This means that we would need to account for when a viewlet only has a single view and the view actions are collapsed with the title: And when a viewlet already has a context menu: Clickable titleThis would make the title on all views clickable and surface the same menu. |
@misolori great work, love it. Especialy the first since it makes it very discoverable. The only nit pick, when a viewlet already has a context menu: I would do it So do not put the Extension actions in a submenu. But the Views should still be the first entry. fyi @sbatten @sandy081 @bpasero even though I think this will be discussed in today's UX call. |
I like moving them to |
@isidorn got it, so then the context menu would look like this: |
Feedback from our ux sync:
|
Great feedback, all makes sense. |
So I don't think we're going to find a good icon for "views" since that is a pretty hard concept to show and we already have similar icons that represent view: I still think we should stick with using the ellipsis since we also use this for both overflow and showing actions (view context menus and editor ellipsis). Here's how I think we can use the pattern in both:
|
@misolori I like this suggestion a lot for the panel. |
For the first run experience I think a good first steps for this milestone are the following:
We'll see how these changes are accepted by the community and then next milestone we can
Let me know if this makes sense to you @misolori |
This comment has been minimized.
This comment has been minimized.
So for this milestone we only need to move the npm script to an extension. |
I see that we have created an issue for moving the npm scripts view out to an extension.
|
I see we have hidden the npm scripts view by default which is great. As for the panel, we could render |
Helps first-run experience, see here: #98614 (comment)
@isidorn I made the changes to hide the Timeline view when there are no (excluded) registered providers -- this should help the first-run experience at least when the Timeline view wouldn't be useful. |
This issue to explore how we might improve the (default) first run experience from the file explorer (and other areas).
Current Experience
Desktop
Today, when you install VS Code for the first time and open a file you are greeted with a series of views in the explorer:
Proposal
We can consolidate some of the features that have overlap in other areas:
Open Editors
in favor of Editor TabsOutline
in favor of Breadcrumbs +Go To Symbols in Editor
NPM Scripts
in favor of adding an actionin the editor toolbarvia codelenses in thepackage.json
file to surface itOther Ideas
In addition to this proposal, we also discussed the following options that would require more engineering effort:
git
related featuresGo To Symbols in Editor
quick pick that toggles the outline viewThe text was updated successfully, but these errors were encountered: