The Activities available in the container are defined in the AndroidManifest.xml file.
ContainerPrefrences and HistoryList Activities can be included/excluded from the container application by including/excluding them from AndroidManifest.xml. If excluded, the Options Menu should be modified accordingly.
The ICEmobileContainer Activity is the main Activity for the device container and presents the web application interfaces in a WebView. There are a number of different aspects of the container that can be customized to meet application-specific requirements, including:
The ContainerPreferences Activity extends the standard PreferenceActivity. The set of preferences is defined in the XML file preferences.xml. The ICEmobileContainer implements the onSharedPreferenceChanged() listener. The following stock preferences are supported:
The HistoryList Activity implements a list of recently visited URLs and is based on a standard ListActivity. The size of the history list is set in the constructor, and is controlled by a constant in the ICEmobileContainer Activity.
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 ICEmobileContainer build environment is based on standard Android command line project management support, and utilizes the ant build tool. The source code is split into separate container and integration directories, with the device integration capabilities implemented as separate library projects under the integration directory.
The device container lives in the directory mobi/client/android/container. The debug version of the container can be installed on a device or emulator with the commands
Integration libraries to be included in the build are defined in the project.properities file.
Each of the device integration capabilities is included as a separate library project in the directory mobi/client/android/integration. An individual library can be built with the command
To deploy your customized Device Container in a production environment you need to follow the standard Android publication process. To build a publishable application, build the container using the command
This will produce an optimized and obfuscated .apk file, that must be signed before publishing the application. Signing is achieved using standard the Android signing process.
© Copyright 2016 ICEsoft Technologies Canada Corp.