- From: Rob Manson <roBman@buildAR.com>
- Date: Mon, 20 Oct 2014 15:26:37 +1100
- To: public-media-capture@w3.org
On 20/10/14 2:14 PM, Robert O'Callahan wrote: > Generally I think we should only introduce additional objects and > interfaces when there's some clear rationale for doing so, because all > other things being equal, they add complexity. I don't see such a > rationale here. Spec readability issues are not very important, > especially because you can easily organize the spec to group together > the specs for a particular subset of attributes. ImageCapture is > currently a small interface so moving PhotoSettings attributes into it > will not bloat it to an unreasonable size. E.g. writing > imageCapture.redEyeReduction = true; > imageCapture.zoom = 1.5; > image > var promise = imageCapture.takePhoto(); > looks reasonable to me. As an alternative perspective, especially in this case it would be nice as a web dev to be able to grab the settings/options object and just iterate over that to list the settings/options the user could change in a UI. If they're all at the same level as other attributes then this is no longer a simple step. roBman
Received on Monday, 20 October 2014 04:20:35 UTC