The RCP Browser component is based on the DOM Browser. The Web Browser is an easy to embed in any UI application based on the Lotus® Expeditor client. The design of the RCP Browser focuses on Web page rendering, and provides useful enhanced functions. Further, it provides a flexible way to allow applications to create a Web browser by default or specify different back-end browsers available for use with the Lotus Expeditor client.
Back-end browser support
This section details which platforms contain back-end browser support.
Table 1. Back-end browser support
|Windows® Platforms ||IE_SERVICE |
|Linux® Platforms ||XULRUNNER_SERVICE |
|Mac OS X (Intel®) ||XULRUNNER_SERVICE |
Creating browsers with a specified back-end browser
You can create a generic Web browser with a default back-end browser, based on Windows Internet Explorer or the XULRunner runtime on other supported platforms. You can also create a Web browser with a specified back-end browser that invokes the WebBrowser
When you implement a specified back-end browser using the WebBrowser
constructor with WebBrowser
, it has the following features:
- IE_SERVICE style to base the browser on Internet Explorer
- IE_SERVICE_WITH_APPLET style to base the browser on Internet Explorer and also support an Applet
- XULRUNNER_SERVICE style to base the browser on XULRunner
The administrator can also specify the back-end browser before Lotus Expeditor starts with a preference in the plugin_customization.ini
file. The preference key is com.ibm.rcp.browser.service/BackEndBrowser
. The value can be any of the following:
You can display Web pages (HTML/DHTML(CSS/Script), XML) and plug-ins (Applet/ActiveX/Flash/PDF).
Basic browser control and event handling
The browser supports basic control methods and event handling. These features include:
- Title changing events
- New window events
- Document loading complete events
- Close window events
- Progress changing events
- Status changing events
- Context event (XULRUNNER_SERVICE only)
- Download events
- Visibility changing events
W3C DOM accessing
You can use the W3C DOM APIs (org.w3c.dom, org.w3c.dom.*
) to manipulate the DOM tree after the HTML page loads, by querying the org.w3c.dom.html.HTMLDocument
object reference from the RCP Browser control.
Refer to Using and enhancing an RCP Browser
for samples and use cases for enhancing the RCP Browser.
More browser functions
This section details additional functions of the RCP Browser.
- Single-Sign-On (SSO): Support to set cookie strings to current RCP Browser control, and allowing Single Sign-On (SSO) with the server
- History control: Support to query and navigate with history data
- Proxy support: Support to set the proxy for the RCP Browser
- Print support: Support of general print/print preview functionality for RCP Browser content
Parent topic: Implementing an RCP browser: XPD622