Project contents

When you create a HATS rich client project, you are prompted to select a target platform. This selection indicates where you plan to deploy the application. The differences between a project targeted for deployment to Eclipse RCP and Lotus Notes® or Lotus® Expeditor Client are minor. The following characteristics are common to every HATS rich client project:

• Project structure including templates, transformations, images, Java™ source, macro handlers, macros, and screen captures folders
• HATS-specific project artifacts including the application.hap file, connection files, and event files
• The ComponentWidget.xml file, which is the component and widget registry file
• The plugin.xml file with one view, the transformation view, registered in it
• Plug-in dependencies on runtime plug-ins
• A Perspective class, included in the HATS RCP Runtime Extension project, responsible for laying out views on the page. See HATS RCP Runtime Extension project.

Addition for projects targeted for deployment to Eclipse RCP:

• An Application class, included in the HATS RCP Runtime Extension project, because Eclipse RCP requires an application to launch. See HATS RCP Runtime Extension project.

Additions for projects targeted for deployment to Lotus Notes® and Lotus® Expeditor Client:

• Registrations for the application switcher entry in the plugin.xml of the HATS RCP Runtime Extension project. This allows a user to launch the HATS application from the application switcher in the Lotus Notes® and Lotus® Expeditor Client environments.
• Key bindings for the Lotus Notes® platform in the plugin.xml of the HATS RCP Runtime Extension project. This allows a user to have key mappings defined for use in the Lotus Notes® environment.