The Blackberry container is a standard Blackberry native UIApplication implemented under OS6. Its implementation includes the following aspects:
The ICEmobileContainer class is the main UIApplication subclass for the device container and presents the web application interfaces in a BrowserField instance. Configurable aspects in the BlackBerry Container include:
The BlackberryOptionsProvider class implements the OptionsProvider interface and is responsible for populating a Screen subclass (provided by the system) with the widgets required to edit and display the properties exposed by the BlackberryOptionsProperties class. The Blackberry ICEmobileContainer fetches the value of the properties from the Persistable class and uses them to configure operations both during startup and when notified by the OptionsProvider that the Options have been saved. The following stock preferences are supported:
The RIM BrowserFieldHistory object supports the notion of back/forward various page counts, but doesn't support displaying the URLs so we have implemented a HostoryManager that supports the last 10 URLs visited.
The ICEmobileContainer performs no specific branding of the container view itself, so all branding of the UI is achieved in the web application. The following elements of the container can be modified to brand the native container application. The Eclipse project manages the standard Blackberry application description file: BlackBerry_App_Descriptor.xml and therein are some branding aspects:
The ICEmobileContainer build environment is based on the Blackberry Java development plugin for Eclipse. This plugin allows the creation of Blackberry projects with HelloWorld applications, project continuous build and deployment in either the simulator or device menu choices. Debugging can be done in either the simulator or an actual device (with limitations). Network transport is achieved in the simulator via an MDS simulator available in the SDK.
The device container lives in the directory mobi/client/blackberry/container.
No such concept in Blackberry. The script classes for all integration libraries are included in all projects.
Application deployment is done through project specific menus in Eclipse. Project signing is performed by applying to RIM for project signing keys as described here and, once they arrive from RIM, installing them into Eclipse. The signing itself is done through project specific menus in Eclipse which is part and parcel of installing to a device.
© Copyright 2016 ICEsoft Technologies Canada Corp.