BlackBerry WebWorks SDK for Tablet OS Beta3 now live!


BlackBerry PlayBook tablet

The BlackBerry® WebWorks™ SDK for Tablet OS Beta has been progressing very well, many thanks in part due to your continued feedback. If you haven’t done so already, please update to the latest Beta of the BlackBerry WebWorks SDK for Tablet OS. Important architectural changes have been implemented in v1.0.0.23 of the BlackBerry WebWorks SDK, so developers will need to re-compile existing applications using this SDK in order for them to successfully run on the new BlackBerry® Tablet OS simulator v.0.9.4.

What’s new in this release?

Our development teams have been very active since the last release, and have made some terrific enhancements in the capabilities, stability and performance of the Beta3 version of the SDK. Some notable improvements include:

  • Code signing enabled – you can now secure your application using the BlackBerry code signing process for BlackBerry Tablet OS. Learn more about signing your applications.
  • AJAX support for local context. This fix improves the quality of support for using AJAX to retrieve local resources. A benefit of this fix includes improved support on the BlackBerry® PlayBook™ tablet for JavaScript® frameworks like jQuery.
  • Loading screen image – Developers can define a loading screen and transition effect in their config.xml file to improve the user experience during application startup.
  • Major improvements in Mac support – Absolute paths now allowed in ZIP archive; _MACOSX folder no longer being included in BAR file; Format of bbwp command line arguments changed from “-“ to “/”.

As always, please refer to the release notes for information about what has been improved in the current release.

Installation Tips

If you do not have any previous version of the BlackBerry WebWorks SDK development tools installed, please follow the “Getting Started” guides for Windows® or Mac. Otherwise, existing developers are reminded that they must uninstall any previous versions of the BlackBerry WebWorks SDK for Tablet OS before upgrading. To make this step easy, you can find an “Uninstall BlackBerry WebWorks SDK for PlayBook.exe” utility within the /bbwp folder of the installation folder.

Adding additional versions of the BlackBerry Tablet OS simulator to VMWare® player is completed using the exact same steps followed when you first installed a BlackBerry Tablet OS virtual machine. As a friendly reminder, developers do not need to delete previous versions of the BlackBerry Tablet OS simulator. These can be kept installed in case you wish to troubleshoot behavior between the multiple BlackBerry Tablet OS versions.

Once you have updated to the latest version of the BlackBerry WebWorks SDK for Tablet OS, you can quickly restore code signing functionality simply by updating your file and generating the sigtool.p12 file, as documented in the Configure signing for tablet applications guide.

What to expect next

We’re not finished yet! Developers can continue to expect improvements to be added to the BlackBerry WebWorks SDK for Tablet OS in the coming weeks as we get closer to the BlackBerry PlayBook tablet launch date in the U.S and Canada.


If you have questions or concerns, discovered a bug, or even have a great idea for a new feature at any point in your development lifecycle, we want to hear from you! Whether positive or negative, we do want your feedback as it helps to make this platform great.

For questions or comments, send us a message via Twitter® or the Web Community Forums. For bug reports or feature enhancement requests, submit an item using the Developer Issue Tracker.

Join the conversation

Show comments Hide comments
+ -
  • Anonymous

    Hmm – isn’t this the update that was posted a few weeks back?

  • BlackBerry WebWorks SDK for Tablet OS Beta 3 now available | PocketBerry

    […] Read more >> […]

  • Jason Schroeder

    Should we re-package our Beta2 applications and re-submit to BlackBerry AppWorld?

    • Anonymous


    • Tim Neil

      Yes, WebWorks Beta2 applications need to be re-packaged and re-submitted to AppWorld. The version of the Tablet SDK used with Beta2 is not binary compatible with 0.9.4 and RTM of the PlayBook OS

  • M van Hylckama Vlieg

    Umm… I’m just as confused as Marc_Paradise here.
    What’s going on? 🙂

    • Tim Neil

      Hi there,

      This is simply a follow up post for those who may have not known that the Beta 3 SDK was available.

      If you already have Beta 3 of the WebWorks SDK you are good to go 🙂

  • Me

    Either RIM “re-announces” these old news items trying to get attention or they are just inept and clueless as to what’s already been released. Either way it’s sad.

  • Anonymous

    This blog post took a bit longer than expected to be published, and so is coming out later than we had hoped. Sorry for any confusion. Although similar to Tim’s post from a few weeks back, we wanted to take a moment to focus on the Beta3 release.

    The most important thing to note is that developers are highly encouraged to rebuild and resubmit their applications to App World whenever a new version of the WebWorks SDK for Tablet OS is released. Currently this is Beta3. If you have already done this, then no action is necessary.

    • Anonymous

      OK, thanks for clarifying

  • Second

    I agree with the other commenters. This post is very confusing. For future postings like this, it would help a great deal if you specify that you are referring to a version that’s been out for three weeks now (instead of “Beta3 now live!”).

    The information in the post itself is helpful, but it might’ve caused more confusion than clarity.

  • Berryreview

    Just as a follow up note. This part of the post:

    Format of bbwp command line arguments changed from “-“ to “/”.

    Is actually the wrong way around. Oh and the documentation at this link is still totally wrong:

    What I really am curious to know is why does code signing and packaging have to be such a “scratch your left ear with your right hand” approach? For example why must we uncomment this line which many developers are running into when they upgrade to a new beta:

    Better yet why MUST we increment the package ID for signing?

    Where do these requirements come from? Oh and don’t forget the command line code singing process requires you to enter yet another -BuildID… No Idea what that one does…

  • Jason

    I’ve tried to create an app to get approved for the free playbook offer… first it was rejected after I used beta2, while beta3 came out while my app was pending. Then rejected with a problem with my icon file. Is it 86×86 or 90×90? I know this is beta but having trouble with the information that is being released and the timing of it all. My app is back in the pending queue, but is it still eligible for the playbook offer?

  • David Shannon

    Ughhhh! waiting for yet another approval – if Rim want developers for PlayBook, why do they make us contend with this crap?

blog comments powered by Disqus