W3C home > Mailing lists > Public > public-media-capture@w3.org > September 2012

RE: Settings retrieval/application API Proposal (formerly: constraint modification API v3)

From: Josh Soref <jsoref@rim.com>
Date: Wed, 12 Sep 2012 15:06:13 +0000
To: Media Capture <public-media-capture@w3.org>
Message-ID: <957F1ECDA90E004B8DBDE23CFC94E3A33A55A261@XMB103ECNC.rim.net>
Travis wrote: 
> Note: this is how the Windows 8 Camera capture API [1] is factored. The object basically looks like this:
> interface MediaDeviceControlCapabilities {
>   float value;
>   float min;
>   float max;
>   float step;
>   float default;
>   boolean supported;
>   boolean autoModeSupported;
> }

A very clean approach.

> Pros: it does nicely factor the capabilities into an object-centric view

+1
> Cons: it leads to additional nesting in a constraint package (which may be OK): { videoWidth: { min: 1024, max: 1920 }}

I actually like this, it doesn't seem like a con to me.

> [1] http://msdn.microsoft.com/en-us/library/windows/apps/windows.media.devices.mediadevicecontrolcapabilities.aspx


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 12 September 2012 15:06:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:01 GMT