Java Reference
In-Depth Information
{
public void widgetSelected(SelectionEvent evt)
if (evt.widget.equals(urlCommand))
{
QueryDialog urlDialog =
new QueryDialog(shell, SWT.NONE, QueryDialog.STANDARD);
urlDialog.setPromptText("URL:", "http://");
browser.setUrl(urlDialog.open());
shell.redraw();
}
// handle "Back"
else if (evt.widget.equals(backCommand))
{
if (browser.isBackEnabled())
{
browser.back();
}
}
// handle "Forward"
else if (evt.widget.equals(forwardCommand))
{
if (browser.isForwardEnabled())
{
browser.forward();
}
}
}
...
WhentoUseeSWT
There are some considerations to be taken into account when choosing
to use eSWT instead of LCDUI. MIDP LCDUI has not been updated
with any significant improvements since it was designed, because it
must be available on low-end devices. For that reason, LCDUI does not
provide much support for the user experience of high-end devices, such
as Symbian smartphones.
On the other hand, although SWT was designed as a cross-platform
GUI toolkit and the embedded version aims to reach more mobile
platforms, eSWT is not defined by the JCP and remains a non-standard
API that is not supported by every mobile platform.
In summary, eSWT is a powerful option on Symbian smartphones,
which provides a rich and compelling set of UI components that can
be used as an alternative to MIDP LCDUI, provided that the Java ME
implementation supports it.
3.2.4 IAPInfo API
The IAPInfo API, which was introduced in S60 3rd Edition FP2, enables
Java applications to access information, such as:
•
Internet Access Points (IAP) information, such as ID, name, bearer and
service type
•
Destination Network information, such as ID, name and associated
access points
