W3C home > Mailing lists > Public > public-device-apis@w3.org > December 2009

RE: Next steps on Capture API?

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Thu, 10 Dec 2009 10:28:22 -0800
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D312CB3D531B@orsmsx501.amr.corp.intel.com>
What I got from the Ajaxian's posting are:
- API is simple but limited and would like to support for realtime, like video chat
- Ability to have frequency and waveform data for captured audio similar to Flash.
- API seems to be designed mainly for mobile devices. It would be nice with API with more capabilities for more powerful devices, so JS can compete with Flash.

Thanks
Dzung Tran


-----Original Message-----
From: Anssi Kostiainen [mailto:anssi.kostiainen@nokia.com] 
Sent: Thursday, December 10, 2009 12:53 AM
To: Tran, Dzung D
Cc: public-device-apis@w3.org
Subject: Re: Next steps on Capture API?

On 8.12.2009, at 20.03, ext Tran, Dzung D wrote:

>  I was wondering what would be our next steps in the Capture API.  
> There are lot of discussions going on in the WG. I think we need to  
> come to a consensus, so that we can make some progress on the API.
>
> Here is a list of all the discussions so far:
> 1. Keep it simple and let all the configurations happen natively in  
> the native Camera Application
> 2. Add configuration options for v1.
> 2. <input type=...> as the API
> 3. http://www.w3.org/mid/AB072C1D-8194-45A8-968E-5E44D3B8F96E@robineko.com
> 4. Adding websocket as a parameter Capture, don't know how this will  
> work.
> 5. Viewfinder in v1?
> ...
> ...anything else that I miss

The Capture API got some public review via Ajaxian (thanks Dion!):

<http://ajaxian.com/archives/w3c-capture-api-our-in-draft>

There are some good comments so I think the spec editors should follow  
up and perhaps invite interested people to join the discussion on this  
list.

-Anssi
Received on Thursday, 10 December 2009 18:29:07 GMT

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