

This is cut number one at a tcl binding to Motif.

Notes
-----

Scrolled Lists/Text
The Motif XmCreateScrolled... actually create two objects: a Scrolled
Window, and the List/Text/..., and return the child. This child (List/Text)
is used in most other operations such as XmTextPosition. However, it is the
parent Scrolled Window that is needed in geometry stuff such as putting
it in a Form. This is tedious and a cause of many errors, with special
case code everywhere. I have resolved this by "special casing" only the
create functions. On create you have to supply the pathnames of *both*
of the objects. e.g. if the parent is .parent, you create a new object by

	scrolledText .parent.scrolledWindow.text

You then use .parent.scrolledWindow.text for all text operations, and
.parent.scrolledWindow for all geometry stuf.

SimpleMenu
Menus are tedious in Motif. Many authors make their own simple interfaces
to this. OSF created SimpleMenus as their contribution. I am not supporting
them, because they create their own widgets outside of the control of my
stuff.

Gadgets
Gadgets were invented because X servers were once too slow and too limited in
memory. So they put the onus back on the client side! Gadgets are a con, a
source of much complexity back on the application side and should vanish.
I am not suppporting them. So there. 
