W3C home > Mailing lists > Public > public-media-capture@w3.org > April 2013

Re: VideoStreamTrack: takePhoto()

From: Harald Alvestrand <harald@alvestrand.no>
Date: Mon, 08 Apr 2013 16:01:55 +0200
Message-ID: <5162CDD3.8060805@alvestrand.no>
To: Robin Berjon <robin@w3.org>
CC: public-media-capture@w3.org
On 04/08/2013 03:18 PM, Robin Berjon wrote:
> On 08/04/2013 14:35 , Harald Alvestrand wrote:
>> Thanks for the corroboration that there are at least 2 people in the
>> world who think that.
>
> Well, as a community we've only been hashing out designs for a few 
> years it's true. And we've only deployed futures in some minor 
> projects like jQuery or Angular.

jQuery is wholly implemented in Javascript, isn't it?
I don't know Angular at all, so won't speak to that.

The API we're talking about here crosses the browser/Javascript boundary.

The question I asked first is (making it more precise) is whether there 
is any project that has specified, coded and deployed futures as 
specified in the DOM specification as part of the browser/Javascript 
boundary.

The answer, given the age of the specification, is clearly a resounding NO.

Some group has to be the first one to incorporate futures into their 
specification, and show that it works for them. Anne claims that the 
IndexedDB WG has volunteered.

I'll be happy to revisit the issue once it's clear that they've succeeded.
Received on Monday, 8 April 2013 14:02:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:24:40 UTC