incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Drew Walters <deedu...@gmail.com>
Subject Re: Playbook cordova-js testing
Date Tue, 27 Mar 2012 14:32:42 GMT
Gord, any update on the status of Playbook?

On Thu, Mar 22, 2012 at 2:07 PM, <gtanner@gmail.com> wrote:

> Also:  tested the battery events on the playbook and they are working fine!
>
> I would like to get this into master before the reorg happens.
> Sent on the TELUS Mobility network with BlackBerry
>
> -----Original Message-----
> From: Drew Walters <deedubbu@gmail.com>
> Sender: purdrew@gmail.com
> Date: Thu, 22 Mar 2012 13:49:40
> To: <callback-dev@incubator.apache.org>
> Reply-To: callback-dev@incubator.apache.org
> Subject: Re: Playbook cordova-js testing
>
> Yeah, benefit of all the stubbed out API in cordova-js which weren't
> there in 1.5 BlackBerry implementation.  Whether the implemented API
> actually work is the real question :-)
>
> On Thu, Mar 22, 2012 at 12:58 PM, Gord Tanner <gord@tinyhippos.com> wrote:
> > Current Status on PlayBook for cordova.js
> >
> > 1.5: 306 of 530 tests passed
> > cordova-js: 356 of 551 tests passed.
> >
> > Interesting that we have more passing but things
> > like navigator.device.capture is not working in cordova-js.
> >
> > Gord
> >
> > On Wed, Mar 21, 2012 at 4:34 PM, Drew Walters <deedubbu@gmail.com>
> wrote:
> >
> >> 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 <deedubbu@gmail.com>
> 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 <fil@adobe.com> wrote:
> >> >> Beat me to it Gord ;P
> >> >>
> >> >> On 3/21/12 12:43 PM, "Filip Maj" <fil@adobe.com> 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" <deedubbu@gmail.com> 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?
> >> >>>
> >> >>
> >>
> >
> >
> >
> > --
> > Gord Tanner
> > Senior Developer / Code Poet
> > tinyHippos Inc.
> > @tinyhippos
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message