The idea is to nudge extensions in the direction of minimalist UI the same
way chrome itself is minimalist.
In that vein, I'd suggest you try out page actions so see if they suit your
needs. One thing that might help is that we recently landed support for a
popup triggered from a page action, similar to how browser actions have a
popup. The docs still need to be updated to reflect this, but here's an
example:
In your manifest.json
"page_action": {
"default_icon": "icon.png",
"popup": "page_action_popup.html"
}
In a script block in your background page:
// Price comparison completed and we have a result. (Imagine the
// target tabid was hung off the result object.)
chrome.pageAction.show(result.tabid);
In your page_action_popup.html, you could use the messaging API or even the
chrome.extension.getBackgroundPage API to get the right data to display.
On Mon, Nov 9, 2009 at 9:44 AM, Evgeny Shadchnev <evgeny.shadch...@gmail.com
> wrote:
> Thanks for the link. As far as I get from this spec, this is a way of
> notifying the user about 'system-wide' events that are not specific to
> a web-page. In my extension, I compare the prices in the background
> while the user is shopping and show notifications which are seen on
> the page with the product. A notification shown outside the page (that
> would look like Growl to the user, I assume) doesn't really help in
> this case. I'm considering injecting my notification in the DOM of the
> page to emulate infobars but it is a hack, so I'm not too keen on it.
>
> Re: the decision to stick to page actions/browser actions. I can
> understand why you decided to remove toolstrips in favour of
> page/browser actions but this doesn't really explain why it's
> forbidden to use infobars.
>
> Evgeny
>
> On Mon, Nov 9, 2009 at 5:19 PM, Marcos Aruj <marcos.a...@gmail.com> wrote:
> > You can also use desktop notifications:
> >
> http://dev.chromium.org/developers/design-documents/desktop-notifications/api-specification
> > But you would need a nightly build to use it from your extension. It's
> not
> > included in the latest dev release.
> >
> > On Mon, Nov 9, 2009 at 11:14 AM, Antony Sargent <asarg...@chromium.org>
> > wrote:
> >>
> >> See this long thread for why we're going with just page actions /
> browser
> >> actions for now:
> >>
> >>
> https://groups.google.com/group/chromium-extensions/browse_thread/thread/f2505dd16a5c9e43/a0127be1557d948b
> >>
> >>
> >> On Mon, Nov 9, 2009 at 7:01 AM, Evgeny Shadchnev
> >> <evgeny.shadch...@gmail.com> wrote:
> >>>
> >>> Hello,
> >>>
> >>> I'm porting InvisibleHand (http://www.getinvisiblehand.com/) Firefox
> >>> extension to Google Chrome. InvisibleHand makes extensive use of
> >>> Firefox notifications (infobars) but Chrome API doesn't allow the
> >>> extension to show an info bar. Will the extensions be allowed to
> >>> display an info bar? If so, when can we expect an API please?
> >>> Otherwise, how can I notify the user of a better price other than
> >>> with a flashing icon?
> >>>
> >>> Best regards,
> >>> Evgeny
> >>>
> >>>
> >>
> >>
> >> > >>
> >
> >
> >
> > --
> > Marcos Aruj Alvarez
> > Ingeniero de Software
> > -------------------------------
> > marcos.a...@gmail.com
> > -----
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
