incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Kim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-117) Capture API captureAudio not currently supported
Date Wed, 13 Jun 2012 23:03:43 GMT

    [ https://issues.apache.org/jira/browse/CB-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294707#comment-13294707
] 

Tim Kim commented on CB-117:
----------------------------

It appears this ticket has been left hanging even though there were some updates. The commit
from Drew: https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-blackberry-webworks.git;a=commit;h=fe00353449aadd0b8883aa6256214fbf21af34a5
(and later commits) seems to have fixed this one pretty good. 

It appears that captureAudio is working from my test results on device. However, attempting
to use the webworks microphone api on playbook 2.0 currently returns undefined when calling
the blackberry.media.microphone object. 

In addition, Drew wrote his captureAudio functions natively for the regular blackberry smart
phone so no need to worry about making webworks microphone calls for that. 
                
> Capture API captureAudio not currently supported
> ------------------------------------------------
>
>                 Key: CB-117
>                 URL: https://issues.apache.org/jira/browse/CB-117
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: BlackBerry
>    Affects Versions: 1.2.0
>         Environment: BlackBerry 9900 7.0.0.317
>            Reporter: Filip Maj
>            Assignee: Tim Kim
>
> Reported by Jeff
> According to https://github.com/callback/callback-blackberry/blob/master/javascript/webWorksPluginManager.js#L69
we automatically return unsupported.
> This should actually route to the webworks microphone API https://bdsc.webapps.blackberry.com/html5/apis/blackberry.media.microphone.html#.record

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message