Something cool coming in BB10 is support for the notification API: https://github.com/blackberry-webworks/BB10-WebWorks-Framework/blob/next-mv-notification-webplatform/ext/notification/client.js
Polyfills in the W3C Notificaiton API to tie into system notifications. On Wed, Sep 19, 2012 at 2:08 PM, Filip Maj <f...@adobe.com> wrote: > I guess so? My goal was to tie into the Android status bar / iOS > notification center > > On 9/19/12 11:02 AM, "Brian LeRoux" <b...@brian.io> wrote: > >>thats rad. thought it was just timer based---anyhow. that'd be an alert >>amirite? >> >>On Wed, Sep 19, 2012 at 7:49 PM, Filip Maj <f...@adobe.com> wrote: >>> I tried my hand at this last week. Local notification cannot be shown on >>> iOS when the app is running. Kinda threw off my attempts at a simple >>> prototype :s >>> >>> On 9/19/12 8:00 AM, "Brian LeRoux" <b...@brian.io> wrote: >>> >>>>think we want to try to spec out both local or remote notifications >>>>(in ios parlance); this needs far more work for us to figure out what >>>>could map to the devices (if at all) >>>> >>>>On Wed, Sep 19, 2012 at 4:47 PM, Plaquette, Paul >>>><paul.plaque...@intel.com> wrote: >>>>> by "notifications" you mean "Push Notifications" sent by a server >>>>>right? >>>>> >>>>> the W3C notification API is about showing notifications and user >>>>> interaction on a device >>>>> for "Push notifications" we could look at the Server Sent event from >>>>>the >>>>> W3C >>>>> (by the way this is used in Tizen) >>>>> >>>>> http://www.w3.org/TR/notifications/ >>>>> http://www.w3.org/TR/eventsource/ >>>>> >>>>> >>>>> regards, >>>>> Paul >>>>> >>>>> >>>>> On Wed, Sep 12, 2012 at 2:08 PM, Brian LeRoux <b...@brian.io> wrote: >>>>> >>>>>> Hi everyone, I spent some time today gardening the wiki around the >>>>>> roadmap [1] most notably publishing a tentative release schedule. >>>>>>Keep >>>>>> in mind, we employ a release train wherein we ship a MINOR once a >>>>>> month, upon consensus of course, aiming for an ultimate MAJOR in the >>>>>> summer. That is to say, we ship features when they are ready, and not >>>>>> to any specific date. >>>>>> >>>>>> Please review it, and let your comments be known here on the list, so >>>>>> we can plan/adjust accordingly. Our theme to close out 2012 is >>>>>> finalizing workflow tools for plugin authoring, discovery, >>>>>> installation, and removal. (In addition to new platforms and refined >>>>>> APIs of course!) >>>>>> >>>>>> In 2013, as long as the mayans were wrong, we'll be looking at the >>>>>>oft >>>>>> discussed Core API Audit. The sheer enormity of this task requires >>>>>> planning documentation of its own [2] and requires much more detail >>>>>>to >>>>>> move forward. I'll be kicking up separate threads for each Core API >>>>>>in >>>>>> the coming weeks. >>>>>> >>>>>> As always: feedback pls! >>>>>> >>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects >>>>>> [2] http://wiki.apache.org/cordova/Core%20API%20Audit >>>>>> --------------------------------------------------------------------- >>>>>> Intel Corporation SAS (French simplified joint stock company) >>>>>> Registered headquarters: "Les Montalets"- 2, rue de Paris, >>>>>> 92196 Meudon Cedex, France >>>>>> Registration Number: 302 456 199 R.C.S. NANTERRE >>>>>> Capital: 4,572,000 Euros >>>>>> >>>>>> This e-mail and any attachments may contain confidential material for >>>>>> the sole use of the intended recipient(s). Any review or distribution >>>>>> by others is strictly prohibited. If you are not the intended >>>>>> recipient, please contact the sender and delete all copies. >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ____________________________ >>>>> >>>>> Paul Plaquette, >>>>> Senior Software Engineer >>>>> Intel Corporation SAS >>>>> Open Source Technology Center >>>>> France, Montpellier >>> > -- Gord Tanner Senior Developer / Code Poet tinyHippos Inc. @tinyhippos
