painless panes for smalltalk windows  current windowing systems (i.e., macintosh, smalltalk) give the user flexibility in the layout of their computer display, but tend to discourage construction of new window types. glazier is a knowledge-based tool that allows users to construct and test novel or special purpose windows for smalltalk applications.  the use of glazier does not require understanding smalltalk's windowing framework (goldberg, 1984; goldberg & robson, 1983). as a new window is specified, glazier automatically constructs the necessary smalltalk class, and methods (programs). windows are interactively specified in a glazier window - the user specifies type and location of panes through mouse motions. panes can contain text, bit-maps, lists, dials, gauges, or tables. the behavior of a pane is initially determined by glazier as a function of the pane type and related defaults. these default behaviors allow the window to operate, but do not always display the application information desired. in that case, the user can fix the window's behavior by further specification. such alterations require only knowledge of the application, not of the windowing system.  glazier allows the prototyping and development of full-fledged smalltalk windows, and allows a flexibility that will change window usage in two ways. first, it will allow end users to construct special purpose windows for viewing data from an application in manners unanticipated by the system designers. second, system developers will be encouraged to prototype and evaluate many window configurations before settling on a final choice. both alternatives will result in windows that are more satisfying to the end-user.  the makeup of smalltalk or macintosh-style windows is typically viewed as a fixed component of the computer interface. windows are provided to the end user by the system designer and cannot be customized. sadly, users are not allowed the flexibility of their window contents that windows allow for display contents. thus, the user is forced to use windows that may not precisely fit the needs for his or her use of the application.  of course, the option of adding new windows is available to some users. a skilled smalltalk user can construct a special-purpose window in an afternoon. completion of such a task requires detailed knowledge of smalltalk's model- view-controller (mvc) paradigm (goldberg, 1984; goldberg & robson, 1983). this is perceived as an inconvenient, tedious task and is hardly something a novice smalltalk programmer can or should attempt.  this paper discusses glazier, a tool that encapsulates knowledge about building smalltalk windows, and assists a user in developing new smalltalk windows. glazier works as an assistant, relieving the user from the burden of thinking about windowing details. instead, the user needs only to understand how to operate the data structures for the application being displayed by the window. window development now becomes a symbiotic process, glazier provides the knowledge on how to build the window and the user provides knowledge about how the application is used and how the window should behave.  there are a numerous other systems to support interface development in a like manner. bass (1985) describes a system for developing vt100 style interfaces on top of base-level applications. the system supports a wide range of user needs, but cannot be configured dynamically by the user. the trillium system (henderson, 1986) supports prototyping of copying machine interfaces and allows designers to build and test control panels. other user interface management systems support construction of front ends for applications (hayes, szekely, & lerner, 1985). none of these systems, however, has provided the user or developer with a dynamic environment for building generic windows. glazier allows a user to build a wide range of window types, and use them as they are being built.  this paper will discuss the operation of the glazier, the method for constructing windows, and finally the implications of this new window construction technique.  james h. alexander