Jesse, where have we landed on the issue of the local-notifications plugin change?
It seems to me that whatever change we make isn't particularly relevant to other platforms. Since Windows Cordova apps are entirely in JS, the solution has to be in JS. Why focus on it being an event-based change, instead of a persistent property? From the app developer perspective, the additional event is entirely duplicative (from an API perspective), but the new event you proposed never fires for Android or iOS until it gets implemented. What I had proposed (cordova.env) is just empty on those environments until it got implemented. -----Original Message----- From: Jesse [mailto:purplecabb...@gmail.com] Sent: Tuesday, May 12, 2015 11:49 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova-Windows Release +1 The less branches we maintain the better. @purplecabbage risingj.com On Tue, May 12, 2015 at 11:44 AM, Parashuram N (MS OPEN TECH) < panar...@microsoft.com> wrote: > +1 to merging Cordova-windows10 in master. I don't think it breaks > anything existing, and windows10 support seems to be enabled only via > flags or cli args. I think merging it into master will make developing > windows 10 easier. > > -----Original Message----- > From: Rob Paveza [mailto:rob.pav...@microsoft.com] > Sent: Tuesday, May 12, 2015 11:39 AM > To: dev@cordova.apache.org > Subject: [DISCUSS] Cordova-Windows Release > > Does anyone have a reason to delay a cordova-windows platform release? > Any outstanding patches to land? > > I'm looking to merge Windows 10 support into main and release 4.0.0. > > If not, I will start a release tomorrow. > > Thanks, > -Rob > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
