FM / libXt

/usr/share/doc/libXt

Name	Size	Mode	Actions
acknowledgement.xml	8743	0644	edit dl rm
appA.xml	3644	0644	edit dl rm
appB.xml	32505	0644	edit dl rm
appC.xml	56361	0644	edit dl rm
appD.xml	28405	0644	edit dl rm
appE.xml	38698	0644	edit dl rm
appF.xml	3893	0644	edit dl rm
CH01.xml	89186	0644	edit dl rm
CH02.xml	143010	0644	edit dl rm
CH03.xml	43858	0644	edit dl rm
CH04.xml	78069	0644	edit dl rm
CH05.xml	30989	0644	edit dl rm
CH06.xml	43514	0644	edit dl rm
CH07.xml	150747	0644	edit dl rm
CH08.xml	17593	0644	edit dl rm
CH09.xml	136490	0644	edit dl rm
CH10.xml	67632	0644	edit dl rm
CH11.xml	168130	0644	edit dl rm
CH12.xml	33863	0644	edit dl rm
CH13.xml	30677	0644	edit dl rm
COPYING	5673	0644	edit dl rm
intrinsics.xml	5307	0644	edit dl rm
preface.xml	2733	0644	edit dl rm

Edit: /usr/share/doc/libXt/preface.xml (2733B)

<preface id='About_This_Manual'>
<title>About This Manual</title>

<para>
X Toolkit Intrinsics — C Language Interface is intended to be read by both application programmers
who will use one or more of the many widget sets built with the Intrinsics and by widget
programmers who will use the Intrinsics to build widgets for one of the widget sets. Not all the
information in this manual, however, applies to both audiences. That is, because the application
programmer is likely to use only a number of the Intrinsics functions in writing an application and
because the widget programmer is likely to use many more, if not all, of the Intrinsics functions
in building a widget, an attempt has been made to highlight those areas of information that are
deemed to be of special interest for the application programmer. (It is assumed the widget programmer
will have to be familiar with all the information.) Therefore, all entries in the table of
contents that are printed in <emphasis role='strong'>bold</emphasis> indicate the information that
should be of special interest to an application programmer.
</para>
<para>
It is also assumed that, as application programmers become more familiar with the concepts discussed
in this manual, they will find it more convenient to implement portions of their applications
as special-purpose or custom widgets. It is possible, nonetheless, to use widgets without
knowing how to build them.
</para>

<bridgehead><emphasis role='strong'>Conventions Used in this Manual</emphasis></bridgehead>
<para>This document uses the following conventions:</para>
<itemizedlist spacing='compact'>
  <listitem>
    <para>
Global symbols are printed in <function>this special font</function>. These can be either
function names, symbols defined in include files, data types, or structure names. Arguments to
functions, procedures, or macros are printed in italics.
    </para>
  </listitem>
  <listitem>
    <para>
Each function is introduced by a general discussion that distinguishes it from other functions.
The function declaration itself follows, and each argument is specifically explained.
General discussion of the function, if any is required, follows the arguments.
    </para>
  </listitem>
  <listitem>
    <para>
To eliminate any ambiguity between those arguments that you pass and those that a function
returns to you, the explanations for all arguments that you pass start with the word
specifies or, in the case of multiple arguments, the word specify. The explanations for all
arguments that are returned to you start with the word <emphasis>returns</emphasis> or, in
the case of multiple arguments, the word <emphasis>return</emphasis>.
    </para>
  </listitem>
</itemizedlist>
</preface>

About This Manual X Toolkit Intrinsics — C Language Interface is intended to be read by both application programmers who will use one or more of the many widget sets built with the Intrinsics and by widget programmers who will use the Intrinsics to build widgets for one of the widget sets. Not all the information in this manual, however, applies to both audiences. That is, because the application programmer is likely to use only a number of the Intrinsics functions in writing an application and because the widget programmer is likely to use many more, if not all, of the Intrinsics functions in building a widget, an attempt has been made to highlight those areas of information that are deemed to be of special interest for the application programmer. (It is assumed the widget programmer will have to be familiar with all the information.) Therefore, all entries in the table of contents that are printed in bold indicate the information that should be of special interest to an application programmer. It is also assumed that, as application programmers become more familiar with the concepts discussed in this manual, they will find it more convenient to implement portions of their applications as special-purpose or custom widgets. It is possible, nonetheless, to use widgets without knowing how to build them. Conventions Used in this Manual This document uses the following conventions: Global symbols are printed in this special font. These can be either function names, symbols defined in include files, data types, or structure names. Arguments to functions, procedures, or macros are printed in italics. Each function is introduced by a general discussion that distinguishes it from other functions. The function declaration itself follows, and each argument is specifically explained. General discussion of the function, if any is required, follows the arguments. To eliminate any ambiguity between those arguments that you pass and those that a function returns to you, the explanations for all arguments that you pass start with the word specifies or, in the case of multiple arguments, the word specify. The explanations for all arguments that are returned to you start with the word returns or, in the case of multiple arguments, the word return.