Overview

The Overview tab of the project editor summarizes all of the settings you specified when you created your project.

The General Information section contains the project name and description, the chosen template and theme, and the date last modified.
Note:
A theme is not displayed for projects optimized for mobile devices. For more information, see Developing HATS applications for mobile devices.

Click the link for the current theme to change the project theme. Four options are provided, Standard, Modern Web application (Web-only) or Modern UI application (RCP-only), Classic terminal emulator, and Custom. Each function in the list of settings can be enabled elsewhere in the project settings. This list provides a convenient method of setting the functions in one place that together can be treated as a theme for the appearance and behavior of your application.

The following table shows how each theme setting maps to an individual project setting.
Table 1. Theme setting to project setting map
Theme Setting Project Editor Tab Project Setting
Arrow key navigation (RCP-only) Other Client settings > Enable arrow key navigation
Automatic field advance Other Client settings > Enable automatic field advance
Cursor positioning on protected fields Rendering Widgets > Field > Allow cursor positioning on protected fields
Field extended attributes Rendering Widgets > Field > Enable extended attributes
Host keypad Rendering Host keypad > Show default host keypad
Keyboard support Other Keyboard support > Enable keyboard support
Operator information area Rendering Operator information area > Show OIA
Overwrite mode (initial) Other Client settings > Overwrite mode (initial)
Rendering using monospaced font Rendering Widgets > Field > Render using monospace font

The Standard theme enables the functions that are enabled by default when a HATS project is first created. Selecting the Modern theme deselects all of the individual functions. Selecting the Classic theme selects all of the functions. Selecting the Custom theme allows you to select any other combination of functions.

Note:
For more theme settings when using DBCS support see Project theme settings.
The Testing section contains links that can be used to test your project. For HATS Web projects the links are:
  • Launch on WebSphere® Application Server
  • Launch on WebSphere® Application Server in Debug mode
For HATS rich client projects the links are:
  • Launch on target platform
  • Launch on target platform in Debug mode
Note:
  1. Clicking either of these links will perform the same operation as if you right-click on your project in the HATS Projects view and select either Run on Server (Run if rich client) or Debug on Server (Debug if rich client).
reh: V7 CLD Toolkit SDC Improve RunOnServer of HATS portlets removed portlet testing statement-->For more information about testing HATS portlets see Testing HATS portlets. -->

The Deployment (RCP-only) section includes a Target platform drop-down. Use this drop-down to change the target deployment for your rich client project. This allows you to start building an application targeted for one platform and switch to a different platform at a later time. Supported platforms are Eclipse Rich Client Platform, Lotus Expeditor Client for Desktop, and Lotus Notes.

If you change the target platform here, and it does not match the target platform of the workspace, a message is displayed informing you of this. The action to take in this case depends on which platform you have changed to for this project.

If you changed to a Lotus Notes® or a Lotus® Expeditor Client platform, see Configuring the target platform for information about setting the target platform.

If you changed to the Eclipse Rich Client Platform, select Window > Preferences > Plugin-in Development > Target Platform and select your Rational® SDP installation directory (the default is C:\Program Files\IBM\SDP) from the Location drop-down list.

When prompted to reload the target platform, select Yes.

Also in the Deployment section is a link, open the plug-in manifest, that launches the editor for the plug-in descriptor (plugin.xml) of the project. Advanced rich client development will require modifications to this file.

The Connections, Rendering Settings, and Other Settings sections summarize the settings specified on each of their corresponding tabs. The headings themselves are links to their corresponding tabs which are described in sections that follow.