Remapping keys for HATS rich client applications
In the rich client environment, default keyboard mappings are defined in the plugin.xml file of the HATS RCP Runtime Extension plug-in and apply to all HATS rich client applications running in the same environment.
An Eclipse keyboard context is used to influence what commands
are available to the user at any given moment. When a user is using
a HATS transformation view, the HATS keyboard context is used. This
context is registered in the plugin.xml file
of the HATS RCP Runtime Extension plug-in.
The following example shows how this appears:
<extension
point="org.eclipse.ui.contexts">
<context
name="%KEYBOARD_CONTEXT_NAME"
description="%KEYBOARD_CONTEXT_NAME"
id="com.ibm.hats.rcp.transformationContext"
parentId="org.eclipse.ui.contexts.window">
</context>
</extension>The default keyboard mappings are also defined in the plugin.xml file.
The following example shows how a key mapping for
a HATS application running in Eclipse RCP or Lotus® Expeditor appears in this file:
<extension
point="org.eclipse.ui.commands">
<category
name="%COMMAND_CATEGORY_NAME"
description"%COMMAND_CATEGORY_NAME"
id="com.ibm.hats.rcp.transformationCategory"
</category>
<command
name="[pf1]"
category="com.ibm.hats.rcp.transformationCategory"
id="com.ibm.hats.rcp.send_[pf1]">
</command>
...
</extension>
<extension
point="org.eclipse.ui.bindings">
<key
commandId="com.ibm.hats.rcp.send_[pf1]"
contextId="com.ibm.hats.rcp.transformationContext"
configuration="org.eclipse.ui.defaultAcceleratorConfiguration"
sequence="F1"
</key>
...
</extension>The key bindings for running in Lotus
Notes® are separate
from the other key bindings. The equivalent key binding for the previous
example would be:
<key
commandId="com.ibm.hats.rcp.send_[pf1]"
contextId="com.ibm.hats.rcp.transformationContext"
schemeId="com.ibm.workplace.notes.hannoverConfiguration"
sequence="F1"
</key>