W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2010

Re: Capture API question

From: Andrei Popescu <andreip@google.com>
Date: Fri, 11 Jun 2010 10:41:43 +0100
Message-ID: <AANLkTimLqoiisuO5L0ifwrcYUxrglqDzyB6gcSOCFNGE@mail.gmail.com>
To: Dominique Hazael-Massieux <dom@w3.org>
Cc: public-device-apis@w3.org
Hi,

On Fri, Jun 11, 2010 at 8:05 AM, Dominique Hazael-Massieux <dom@w3.org> wrote:
> Le jeudi 10 juin 2010 à 15:09 +0100, Andrei Popescu a écrit :
>
>> http://dev.w3.org/2009/dap/camera/FPWD.html#formaccess
>>
>> which shows that most of the functionality provided by the Capture API
>> can also be achieved using APIs that already exist in the Web platform
>> (i.e. <input>, File, <video>, etc). However, the spec does not have
>> any discussion about the reasoning behind adding a new API to do
>> something that is already possible. Since, to me at least, the reasons
>> for doing this are not completely obvious, I was wondering if it's
>> worth reconsidering the API or adding a note discussing the advantages
>> over using existing APIs.
>
> The proposed APIs offer additional controls that a form-based approach
> doesn't, e.g. controlling the number of media objects to capture, their
> duration.
>

I see.

> That said, we're very much interested in getting feedback — in
> particular from implementors — on whether these additional features are
> needed/useful in a v1, or if focusing on the form-based approach is more
> cost-effective.
>

On Android we are only implementing the form-based approach for now.
This seems to work pretty well for the majority of the use cases we've
encountered.

Thanks,
Andrei
Received on Friday, 11 June 2010 09:42:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:10 GMT