Difference between revisions of "RAP/Mobile Browser"
|Line 21:||Line 21:|
=== Android ===
=== Android ===
Revision as of 06:11, 1 April 2011
RAP on Mobile Devices
There is a common look and feel, as well as certain features, that most mobile applications have in common, even across different platforms. RAP should, within its capabilities, aim to conform to those. As of RAP 1.4M6, support and features for mobile devices are still somewhat limited. See this bug for a complete overview of planned improvements. General future topics (they are not fixed planning-items) include:
- Providing a new custom-theme that looks less alien on mobile devices. All existing themes (default/fancy/classic) are designed to look similar to SWT on desktop operating systems, especially MS-Windows. This new theme would be more "inspired" by the look of MacOS and iOS. An special version of this theme could also increase paddings and dimensions for widgets to be more touch-friendly.
- Providing touch-features. Currently all interactions on touchscreens are translated into mouse-events. However, this approach is somewhat limiting since there are severe differences between an touch interface and a mouse/keyboard interface. Events like mousemove and mouseover have no generally counterpart in a touch-interface, and features like multitouch are not possible to translate into mouse-events. Since SWT now has a Touch-API, one possible solution would be to implement this, other would require custom-widgets specifically designed for mobile devices.
- Improving general performance. Mobile devices are less powerful than current desktop-PCs, and RAP applications are very demanding for a web-application. Startup-time, render-time and animations could be better. However, with the current client, which aims towards to bring the full SWT feature-set to desktop-browser, there is limited room for improvement. See next point.