Live data from Hacker News

Introducing the Command Bar

github.com

81–90 of 101 posts

Re: Introducing the Command Bar

#81

Earlier quoted context omitted.

I'd like to counter here that I prefer that sites don't assign vim bindings, or at least allow me to disable them. The reason being that I make extensive use of the vimium Chrome plugin (similar to pentadactyl on Firefox), which maps common vim keys to useful browser shortcuts (j/k to scroll, shift-j/k to switch tabs, f to enable a "type to click links" mode, etc). On 99% of the websites I use, I almost never need to…

I'm not trying to troll, but frankly, I don't understand why people who want to use advanced extensions like Vimium/Pentadactyl opt for Chrome and its crippling extension API. With Pentadactyl, what you describe just isn't a problem: the extension captures the keys and prevents websites from screwing that up, unless you want to access them, in which case you just press C-z to enable 'Pass Through' mode.

I use Chromium over Firefox purely so I can open many tabs without having to scroll the tab bar. I use extensions to bind keys, block content, block scripts, etc. I realise these work better (and some only work) in Firefox. But the scrolling tab bar is a deal breaker.

Re: Introducing the Command Bar

#82

Well, we already have a command bar at the top of the window. What about these commands? http://github.com/username http://github.com/username/follow http://github.com/username/unfollow http://github.com/me/dashboard http://github.com/me/notifications http://github.com/username/reponame/search/term http://github.com/username/reponame/branchname

What is your point? REST is meant to make it easy for machines to talk to each other.

My point is that the address field of my browser is already a "command bar" and that the URI is already a command line.

With a carefully chosen URI scheme, 100% RESTful or not, you have your command bar.

Re: Introducing the Command Bar

#84

Earlier quoted context omitted.

What is your point? REST is meant to make it easy for machines to talk to each other.

My point is that the address field of my browser is already a "command bar" and that the URI is already a command line. With a carefully chosen URI scheme, 100% RESTful or not, you have your command bar.

Personally I don't relish the thought of memorizing the REST API of every website I visit. Anyways, it's not like they did away with the URI scheme you are describing...

Re: Introducing the Command Bar

#85
post #5

Earlier quoted context omitted.

hitting 's' anywhere on the page activates the command bar. I will use this a lot.

Thanks for the 's' tip. Too bad they didn't also use '/', like gmail and atlassian products.

A downside of using '/' is that it is already used in Firefox to mean search-in-page.

Re: Introducing the Command Bar

#88

Earlier quoted context omitted.

My point is that the address field of my browser is already a "command bar" and that the URI is already a command line. With a carefully chosen URI scheme, 100% RESTful or not, you have your command bar.

Personally I don't relish the thought of memorizing the REST API of every website I visit. Anyways, it's not like they did away with the URI scheme you are describing...

Agreed.

Re: Introducing the Command Bar

#89
post #2

Playing with this for a few minutes: * I wish it had vim keybindings (ie, hit esc, then use hjkl to navigate) * It gives me the option to follow myself. (Bug?) * I like how I can learn commands via the autocomplete bar (issue, branch, graph, etc) * I like how the autocomplete bar refreshes after I have control-tabbed away and back. Too many autocompletes lose this behavior * Searching in a repository username/repo do…

I hate sites that have vim bindings as i already uses vimium for chrome. Im looking at you fffound and vimeo!
Post reply on HN