You may also, also be interested in the options_page key: http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/options.html (pointing you to the trunk docs because the dev ones haven't been updated yet)
This is a special page that you declare in the manifest. If you do, Chrome will add UI to the management page for users to access your extension's options. You can also have your own UI elsewhere to open this UI if you want. - a On Thu, Oct 29, 2009 at 9:41 PM, Wesley Johnson <[email protected]> wrote: > > Great, thanks for the reference - that will come in handy. > > On Oct 30, 12:32 am, Antony Sargent <[email protected]> wrote: >> No need to declare it. >> >> You may also be interested in the chrome.extension.getURL method to get a >> url for use in chrome.tabs.create or window.open. >> >> http://code.google.com/chrome/extensions/extension.html#method-getURL >> >> On Thu, Oct 29, 2009 at 8:49 PM, Wesley Johnson >> <[email protected]>wrote: >> >> >> >> >> >> > Hi Nick, >> >> > Thanks for the quick reply! That should work for what I need and I'm >> > pleased to here it is possible using an additional page. Does the >> > package dictate that I declare this extra page in the manifest or can >> > it just reside in the directory like images, etc? Thanks again. >> >> > -Wesley >> >> > On Oct 29, 11:40 pm, Nick Baum <[email protected]> wrote: >> > > Hi Wesley, >> >> > > It's not possible to load the existing instance of the background page in >> > a >> > > tab, so the solution is to create a new html page, as you suggested. Note >> > > that this will be able to communicate directly with the background page, >> > and >> > > use the extension APIs, so hopefully it won't be too much of a hassle. >> >> > > -Nick >> >> > > On Thu, Oct 29, 2009 at 7:30 PM, Wesley Johnson >> > > <[email protected]>wrote: >> >> > > > I'm authoring an extension that requires centralized UI for various >> > > > aspects and features. My initial thought is to put it into the >> > > > background page. It's easy enough to call up a tab and set the URL to >> > > > the background html page of your extension. The issue in doing that is >> > > > that it appears to create a new instance of a background page and >> > > > loads that.... >> >> > > > Can I view the actual background page the extension is linked to/ >> > > > communicating with? I know you can use chrome.extension.getViews() to >> > > > loop through views for your extension and find the background view, >> > > > but how to I send that "view" to a tab, so I can see it? If this is >> > > > not possible, which I could understand it might not be since it is, by >> > > > design, a BACKGROUND page - then what are my alternatives for >> > > > rendering additional UI? >> >> > > > Should I just create a new html page and package it up with my >> > > > extension and then just load that into a new tab? It would require >> > > > more work getting my background page to communicate with yet ANOTHER >> > > > view, but it could work. >> >> > > > Thoughts? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
