One of the most notable features of the Scout Kepler release is the support for mobile applications. Scout’s mobile support is based on Eclipse RAP adding an (optional) device transformation component. This component adapts widgets to the target device at runtime.
Let us use the small bug viewer as an example application to show the out-of-the box mobile support provided by the Scout package.
The client application consists of a single form that lists the most recent bugzillas for a given project and assignee. In the Scout SDK, the complete UI model of the form looks as follows.
Comparing the model with the mobile screenshot (shown on the left) we can observe, that the table field is actually rendered as a list. Instead of showing the content of the 10+ columns defined in the model, the content of the first three columns is presented in each list item. Once the user touches a list item a form containing the content of all defined rows is presented (shown on the right mobile screenshot).
The main benefit of the example shown above is the possibility with Scout to write business applications that run on mobile browsers and as desktop applications with the same code base. Below, the same application is shown running with Scout’s SWT UI rendering component.
To play around with the iBug application you can get the sources from Github. Please don’t complain about the parsing of Bugzilla HTML content on the server, I have been fully convinced that this is bad. But – so far – nobody did step forward and provide an alternative implementation doing it properly.
In case you are new to Scout you may want to read the related article in the Eclipse Newsletter (you should be able to have a running hello world in less than 30′).