[
https://issues.apache.org/jira/browse/CB-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072193#comment-14072193
]
Jesse MacFadyen commented on CB-7193:
-------------------------------------
Also, I imagine groupings of capabilities are arbitrary, so there is no need or
expectation that there is a 'capabilities' plugin for each 'core' plugin.
ie. a 'SensorCaps' might make sense and just define if Accel+Compass are
available, and what they can do.
Technically the MediaCapabilities I mentioned, and Ray annotated has some
overlap with HTMLMediaElement [1] canPlayType(in DOMString type) which returns
non-committal values of 'probably' and 'maybe'
[1] https://developer.mozilla.org/en/docs/Web/API/HTMLMediaElement
> Create a "Capabilities" plugin
> ------------------------------
>
> Key: CB-7193
> URL: https://issues.apache.org/jira/browse/CB-7193
> Project: Apache Cordova
> Issue Type: Improvement
> Reporter: Raymond Camden
> Priority: Minor
>
> This is based on an IM conversation I had with Jesse MacFadyen. I promised to
> write it up. HIs idea, my write up, so any mistakes blame on me.
> I recently logged an ER for supporting a "IsCameraAvailable" request in the
> Camera API. JF mentioned that a general purpose Capabilities API would be a
> good place for this. Specifically a CameraCapabilities plugin.
> You could then have a MediaCapabilities plugin to support things like
> canPlayMp3, canPlayWav, etc.
> Basically - one plugin per 'area' of capabilities.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
