Difference between revisions of "Build Environment Effort/HID List"
(Created page with '== The problem== GUI elements like controls, dialogs or windows and functions (commands, sometimes called "slots") in OOo have IDs. Such an ID is called "help ID" (HID). They can…') |
(→The problem) |
||
| Line 1: | Line 1: | ||
== The problem== | == The problem== | ||
GUI elements like controls, dialogs or windows and functions (commands, sometimes called "slots") in OOo have IDs. Such an ID is called "help ID" (HID). They can be used to assign help content to them or address them from the OOo testtool application. In the first case OOo uses the HID to create a help content URL and request the corresponding help text from the help content provider. In the second case the ID can be used to e.g. send commands from the testtool application to trigger some actions, e.g. "click" a button or execute a command. In the testtool application and the test scripts that are executed by it HIDs are strings, sometimes called "long names", inside OOo HIDs for commands (slots) are the same as in the testtool application, but HIDs for GUI elements are long integer values. In the same way the mentioned help URLs either contain the "long name" of a command or the numerical ID of a GUI element. | GUI elements like controls, dialogs or windows and functions (commands, sometimes called "slots") in OOo have IDs. Such an ID is called "help ID" (HID). They can be used to assign help content to them or address them from the OOo testtool application. In the first case OOo uses the HID to create a help content URL and request the corresponding help text from the help content provider. In the second case the ID can be used to e.g. send commands from the testtool application to trigger some actions, e.g. "click" a button or execute a command. In the testtool application and the test scripts that are executed by it HIDs are strings, sometimes called "long names", inside OOo HIDs for commands (slots) are the same as in the testtool application, but HIDs for GUI elements are long integer values. In the same way the mentioned help URLs either contain the "long name" of a command or the numerical ID of a GUI element. | ||
| + | |||
| + | Obviously OOo and the HID "customers" speak different languages and so a translator is needed. This translator is the famous (notorious?) "HID list", hid.lst. It defines a mapping from long name to numerical ID. If a test script contains a "long name" of a GUI element, the test tool "translates" it into the assigned numerical ID and uses it to address said GUI element. OTOH if a help is requested for a GUI element, the help content provider internally "translates" the ID in the help URL to find the content using the "long name". So far, so good. | ||
Revision as of 16:52, 12 November 2009
The problem
GUI elements like controls, dialogs or windows and functions (commands, sometimes called "slots") in OOo have IDs. Such an ID is called "help ID" (HID). They can be used to assign help content to them or address them from the OOo testtool application. In the first case OOo uses the HID to create a help content URL and request the corresponding help text from the help content provider. In the second case the ID can be used to e.g. send commands from the testtool application to trigger some actions, e.g. "click" a button or execute a command. In the testtool application and the test scripts that are executed by it HIDs are strings, sometimes called "long names", inside OOo HIDs for commands (slots) are the same as in the testtool application, but HIDs for GUI elements are long integer values. In the same way the mentioned help URLs either contain the "long name" of a command or the numerical ID of a GUI element.
Obviously OOo and the HID "customers" speak different languages and so a translator is needed. This translator is the famous (notorious?) "HID list", hid.lst. It defines a mapping from long name to numerical ID. If a test script contains a "long name" of a GUI element, the test tool "translates" it into the assigned numerical ID and uses it to address said GUI element. OTOH if a help is requested for a GUI element, the help content provider internally "translates" the ID in the help URL to find the content using the "long name". So far, so good.
