Forgot your password?

RIM’s WebWorks Development Tips and Tricks for the PlayBook

WebWorks Compile

Over the past few days we have pointed out a few concerns developers, including myself, have run into with setting up the PlayBook development environment. Tim Neil over at the official BlackBerry Blog was kind enough to share his tips and tricks for how to quickly get up and running developing WebWorks apps for the BlackBerry PlayBook. He shares a batch file to help speed up the compiling and deploying of the app which is nice for those of you who prefer that. The examples are windows based but the ideas are not too different on a Mac but you will not be able to use the batch file.

Check out the tips and tricks at this link

1 comment on this postSubmit your comment!
  1. I’ve been working on a game for the PB (built using sencha touch – incredible framework!). I’ve been testing locally on Chrome, as the rendering is the same as the Playbook’s webkit browser and I’m not yet using any of the (rather limited) PB-specific API.

    Last night – prompted by the blog post referenced above – I decided to finally build/test on the Playbook itself. I already had installed the SDKs and simulator, so I followed the step-by-step for the deployment batch. It took me about 5 minutes (including writing the batch file itself) to get the game deployed to and running on the simulator. Subsequent updates took seconds only.

    A couple of caveats:
    * don’t forget you have to create a config.xml and include it in your zip file (docs here:
    * If you use the BB phone config.xml docs, it refers to a rim:maxcache element. If you use that element, your app won’t compile.)

BlackBerry© is a registered Trademark of BlackBerry Limited. BerryReview is in no way affiliated with BlackBerry Limited though sometimes their lawyers send us love letters...

Copyright © 2007-‘2018’ BerryReview LLC