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

Explore variations for File > New file and File > New file... #145046

Closed
lychung7 opened this issue Mar 14, 2022 · 5 comments
Closed

Explore variations for File > New file and File > New file... #145046

lychung7 opened this issue Mar 14, 2022 · 5 comments
Assignees
Labels
ux User experience issues
Milestone

Comments

@lychung7
Copy link
Contributor

This is the current experience in the File menu for creating a new file and we want to explore different variations to improve the UX.

Screen Shot 2022-03-14 at 7 52 05 AM

@lychung7 lychung7 self-assigned this Mar 14, 2022
@miguelsolorio miguelsolorio added this to the March 2022 milestone Mar 14, 2022
@miguelsolorio miguelsolorio added the ux User experience issues label Mar 14, 2022
@lychung7
Copy link
Contributor Author

lychung7 commented Mar 16, 2022

As a duplicate of New File and New File... in the File menu can be confusing, here are a couple of ideas to distinguish between the two.

Screen Shot 2022-03-15 at 3 13 25 PM

The first idea on the left is using New Text File and New Editor.... There was previous feedback around introducing the term Editor to the File menu and I thought this could distinguish between immediately opening up a file vs. opening up a quick pick of editor options like below. The second idea was to call the two menu items New Untitled File and New File....

new editor  quick pick

Also, to help users not have to switch editors, there is another idea of adding a second entry point in the placeholder text of an empty text file. Clicking on choose a rich editor would open a similar quick pick with editor options.

choose a rich editor link

choose a rich editor link-1

Based on team feedback, instead of choose a rich editor, we could use the phrase select a different editor.

@joaomoreno joaomoreno added the feature-request Request for new features or functionality label Mar 25, 2022
@rzhao271 rzhao271 modified the milestones: March 2022, April 2022 Mar 25, 2022
@Zerotask
Copy link

It would be great if VS Code could offer the creation of specific files.
For example I have a PHP project, then a new file is mostly a PHP class which consists of specific content. This menu could then additionally offer me the option New PHP class. If I enter User, it would create:

<?php

class User {

}

@AlbertoFabbri93
Copy link

In my opinion option B is more clear.

@Sukrit303
Copy link

B is more clear.

@rzhao271 rzhao271 modified the milestones: June 2022, July 2022 Jul 5, 2022
@miguelsolorio
Copy link
Contributor

miguelsolorio commented Jul 25, 2022

Closing this as complete, refs #153860

CleanShot 2022-07-25 at 09 03 29@2x

CleanShot 2022-07-25 at 09 03 39@2x

CleanShot 2022-07-25 at 09 04 05@2x

@miguelsolorio miguelsolorio removed the feature-request Request for new features or functionality label Jul 26, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Sep 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ux User experience issues
Projects
Status: 📋 Backlog
Development

No branches or pull requests

8 participants