Nathan, The point is that you use the Canvas API to *draw* the image on the fly. You aren't creating an image for every possible time :)
Cheers, Dion On Thu, Oct 15, 2009 at 7:10 AM, Nathan J. Brauer <m...@nathanbrauer.com>wrote: > > Dion: I hope you were kidding (no offense if you weren't) haha > Aaron: The way that the BrowserActions is setup, the developer of the > analog clock would have to have a different image for every single > possible time so it'd be quite bloated. > > I completely agree with Jack (except for "I am standing out of > it" ...technically you're not standing out of it if you're sharing > your opinion, but I get what you mean, kinda). > > > On Oct 15, 6:04 am, Aaron Boodman <a...@chromium.org> wrote: > > I feel like you could create a pretty sweet analog clock in that > > space. More information could be accessed via the bubble. > > > > - a > > > > > > > > On Wed, Oct 14, 2009 at 4:01 PM, Dion Almaer <d...@almaer.com> wrote: > > > You could create a date and time in tiny font and fillText it to a > canvas > > > that is the browser action image? :/ > > > > > On Wed, Oct 14, 2009 at 9:16 AM, Teo <teomina...@gmail.com> wrote: > > > > >> I also made a Date/Time extension and am currently a bit confused > > >> about the recommended way to just show info... At least if we could > > >> also render HTML in the buttons, not just images... > > > > >> On Oct 14, 6:22 pm, NathanBdot <m...@nathanbrauer.com> wrote: > > >> > This is very disappointing. I think it would be a better solution > to > > >> > make the toolstrips always on the top (--show-extensions-on-top) as > > >> > the default (like here:http://bit.ly/5nZFm). This provided an > > >> > excellent UI that fit well with the current setup and had all the > > >> > functionality of the toolstrips. I believe Browser Actions are > great > > >> > tools as well, but each serve different purposes. Take the Time > > >> > extension (see the same link) as a simple example. There is simply > no > > >> > way to replicate that with a BrowserAction. > > > > >> > On Oct 14, 12:51 am, Aaron Boodman <a...@chromium.org> wrote: > > > > >> > > Not on the mac yet :(. Windows has it, linux will have it soon. > We'll > > >> > > update here or on the release blog when there is news. > > > > >> > > - a > > > > >> > > On Tue, Oct 13, 2009 at 10:46 AM, Edwin Khodabakchian > > > > >> > > <edwin.khodabakch...@gmail.com> wrote: > > > > >> > > > I think that this is a good design decision. Is there a mac > build > > >> > > > which already has support for the browser action so that we can > > >> > > > start > > >> > > > to port our extensive? > > >> > > > Thanks, > > >> > > > Edwin > > > > >> > > > On Oct 12, 2:41 pm, Aaron Boodman <a...@chromium.org> wrote: > > >> > > >> Hello all, > > > > >> > > >> As a few of you have noticed from changes in the bug system, > we've > > >> > > >> decided > > >> > > >> to replace toolstrips with a new extensions UI surface area: > > >> > > >> browser > > >> > > >> actions<http://code.google.com/p/chromium/wiki/BrowserActions> > > >> > > >> . > > >> > > >> Here is what they look like: > > > > >> > > >> [image: browser_action.png] > > > > >> > > >> A browser action is a 19px image button that shows up in the > main > > >> > > >> Chrome > > >> > > >> toolbar to the right of the omnibox. They can be rendered from > a > > >> > > >> static set > > >> > > >> of images in your extension, or you can render them dynamically > > >> > > >> using the > > >> > > >> HTML5 canvas. > > > > >> > > >> They can also optionally have a popup, which is implemented > using > > >> > > >> HTML, > > >> > > >> similar to how toolstrips worked. > > > > >> > > >> We will be disabling toolstrips before the beta release of > Chrome > > >> > > >> 4, so we > > >> > > >> encourage extension developers to start converting their > extensions > > >> > > >> to use > > >> > > >> browser actions soon. We'll be updating the docs in the coming > > >> > > >> weeks with > > >> > > >> details. > > >> > > >> Even though we are still in the dev channel of Chrome, where > > >> > > >> everything is > > >> > > >> subject to change, we try to avoid ever breaking APIs. So we > didn't > > >> > > >> come to > > >> > > >> this decision lightly. The reason we did it that we got a lot > of > > >> > > >> negative > > >> > > >> feedback about the toolstrip shelf across the bottom of the > > >> > > >> browser. Many > > >> > > >> users did not like the wasted space, particularly when only one > > >> > > >> extension > > >> > > >> was installed. > > > > >> > > >> When we stepped back and thought about the use cases, we came > to > > >> > > >> the > > >> > > >> conclusion that most extensions don't really need to show > complex > > >> > > >> UI in the > > >> > > >> toolbar -- a single button with an expandable area is usually > > >> > > >> sufficient. > > >> > > >> This also had the advantage of being a more prominent location > and > > >> > > >> fitting > > >> > > >> better with Chrome's sparse aesthetic. > > > > >> > > >> While we understand this change is frustrating and won't work > > >> > > >> perfectly for > > >> > > >> every extension, we think it is for the best, and are excited > to > > >> > > >> see what > > >> > > >> you can do with it. > > > > >> > > >> If you want to get started even before we finish the docs, you > can > > >> > > >> take a > > >> > > >> look at our samples, which have already been converted: > > > > >> > > >> - > > > > >> > > >> > http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/exte... > > >> > > >> - > > > > >> > > >> > http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/exte... > > >> > > >> - > > > > >> > > >> > http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/exte... > > >> > > >> - > > > > >> > > >> > http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/exte... > > >> > > >> - > > > > >> > > >> > http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/exte... > > > > >> > > >> I'll post on this mailing list as the browser action API > solidifies > > >> > > >> and the > > >> > > >> documentation is completed. > > > > >> > > >> - a > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensions@googlegroups.com To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
