BlackBerry 10 WebWorks SDK
Release: BlackBerry 10 WebWorks SDK 188.8.131.52
The BlackBerry 10 WebWorks SDK offers support for developing applications for the BlackBerry 10 OS. You can test BlackBerry WebWorks applications using the Ripple emulator and the BlackBerry 10 Dev Alpha simulator. The BlackBerry 10 WebWorks SDK does not include the simulator. See Installing and Configuring the Simulator for information on installing the BlackBerry 10 Dev Alpha simulator.
Porting apps from BlackBerry PlayBook OS to BlackBerry 10
BlackBerry WebWorks applications packaged for the BlackBerry PlayBook OS must be repackaged for the BlackBerry 10 OS using the BlackBerry 10 WebWorks SDK. This might not be obvious because for both platforms the output from the packaging process is a .bar file. However, a .bar file that was created for the PlayBook OS will not work on BlackBerry 10.
For more information, see Porting apps from the PlayBook OS to BlackBerry 10.
New in this release
Support for physical keyboard: The BlackBerry WebWorks SDK now provides keyboard support for the Dev Alpha C device with physical keyboard. You can access keyboard events on the Dev Alpha C device using the DOM 3 KeyboardEvent interface.
Support for the Payment Service SDK : The BlackBerry WebWorks SDK now supports the Payment Service SDK. The Payment Service SDK provides a set of classes that allow you to connect your application with the Payment Service, which processes the purchases that users make in the BlackBerry World storefront. You can use these APIs to create a highly secure and consistent purchase experience that permits users to make purchases without leaving your application.
Support for BBM profile boxes: The BlackBerry WebWorks SDK now supports the BBM Profile Box API. The profile box is a customizable box for your app that appears in the current user's BBM profile. You can use it to broadcast achievements or provide updates. The box contains a list of items, each composed of text and an optional icon. The Profile Box API allows you to manage the items in your app's profile box.
Changes to the handling of popups: The BlackBerry WebWorks SDK has changed the way popups are handled. Previously, all popups were blocked. Now, popups are displayed in a child browser window by default. To prevent a WebWorks app from displaying popups without user intervention, you must enable the popup blocker in the config.xml file.
A new parameter (<param name="popupBlocker" value="enable">) is available to allow you to enable the popup blocker. For information, see the <param> element.
BlackBerry WebWorks apps can now access personal contacts created in the Contacts application.
If a BlackBerry WebWorks app uses an external page as the start page, and the config.xml does not have the appropriate <access> element defined, the page is now opened in a child browser window.
Text is now correctly displayed in dialog boxes.
If you add multiple context menu items with the same name property, BlackBerry WebWorks now properly handles the error.
BlackBerry WebWorks Packager
The WebWorks Packager shows incorrect usage for the bbwp command.
The WebWorks Packager will successfully package a WebWorks application even when the config.xml file contains an invalid <access> element with an empty uri attribute. For example: <access uri="" subdomains="true"></access>
A packager exception occurs if the <action> or <mime-type> elements are empty.
Workaround: Ensure that these elements are not empty.
The packager does not indicate whether the Web Inspector has been enabled.
When you close an application while a battery event listener is running, an error occurs.
The packager does not produce verbose messages when you specify the -v or --verbose option.
An unclear error message is displayed during packaging when you specify the -v or --verbose option.
If you specify -v during packaging, the version number always displays as 184.108.40.206.
If you specify an archive name with the extension .zip.zip, an error does not occur during packaging.
Workaround: Ensure that the extension for your archive file name is not duplicated.
BlackBerry WebWorks Framework
blackberry.pim.calendar.findEvents() does not return any events when events are sorted by location.
When an extension lists another extension as a dependency, that extension's client file is not loaded.
Image Cropping with the FilePicker Card is not working as expected in WebWorks applications.
getUserMedia() is not working as expected in WebWorks applications.
There are behavioral inconsistencies with whitelisting when trying to access a file from the local file system.
You can not currently access the BBM profile picture of other users with the BBM API.
When launching a WebWorks application on the simulator with Web Inspector enabled, the Web Inspector IP address is not displayed in the alert dialog.
BBM API does not work on the simulator.
Clicking an unknown protocol link can cause some APIs to no longer work as expected.
The context menu cannot share a link title.
blackberry.event.registerEvent should not be public.
BBM Social Platform
When a C-only app uses the BBM Social Platform APIs, the compiler requires additional non-C libraries to be added manually (libQtCore and libcpp).
If BBM Connect (Settings -> Security and Privacy -> Application Permissions) for an app is turned OFF before launching the app, toggling BBM Connect doesn’t update the registration status of the app.
Workaround: Turn BBM Connect ON before launching the app.
When BBM Connect (Settings -> Security and Privacy -> Application Permissions) is toggled from ON to OFF or from OFF to ON, the registration and permission states are not updated.
Images that use transparency might not appear correctly in the user's list of BBM applications.
Last modified: 2013-04-25