We are working on adding larger spaces that extensions can put UI on. The first one is called "moles". It isn't exactly the same as the bottom bar that Firebug uses, but we're excited about it and think it will add some cool possibilities.
If you're interested in seeing the **very early and hardly working** API and code, the docs are here: http://chromeextensionsdocs.appspot.com/toolstrip.html#method-expand But note that moles are just barely getting started so all this will change a lot. - a On Tue, Sep 1, 2009 at 11:07 AM, DonShmon<[email protected]> wrote: > > I have the same question. bump. > > On Aug 26, 5:44 pm, Michael Weber <[email protected]> > wrote: >> I've looked through the documentation, built a simple extension, and >> run all the samples in the Chromium source tree, and it appears that >> the only wait to create a large UI for a Chrome extension is to open a >> new window (larger than toolstrip). >> >> Is there a way (or a plan for a way) to add an extension-defined >> horizontal or vertical pane to an existing window to host the >> extension contents? For example, the way Firebug uses a resizeable >> panel in Firefox? >> >> I'm thinking of a panel that, like a toolstrip, hosts its own html >> page / fragment, as opposed to modifying the loaded page's DOM. >> >> I understand that the design guideline is to us as little space as >> possible, but some extensions need significant space on the same page >> with which they are associated. >> >> cheers >> Michael > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
