Thanks for your help. I actually tried the getURL approach just before reading your answer and it worked. Thanks ;)
Regarding the collapse/expand o toolstrip&moles defined in the manifest, yes, maybe by just calling expand/collapse with no url should work with what's defined in the manifest. Thanks again for your help. On Sep 9, 4:38 pm, Erik Kay <[email protected]> wrote: > On Wed, Sep 9, 2009 at 1:39 PM, Markitusss<[email protected]> wrote: > > > Hi all, > > > Question about moles: > > > How can I specify a local url when expanding, collapsing a toolstrip? > > I can pass {url : "http://www.google.com"} and it sows correctly, but > > tried several ways of passing a local html with no luck. How is it > > done? > > This is a bug that came up in another thread. I > filedhttp://crbug.com/21424about it. The bug is that we're not handling > relative URLs correctly. To work around this, use > chrome.extension.getURL() to construct an > URL:http://code.google.com/chrome/extensions/extension.html#method-getURL > > > Also, is there a way of defining the collapsed/expanded html in the > > manifest, and control them programatically via chrome.toolstrip.expand/ > > collapse ? > > Not at the moment. How would you expect this to work? Just expand > with no url argument specified? > > Erik > > > > > > > Thanks for your help, > > > Marcos > > > On Aug 4, 11:34 am, Gavin <[email protected]> wrote: > >> If I could have a transparent overlay that I could control as if it > >> were an element in the content area, I'd be very pleased. I was > >> messing around doing this with my content script, but it's a pain to > >> make sure it's always the topmost element in the z-order, and on top > >> of flash elements, etc. > > >> I'm perfectly fine with themolebeing a place to put config-ish UI, > >> but treating the entire browser window as a surface that can be > >> overlain with other widgets. For example, a developer tools palette, > >> post-it notes, etc. > > >> On Aug 3, 9:21 pm, Erik Kay <[email protected]> wrote: > > >> > On Mon, Aug 3, 2009 at 6:31 PM, Gavin<[email protected]> wrote: > >> > > Great, got this working. Naturally I want features -- just tell me if > >> > > any of them are done/imminent and I won't try to make patches for you. > > >> > Of course. This is only a first rev. Expect more to be arriving > >> > shortly. > > >> > > 1) Regular CSS control over themolewindow itself. I'd like to make > >> > > the UI translucent, for example, so I loose less page context. I'd > >> > > also like to set stuff like overflow:hidden, corner radius, etc. > > >> > For themolewindow itself, I don't think we'll get to things that > >> > require transparency in the near future. There are some tradeoffs > >> > with transparent windows and live HTML rendering that are non-trivial. > > >> > > 2) Fancy CSS control over showing themole, with animation > >> > > transitions, etc. In other words, specify that themoleappears via > >> > > changing its opacity from 0 to something, or it's left margin, or its > >> > > top margin, etc. > > >> > You can expect some animation to happen when themoleexpands and > >> > contracts. Two things will change about the page when this happens: > >> > the height and the class of the body (the second isn't implemented > >> > yet). Given this, you should be able to do some additional CSS > >> > animations on the content of the page in some cases. > > >> > > 3) Be able to set height as a percentage (100% for a toolbar for my > >> > > extension), > > >> > As a percentage of what? The the content area? > > >> > > and anchor themoleany way I want with regular top/left/ > >> > > bottom/right properties (including all four at 0 if I want a "full- > >> > > frame overlay" thing. > > >> > Are you talking about anchoring to different parts of the window frame > >> > (like a sidebar)? If so, I expect we'll have more specific support > >> > for that, similarly for overlays. > > >> > Thanks for taking it for a spin. I appreciate the feedback. > > >> > Erik > > >> > > On Jul 31, 8:36 am, Erik Kay <[email protected]> wrote: > >> > >> This is still a work in progress (it will be in a more useful state > >> > >> next update). Sorry I haven't updated the docs. Here's a quick > >> > >> sample manifest change: > > >> > >> "toolstrips": [ > >> > >> { > >> > >> "path": "toolstrip1.html", > >> > >> "mole": "lorem_ipsum.html", > >> > >> "mole_height": 200 > >> > >> } > >> > >> ] > > >> > >> You can open and close by hovering over the toolstrip and clicking on > >> > >> the toolstrip handle that appears (yes, UI is not final here either). > > >> > >> I'll update the docs and get a better example up over the weekend. > > >> > >> Erik > > >> > >> On Fri, Jul 31, 2009 at 6:00 AM, Julian Harris<[email protected]> wrote: > >> > >> > +1 > >> > >> > On Fri, Jul 31, 2009 at 1:53 PM, sebastian.zim > >> > >> > <[email protected]> wrote: > > >> > >> >> I was wondering this too. I got no help from the extensions > >> > >> >> HOWTO... > > >> > >> >> On Jul 31, 10:07 am, "Daniele S." <[email protected]> wrote: > >> > >> >> > In the last release I read: > > >> > >> >> > * Introduce moles! These are a new extra area that can pop up > >> > >> >> > above > >> > >> >> > toolstrips. > > >> > >> >> > How can I use them? Is there some sample code? > > >> > >> >> > Daniele S. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
