Re: Logistics Media Capture call Aug 28th

Hi Balwinder.  I'll send you a private email and we can coordinate on a time to talk.

-- dan

On Aug 28, 2013, at 1:08 PM, Balwinder Kaur wrote:

> 
> Hi,
> 
> During the discussion on the output device selection ability, I mentioned that I would be interesting in having a discussion and learning the historical decision making around how devices can be selected programmatically from an HTML5 application.
> 
> The primary use case I was looking at was creating an HTML5 Camera application for an Android Device, where I would like to choose a front facing or rear facing camera depending on the application without the user having to pick one from a browser pop-up.
> 
> I look forward to have a one on one with folks on the call. 
> 
> Thanks,
> Balwinder Kaur
> 
> ****************
> <C2008861-3BF8-4484-B969-AD0132BDD3A1[1].png>
> Balwinder Kaur
> Senior Member, Technical Staff
> (408) 660-2766 Desk, (510) 996-2953 Cell, (408) 660-2343 Fax
> bkaur@aptina.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On 8/26/13 10:40 PM, "Stefan Håkansson LK" <stefan.lk.hakansson@ericsson.com> wrote:
> 
>> Time: 15:00 - 16:30 UTC
>> 
>> Call in to:
>> UW_MdCap
>> Wednesday, 28 August 15:00-16:30 UTC (11:00am-12:30pm Boston local)
>> Zakim Bridge +1.617.761.6200, conference 6227 ("MCAP")
>> 
>> IRC: #mediacap at irc.w3.org
>> 
>> 
>> Agenda (draft):
>> ===============
>> * Welcome, scribe, get started: 10 min
>> 
>> * Media Capture and Streams: 60 min
>> 
>>          Status (editing, bug resolving)
>>          Test suite… (Dom)
>>          Open Items
>>              19594 Remove “blob” as type of CreateObjectURL result
>>              21618 Ended state of an empty MediaStream
>>              22251 Add error codes for “Hardware unavailable” and “No
>> devices found”
>>          Output device selection
>> 
>> * AoB 10 min
>> 
>> * Conclude, wrap up: 10 min
>> 
>> 
>> 
> Aptina, LLC / 3080 North First Street, San Jose, CA 95134.
> 
> This e-mail and any attachments contain confidential information and are solely for the review and use of the intended recipient. If you have received this e-mail in error, please notify the sender and destroy this e-mail and any copies.
> 
> <C2008861-3BF8-4484-B969-AD0132BDD3A1[1].png>