how to view the file below
...\" $XConsortium: CH1 /main/16 1996/12/11 14:57:11 kaleb $
...ps 11
...nr PS 11
...ds LH \fBAthena Widget Set\fP
...ds CH
...ds RH \fBX11, Release 6.3\fP
...bp 1
...af PN 1
\&
...sp 1
...ce 3
\s+1\fBChapter 1\fP\s-1
\s+1\fBAthena Widgets and The Intrinsics\fP\s-1
...sp 2
...nr H1 1
...if \n(GS .nr nh*hl 1
...nr H2 0
...nr H3 0
...nr H4 0
...nr H5 0
...LP
...XS
Chapter 1 \- Athena Widgets and The \*(xI
...XE
The X Toolkit is made up of two distinct pieces, the Xt \*(xI and a
widget set. The Athena widget set is a sample implementation of a
widget set built upon the \*(xI. In the \*(tk, a widget is the
combination of an X window or subwindow and its associated input and
output semantics.
...LP
Because the \*(xI provide the same basic functionality to all widget
sets it may be possible to use widgets from the Athena widget set with
other widget sets based upon the \*(xI. Since widget sets may also
implement private protocols, all functionality may not be available when
mixing and matching widget sets. For information about the \*(xI, see
the \fI\*(xT\fP.
...LP
The Athena widget set is a library package layered on top of the \*(xI
and Xlib that provides a set of user interface tools sufficient to build
a wide variety of applications. This layer extends the basic
abstractions provided by X and provides the next layer of functionality
primarily by supplying a cohesive set of sample widgets. Although the
\*(xI are a Consortium standard, there is no standard widget set.
...LP
To the extent possible, the \*(xI are "policy-free". The application
environment and widget set, not the \*(xI, define, implement, and
enforce:
...IP \(bu 5
Policy
...IP \(bu 5
Consistency
...IP \(bu 5
Style
...LP
Each individual widget implementation defines its own policy. The \*(tk
design allows for, but does not necessarily encourage, the free mixing
of radically differing widget implementations.
...NH 2
Introduction to the \*(tk
...LP
...XS
Introduction to the \*(tk
...XE
...IN "introduction" "" "@DEF@"
The \*(tk provides tools that simplify the design of
application user interfaces in the X Window System programming environment.
It assists application programmers by providing a set of common
underlying user-interface functions. It also lets widget programmers
modify existing widgets, by subclassing, or add new widgets. By using
the \*(tk in their applications, programmers can present a similar
user interface across applications to all workstation users.
...LP
The \*(tk consists of:
...IP \(bu 5
A set of \*(xI functions for building widgets
...IP \(bu 5
An architectural model for constructing widgets
...IP \(bu 5
A widget set for application programming
...LP
While the majority of the \*(xI functions are intended
for the widget programmer,
a subset of the \*(xI functions are to be used by application programmers
(see \fI\*(xT\fP).
The architectural model lets the widget programmer design new widgets
by using the \*(xI and by combining other widgets.
The application interface layers built on top of the \*(tk include a
coordinated set of widgets and composition policies.
Some of these widgets and policies are specific to a single
application domain, and others are common to a variety of
Reply to: