
Output of getusers.c
The components in the program do not have any functionality; the program is used solely to demonstrate how panels
of arbitrary widgets can be displayed in a ScrolledWindow. The widget hierarchy is irrelevant to the operation of the
ScrolledWindow. In this particular case, the ScrolledWindow is a child of the top−level shell. We could have used a
MainWindow widget in place of a ScrolledWindow; these two components are interchangeable because the
MainWindow is subclassed from the ScrolledWindow. See Chapter 4, The Main Window, for more details on how
the MainWindow widget fits into the design of an application.
We used arbitrary values for the width and height of the ScrolledWindow; they were chosen because they seemed to
work best. If you are using a ScrolledWindow with a number of other widgets in an interface, you do not need to
specify an initial size for the ScrolledWindow. Since the ScrolledWindow is extremely flexible, you can allow its
parent or its siblings to control its size. ScrolledWindows work well with PanedWindows because they can be
adjusted easily. However, the ScrolledWindow does not have a sensible default size, so you should provide an initial
geometry if the ScrolledWindow is going to control its own size. In this case, the size that you choose for the widget
should be based on the aesthetics of the data that is being displayed.
In the example, the child ...