Notes concerning the version of `xwaste' created in this directory:

   The Chapter 10 version of `xwaste' accommodates color workstations by
always creating pixmaps based on the screen depth.  This is perhaps the
easiest approach.  However, with this approach the off-screen pixmap uses
much more memory than it actually needs.
   The best approach is to create a GC that matches the workstation (in
depth) for displaying the pixmap in the wastebasket window.  Three separate
GC should be created for working with the pixmap.  Then, XCopyArea() and
XCopyPlane() can be used as appropriate to copy the pixmap to the window.
   Note that if you're using relatively small pixmaps in an application,
it may be better to create the pixmaps with the same depth as the screen,
because this approach will allow you to use XCopyArea(), regardless of
screen depth, and XCopyArea() is much faster than XCopyPlane().  There is
a cross-over point, however, where the size of the pixmap, specifically
its memory usage, becomes excessive and overall performance can be enhanced
by using a single-plane pixmap, even though XCopyPlane() must be invoked if
the application is running on a color workstation.
   This version of `xwaste' provides a good comparison of the effect of
creating large pixmaps on a color workstation without regard for memory
consumption.  In contrast to the Chapter 10 version of `xwaste', this
implementation uses a single-plane wastebasket pixmap.  If you have a
color workstation, you will notice dramatic differences in performance for
the two different versions of `xwaste' -- this version is much faster.
   Note that the actual color that used has no effect on performance--only
the depth of the drawables.  To illustrate this point this version of
`xwaste' adds foreground and background resources for the browser window.
   The differences in the source code are quite limited.  The main
objective in using two different approaches is simply to contrast the
dramatic performance differences on color workstations.
