ICEfaces
  1. ICEfaces
  2. ICE-11015

ace:growlMessages - Add support for Native Platform Notifications

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.BETA, 4.2
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      Any
    • Assignee Priority:
      P2
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial

      Description

      A new ACE component that leverages browser native notifications would be a popular and useful addition to ICEfaces. The component would shield app developers from writing and managing the Javascript themselves.

      These notifications could be used in tandem with ICEpush, or just for app level notifications (in the same way ace:growlMessages is used now).

      Since the user has to give permission for browser notifications we could even have this new component gracefully fall back to a built in toast/growl style if the user disallows native notifications.

      https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API

        Activity

        Hide
        Carmen Cristurean added a comment -

        Verified 5) with ICEfaces4 trunk r49316 on MS Edge38, Chrome53/ Windows10 OS.

        Show
        Carmen Cristurean added a comment - Verified 5) with ICEfaces4 trunk r49316 on MS Edge38, Chrome53/ Windows10 OS.
        Hide
        Ken Fyten added a comment -

        Reopened to adopt the "for='@inView'" attribute configuration on the ace:message(s) components to avoid rendering messages for components that are no longer in the view.

        Show
        Ken Fyten added a comment - Reopened to adopt the "for='@inView'" attribute configuration on the ace:message(s) components to avoid rendering messages for components that are no longer in the view.
        Hide
        Mircea Toma added a comment -

        Adopting the "for=@inView" strategy cannot work in the case of the demoes. The messages are created by the backing bean so there is not component to point to. Also, the view does not change when nvigating in bewteen demoes so the messages will still be propagated.

        Show
        Mircea Toma added a comment - Adopting the "for=@inView" strategy cannot work in the case of the demoes. The messages are created by the backing bean so there is not component to point to. Also, the view does not change when nvigating in bewteen demoes so the messages will still be propagated.
        Hide
        Ken Fyten added a comment -

        Re-opened to add documentation to the existing growlMessages Wiki topic (http://www.icesoft.org/wiki/display/ICE/GrowlMessages) for Native Notifications, including the min. spec required for browsers and platform OSs.

        Show
        Ken Fyten added a comment - Re-opened to add documentation to the existing growlMessages Wiki topic ( http://www.icesoft.org/wiki/display/ICE/GrowlMessages ) for Native Notifications, including the min. spec required for browsers and platform OSs.
        Hide
        Mircea Toma added a comment -

        Added documentation for Native Notifications.

        Show
        Mircea Toma added a comment - Added documentation for Native Notifications.

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Carlo Guglielmin
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: