Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 97A29183AA for ; Wed, 12 Aug 2015 02:25:16 +0000 (UTC) Received: (qmail 42984 invoked by uid 500); 12 Aug 2015 02:25:16 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 42956 invoked by uid 500); 12 Aug 2015 02:25:16 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 42940 invoked by uid 99); 12 Aug 2015 02:25:15 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Aug 2015 02:25:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 7CDC1DC6C6 for ; Wed, 12 Aug 2015 02:25:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id EV7vwkPgAN9W for ; Wed, 12 Aug 2015 02:25:04 +0000 (UTC) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 67AD0205B0 for ; Wed, 12 Aug 2015 02:25:03 +0000 (UTC) Received: by oiev193 with SMTP id v193so2051590oie.3 for ; Tue, 11 Aug 2015 19:24:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=WLDQ0ocRs5yhcxXBNn+L5Asv4091eGY9TRjzQ9VhlaI=; b=TQKzOsnQ6ygP/TQ6ck5Se0UGJL8DQsT865D52tcxtEt5hLRZ3xbuAJty1vD03rWdkW e6S4F2oOrJED3nV1cn9Wcd4FvobLjNmpYYLmco+o0Y7aueHbfv2xNIwNgs2QWifX9P0c zXPPOLckenoms3j2A3j4vEtuijZuar45xe6yF28q2uLcPYDm+659oXdpzwdskgaF66GI opkbN5LKtlWgn/mpJyZsEDnZK2xOT3/bNHPJMR6JRAK66m9JYPomMtFZbs+PAcu/5PxM 2POuW2SXQLZJKcfe2c+FDplgxZ1idbQ+pxyKoIC60sSPaYLQKiWKWqTN0m9q4tVr+DA7 4dQw== X-Received: by 10.202.169.138 with SMTP id s132mr21699086oie.71.1439346295840; Tue, 11 Aug 2015 19:24:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.98.193 with HTTP; Tue, 11 Aug 2015 19:24:16 -0700 (PDT) In-Reply-To: References: From: Shazron Date: Wed, 12 Aug 2015 10:24:16 +0800 Message-ID: Subject: Re: Dialogs plugin alignment with W3C notification To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=001a113cdbbeac703e051d13ec76 --001a113cdbbeac703e051d13ec76 Content-Type: text/plain; charset=UTF-8 Not sure if I agree about rolling this into the Notification plugin: https://github.com/apache/cordova-plugin-dialogs which is materially different in that the dialogs it shows are more intrusive (modal) and have buttons etc and conform more to JavaScript alert, prompt and confirm. This should be a different plugin. On Sat, Aug 8, 2015 at 5:45 AM, Darryl Pogue wrote: > My problem with the W3C spec is that there is no mechanism for scheduling > notifications. You tell it to show a notification, and that notification > appears on the screen. The API as spec'ed is already supported in > Chrome/Chromium (on Android and desktop), Safari (on desktop), and Firefox > (desktop, possibly Android?). > > The local-notification plugin doesn't quite match the W3C spec naming, but > it's close enough that it would be minimal work to make it align. That > still leaves the big question of whether to align with the spec (and > browser implementations) which are largely useless, or to add a > non-standard feature to allow scheduling into the future. > Along with that comes scheduling repeating notifications, and canceling > future notifications, and all sorts of fun problems when you can easily > send your phone into an infinite loop of notifications triggering. > > When I've talked to anyone about the gap in the W3C spec, the answer has > always been either ServiceWorkers or the Push API :( > > On 7 August 2015 at 14:37, Joe Bowser wrote: > > > I think we can as long as we include where it came from in the NOTICE > file > > and if the licence is compatible. Since this is Apache 2.0, we should be > > fine, but it would be better if the people who wrote the plugin were to > > contribute it. > > > > That said, Local Notifications are trivial to write (at least for > Android), > > and we should just add it into our plugin, since this would be much > > easier. Of course, given our current backlog of issues, I don't think > I'll > > get around to this any time soon, so patches and pull requests are > welcome. > > > > On Fri, Aug 7, 2015 at 1:33 PM Carlos Santana > > wrote: > > > > > I don't think we can accept code into Apache Cordova repos if there is > no > > > ICLA for the originator/owner of the code. > > > You can work with originator of the code to see if he wants to "donate" > > and > > > go thru contribution process to get his code into Apache Cordova. > > > > > > From our website: > > > > > > In order for your changes to be accepted, you need to sign and submit > an > > > Apache ICLA (Individual > > Contributor > > > License Agreement). Then your name will appear on the list of CLAs > signed > > > by non-committers > > > or > Cordova > > > committers < > http://people.apache.org/committers-by-project.html#cordova > > >. > > > > > > And don't forget to test and document your code. > > > > > > > > > > > > > > > On Fri, Aug 7, 2015 at 8:41 AM Paul Contat > > wrote: > > > > > > > Hi everyone, > > > > I have seen that the description of dialog plugin is "Cordova > > > Notification > > > > Plugin" so I would like to know if adding web notification[1] into > > dialog > > > > plugin is a good idea? > > > > > > > > If yes, is it acceptable to create a wrapper with the correct > > > > implementation around an existing third party plugin[2] or rather > > create > > > > the native side from scratch? > > > > Here is the associate Jira issue : > > > > https://issues.apache.org/jira/browse/CB-6071 > > > > > > > > [1] http://www.w3.org/TR/notifications/ > > > > [2] https://github.com/katzer/cordova-plugin-local-notifications/ > > > > > > > > Thanks, > > > > Paul Contat > > > > > > > > > > --001a113cdbbeac703e051d13ec76--