- From: Dušan Maliarik <dusan.maliarik@gmail.com>
- Date: Fri, 15 Apr 2011 19:11:41 +0200
- To: public-device-apis@w3.org
- Message-ID: <BANLkTik=6VpKSBnUjodiDwoAOEJ-wGB2ig@mail.gmail.com>
Hi, first of all thank you for the effort, I consider it a move in the right direction. What I miss is an API allowing access to live capture data. The document demands user agent to implement a UI and control for the media capture. I don't think this is in line with most of other HTML features. What makes WWW and HTML different from desktop applications, is that gives an opportunity to create any kind of UI, or style of a document in any way that HTML and CSS allows. Web developers are free to present interactive elements in any form and style they want. Media Capture API considers this an unnecessary burden thrown at web developers, and leaves all this to be implemented inside a browser. While this certainly makes things easier for browser developers, it takes away many opportunities for innovation on the side of web developers. There are many use cases when custom UI, styling and scripting is desirable. In particular, it's missing access to live data from media capture device, which could be processed and acted upon, eventually resulting in user - browser interaction. Applications ranging from simple media filters, augmenting signal on the go, to computer vision and server powered speech recognition. -- *+* *Best regards*, Dušan Maliarik *+*
Received on Monday, 18 April 2011 07:09:22 UTC