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

RE: Proposal for Picture settings

From: Mandyam, Giridhar <mandyam@quicinc.com>
Date: Fri, 26 Oct 2012 21:47:23 +0000
To: Jim Barnett <Jim.Barnett@genesyslab.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <CAC8DBE4E9704C41BCB290C2F3CC921A16317167@nasanexd01h.na.qualcomm.com>
Hi Jim,
I leveraged Travis's definition for MediaSettingsRange:  http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/proposals/SettingsAPI_proposal_v4.html#mediasettingsrange-interface.

I defined a MediaSettingsItem as a sort of counterpart to the MediaSettingsList(http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/proposals/SettingsAPI_proposal_v4.html#mediasettingslist-interface), but specifically for data types derived from an Enum.  The main difference in my view is that the MediaSettingsItem is essentially a MediaSettingsList with only one item.  My other intention with MediaSettingsItem is to define a single data type that can be both queried for its current setting but also defines a method for setting a new value.

Currently in Travis's doc, querying of the current value setting and the assignment of a new value to that setting result in different attributes.  As an example, in the PictureandVideoSettings interface (http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/proposals/SettingsAPI_proposal_v4.html#pictureandvideosettings-mix-in-interface), there is a readonly attribute zoom for querying the current zoom setting and there is a writeable attribute of type MediaSettingsRange zooms to allow for setting the zoom value. I think we should discuss this in the group further (maybe during the F2F), because it seems inefficient.

-Giri
From: Jim Barnett [mailto:Jim.Barnett@genesyslab.com]
Sent: Friday, October 26, 2012 2:06 PM
To: Mandyam, Giridhar; public-media-capture@w3.org
Subject: RE: Proposal for Picture settings

One other minor question:  why does MediaSettingsItem have a read only 'value' attribute, while MediaSettingsRange does not?  Is there any reason that we would want to see the current value for the former but not the latter?


-          Jim

From: Mandyam, Giridhar [mailto:mandyam@quicinc.com]
Sent: Friday, October 26, 2012 4:43 PM
To: public-media-capture@w3.org<mailto:public-media-capture@w3.org>
Subject: Proposal for Picture settings

Hello,
I'd like this to be considered for Picture-specific settings on gUM. The proposal can be found at http://gmandyam.github.com/media-capture/.

-Giri Mandyam, Qualcomm Innovation Center
Received on Friday, 26 October 2012 21:47:54 GMT

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