Also, not sure if its helpful, but I did notice that the battery API implementation was missing for Playbook and the wrong service name was being used for Capture so I mocked up those changes:
https://github.com/deedubbu/incubator-cordova-js/commit/4d5d1afc89cfcc02732b59d728b06f18978656f4 Of course, have not been able to test them. On Wed, Mar 21, 2012 at 3:26 PM, Drew Walters <[email protected]> wrote: > Thanks guys. Much appreciated, now I can stop banging my head against > the desk for a little while. All my updates to cordova-js are in > master. For native side, my changes are in this branch in my fork: > > https://github.com/deedubbu/incubator-cordova-blackberry-webworks/tree/cordova-js > > Only thing relevant for playbook in that branch is the changes to the > build script. So, no real need to clone my branch to test playbook if > you just build cordova.playbook.js from cordova-js. > > On Wed, Mar 21, 2012 at 2:44 PM, Filip Maj <[email protected]> wrote: >> Beat me to it Gord ;P >> >> On 3/21/12 12:43 PM, "Filip Maj" <[email protected]> wrote: >> >>>That is awesome, nice work Drew! >>> >>>I've got a PB and so does Tim, between the two of us we should be able to >>>run through everything. That being said there are still missing APIs for >>>Playbook in its current implementation as far as I know: File being the >>>big one. >>> >>>Mayhaps someone from RIM can help out as well? /hint hint nudge nudge >>> >>>On 3/21/12 12:39 PM, "Drew Walters" <[email protected]> wrote: >>> >>>>I've completed my testing of cordova-js with the BlackBerry platform >>>>(smartphone only) and am happy enough with its state that I'd like to >>>>switch the repo over to using cordova-js. Problem is, the >>>>blackberry-webworks repo also contains the Playbook code. The >>>>Playbook simulators (v1.0 and v2.0) have been giving me fits for the >>>>past day which makes it frustrating/impossible to debug. I do not >>>>have an actual Playbook device to test with. Is there someone else >>>>that can grab the latest cordova-js for Playbook and test it >>>>out/debug? >>> >>
