The Browser Options menu allows you to change the default language, modify the default language settings, set various user preferences, change information relating to the makefile integration with other tools, internationalization, and the importing of GIL files.
Choose Options from the Browser menu bar to display the following menu:
You can select the language for each application or change the default language at any time during your Builder Xcessory session.
Saves the selected language as the default language. The language is saved to the .bxrc file and becomes the default language when you perform a New operation or when you restart Builder Xcessory.
Displays the Generation Preferences dialog for the currently specified language. For each tab panel, you can choose the settings for the current project, or save the settings as default values (Save As Default) that are written to your .bxrc file. The default settings appear when you perform a New operation or restart Builder Xcessory.
The following sections describe the Code Generation Preferences dialog for each available language.
The C++ Generation Preferences dialog is divided into four tabs:
The following sections describe the options for each tab panel.
Click on the File Names tab to display the File Names menu of the C++ Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Directory Path field allows you to specify the directory into which generated files will be written.
The File Output Names field specifies the following files (defaults are in parentheses):
· Imakefile (Imakefile) is the imakefile that specifies C++ imake information.
· Makefile (makefile-C) is the C++ makefile.
· Class Tree Root (UIComponent) contains the root class from which all classes created in Builder Xcessory are derived.
· Main (main-C.C) initializes the Motif toolkit and creates your application's shell widgets and classes. Changing this allows you to use a different base class for your application components. Builder Xcessory creates an unrealized applicationShell and creates all topLevelShell children for all top-level windows. To modify the main-C.C file for your application, make your changes in the user code blocks. Any changes made outside the user code blocks will be overwritten in subsequent generations. To write your own main routine, disable subsequent file generation by unsetting the toggle.
· Constants (defs-C.h) contains pixmaps, declarations of constants, and global instances of widgets or classes used in the interface.
· Utilities (bxutils-C.C) contains convert functions.
· Callbacks (callbacks-C) contains any callback information for non-class widgets.
· App Defaults (app-defaults) is the file that includes all resources with app-defaults value set to App. The user can change an app-default resource value by editing the app-defaults resource file, overriding the file from a local resource file, or entering the toolkit option -xrm on the command line.
Click on the Application tab to display the Application menu of the C++ Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file. When you install your application, the app-default file name should be the same as the application class name.
The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications.
You can set the following toggle options:
· User-Specified Main Loop specifies a function to call rather than XtAppMainLoop.
· Initialize Localization Support supports whether or not to generate a call to XtSetLanguageProc in the application initialization. Calling this function enables support in X and Motif for non-English locales.
· Generate Derived Files generates an additional subclass for each user-defined class. If set, all application code must be written in the derived file. Default name is "class name"Derived.C.
· (Parented) Dialog Shell Initially Unmanaged toggles to manage Dialog Shells, such as XmDialogShell, in the main-C.C file.
· Use Old Style Constructor for backward compatibility. In previous versions of Builder Xcessory, constructors for user-defined classes created the interface, and the parent widget ID was passed as a parameter.
· Remove Overridden Exposed Callbacks removes the class callbacks when overridden. Otherwise both methods will be called.
· Don't Create Unmanaged Windows delays creation of unmanaged windows.
· Ignore Geometry Resources on Shells does not print shell geometry (x, y, width, height) in the output code.
· Delete Nested Classes in Destructor deletes nested classes created with a New operation inside the create method in the destructor.
Click on the Include Info tab to display the Include Info panel of the C++ Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Click on the Makefile tab to display the Makefile panel of the C++ Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Name of the target of the make executed when Make Application is selected from the Browser Project menu (default is main-C).
Setting the toggle option Don't Include Ungenerated Class Files excludes classes for which you disabled code generation (see Generate Class ) from the list of source and object files that comprise your application. This is useful if you collected classes into a library, and want to link your application with this library.
The ViewKit Generation Preferences dialog is divided into the following five tabs:
The following sections describe the options for each tab panel.
Click on the File Names tab panel to display the File Names menu of the ViewKit Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Directory Path field allows you to specify the directory into which generated files will be written.
The File Extensions field specifies the following file extensions:
· ViewKit Source Extension contains the value appended to the ViewKit source file name after a dot. The default is C.
· ViewKit Header Extension contains the value appended to the ViewKit header file after a dot. The default is h.
Click on the Application tab to display the Application panel of the ViewKit Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file When you install your application, the app-default file name should be the same as the application class name.
The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications .
You can set the toggles for the following options:
· Custom Event Processing allows you to specify that name of a function to pass to VkApp::run(). ViewKit will call this function for every X event received. Builder Xcessory will also generate a stub for this function in main-vk.C
.
· UseVkApp Subclass allows you to specify a subclass of VkApp to use in main-vk.C
.
Allows you to specify the include file for the VkApp subclass specified when you set the UseVkApp Subclass toggle
You can set the following toggle options:
· Remove Overridden Exposed Callbacks removes the class callbacks when overridden. Otherwise both methods will be called.
· Delete Nested Classes in Destructor deletes nested classes created with a New operation inside the create method in the destructor.
· Initialize Fallback Resources inserts code and a user code block in main-vk.C
where you can insert you application's fallback errors.
· (Parented) Dialog Shell Initially Unmanaged toggles whether dialogs initially should be hidden regardless of their state in Builder Xcessory.
· Use VkRunOnce allows you to specify that only one single instance of an application can be run on any system at any one time. Also allows you to pass arguments to the running version of the application. Selecting this option will cause an instance of VkRunOne2 to be created in main-vk.C
.
· UseToolTalk uses VkMsgApp (instead of VkApp) which sets up a ToolTalk session. All windows are subclassed from the VkMsgWindow instead of VkWindow, and VkMsgComponent is used instead of VkComponent. In cases where you specify your own subclasses of VkApp or VkComponent, the generated code assumes they are subclasses of VkMsgApp or VkMsgComponent, respectively.
Click on the ViewKit Classes tab to display the Classes panel of the ViewKit Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
You can set the following toggle options:
· Generate UIAppDefaults Structure controls whether code for resource defaulting is generated in each class. It is selected by default, largely for backward compatibility. In most cases, the ViewKit supported defaultResources is sufficient and you can deselect this option.
· Remove Overridden Exposed Callbacks removes the class callbacks when overridden. Otherwise both methods will be called.
· Delete Nested Classes in Destructor deletes nested classes created with a New operation inside the create method in the destructor.
· Ignore Geometry Resources on Shells does not print shell geometry (x, y, width, height) in the output code.
· Generate VkTabbedDeck Source Code allows you to choose to have source code for the VkTabbedDeck class generated into you working directory.
Click on the Include Info tab to display the Include Info panel of the ViewKit Generation Preference dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Click on the Makefile tab to display the Makefile panel of the ViewKit Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Name for the command make executed when Make Application is selected from the Browser Project menu. Default is main-vk.
The C Generation Preferences dialog is divided into four tabs:
The following sections describe the options for each tab panel.
Click on the File Names tab to display the File Names panel of the C Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Directory Path field allows you to specify the directory into which generated files will be written.
The File Output Names field specifies the following files:
Click on the Application tab to display the Application panel of the C Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file.
The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications .
You can set the following options:
· User-Specified Main Loop specifies a function to call in place of the call to XtAppMainLoop.
· Initialize Localization Support supports whether or not to generate a call to XtSetLanguageProc in the application initialization. Calling this function enables support in X and Motif for non-English locales.
· (Parented) Dialog Shell Initially Unmanaged toggles to manage Dialog Shells, such as XmDialogShell, in the main-c.c file.
· Put (Unparented) Dialog Shells in Creation Routines generates code to create the XmDialogShell in the creation-c.c file when a dialog shell that is the child of the root is encountered.
· Reverse Order of (Parented) Dialog Shells reverses the order of Dialog Shells that were not children of the root.
· Remove Overridden Exposed Callbacks removes the class callbacks when overridden. Otherwise both methods will be called.
· Don't Create Unmanaged Windows delays creation of unmanaged windows.
Click on the Include Info tab to display the Include Info panel of the C Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Click on the Makefile tab to display the Makefile panel of the C Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Name of the target of the make executed when Make Application is selected from the Browser Project menu (default is main-c).
Setting the toggle option Don't Include Ungenerated Class Files excludes classes for which you disabled code generation (see Generate Class ) from the list of source and object files that comprise your application. This is useful if you collected classes into a library, and want to link your application with this library.
The UIL Generation Preferences dialog is divided into four tabs:
The following sections describe the options for each tab panel.
Click on the File Names tab to display the File Names panel of the UIL Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Directory Path field allows you to specify the directory into which generated files will be written.
The File Output Names field specifies the following files:
.uid
file which is then read by the Mrm calls at run-time to create the widgets. Builder Xcessory generates a backup file whenever it overwrites an existing UIL file. Automatic backup is provided for the default filename uil.uil or any customized filename. If, for example, you write the renamed UIL file new_uil.uil, and a copy of this file already exists, Builder Xcessory generates the backup file new_uil.uil~. These UIL files are identical to the files generated when you select Save from the Browser File menu.Click on the Application tab to display the Application panel of the UIL Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file.
The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications .
You can set the following options:
· User-Specified Main Loop specifies a main loop to replace XtAppMainLoop.
· Don't Create Unmanaged Windows delays creation of unmanaged windows.
· Ignore Geometry Resources on Shells does not print shell geometry
(x, y, width, height) in the output code.
Click on the Include Info tab to display the Include Info menu of the UIL Generation Preferences dialog:
Click on the Makefile tab to display the Makefile panel of the UIL Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
The Java Generation Preferences dialog is divided into three tabs:
The following sections describe the options for each tab panel.
Click on the File Names tab to display the File Names menu of the Java Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Allows you to specify the directory into which to write generated files.
The File Output Names field specifies the following files:
Click on the Application tab to display the Application panel of the Java Generation Preferences dialog:
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
You can set the following toggle options:
· Applets Implement Runnable toggles whether generated applets will implement the runnable interface for threading. All applets or subclasses of applets will Implement Runnable. Off by default.
· Generate HTML files for all valid classes
· Dialog Shells Initially Unmanaged
Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.
Setting the toggle option Don't Include Ungenerated Class Files excludes classes for which you disabled code generation (see Generate Class ) from the list of source and object files that comprise your application. This is useful if you collected classes into a library, and want to link your application with this library.
Displays the User Preferences dialog. The User Preferences dialog is divided into the following five tabs:
The following sections describe the options for each tab panel.
Allows you to change the placement grid dimensions. Enter the width of a grid square in pixels in the Grid Units text field. Default value is 10.
You can set the following toggle options:
You can set the following toggle options:
· Always Generate Pixmaps generates code for any pixmaps loaded into Builder Xcessory, even if unused. Typically, Builder Xcessory will generate only code for pixmaps used in the application. Unset by default.
This menu allows you to select the kind of shell created when you drag and drop an object from the Palette with MB1. The shell options on the scroll menu include the following:
Default value is TopLevelShell.
Displays the Tools Customization dialog. The Tools Customization dialog is divided into the following tabs:
The following sections describe the options for each tab panel.
Click on the Source Code Control tab of the Tools Customization dialog to display the Source Code Control panel:
Allows you to reset the value of several resources related to the following options (available based on the supported environments and platforms).
Select one of the available systems, including your environment's source code control system. RCS (Revision Control System), SCCS (Source Code Control System), and other source code control systems allow you to manage code in a multi-developer environment.
Typically, the program forces you to check out a file to modify it, and prevents other users from modifying the file until it is checked back in. Source code control programs also keep track of the revisions made between subsequently checked-in files, to allow quick reconstruction of a previous version of a file. Consult your source code control documentation for more detailed information.
The source code menu allows you to select your source code control system. If you start Builder Xcessory from within your development environment, select the Use Environment Manager option to use your environment's system.
If your environment does not have a source code control system, or you want to use another system, select one of the following options:
The following text fields are available on the Source Code Control menu (defaults depend on whether you selected RCS, SCCS, Clear Case or User Specified):
Builder Xcessory executes many of the source code control commands by constructing a command as it would be entered at a shell prompt. The command lines for the various commands use symbolic representations for the various user-specified command line options.
Builder Xcessory substitutes the appropriate value for the representation when it builds the command line. In general, the options syntax is as follows:
Everything within the brackets "[ ]" is substituted for the option name in the command line. Most options may also include "%s" within the brackets "[ ]", indicating where to insert dynamically determined text, (such as a file name or a line number).
For example, assume a command to check out a file from source code control was "checkout" and it takes the name of the file to check out as an argument. The following is entered:
If the filename argument must follow the flag "-f", the command is entered as follows:
The following list describes the command line option substitutions available for source code control commands:
The Debugger & Build Manager menu allows you to select your debugger, as follows:
The following table describes the available editors and their respective command line options:
Enter the command of your choice according to the option specifications described in the following section, Options syntax in Builder Xcessory . |
Builder Xcessory uses the tool emacsclient
to tell Emacs to load a file and display the buffer. Emacs must be running. Builder Xcessory issues a request of this "Edit Server". By default, Emacs is not configured to run as a server. In order for the emacsclient
tool to work, you must add the following Emacs Lisp command to your .emacs
file (the file that emacs
runs at startup):
Enter this line exactly as shown, including parentheses. Once Emacs loads and executes the .emacs
file again (usually when it starts), it recognizes edit requests from emacsclient
.
Running Emacs with emacsclient
requires that the emacsclient
executable and Emacs executable be run on the same machine. The socket that emacsclient
uses to communicate with emacs
is a local socket.
To enable emacs
to run on one system and the client program to make edit requests from another system, you can usegnuclient. gnuclient
works similarly to emacsclient
, but also includes the following features:
· The -q
option forces gnuclient
to send its edit request but not wait for the request to complete. The gnuclient
process exits as soon as it sends the edit request.
· The gnuclient
software includes the ability to specify another host on which emacs
is running and to make the edit request on that machine.
The gnuclient
software is available with FTP from most GNU Emacs Lisp archive sites. To use gnuclient
/gnuserv
, include the following in the .emacs
file:
Builder Xcessory executes the text editor commands by constructing a command as it would be entered at a shell prompt. The command lines for the various commands use symbolic representations for the various user-specified command line options.
Builder Xcessory substitutes the appropriate value for the representation when it builds the command line. In general, the options syntax is as follows:
Everything within the brackets "[ ]" is substituted for the option name in the command line. Most options may also include "%s" within the brackets "[ ]", indicating where to insert dynamically determined text, (such as a file name or a line number).
For example, assume a command to edit a file was "editor" and it takes the name of the file to edit as an argument. This is entered as the following:
If the filename argument must follow the flag "-f", the command is entered as
Click on the Test Tools tab of the Tools Customization dialog to display the Test Tools panel:
Setting the XRunner Library toggle specifies the library that your application is linked to for XRunner to communicate with the application.
When you compile, append xrunner to the standard make command, as follows:
When using Imakefiles generated by Builder Xcessory, enter make xrunner
(uses the last generated Makefile):
When the toggle is set, XRunner targets are added to makefile, so that the XRunner libraries are built into the executable. When you run XRunner outside of Builder Xcessory, XRunner will query your application according to this setting.
Setting Purify Command specifies the command which Builder Xcessory places in front of the compile line in the generated C or C++ Makefile for the application. When you compile, append pure to the standard make command, as follows:
For the correct Imakefile enter make pure
(uses the most recent Makefile generated from the Imakefile):
When the toggle is set, the "pure" targets is added to makefile, so that the Purify commands are built into the executable. The application validates memory use and reports when a memory violation occurs. Purify will also report any leaked memory.
Setting MemAdvisor Command specifies the command which Builder Xcessory places in front of the compile line in the generated C or C++ Makefile for the application. When you compile, append pure to the standard make command, as follows:
For the correct Imakefile enter make pure (uses the most recent Makefile generated by Imakefile):
When the toggle is set, MemAdvisor targets are added to makefile, so that the MemAdvisor commands are built into the executable. The application validates memory use and reports when a memory violation occurs. MemAdvisor will also report any leaked memory.
Displays the GIL Customization dialog.
Interface files created with Devguide may be imported into Builder Xcessory, allowing you to incorporate existing GIL(Guide Interface Language) interfaces into interfaces you create with Builder Xcessory.
The GIL Customization dialog allows you to set the following GIL to UIL converter options: