Ahh dang. Hopefully for 1.7 then, but we're awfully close. On 3/29/12 5:55 AM, "Drew Walters" <[email protected]> wrote:
>For the record, here are the mobile-spec results I received for >various OS levels while developing my branch for the cordova-js merge >(* indicates actual device, others are simulators): > >OS Level Model Result >-------------- --------- ---------- > 5.0.0.713 9550 698-736 > 6.0.0.246 9800 760-776 >*6.0.0.600 9800 763-789 > 7.0.0.540 9810 761-776 > 7.1.0.130 9860 763-776 > >Failures were reviewed to confirm they were expected failures that >pre-existed the cordova-js merge (compass, media, storage, etc.). >There are more passing/executed now then before the cordova-js merge >but this is mainly due to API's existing (compass, media, etc.) which >did not before, even though those API's have no native implementation >behind them. > >On Wed, Mar 28, 2012 at 8:33 PM, Drew Walters <[email protected]> wrote: >> Correct. I'm not committing the Cordova-js blackberry merge until we >>have >> playbook at a state that matches 1.5. >> >> On Mar 28, 2012 7:47 PM, <[email protected]> wrote: >>> >>> I know he mentioned that blackberry was fine but playbook still needs a >>> little work. >>> >>> I have a few commits to playbook locally but still feels a little off. >>> >>> Gord >>> ------Original Message------ >>> From: Tim Kim >>> To: [email protected] >>> ReplyTo: [email protected] >>> Subject: Re: Tag BlackBerry for 1.6.0rc1? >>> Sent: Mar 28, 2012 8:34 PM >>> >>> > >>> > If so: dude. Rad. MERGE THAT SHIZZLE IN AND TAG RC1!!! >>> >>> I'm afraid I cannot just yet - I cannot commit so ya. Also, I think I'd >>> like to know what Drew thinks because it's pretty much all of his >>>commits. >>> >>> >>> Sent on the TELUS Mobility network with BlackBerry
