Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home for chromium.org
« Groups Home
Message from discussion Proposal: extension API: activating extensions through Omnibox
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Antony Sargent  
View profile  
 More options Feb 22 2010, 2:06 pm
From: Antony Sargent <asarg...@chromium.org>
Date: Mon, 22 Feb 2010 11:06:27 -0800
Local: Mon, Feb 22 2010 2:06 pm
Subject: Re: [chromium-dev] Proposal: extension API: activating extensions through Omnibox

If you're interested in getting a few easier patches in to learn some of the
process and codebase (and extensions system in particular), you can search
for "feature:extensions helpwanted" at crbug.com, or just follow this link:

http://code.google.com/p/chromium/issues/list?q=feature:extensions+he...

On Mon, Feb 22, 2010 at 12:02 AM, Aaron Boodman <a...@google.com> wrote:
> Hi Zoran,

> We've definitely thought along these lines before, and I personally
> think something like this would be a really great addition to the
> extension system.

> A few thoughts I've had on this idea:

> * 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.

> ===

> As for how to get started, the best thing to do is to fix some smaller
> bugs first to get the hang of working on Chromium. You'll have to work
> up to bigger features over time. If you're interested, there's more
> information on how to get started here:

> http://dev.chromium.org/developers

> - a

> On Sun, Feb 21, 2010 at 10:26 PM, Zoran Rilak <zoran.ri...@gmail.com>
> wrote:
> > Hi devs,

> > this is a proposal for a new extension API to would allow invoking
> > extensions by entering text in the Omnibar.  In brief:

> >  [☆| gtalk dilbert                ]    // user enters "gtalk dilbert"
> > in the omni-bar and hits Enter

> >  // behind the scenes, ExtensionsService is queried for one that has
> > registered "gtalk" as its trigger keyword.
> >  // The extension is then sent the contents of Omnibox, which it uses
> > to do its thing, for example:

> > +---------------+    // extension opens Gmail, pops ups a chat with
> > Dilbert
> > |Gmail          |    // and focuses the textarea.
> > |   ..........  |
> > |   ..........  |
> > |       +-------+
> > |       |Dilbert|
> > |       |       |
> > |       |       |
> > |       |[#    ]|
> > +-------+-------+

> >  This would allow extensions to register interest in processing user
> > input from the Omnibox.  The basic premise is simple enough; I for one
> > love the Omnibar and off the top of my head I can think of half a
> > dozen different ways to put it to even heavier use through extensions
> > (see [1] for a couple more use cases), but I suspect it would be a
> > fairly major feature to consider adding.  I'm willing to dig down into
> > the code base and start implementing it but I'd really appreciate a
> > few pointers first.  Should this idea be pursued?  Does it have a
> > future in Chromium?

> > ---
> > [1]
> http://groups.google.com/a/chromium.org/group/chromium-discuss/browse...
> >     More thoughts on this and a few use cases written in a case of a
> > severe sleep deprivation; caveat emptor.

> > --
> > Chromium Developers mailing list: chromium-...@chromium.org
> > View archives, change email options, or unsubscribe:
> >    http://groups.google.com/a/chromium.org/group/chromium-dev

> --
> Chromium Developers mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
>    http://groups.google.com/a/chromium.org/group/chromium-dev


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.