|Keyboard usage with AwesomeBar HD||Edward Lee||4/29/11 11:27 AM|
|Re: Keyboard usage with AwesomeBar HD||das...@mozilla.com||4/29/11 11:39 AM|
On Fri Apr 29 11:27:16 2011, Edward Lee wrote:
Ya know, once the UI stabilizes, this is something that we could show
|Re: Keyboard usage with AwesomeBar HD||Boris Prpic||4/29/11 1:33 PM|
I see this addon as a great way to move search beyond Google. I think that there are a lot very useful vertical search engines out there and that this addon if integreated in Firefox could really popularize them.
You can add a big list of engines to Firefox and make a algorithm to suggest relevant ones based on user's keywords, location, past searches and other data..
|Re: Keyboard usage with AwesomeBar HD||Sriram Ramani||4/30/11 2:41 AM|
I really like this concept. The search bar has a lot of search engines. And new engines can be added easily in Firefox. This addon leverages the potential of those search engines my exposing them.
However, I tend to feel the entirely big list as a clutter. When Firefox is moving towards clutter free interface, showing a big list of text is something users wouldn't like (as per HCI principles).
How about showing the different search engines in the awesome bar suggestions? https://addons.mozilla.org/en-US/mobile/addon/near-me-271823/ - shows an example of the same.
In that addon's case, there were just 3 options. In case of Firefox's list of search engines, it is many. This can be supported in a different manner.
When an user types "m", the first suggestion in Awesome Bar can be "search for Movies in IMDB". User can click on this, and this will be loaded into the URL bar like the way "AwesomeBar HD" supports [ i.e.: "movies: " ]. Now the user can enter his search term and search for the same.
Also, changing of the search engines is a nice feature of this addon. This can be mapped to the above idea easily. Just like "Switch to tab : " option that is currently supported, on user's select as mentioned above, the URL bar can show "Search for movie in IMDB : ". This IMDB will be like the newly proposed "Search engine indicator" with a drop button [http://areweprettyyet.com/5/searchBar/#]. Users can click on it to change the Default search engine.
[ P.S.: For want of space, the "Search for" can be represented with a search icon in the place of favicon, as the users know that this is a search option ].
I couldn't come up with mockups to explain my idea more clearly. I'll try to come up with some next week.
|回覆：Keyboard usage with AwesomeBar HD||Robert Roth||5/5/11 7:37 PM|
I do all my locationbar selecting/editing by keyboard, but I cannot see my cursor, so I have to guess where I am before typing.
(this is on Aurora branch).
As a side note, this doesn't allow the ctrl-click on URL segments for LocationBar2
|Re: Keyboard usage with AwesomeBar HD||Kai Lim||5/6/11 3:10 AM|
I'm loving the concept of essentially making the awesomebar a sort of google without google. Im also quite glad that the search function jumped up in speed.
Probably one of the things im really interested in is what happens if the awesomebar were to bypass the homepage all together?
By this i mean, say we wanted to find something on youtube. We first go on youtube.com, then type in whatever we want in the searchbar. What if the awesomebar were to become this searchbar while
simultaneously bypassing the homepage and going straight to the results? We could type in the awesomebar "youtube:" to instantly search for videos rather than go through sub menus in the current version. This concept could be applied
to searching through other websites as well, not just youtube.
Would it be possible to get this done?
|Re: Keyboard usage with AwesomeBar HD||Edward Lee||5/6/11 5:00 PM|
On Fri, May 6, 2011 at 3:10 AM, Kai Lim <samur...@gmail.com> wrote:Are you asking for something different than what currently happens
when you type "videos: mozilla"? In fact you can just copy/paste this
into your location bar: "v:mozilla".
|Re: 回覆：Keyboard usage with AwesomeBar HD||Edward Lee||5/6/11 5:01 PM|
On Thu, May 5, 2011 at 7:37 PM, Robert Roth <noma...@gmail.com> wrote:Does this happen when you're trying to move the cursor with the
keyboard by pressing left/right? Could you try with v6 as it changes
how the textbox in the location bar works especially when the url is
|Re: Keyboard usage with AwesomeBar HD||Kai Lim||5/7/11 5:09 AM|
yes, but rather than configuring the sub menu. I think it makes it more intuitive than typing in "videos:"
|Vs: Keyboard usage with AwesomeBar HD||Leho Kraav||5/8/11 3:28 AM|
i am stumped. on Linux, FF4.0, i cannot copy URL from A-HD. pressing CTRL+L or clicking the URL with mouse immediately clears the location. this does not seem to behave at all as written in the blog.
|Re: Vs: Keyboard usage with AwesomeBar HD||Edward Lee||5/9/11 5:15 PM|
On Sun, May 8, 2011 at 3:28 AM, Leho Kraav <le...@kraav.com> wrote:Were you trying to right-click to copy the url? That should be fixed
with issue 277:
v9 should also fix issues with the tab panel trying to open and
|Re: Vs: Keyboard usage with AwesomeBar HD||HbbS||5/9/11 6:28 PM|
The situation is getting worse.
On the nightly build of today, Awesome Bar HD 7 totally disabled the CTRL+L shortcut.
I cannot copy, paste or input on it.
|Re: 回覆：Keyboard usage with AwesomeBar HD||Robert Roth||5/9/11 6:51 PM|
The v6 update never showed up for me, but now I have v7.
|Re: Vs: Keyboard usage with AwesomeBar HD||Edward Lee||5/9/11 8:14 PM|
On Mon, May 9, 2011 at 6:28 PM, HbbS <hebert....@gmail.com> wrote:Can you try forcing an update to 8 by downloading it here?
|Re: Vs: Keyboard usage with AwesomeBar HD||HbbS||5/9/11 9:30 PM|
|Re: Vs: Keyboard usage with AwesomeBar HD||Edward Lee||5/9/11 9:59 PM|
On Mon, May 9, 2011 at 9:30 PM, HbbS <hebert....@gmail.com> wrote:Gah! Sorry about that. I assumed that was an artifact of the test
machine I used to track down the original problem.
You'll need to restart Firefox if you've installed v8 though.
|Vs: Re: Vs: Keyboard usage with AwesomeBar HD||Leho Kraav||5/10/11 6:17 AM|
teisipäev, 10. mai 2011 7:59.53 UTC+3 kirjutas Edward Lee:Gah! Sorry about that. I assumed that was an artifact of the test
Problem is fixed on Linux, I appreciate it!