DTBUILDER(1)
π NAME π
dtbuilder β the CDE Application Builder, bestie. That's the whole vibe. (It lives in the user cmd corner of the manual, iykyk.)
β¨ SYNOPSIS β¨
dtbuilder [projectfile] [-useWC classCaret]
That's it. That's the whole summoning ritual. π―οΈ
π¦ DESCRIPTION π¦
Okay so <pink>dtbuilder</pink> is an interactive application development tool and a user interface management system for CDE β no cap. Its full government name is the CDE Application Builder, and the entire point of it is to make developers' lives easier when they're constructing applications that integrate all nice and pretty into CDE. π
It hands you two basic services, and honestly? Both iconic:
- it helps you assemble Motif objects into the application user interface you actually want, and
- it generates the appropriate calls to the routines that support CDE desktop services (think
ToolTalk, sessioning, Help β the whole squad).
π OPTIONS π
-useWC classβ Use the specified widget class whenever possible. Valid values are:dtβ GenerateDtComboBoxandDtSpinBoxwidgets. This value retains the CDE 1.0 behavior.xmβ GenerateXmComboBoxandXmSimpleSpinBoxwidgets. This value selects the Motif/Xm behavior.
Pick your fighter wisely. β
πΈ OPERANDS πΈ
dtbuilder accepts an optional filename operand, and it reads that as the name of an application project file that should be loaded up for editing. That file should be in the BIL format defined for use by the Application Builder β periodt.
If you don't specify a project file, then dtbuilder comes up "empty", ready for a brand-new application to be developed interactively by you. Blank canvas energy. π¨
π RESOURCES π
If the -useWC option isn't specified, dtbuilder goes looking at the useWidgetClass resource in the Xt resources table to figure out which class to use for generated widgets. The class/type is XmCUseWidgetClass/XtEnum, and the valid values are:
xm(the default) β GenerateXmComboBoxandXmSimpleSpinBoxwidgets. This value selects the Motif/Xm behavior.dtβ GenerateDtComboBoxandDtSpinBoxwidgets. This value retains the CDE 1.0 behavior.
So like β same two choices, just sneaking in through the resources door instead of the command line. π
π STDIN π
Not used. She does not want your piped input, thank you. π
π§ INPUT FILES π§
A project file that's gonna be processed by dtbuilder must to be in the BIL format defined for the CDE Application Builder. (Yes, that's the original wording, and yes, we're keeping it exactly as-is. π)
Interactively, the Application Builder provides facilities for loading additional project files, plus application module files (which also must be in the BIL format) and interface files that use Motif's UIL format. So many files, so little time. π
π ENVIRONMENT VARIABLES π
None. Nothing to set. Go touch grass. π±
π₯ ASYNCHRONOUS EVENTS π₯
The dtbuilder utility takes the standard action for all signals. Very chill of her. π«Ά
β STDOUT β
Not used. Not a single crumb of output.
π STDERR π
Used only for diagnostic messages. That's the one and only thing it's for, ngl.
π OUTPUT FILES π
None by default. π
Interactively, though? 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. Save and export, two separate little moments. β¨
π EXTENDED DESCRIPTION π
None. That's it, that's the section. π
π EXIT STATUS π
The following exit values are returned:
0β Normal termination. She ate and left no crumbs. β1β Abnormal termination. Thedtbuilderutility was unable to allocate necessary memory or spawn the code generator. π
π¦ CONSEQUENCES OF ERRORS π¦
Default. Nothing extra to report. π
πΈ APPLICATION USAGE πΈ
Because 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. It's the front door, not the house. π
Also: CDE provides an "AppBuilder" action so the Application Builder can be invoked through the standard action interface β including through the Application Manager. Clickable king behavior. π
β¨ EXAMPLES β¨
dtbuilderβ This runs the CDE Application Builder, presuming that the user will either be creating a new project or will load one interactively through the Application Builder's"File"menu.dtbuilder myproject.bipβ Starts the CDE Application Builder and instructs it to load the project defined in the filemyproject.bip.
dtbuilder
dtbuilder myproject.bip
Two commands, zero notes. Slay. π₯
π«Ά SEE ALSO π«Ά
Go read those too, bestie, they're part of the lore. π
Friendly reminder: this whole page is filed under dtbuilder(user cmd) β that's the manual section she belongs to. π
Alright, that's the whole page! Same dtbuilder(user cmd) source/version vibes and everything, no dates to report β so consider this your cute sign-off. Mwah. πβ¨π
π¦ where this page comes from
- nixos 26.05: cde 2.5.3
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms