On Mon, Feb 22, 2010 at 12:02 AM, Aaron Boodman <a...@google.com> wrote:
> * It would be neat if the keyword ("gtalk" in your example) were
> derived automatically from the extension name, and if the omnibox were
> clever about matching. So if you have an extension named "Google
> Talk", typing "gt" or "gtalk" or "googletalk" would all match. This
> also elegantly handles the issue of conflicts.

> * It would be cool if the extension could interact with the omnibox
> session, rather than just accepting all the input. The way I imagine
> this working is that if you type "gtalk", you get all the usual
> suggestions, from your history, bookmarks, etc, along with an
> additional suggestion for the "Google Talk" extension you have
> installed which declares it interacts with the omnibox:

> [☆| gt ]
> -----------------------------------------------------
> [ icon | http://www.google.com/talk ]
> [ icon | gtalk ]
> [ icon | Google Talk ]
> ...

> If you select the "Google Talk" entry and press "Tab", you enter a new
> mode where you've accepted that you're only dealing with the
> extension. At this point, the extension could expose additional
> information to help the user enter the query. For example, it could
> expose how many arguments it wants, or help with autocompleting, or
> whatever. So, for the gtalk extension, maybe it takes one argument
> which is the person to talk to. The omnibox might change to:

> [ icon | Google Talk: <contact name> ]
> -----------------------------------------------------
> [ icon | Google Talk: b...@gmail.com ]
> [ icon | Google Talk: na...@gmail.com ]
> [ icon | Google Talk: s...@gmail.com ]
> ...

> And of course as you type, the system could keep sending the current
> query to the extension, which could refine the suggestions.