On Mon, Jul 13, 2009 at 1:46 PM, Evan Martin<[email protected]> wrote: > On Mon, Jul 13, 2009 at 1:44 PM, Aaron Boodman<[email protected]> wrote: >> Increased awesomeness, shorter, more descriptive method names. Also it >> seems like having a utility function lying around that can decode a >> user-supplied image would be really useful for a variety of >> applications in the future. > > Unless people are forced to use this function (perhaps by not > providing an alternative) it seems unlikely extension developers will > use it.
I think I've confused you. Sorry, I should have been more detailed. Right now developers must specify a list of all icons their page action will use ahead of time, in the manifest. Then, at runtime, they specify which icon to switch to. The doc is here: http://dev.chromium.org/developers/design-documents/extensions/page-actions-api The reason the API is like this is that we must decode these images in a sandboxed process, and we currently do all the work at install time. So we need to know the list of images to decode at install time. What I'm proposing is generalizing the sandboxed process we use to do this decoding, so that it can be used at anytime -- not just at install time. Callers, including the page actions UI could say "get me image foo/bar/gaz.gif from extension xyz" and not care whether this entails a sandboxed decoding or not. We could then get rid of the pre-specified list of images for the page actions API, and it seems like we'd probably want to do similar sorts of things in the future with other extensions UI, so this capability may be reused. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
