The management of the work area is not immediate: the main window must know which of its children is the work area before you can manage that widget. The following example produces a prototype interface for a standard application:
#! /usr/sgitcl/bin/moat xtAppInitialize xmMainWindow .top -showSeparator True \ -commandWindowLocation command_below_workspace xmMenuBar .top.bar managed xmCascadeButton .top.bar.File managed xmCascadeButton .top.bar.Help managed xmDrawingArea .top.work \ -width 320 -height 240 \ -background black .top setValues -workWindow .top.work .top.work manageChild xmCommand .top.com managed \ -historyVisibleItemCount 0 \ -textFontList -*-courier-medium-r-*--12-*-*-*-*-*-* .top.com commandEnteredCallback {%value} .top setValues -width 600 -height 500 .top manageChild . realizeWidget . mainLoopThe xmMainWindow widget defines these resources, renaming resources of the parents, as shown in Table 4-50.
Table 4-51 lists the callbacks associated with xmMainWindow.