How does Snit initialize options delegated to other components?
For hull components, Snit assumes that Tk will do most of the work automatically. Hull components are somewhat more complicated, because they are matched against the option database twice. A component widget remains a widget still, and is therefore initialized from the option database in the usual way. A text widget remains a text widget whether it is a component of a megawidget or not, and will be created as such. But then, the option database is queried for all options delegated to the component, and the component is initialized accordingly–provided that the install command is used to create it.
