I think it may be a good idea to allow specifying more than one type of gleam in the manifest in the same "gleam" block. Currently, if you're interested in images and links, you have to specify two gleam blocks (that's how I understand this), one with type "image", and one with type "link", with remaining things repeated.
On Thu, Jun 4, 2009 at 05:38, Aaron Boodman <a...@chromium.org> wrote: > > I think the UI should be a single icon initially to conserve space, > but when the user selects the icon, the extension could choose to > display a floating toolstrip (we have some ideas about the > implementation of those too but I haven't written them down yet). > > - a > > On Wed, Jun 3, 2009 at 1:58 PM, Andrew Charlton <adcharl...@gmail.com> wrote: >> >> Could a gleam maybe be a popup toolstrip rather than a single icon - I >> think that would open up lots of possibilities. You could have >> something like chrome.gleam.getSelected to return the selection. >> >> On Jun 4, 8:00 am, Aaron Boodman <a...@chromium.org> wrote: >>> [I actually created this awhile ago, but never sent it 'round] >>> >>> It is really common for extensions to want to offer additional >>> contextual options for content elements. For example "Download this >>> movie", "edit this image", "call this phone number", etc. >>> >>> You can use content scripts for this, but since it is such a common >>> task, I think it deserves its own proper API. This would allow this >>> class of extensions to interact well with pages, with each other, and >>> have a nice consistent UI. >>> >>> Anyway, here's an API proposal for such a thing: >>> >>> http://dev.chromium.org/developers/design-documents/extensions/gleam-api >>> >>> Comments wanted! >>> >>> - a >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
