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

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).

> In current form Capture API implements launcher type of approach. It is mainly based on Google and Nokia proposals. I think that was a reasonable starting point as these proposals can be seen as subset of more feature rich BONDI proposal.

Yes, I agree with this analysis. It is also possible that the functionality levels may correspond to a web browser vs widgets distinction. Thus v1 could be the basics that everyone does, and v2 could add the less securable stuff that would be available to widgets. That way at least the core functionality is coherent.

> I think viewfinder can be problematic feature for v1. Significant integration is needed between web rendering engine and native camera application/API in the host device. Additionally I believe that not all platforms have native APIs to stream live viewfinder image. Therefore as far I know for example PhoneGap is providing only launcher type of camera API. In that sense situation is similar to Contacts API and its searching functionality. Any comments?

+1 on doing that in v2.

Robin Berjon
  robineko  hired gun, higher standards

Received on Wednesday, 2 December 2009 12:17:02 UTC