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

RE: First stab at the Capture API (aka Camera API)

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Thu, 3 Dec 2009 17:13:51 -0800
To: Frederick Hirsch <frederick.hirsch@nokia.com>, Oksanen Ilkka <Ilkka.Oksanen@nokia.com>
CC: ext Robin Berjon <robin@robineko.com>, public-device-apis <public-device-apis@w3.org>, "'Ingmar.Kliche@telekom.de'" <Ingmar.Kliche@telekom.de>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D312C8AC7251@orsmsx501.amr.corp.intel.com>
If you meant are "white balance" and "resolution" basic functions in photography, then the answer is "YES"

Dzung Tran 

-----Original Message-----
From: Frederick Hirsch [mailto:frederick.hirsch@nokia.com] 
Sent: Thursday, December 03, 2009 02:04 PM
To: Oksanen Ilkka
Cc: Frederick Hirsch; ext Robin Berjon; Tran, Dzung D; public-device-apis; 'Ingmar.Kliche@telekom.de'
Subject: Re: First stab at the Capture API (aka Camera API)

Aren't setting white balance and resolution pretty basic to meaningful  

regards, Frederick

Frederick Hirsch

On Dec 2, 2009, at 8:40 AM, Oksanen Ilkka (Nokia-D/Espoo) wrote:

> ext Robin Berjon wrote:
>> On Dec 2, 2009, at 11:27 , Ilkka Oksanen wrote:
>>> One clear missing feature is setting of preferred settings,
>>> especially preferred image/video resolution. Currently it's
>>> possible get the supported camera resolutions but not select which
>>> of them is preferred when images or videos are captured. If
>>> possible this is something I would like enhance still during this
>>> week.
>> In general, how strongly do you feel that this is a required feature
>> for v1? I certainly agree that it's useful, but off the top of my
>> head the most useful use cases don't strictly require it (and since
>> the size is returned, it can be enforced in script).
> For me it's difficult to imagine a realistic use case where just  
> getting
> a list of supported resolutions and formats is enough while setting  
> the
> preferred resolution and format is not possible. That is what the  
> draft
> allows currently.
> Therefore I believe there are two options. Either remove
> supportedImageFormats, supportedVideoFormats and supportedAudioFormats
> variables from the API or complement those with ability to set the
> preferences based on values of these variables. If the second option
> affects to overall schedule of our v1 work then I'm ready to consider
> resorting to the first option.
>      -ilkka
Received on Friday, 4 December 2009 01:14:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:41 UTC