Name
dtbuilder [projectfile] [-useWC class]
The dtbuilder utility is an interactive application development tool and user interface management system for CDE. Known more fully as the CDE Application Builder, dtbuilder is designed to make it easier for developers to construct applications that integrate well into the CDE. It provides two basic services - aid in assembling Motif objects into the desired application user interface and generation of appropriate calls to the routines that support CDE desktop services (e.g. ToolTalk, sessioning, Help).
The dtbuilder utility accepts an optional filename operand that is interpreted as the name of an application project file that should be loaded for editing. This file should be in the BIL format defined for use by the Application Builder.
If no project file is specified, then dtbuilder comes up "empty", ready for a new application to be developed interactively by the user.
If the -useWC option is not specified, dtbuilder uses the useWidgetClass resource in the Xt resources table to determine which class to use for generated widgets. The class/type is XmCUseWidgetClass/XtEnum and the valid values are:
Not used.
A project file to be processed by the dtbuilder utility must to be in the BIL format defined for the CDE Application Builder.
Interactively, the Application Builder provides facilities for loading additional project files, as well as application module files (which also must be in the BIL format) and interface files that use Motif’s UIL format.
None.
The dtbuilder utility takes the standard action for all signals.
Not used.
Used only for diagnostic messages.
None by default.
Interactively, the Application Builder provides facilities for writing ("saving") application project and module files, both of which must be in the BIL format, and also for writing ("exporting") interface files that use Motif’s UIL format.
None.
The following exit values are returned:
Default.
Because the dtbuilder is a complex, highly-interactive tool, users typically consider the command line interface as little more than the way to start up the Application Builder.
CDE provides an "AppBuilder" action so the Application Builder can be invoked through the standard action interface, including through the Application Manager.