addEventListener or nothing
anyone can wrap it in a promise if they want

@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 10:57 AM, Brian LeRoux <b...@brian.io> wrote:

> bonus: https://gist.github.com/brianleroux/cc8b4adc0f9f0b7df654
>
> (I have no idea if this is the best way…not being a fan promises but
> willing to cede they have won this round.)
>
>
> On Thu, Aug 7, 2014 at 10:50 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > ah, sometimes you have read inbetween the lines w/ Joe's messaging
> >
> > he's right, it is broken, and he did state why: its a blocking API
> >
> > our feedback would be perhaps received better with a concrete proposal:
> > throw out the current spec and rewrite it using DOM promises or whatever
> > flavor of the month we have for async querying of data. the current
> > blocking API is not implementable by our bridge (async) so we can't do
> much
> > with it. ideally all web apis are async anyhow. ideally spec writers know
> > this about the web and browsers, but alas.
> >
> >
> >
> >
> > On Thu, Aug 7, 2014 at 8:06 AM, Lisa Seacat DeLuca <ldel...@us.ibm.com>
> > wrote:
> >
> >> Joe~
> >>
> >> Thank you for responding.  I just finished up sharing our thoughts on
> the
> >> Device APIs Working Group status call.  They appreciate the overall "it
> is
> >> broken" feedback but could really benefit from a concrete proposal on
> how
> >> to improve the battery specification.  Do you, or anyone else from the
> >> Cordova team, want to take a stab at putting together a formal
> >> proposal/recommendation that I can bring back to the DAP team?  This is
> an
> >> opportunity for us to help shape the spec!
> >>
> >> Here's a link to the current specification:
> >> http://www.w3.org/TR/battery-status/
> >>
> >>
> >> Lisa
> >>
> >> Lisa Seacat DeLuca
> >> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> >> <ldel...@apache.org> | | *ldel...@us.ibm.com* <ldel...@us.ibm.com> |
> >> *lisaseacat.com* <http://www.lisaseacat.com/> | [image: follow
> >> @LisaSeacat on twitter] <http://www.twitter.com/LisaSeacat>| [image:
> >> follow Lisa Seacat DeLuca on linkedin]
> >> <http://www.linkedin.com/in/lisaseacat>
> >>
> >>
> >>
> >> From:        Joe Bowser <bows...@gmail.com>
> >> To:        dev <dev@cordova.apache.org>
> >> Date:        08/06/2014 02:45 PM
> >> Subject:        Re: W3C Battery Feedback request
> >> ------------------------------
> >>
> >>
> >>
> >> The spec is flawed in that there's no way we could implement it as it
> >> stands. The spec needs to be reworked to be more event driven and
> >> asynchronous.   Right now it's too much like device with everything up
> >> front.
> >>
> >> This is all based on memory, but the spec was seriously broken the last
> >> time I looked.
> >> On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca" <ldel...@us.ibm.com>
> wrote:
> >>
> >> > I sent a note back in June asking if anyone had any feedback for the
> >> > Device API's Working Group for the battery concerns that we had
> >> previously
> >> > voiced related to the battery spec.
> >> >
> >> >
> >>
> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results
> >> >
> >> > I need to update the DAP team on Thursday with any thoughts Cordova
> has
> >> so
> >> > if anyone has any feedback please reply asap.  The link to the first
> >> email
> >> > has the questions from the DAP team to Cordova.
> >> >
> >> > Thank you!
> >> >
> >> >
> >> > Lisa
> >> >
> >> > Lisa Seacat DeLuca
> >> > Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> >> > <ldel...@apache.org> | | *ldel...@us.ibm.com* <ldel...@us.ibm.com> |
> >> > *lisaseacat.com* <http://www.lisaseacat.com/> | [image: follow
> >> > @LisaSeacat on twitter] <http://www.twitter.com/LisaSeacat>| [image:
> >> > follow Lisa Seacat DeLuca on linkedin]
> >> > <http://www.linkedin.com/in/lisaseacat>
> >> >
> >> >
> >>
> >>
> >
>

Reply via email to