[whatwg] unsubscribe
Re: [whatwg] Device proximity and light events
There is a discussion on the DAP WG, we like the simplicity of the proposal however there is an important feature that is missing which is ability to set the report interval and threshold. Thanks Dzung Tran -Original Message- From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Doug Turner Sent: Wednesday, May 09, 2012 7:31 AM To: Anne van Kesteren Cc: Jonas Sicking; wha...@whatwg.org; Scott González; JOSE MANUEL CANTERA FONSECA; Andrei Popescu; Carr, Wayne Subject: Re: [whatwg] Device proximity and light events On May 9, 2012, at 3:14 AM, Anne van Kesteren wrote: On Wed, May 9, 2012 at 5:59 AM, Doug Turner do...@mozilla.com wrote: Where was that discussion? This came up at the WebApps F2F and there was general agreement that if we added new events adding new event handler attributes would make sense. Was there any notes taken? Feature detection of some kind is useful as forcing people to do UA sniffing leads to badness. I am not arguing that it shouldn't be done. I just don't think it as important as most people. For example, even if the device is present, it may be off or not responding. In that case, you'll have a feature that tests positive and never receive any events.
Re: [whatwg] Device proximity and light events
Hello Doug, Proximity and Light is currently in the Sensor API spec at: http://dvcs.w3.org/hg/dap/raw-file/tip/sensor-api/Overview.html This spec is in process of revising. I am planning to update this in the next couple of days. Thanks Tran -Original Message- From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Doug Turner Sent: Friday, May 04, 2012 11:02 AM To: wha...@whatwg.org Subject: [whatwg] Device proximity and light events I have added two new events to Firefox which allow web apps to detect light and proximity changes. http://dougturner.wordpress.com/2012/03/22/device-proximity-sensor/ http://dougturner.wordpress.com/2012/03/26/device-light-sensor/ I'd like feedback and to see if there was any interest in supporting these events in other UAs. Thanks Doug
Re: [whatwg] Do we really need to introduce a device element for giving access to webcams and mikes?
The device was added by Ian Hickson in response to some of the work in the W3C DAP working group. The original intent was to make sure the user are actively grant permission to a particular device camera or microphone instead of just click okay since some malicious site can just capture and post it on the internet. Here is a reference to the work in W3C DAP: http://dev.w3.org/2009/dap/camera/Overview.html Some threads on the topic: http://lists.w3.org/Archives/Public/public-device-apis/2009Dec/0248.html http://lists.w3.org/Archives/Public/public-device-apis/2009Dec/0194.html Thanks Dzung Tran, -Original Message- From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Julien Cayzac Sent: Monday, May 03, 2010 07:41 PM To: whatwg@lists.whatwg.org Subject: Re: [whatwg] Do we really need to introduce a device element for giving access to webcams and mikes? On Tue, May 4, 2010 at 11:37 AM, Julien Cayzac julien.cay...@gmail.com wrote: I am not sure if I get your point here: are you saying that using the webcam locally in a canvas and somehow transmitting the webcam video over the network are two independent permissions to grant? If so, how would you detect the latter, since by allowing the page to manipulate the video in canvas you would give it permission to use toDataURL() too, so it could still transmit frames to the server or to other party if a ConnectionPeer is involved? To answer my own question: by raising the origin-clean flags of the canvas element the webcam was attached to. Now, I see no reference to any interaction between device and canvas mentionned in http://dev.w3.org/html5/html-device/ Julien. -- Julien Cayzac http://julien.cayzac.name/ skype://jcayzac?chat
Re: [whatwg] Web API for speech recognition and synthesis
Currently the W3C Device API WG is working on a Capture API which will include microphone capture and audio streaming capabilities. The current draft is at: http://dev.w3.org/2009/dap/camera/ It is pretty rough and still in working progress, so for instance streaming is not there. Thanks Dzung Tran On Sun, Dec 13, 2009 at 6:46 PM, Ian McGraw imcg...@mit.edumailto:imcg...@mit.edu wrote: I'm new to this list, but as a speech-scientist and web developer, I wanted to add my 2 cents. ?Personally, I believe the future of speech recognition is in the cloud. Here are two services which provide Javascript APIs for speech recognition (and TTS) today: http://wami.csail.mit.edu/ http://www.research.att.com/projects/SpeechMashup/index.html Both of these are research systems, and as such they are really just proof-of-concepts. That said, Wami's JSONP-like implementation allows Quizlet.com to use speech recognition today on a relatively large scale, with just a few lines of Javascript code: http://quizlet.com/voicetest/415/?scatter Since there are a lot of Google folks on this list, I recommend you talk to Alex Gruenstein (in your speech group) who was one of the lead developers of WAMI while at MIT. The major limitation we found when building the system was that we had to develop a new audio controller for every client (Java for the desktop, custom browsers for iPhone and Android). ?It would have been much simpler if browsers came with standard microphone capture and audio streaming capabilities. -Ian
