Re: [Bug 25775] New: Do we need both MediaDeviceKind and SourceTypeEnum

On 05/18/2014 03:53 PM, bugzilla@jessica.w3.org wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=25775
>
>             Bug ID: 25775
>            Summary: Do we need both MediaDeviceKind and SourceTypeEnum
>            Product: WebRTC Working Group
>            Version: unspecified
>           Hardware: PC
>                 OS: All
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: Media Capture and Streams
>           Assignee: public-media-capture@w3.org
>           Reporter: fluffy@cisco.com
>                 CC: public-media-capture@w3.org
>
> Seems we could use one enum for both. Thoughts?
>
mediadevicekind is

enum MediaDeviceKind {
    "audioinput <#idl-def-MediaDeviceKind.audioinput>",
    "audiooutput <#idl-def-MediaDeviceKind.audiooutput>",
    "videoinput <#idl-def-MediaDeviceKind.videoinput>"
};




sourcetypeenum is

enum SourceTypeEnum {
    "none <#idl-def-SourceTypeEnum.none>",
    "camera <#idl-def-SourceTypeEnum.camera>",
    "microphone <#idl-def-SourceTypeEnum.microphone>"
};

The name SourceType is inappropriate for audio output. If we use MediaDeviceKind in both places, I don't see a big issue.





-- 
Surveillance is pervasive. Go Dark.