Softpedia >Windows >Programming >SDK/DDK >BlackBerry 10 WebWorks SDK >  Changelog

BlackBerry 10 WebWorks SDK Changelog

What's new in BlackBerry 10 WebWorks SDK 2.0.0.54 Beta

Nov 28, 2013
  • BlackBerry WebWorks GUI:
  • The new BlackBerry WebWorks GUI interface makes the development process easier and faster than ever. You can now create and build your app, set its preferences, and deploy it to simulator or device without using the command line.
  • Plugins:
  • The alignment with Apache Cordova has changed the way APIs are added to your app. You will need to add plugins, which represent an API or set of APIs, to add features to your app. BlackBerry WebWorks SDK 2.0 contains Cordova plugins for standard mobile features and custom BlackBerry WebWorks plugins for BlackBerry-specific functionality.
  • BlackBerry ID Token:
  • The BlackBerry ID Token is now used for signing, which aligns your keystore to your BlackBerry ID account. Your BlackBerry ID token is all you need to sign your app and create a debug token.
  • Simplified Build and Deploy Process:
  • You can now build your app and deploy it to a device or simulator in a single step. If you need a debug token, the tools will take care of that for you too.

New in BlackBerry 10 WebWorks SDK 1.0.4.11 (Feb 13, 2013)

  • 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 () is available to allow you to enable the popup blocker.
  • Fixed issues:
  • 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 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.

New in BlackBerry 10 WebWorks SDK 1.0.3.8 Beta (Nov 29, 2012)

  • New in this release:
  • webworks.js bundled with app: The BlackBerry WebWorks Packager now automatically bundles the latest webworks.js file as chrome/webworks.js. You must include in your web pages
  • Packager accepts folder location and .zip file: The BlackBerry WebWorks Packager now allows you to specify either your application's .zip file or the application's folder location as input. You can also use a .bbwpignore file to exclude certain files and patterns from the packaging process. For more information
  • rim:header attribute supported for BlackBerry 10: The element supports a new attribute, rim:header. The rim:header attribute is an optional attribute that allows you to specify HTTP header text that is added to every HTTP request made by the application. This allows you to differentiate the request from those requests coming from the BlackBerry Browser, enabling you to respond to the request differently based on the source application
  • You must set the appropriate permissions to use webkitGetUserMedia(): To use the HTML5 webkitGetUserMedia() method to access the device's camera and microphone, you must set the use_camera and record_audio permissions in your config.xml file.
  • Support for child browser windows: There is now support for opening a browser window from within a BlackBerry WebWorks application. This feature can be used to request authentication on behalf of a third party, which is often displayed in a new tab or window. Using window.open() or specifying an anchor target of _blank causes a secondary browser window to open on top of the WebWorks application. This feature allows WebWorks applications to support the common use case in which embedded content from a third-party site or service launches a new window to request credentials. Support for this feature is enabled by default. A new parameter () is available to allow you to disable support for child browser windows.
  • Support for toasts: WebWorks applications now support toasts. Toasts are simple messages that popup for a specified period of time and then automatically disappear without any interaction from the user.
  • Additional support for sensors: The WebWorks SDK now includes the Sensors API. This API provides programmatic access to all device sensors that can not be accessed using HTML 5 APIs. You can retrieve sensor data from the accelerometer, gyroscope, light sensor, magnetometer, and rotation sensor, among others. You can use these readings to make your apps responsive to a wide range of user and environmental input.
  • Changes to the orientation feature: There has been a change in the syntax that is used to set the orientation in the config.xml file.
  • Additional programmatic support for orientation: The WebWorks SDK now provides support for controlling the orientation of your WebWorks application programmatically. Previously, orientation was specified exclusively through the config.xml file. You can now control orientation programmatically as well, using blackberry.app.lockOrientation() and blackberry.app.unlockOrientation().
  • Localization support for config.xml elements: The and elements in the config.xml file now support the xml:lang attribute. This attribute allows you to specify the language associated with these elements, allowing you to provide localized versions of these elements.
  • Support for system permissions: WebWorks applications now support system permissions. System permissions are identified using a new system attribute with the element in your config.xml file. Setting system="true" allows you to indicate that the permission you are defining is a system permission. Currently, the only permission that must be designated as system permission is _sys_use_consumer_push.
  • Fixed issues:
  • BlackBerry WebWorks Framework:
  • You could not close or minimize an application after the application receives a push notification.
  • Feature permissions specified on the config.xml file did not apply to embedded content.
  • BBM Social Platform:
  • If a user denied an app permission to connect to BBM when the app first launched, or changed the permissions in the global settings for the app, the app crashed.
  • When a user launched an app and the app attempted to register with the BBM Social Platform, after the user clicked Continue in the BBM Setup dialog, BBM did not launch.