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

Improve letterpress shortcuts #12716

Closed
joaomoreno opened this issue Sep 27, 2016 · 15 comments
Closed

Improve letterpress shortcuts #12716

joaomoreno opened this issue Sep 27, 2016 · 15 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded

Comments

@joaomoreno
Copy link
Member

joaomoreno commented Sep 27, 2016

First:

  • What does Open File in Folder mean? Why not Quick Open?
  • Why is Move Lines Up/Down in there? As a matter of fact, why are Add Cursors and Open Terminal too? We should just give the user the essential to get started, not random commands that make us look cool.

Finally, a little bit of styling care goes a long way:

image

@joaomoreno joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Sep 27, 2016
@joaomoreno joaomoreno added this to the September 2016 milestone Sep 27, 2016
@chrmarti
Copy link
Collaborator

Is this Windows? (The keybindings display better on OSX, will need to check why.)

Quick Open seems at least as opaque to new users if not more than Open File in Folder. We should still try to think of a better name. The command palette uses Go to File....

We picked the commands by looking at which are used the most, yet not trivial like clipboard actions.

@joaomoreno
Copy link
Member Author

Also on OS X it looks odd as the format is something like: this or that or these. It would look much better if each shortcut is isolated visually instead of grammatically.

Go to File is a good alternative.

@bgashler1
Copy link
Contributor

@joaomoreno you mentioned style; what would you like to see different?

@bgashler1
Copy link
Contributor

bgashler1 commented Sep 27, 2016

For new users, it would be nice to have the most essential commands only. Chances are they are not going to remember about the moving lines up/down right away and stuff. It would be cool if down the road we could progressively introduce more advanced commands that may keep this area fresh and useful.

@joaomoreno
Copy link
Member Author

joaomoreno commented Sep 27, 2016

@bgashler1 Notice the screenshot in the first post.

Something like Ctrl Shift P F1 is so much better than something like Ctrl+Shift+P, F1.

@bgashler1
Copy link
Contributor

bgashler1 commented Sep 27, 2016

@joaomoreno ah, I see. I personally like the kbd tag as well. We had something kind of like that an earlier draft. Not sure what you think...

screen shot 2016-09-27 at 10 08 47 am

But I think some of the team preferred just the text.

Maybe your darker approach would be more appealing to them, though.

On a side note, shouldn't it be Ctrl+Shift+P or F1 instead of each keybinding appearing together in one whole <kbd></kbd> tag?

@joaomoreno
Copy link
Member Author

I really don't think it should. I would save separation for chording.

@chrmarti
Copy link
Collaborator

@joaomoreno
Copy link
Member Author

joaomoreno commented Sep 28, 2016

Please don't keep it as is. At least use a monospace font.

@bgashler1
Copy link
Contributor

bgashler1 commented Sep 28, 2016

@joaomoreno IMO, I don't think the monospaced font looks quite right.
screen shot 2016-09-28 at 4 11 07 pm

Also we are using Segoe UI font in the command palette
screen shot 2016-09-28 at 4 12 37 pm

Which also is partly why we ended up not including the block background behind the keys in the initial implementation of this (even though it was originally designed as such, as shown in above comment).

However, here's what it looks like with the block decorations.
screen shot 2016-09-28 at 4 30 18 pm

You'll notice the decorations had to be darker than the empty workspace (for accessibility reasons we cannot afford any less contrast on the text, or else it's not compliant). This color is actually the same color as the letterpress.


Do we want to go forward with this? @chrisdias, if I remember right, I think you originally wanted just the plain text. @bpasero care to chime in?

If we do want to do this, I would need @chrmarti to put in some logic that puts spans around each keybinding (not the "/"s) and the spans' class could be named say "keybinding-block".

Then the decoration CSS is

.keybinding-block {
    background: #171717;
    padding: 3px;
    border-radius: 2px;
    display: inline-block;
}

And we would adjust the table's border spacing to border-spacing: 13px 13px

@joaomoreno
Copy link
Member Author

Right about monospace! Love your last screenshot!

@chrmarti
Copy link
Collaborator

The contrast between block decorations and keybindings is too low for me to be useful. If we want to add these, I'd suggest to find a way to increase that.

@joaomoreno
Copy link
Member Author

joaomoreno commented Sep 29, 2016

Make sure you try it in all the themes, since each theme has a different background... We're just picking the worst example here.

There are other ways to show contrast, like a border, just like in the following example:

image

@bpasero
Copy link
Member

bpasero commented Sep 29, 2016

Imho the spacing now looks bad on Windows:

image

@chrmarti
Copy link
Collaborator

Fixed the letter-spacing on Windows and Linux. No further action planned for September. Thanks.

@roblourens roblourens added the verified Verification succeeded label Sep 30, 2016
@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
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants