RE: Question about HTML Media Capture specification

> I'm Jongseok Yang and webkit engineer in SAMSUNG Electronic.
> I'm trying to implement HTML Media Capture spec. but I'm not sure that.
> I think that the operation of the specification is like the below. 
> Could you give some comment if it's not correct?
 
> The "capture" attribute is just optional. Even if there is no "capture"
> attribute in the File Upload state, the user agenet should invoke some
> interface that allow to take a picture, record a sound file, recorder
> video, or select a file from file system.

> Ex1)  <input type="file" accept="image/*">
>    => It's to allow to take picture, select a file from file system.
>    => The file picker will present the interface for the file system by
> default. The user can select the interface for camera within the file picker

That's an implementation detail.

Your average file picker button is "[ Browse... ]", but nothing prevents it from being:

"[ 📷| Browse... ]", where clicking on 📷 triggers a Camera [1].

> Ex2)  <input type="file" accept="audio/*"> 
>    => It's to allow to recorder a sound, select a file from file system.
>    => The file picker will present the interface for the file system by default.
> The user can select the interface for voice recorder within the file picker

Your average file picker button is "[ Browse... ]", but nothing prevents it from being:

"[ 🎤| Browse... ]", where clicking on 🎤 triggers an Audio Recorder [2].

> Ex3)  <input type="file" accept="video/*">  
>    => It's to allow to recorder a video, select a file from file system.
>    => The file picker will present the interface for the file system by default.
> The user can select the interface for voice recorder within the file picker

Your average file picker button is "[ Browse... ]", but nothing prevents it from being:

"[ 🎥 | Browse... ]", where clicking on 🎥 triggers a Movie Studio [3]. 

> Ex4)  <input type="file" accept="image/*" capture="camera">
>    => It's to allow to take picture, select a file from file system.
>    => The file picker will present the interface for camera by default.

It would be perfectly legal for Keyboard based UIs to make the first triggerable thing (typically by pressing space) when one tabs into a control like the ones I've described above change between the <record> and <browse> actions based on the presence of <capture>.

> The user can select the interface for file system within the file picker
> Ex5)  <input type="file" accept="image/*" capture="microphone">
>    => It's to allow to take picture, select a file from file system.
>    => The capture attirbute is ignored because the value is "microphone" but it is not allowed to record a sound 
>    => It's the file picker present the interface for camera by default.
> The user can select the interface for camera within the file picker

This should be an implementation detail.
 
> I think that the same file picker should be launched in all cases and the file picker includes all intefaces.

This is an implementation detail.

> I think that it's not easy to implement the file picker.

This probably depends on your OS / Toolkit.

On Windows, it actually isn't too hard to plug in an extra virtual file system, nor is it too hard to preselect it. I'm also fairly certain that one can do some pretty magical things with the file portion of the file system.

> So, My implementation choice is to launch "Interface selector" instead of the file picker.

You certainly should be able to do that, although, it probably isn't the best approach.

> "Interface selector" will present the allowed behavior - "take a picture"
> "record a sound file" "recorder video" "file system"
> At that time, the user will select an interface from the "Interface selector" and the selected interface will be lauched.
 
That will definitely work, but, it probably isn't ideal. OTOH, if you were on Windows, and you modeled it after the "What do you want to do with this USB device" dialog [4], it wouldn't be too bad either. 

[1] http://www.fileformat.info/info/unicode/char/1f4f7/index.htm

[2] http://www.fileformat.info/info/unicode/char/1f3a4/index.htm

[3] http://www.fileformat.info/info/unicode/char/1f3a5/index.htm

[4] http://windows7themes.net/pics/autoplay-import-settings.jpg


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Monday, 27 June 2011 15:06:54 UTC