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

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

From: Ilkka Oksanen <Ilkka.Oksanen@nokia.com>
Date: Fri, 04 Dec 2009 16:23:24 +0200
Message-ID: <4B191B5C.9040304@nokia.com>
To: "ext Tran, Dzung D" <dzung.d.tran@intel.com>
CC: "Hirsch Frederick (Nokia-CIC/Boston)" <Frederick.Hirsch@nokia.com>, ext Robin Berjon <robin@robineko.com>, public-device-apis <public-device-apis@w3.org>, "'Ingmar.Kliche@telekom.de'" <Ingmar.Kliche@telekom.de>
ext Tran, Dzung D wrote:
> If you meant are "white balance" and "resolution" basic functions in
>  photography, then the answer is "YES"
> 

I think the question is whether it should be the native camera
application or the API which provides the means to configure these settings.

To keep things simple in v1.0 most of the configuration could happen
through UI in native side. Resolution (and quality) setting is a special
case in a sense that it affects directly to the file size. Following
could happen more often if there is no way of hinting the preffered
resolution in the API.

  - A widget allows user to set profile picture, max resolution is
    640x480
  - Native camera has the default resolution of 1600x1200
  - User doesn't change resolution and takes the profile image
  - Widget uploads the image to server
  - Server shrinks the image -> Bandwith wasted.

          -ilkka
Received on Friday, 4 December 2009 14:24:27 GMT

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