Setting data for generation into the WML file involves completing several forms with the data appropriate to each named tag. Almost all the data is string (text) or boolean (on/off) data; there are a few items that are lists of strings.
The Edit menu provides several options, each of which is shown on the BX Object Packager Toolbar. Each menu item corresponds to one of the major portions of the WML file. (Refer to Chapter 8--Modifying the WML File for more detailed information, or use the Help menu or the F1 key for context-sensitive help information.)
Selecting a menu item to display the Editor Selector, a list of previously defined values of this type, if any, as shown in the following figure:
Figure 2. Editor Selector with Two Classes Defined
To add a new item, use one of the following methods:
The primary screens are for Classes and Resources. Refer to "Changing Class Information" and "Changing Resource Information" for more information about using these screens. In general, the most important information is presented first.
Typically, only information marked with an asterisk is required, although your particular objects might demand additional specifications.
The data screens are designed so that you can back out your changes without modifying the data. The "Cancel" option restores items to their previous settings without affecting the saved data. You can then reselect the item to edit its associated data.
Note: These screens use the Return key as a signal to save the data and to unpost. You should use the Motif traversal mechanisms (the tab key and the arrow keys, or clicking with the mouse) to move keyboard focus within the window.
The Class Values editor allows you to define how the Builder Xcessory manipulates the widget or component. You can define resources, automatically-created children, and valid children.
In addition, you can define resources. For widgets and gadgets, there are often many resources. If you have the library containing this widget or gadget class in the shared-library form that the Builder Xcessory can load automatically, and are not on SunOS 4, then you can use the Builder Xcessory Object Packager to load the initial resource definitions directly from the library, rather than enter them all by hand.
To load a library, use the following procedure:
The Builder Xcessory Object Packager uses the same search path as the Builder Xcessory, so you can probably specify just the name of the library without specifying a full path to it. When you continue to the next item, you will be asked for confirmation about loading the widget or gadget class from the library.
Note: Because Xt modifies widget classes when they are initialized in such a way that the original information in the widget or gadget class cannot be reconstructed, if you load a library that the Builder Xcessory Object Packager itself uses, you will see best-guess data.