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

Revisit that preview editors show up under "Opened Editors" #6812

Closed
bpasero opened this issue May 24, 2016 · 5 comments
Closed

Revisit that preview editors show up under "Opened Editors" #6812

bpasero opened this issue May 24, 2016 · 5 comments
Assignees
Labels
ux User experience issues workbench-tabs VS Code editor tab issues
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented May 24, 2016

Some issues:

  • for one it makes it very hard to double click on a file in the explorer to pin it because the first mouse down adds it already and pushes down the view
  • then people are confused that the preview editor is open in one position but when you open another editor the preview editor might move up because that other editor was elsewhere
  • Joao also does not like the italic decoration when you have tabs disabled
  • so one proposal would be: only show italics when tabs are enabled and only show it in the tab itself
    (of course we would have to revisit where else we show the italic, e.g. Ctrl+Tab, Cmd+Alt+Tab)
@bpasero bpasero added ux User experience issues workbench-tabs VS Code editor tab issues labels May 24, 2016
@bpasero bpasero added this to the June 2016 milestone May 24, 2016
@bpasero bpasero self-assigned this May 24, 2016
@bgashler1
Copy link
Contributor

bgashler1 commented May 24, 2016

Why it might be good to remove them:

  • I also haven't been loving the italicized text in Open Editors now that I've been using it. I didn't feel like it was strong enough of an indicator to help me find a preview editor that was buried somewhere in a group (it's like a needle in a haystack--I ). I didn't notice that the preview editor was moving in the group, but after seeing @jrieken's gif, I see why this is confusing.
  • Sublime also does not show preview tabs in their Open Files pane, but they do get their own temporary tab, and personally that makes sense to me for the most part.

Why it might be bad to do so:

  • With tabs disabled, it may be confusing after closing a file that a mysterious preview file that was hiding in the stack shows up instead of the file shown above in working files.
  • It may be less obvious how to pin a "Diff view" or some other kind of special editor, because it does not have something you can double click (perhaps we could allow double clicking the editor's title shown at the top of the group).

Ideas on making it work as is:

I thought about how we might solve this without eliminating preview editors completely from the list.

  1. Use smooth motion transitions (like Chrome and Sublime do with tabs)
  2. Always leave a dedicated space at the end of each group's list in Open Editors so that opening/closing a preview editor will never shift the Explorer files up or down.

Look at this crude prototype that demonstrates how smooth motion transitions might make it more clear what's going on in the stack.

previeweditorsinopeneditors_5_24_2016

Thoughts?

@bpasero
Copy link
Member Author

bpasero commented May 25, 2016

@bgashler1 interesting idea, if I understood you correctly, we would keep an empty slot for each possible preview editor. It would look like this:

editors

While it fixes the issue with annoying double click behaviour, it almost looks like a UI bug that we would grow the "Opened Editors" view with an empty element inside.

Let's discuss this in the next planning meeting :)

@joaomoreno
Copy link
Member

Interesting... but doesn't it look ugly?

@bpasero
Copy link
Member Author

bpasero commented May 25, 2016

Summary from the UX meeting regarding the concerns:

That way we think having preview tab in "opened editors" is really not a bad thing to have.

@bpasero bpasero closed this as completed May 25, 2016
@bgashler1
Copy link
Contributor

@bpasero and @joaomoreno yes, the blank space sounded good in my head until I saw it. Definitely not pretty.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ux User experience issues workbench-tabs VS Code editor tab issues
Projects
None yet
Development

No branches or pull requests

3 participants