!--a11y-->
The following example of the tableView Web control shows the different possibilities available for displaying information on different mobile devices. This example also makes it clear that the Web controls for each device are displayed correctly, without your having to develop special source code.
The Web controls are displayed for a specific device in such a way that they support the properties and characteristics of each device.![]()
For example, the same JSP source code contained in the tableView Web control, is displayed as follows on the following mobile devices (and emulators):
|
(1) Pocket-PC emulator |
(2) Palm emulation with Eudora Browser |
(3) WAP emulator |
|
|
|
|
|
JSP example: Source code |
|
<%@ page import="com.sapportals.htmlb.*,com.sap.mobile.htmlb.rendering.*, com.sapportals.htmlb.table.TableView,com.sapportals.htmlb.event.*" %> <%@ taglib uri="htmlb.tld" prefix="hbj" %> |
|
Weather data binding: Source code |
|
package com.sap.mobile.htmlb.test; import com.sap.mw.jco.JCO; import com.sapportals.htmlb.table.TableColumn; public class MobileJspBean { static Object[] colnames = { static int[] colprios = { // Properties: public TableViewModel getModel() { // Default constructor: String mimePath = "/mobilehtmlb/mimes/"; model = new MobileTableViewModel(strWeather, colnames, colprios); TableColumn col6 = model.getColumnAt(6); } } |
![]()

We used emulators to consider the display of JSPs. Emulators are programs that simulate the behavior of real devices. They are particularly well-suited to testing applications, above all if you do not have the device available.
As you can see, the example of the weather information table looks different on different browsers. However, it has been displayed on the screen according to the supported browser characteristics.

However, other WAP-enabled mobile telephones display tables differently (see isTableSupported Method of the ClientInfo Interface).
