DTBUILDER(1)

πŸ“¦
version 2.5.3 Β· 2 versions
, in nixos 26.05

πŸ’– 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 β€” Generate DtComboBox and DtSpinBox widgets. This value retains the CDE 1.0 behavior.
    • xm β€” Generate XmComboBox and XmSimpleSpinBox widgets. 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) β€” Generate XmComboBox and XmSimpleSpinBox widgets. This value selects the Motif/Xm behavior.
  • dt β€” Generate DtComboBox and DtSpinBox widgets. 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. The dtbuilder utility 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 file myproject.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