BlackBerry WebWorks SDK for Tablets

These release notes are for BlackBerry WebWorks SDK for Tablets 2.2.

New in this release

Feature Description

application signing

The process for signing your BlackBerry WebWorks applications has been updated.

tablet simulator

The BlackBerry WebWorks SDK includes the latest BlackBerry Tablet OS SDK.

file save and read support

The blackberry.io.file API now includes support for saving and reading files.

blobToString and stringToBlob support

The blackberry.utils API now includes support for blobToString and stringToBlob functions.

Features

Feature Description

compile, run, and sign BlackBerry WebWorks applications

You can compile and sign BlackBerry WebWorks applications from a command prompt and run them using the BlackBerry Tablet Simulator.

customize applications

You can customize many aspects of your applications by setting screen orientation, using a splash screen, foreground and background colors, screen transitions, swipe gestures, and custom icons. You can also choose what category to display your application under.

set application security and permissions

You can use permissions to enable access to external features and domains, to add functionality to your applications. You can also turn the security capabilities of the device on or off for your application.

produce output for distribution

The BlackBerry WebWorks Packager produces output that you can use to distribute your applications from the BlackBerry App World storefront.

use JavaScript extensions

You can create JavaScript extensions to enhance your applications by adding them to the application archive before you compile the application source. You can change and distribute these extensions.

support for BlackBerry App World services

The BlackBerry WebWorks SDK is architected to support BlackBerry Services APIs in future releases.

enable web inspector

When you package your application, you can enable access to information about elements in the application. You can display this information by using a desktop browser that uses web inspector functionality and accessing the application information directly on the BlackBerry PlayBook tablet.

open source support

The BlackBerry WebWorks Packager and JavaScript extensions are available on GitHub. You can create or modify extensions, view and modify the BlackBerry WebWorks Packager, and contribute to the open source community.

support for many APIs

Include in-App payment services in your application, invoke the camera to take pictures or video and return file path information, invoke the microphone to record audio and return file path information, access the device PIN, check file properties, and access the file system to store, read, write, delete, or copy files.

support for RESTful services for File API

You can choose whether to call BlackBerry WebWorks APIs through JavaScript or AJAX.

This feature is not available for Camera, Microphone, and Payment APIs.

Fixed issues

  • While working in Portrait mode in BlackBerry WebWorks SDK, if you use the zoom and pan functions on a page that is user scalable, the page no longer renders incorrectly. (1456348)
  • Running the script blackberry.invoke.invoke(blackberry.invoke.APP_PHOTOS) now invokes the photo application correctly. (1403593)
  • The splash screen image no longer disappears before the first view of your BlackBerry WebWorks project is added to the stage. (1402770)
  • The debugging mode application no longer crashes if you have another debugging mode application running at the same time.(1246434)
  • Embedded video is no longer obstructed when you scroll the page it is displayed on. (1239665)

Known issues

Issue

Workaround

For BlackBerry WebWorks SDK and Adobe AIR SDK 3.0, Web Inspector does not work properly in the Google Chrome browser. The Web Inspector appears, but no resources are loaded. (2090047)

Use the Safari browser and BlackBerry PlayBook 1.07 software.

Application signing does not work properly if you are using JDK 1.7. Attempts to sign a package will fail. (2089194)

Roll back your JDK to version 1.6. Alternatively, from the bin folder of the JDK, find the msvcr100.dll file and copy it to the bbwp\blackberry-tablet-sdk\bin\ folder.

The Adobe Flash Builder ExternalInterface call does not work for embedding media in BlackBerry WebWorks applications. (1889388)

None

In portrait mode, zoom and pan actions on pages set as user-scalable might cause the page to render incorrectly. (1456348)

Exit and then restart the application.

The BlackBerry PlayBook tablet simulator that is bundled with the BlackBerry Messenger SDK cannot recursively delete folders when the webworks://blackberry/io/dir URI API is called.(1436874)

None

Switching the orientation of the BlackBerry PlayBook while the splash screen or loading screen is running causes the scrolling and HTML elements in the application to be unresponsive.(1426343)

None

The compiling process freezes if you do not specify the cskpassword.(1425720)

Specify cskpassword before compiling in order for the barsigner error to appear.

The page permission dialog appears when the Geolocation API from an external server is called. (1422959)

None

The default icon does not appear when a large custom icon is specified.(1419333)

None

When you use blackberry.invoke.invoke(blackberry.invoke.APP_VIDEOS) to start the Video application, the following message appears: "Cannot open the file. Please check the file permissions and try again." After you close the dialog box, the Video application starts normally. (1237080)

None

During installation, in Mac OS, the default path is displayed as Research In Motion. The specific path should be displayed as /Developer/SDKs/Research In Motion. (1230810)

None

An error occurs if you specify a value greater than 25 characters in length for the name element. The BlackBerry WebWorks Packager does not currently check this length when you package your application. (1200106)

Ensure that you specify a value of 25 characters or less for the name element.

An error occurs if you specify a value greater than 18 characters in length for your application archive (.zip file) file name. The BlackBerry WebWorks Packager does not currently check this length when you package your application. (1200055)

Although the error occurs if the file name is 18 characters or more, the .zip file must be 10 characters or less. Use a file name that is no longer than 10 characters.

In the config.xml file, if you specify an image file that is either incorrect or missing in the application archive file, an Unknown Source exception appears when you package the application. (1198688)

Ensure that you specify the correct name for images you reference in the config.xml file, and that the images exist in the application archive.

When you attempt to sign your application, signing might fail with the message Cannot sign application - failed to find signing keys, if you specified incorrect parameters when you set up signing. For example, when you set up signing, if you specified the following using .pl2 (with a lowercase L instead of a 1) for the output file:

blackberry-keytool -genkeypair -keystore sigtool.p12 -storepass <p12password>
 -dname "cn=<company name>" -alias author

packaging would subsequently fail. (1197063)

Ensure that you correctly specify the output file (and other parameters) when you set up signing. Also, use the specific path (bbwp/bin) for the output file.

BlackBerry WebWorks APIs are not supported in framesets or frames. (1092004)

None

Last modified: 2013-08-14