- From: Randell Jesup <randell-ietf@jesup.org>
- Date: Tue, 13 Mar 2012 13:20:00 -0400
- To: public-media-capture@w3.org
On 3/13/2012 5:04 AM, Harald Alvestrand wrote: > I suspect that most stuff embedded within an application will want to > control its own "viewfinder" UI, so that the more common flow will be: > > getUserMedia(video: true....) > <viewfinder code> > getUserMedia(picture: true) > <process snapshot> > > Having the "preview to choose picture" dialog be required will make > this use case more difficult. Note that response time to grab the snapshot makes a big difference to people; delays on that are *painful* when you try to use it like a camera. So we should be careful about fast-paths from click to capture. Just a "keep in mind". You can get better shutter response time without going through the app again on click/capture. Apps won't *all* want to re-implement the world for flash, exposure, zoom, focus, etc - which is why leveraging some default "camera api" provided by the browser is useful. (In some cases it may be an external camera app). Some will want full flexibility. Some will just want a subset of control. -- Randell Jesup randell-ietf@jesup.org
Received on Tuesday, 13 March 2012 17:22:46 UTC