ICEmobile-Faces 1.0 Beta 3 Release Notes
Dec 22 2011
About This Release
ICEmobile-Faces 1.0 Beta 3 is the final Beta leading to ICEmobile
These Release Notes include the following sections:
ICEmobile 1.0 Beta 3 is available for download in the following formats:
The following new features have been added since Beta 2.
- timeSpinner component has been added for inputting time values.
- outputListItems component has been added for including lists in a list.
- timeSpinner and dateSpinner support native HTML5 controls in iOS 5.
- Single submit and mobi:ajax tag now supported on all input components.
- Play link provided in video output component for better compatibility of video playback.
- Android tablet style sheet has been added.
See complete component documentation in the wiki.
- Android 3.x-based tablets now supported.
- Improved page loading as result of C2DM notification
- Hardware acceleration toggle available in container preferences. Applies only to Android 3.x devices.
- ICEmobile-SX application provides device integration features to mobile Safari browser.
- Improved script extension loading mechanism eliminated the need to reload the application after any GET operation in browser.
- Refactored code to allow for quicker and easier third party extension/modification to the container.
See complete container documentation in the [wiki].
- Cloud Push detection mechanism has been improved.
- Cloud Push email connector now supports configuration of secure SMTP connections.
- Tools bundles now available for NetBeans and Eclipse. Both bundles are add-ons for their respective ICEfaces 3.0 tools bundle.
This release is based on ICEfaces 3.0 RC2, and inherits supported JSF runtimes, browsers, and applications servers from that release. See ICEfaces release notes for details.
- Google Android 2.2 or later
- Apple iOS 4 or later
- Blackberry Platform 6.0
- If your application uses camera, microphone, or camcorder and you wish it to work in both desktop and mobile environments, add
to the form. Note that desktop file upload is not currently supported for ajax-enabled controls, so the submit button for this form should be either h:commandButton or mobi:commandButton. For more advanced Ajax use see [Desktop Portability].
- timeZone support on timeSpinner may show values from different timezone for sample apps (tested using MST). Just using
which returns java.util.TimeZone.getDefaultID(); to get default timeZone of server.
- mobi:ajax support. Components which are naming containers (like Carousel) have limited use for mobi:ajax tag due to jsf findComponent method which will only search to the nearest naming container.
- geolocation not supported on blackberry devices in browser api
- HTML5 input page is ill-behaved on Android tablets when soft keyboard is used. Use of "Next" and "Prev" buttons may not result in proper input field focus, and submit button may not perform as expected. Additionally, scrolling window to show active input field is not occurring. If active input field is not visible, the correct keyboard for that input type may not be shown. This is a result of the composite component used for layout of scrollable panels in this application. Should be replaced with a non-composite component in next release.
- Again, with Android device, under certain conditions the first button press on a page may not perform as expected. A second button press will perform as expected. This problem occurs only once after initial page loading.
- HTML5 audio and video tags are not well supported prior to Android 2.3. Video and audio playback may not work on devices running Android 2.2 or earlier.
- Android 3.x tablets support HW acceleration, but there are know issues with it.
- With HW Acceleration turned off, scrolling of the web view may be erratic, causing the page to disappear sporadically.
- With HW Acceleration turned off, embedded HTML5 video tags will play the audio portion only.
- With HW Acceleration turned on, the page may not paint instantaneously when page updates occur. Touching the screen causes the paint to occur correctly.
- Changing cloud push credentials will only take effect after a page load occurs.
- Flash and zoom controls are not yet available on the Camera widget extension.
- Tactile feedback on camera and upload buttons (and various HTML5 elements) in the various camera screens is lacking. This can lead to multiple submission attempts (or none at all).
- On devices with a slide out keyboard, having the keyboard extended automatically puts the device in Portrait mode. The photo component depends on the Device.getOrientation method call to orient the thumbnail to the screen, so the thumbnail may be rotated incorrectly in this situation.
- In a related sense, the video camera widget sized at 640x480 does not show up fullscreen unless it's used in Landscape mode. This is similar to the RIM camera application where the the same aspect ratio is maintained.
- When using the video recorder, the user is asked for the following permission when using the video camera:
This appears to be a common issue on some devices when using APIs related to using the video camera in either recording or playback.
The aplication ICEmobile is attempting to reset the security timer [Allow][Deny]
Other uses of an API to reset the backlight timer cause this to occur, but the ICEmobile application does not use this API. If this question is asked repeatedly during normal use, it can be
disabled through the application permissions menu:
Options (wrench) -> Device -> Application Management -> ICEFaces Mobile Container -> Edit Permissions -> Interactions -> Reset Security Timer -> [Allow]
- Dongle can be attached to Blackberry device in "charge only" mode only if attempting to write to the filesystems. Camera and videocamera extensions wont work if user is trying to share filesystem with a desktop client.
- Simulator code is extremely slow and can be temperamental depending on simulator networking performance.
- When a video is displayed in the WebKit browser, it renders a black rectangle that persists after the container (and the browser) navigates to a new page. The user must reload the current page to force the browser clear the rectangle.
*Blackberry OS6 uses zxing version 6, which requires the user taking a photo. The container then applies a series of Java image processing operations on the resulting image. For a successful scan, QRCode must be well lit, and the photo taken from such a place that there is no reflection and the image is focusable (via autofocus). Also it seems that the image must be black/white as experience has showed poor results with green or red images.
- Some cosmetic issues exist with components in Eclipse design time view.
Open source community support is available at http://www.icemobile.org.
The ICEmobile community forums are available for questions, comments, or general discussions regarding ICEmobile.