[
https://issues.apache.org/jira/browse/CB-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-359:
-------------------------
Component/s: (was: CordovaJS)
webOS
iOS
Android
JavaScript + mobile-spec tests exist. Next step is updating the native
framework to conform to the API differences imposed by {{exec}} calls for
Android, webOS and iOS. The following is something I wrote up for the cordova
mailing list which describes the API changes enforced by {{exec}} and what
actions the native framework should implement, along with what parameters are
provided.
{quote}
All of this means the the API on the native side for geolocation will change
(sorry iOS!). Basically we have three actions that the Geolocation plugin
should listen for:
* getLocation, which takes as parameters enableHighAccuracy (boolean) and
maximumAge (int as milliseconds).
* addWatch, parameter: only the usual callbackID required.
* clearWatch, parameter: only the usual callbackID required.
getLocation should require very little changing (other than not needing the
timeout parameter anymore, since that is handled on the JS side in my patch).
addWatch should keep a list of callback Ids, and, as soon as we have one watch
started, the native framework should start watching the position for a
"significant position difference". Once that happens, it should fire the
success callback(s) for all stored watch callback Ids. If there is an issue
retrieving position, it should fire the error callback(s) for all stored watch
callback Ids.
{quote}
> Add mobile spec and cordova-js tests for Geolocation module
> -----------------------------------------------------------
>
> Key: CB-359
> URL: https://issues.apache.org/jira/browse/CB-359
> Project: Apache Callback
> Issue Type: Test
> Components: Android, iOS, webOS
> Reporter: Filip Maj
> Assignee: Filip Maj
> Fix For: 1.7.0
>
>
> Need to check that our geo implementations follow the [W3C Geolocation
> Spec|http://dev.w3.org/geo/api/spec-source.html#api_description].
> Looks like the old/stock implementation (unused impl. on Android and current
> one on iOS) are just plain wrong.
> First, add tests to mobile-spec and to cordova-js.
> Then, implement new requirements imposed on native from cordova-js in the
> various native platforms. iOS most important here as is the main platform
> that utilizes our implementation.
> After that is done, we need to test across all of the cordova platforms.
> Finally, once over the documentation.
--
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
