Now I just need an Alfred extension that talks to the backend URLs
Introducing the Command Bar
91–100 of 101 posts
Re: Introducing the Command Bar
#92Earlier quoted context omitted.
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.
Tab Mix Plus, an addon for Firefox allows multi line tab lists and is very customizable.I have been using it for years.
Re: Introducing the Command Bar
#93Great feature - I really like it. My only request is that the suggestions be clickable links so that you can open one in a new tab.
Re: Introducing the Command Bar
#94Earlier quoted context omitted.
Keyboard is at least 100x as productive as mouse (assuming you know what to do and what to type). Even the best peachy UIs cannot change it. Still there are things that aren't convenient to do from CLI like photo retouching, but these are quite obvious exceptions. That said, I'm not sure what would you like to do in such terminal?
I'd like to search for repos, create new repos, create initial files, edit existing, star/unstar, watch/ignore, work with messages etc.
My question was in fact about features that this command bar does not provide. Part of the ones you mentioned was already available before (like file editing), but simply not in a CLI-related manner. Some of these they could surely add, i.e. whatever can be put in this command bar yet not turning it into terminal.
If you're going to do real job, just do in your real terminal emulator, xterm, rxvt, you name it. What's the point of having GitHub terminal in browser? If you want to do quick'n'dirty fixes/improvements directly from the browser, then it's like asking yourself for troubles, because there is quite higher chance that you'll commit a mistake (even literally speaking) than if you'd be using your own terminal that you work with on a daily basis.
You may want to check a few CLI tools:
Re: Introducing the Command Bar
#95If you want a command line for your own site, you can use the GCLI project (BSD licensed, use it freely!)
https://github.com/mozilla/gcli
This is the command line that's in Firefox 16's Developer Toolbar (final release is coming in early October):
https://hacks.mozilla.org/2012/08/new-firefox-command-line-h...
I love command lines, personally :)
Re: Introducing the Command Bar
#96This paradigm is very powerful. The only thing I see missing from these types of interfaces is the ability to select part or all of the output and use it as input for a new command.
Think of it as an intermediate step of piping where the user has the ability to manually filter content. This UI concept would cover the vast majority of UI needs as almost any workflow could be captured with the following...
1.) Issue command that produces 0..N results. 2.) View results in list format. 3.) Select individual results for details view. 4.) Select 0..N results as input to a subsequent command.
Re: Introducing the Command Bar
#97Wow, a command-line interface to a website is something I never thought I'd see. My first reaction was that it's a step backwards because the usual benefits of a command line aren't present here (you're usually already using your mouse, commands can't be piped, no shell scripts to run things in sequence)... But I'm intigued -- maybe it's a possible step forwards? The implementation is very well done. I suppose maybe…
Gmail has something similar, try to press G L and then start typing to move to a label. Might require something to be activated from labs though.
That is cryptic keypress shortcuts, not quite command lines.
Re: Introducing the Command Bar
#98Playing 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!
The site is called VIMeo.
Re: Introducing the Command Bar
#99Earlier quoted context omitted.
For a site like GitHub, I would imagine this is a huge engineering effort to do right. For instance, in a plain vanilla code search facility, how would you expire results efficiently when the text can change from minute to minute (to seconds, to even less)?
Super efficient search would be great and idea, but slightly delayed searching is perfectly acceptable imo. Especially because I am not necessarily looking for extremely up-to-date changes.
Even slightly-delayed searching would be a huge deal, engineeringwise.
Re: Introducing the Command Bar
#100Earlier quoted context omitted.
Not leaving the keyboard is one big thing. I ditched webkit for Firefox in order to be able to use Pentadactyl, but it's worth it to not have to leave the home row. Learning a few commands is not hard, and there is always the ol' mouse to fall back upon if you don't want to remember all those commands.
With vimium[1] you get most of the keyboard-functionality in Chrome that Pentadactyl offers for Firefox. [1]: http://vimium.github.com/
Vimium is awful compared to pentadactyl.