libXaw-1.0.16/ 0000755 0001751 0000144 00000000000 14573370156 010036 5 0000000 0000000 libXaw-1.0.16/test-driver 0000755 0001751 0000144 00000011417 14573370153 012155 0000000 0000000 #! /bin/sh
# test-driver - basic testsuite driver script.
scriptversion=2018-03-07.03; # UTC
# Copyright (C) 2011-2021 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see .
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that program.
# This file is maintained in Automake, please report
# bugs to or send patches to
# .
# Make unconditional expansion of undefined variables an error. This
# helps a lot in preventing typo-related bugs.
set -u
usage_error ()
{
echo "$0: $*" >&2
print_usage >&2
exit 2
}
print_usage ()
{
cat <"$log_file"
"$@" >>"$log_file" 2>&1
estatus=$?
if test $enable_hard_errors = no && test $estatus -eq 99; then
tweaked_estatus=1
else
tweaked_estatus=$estatus
fi
case $tweaked_estatus:$expect_failure in
0:yes) col=$red res=XPASS recheck=yes gcopy=yes;;
0:*) col=$grn res=PASS recheck=no gcopy=no;;
77:*) col=$blu res=SKIP recheck=no gcopy=yes;;
99:*) col=$mgn res=ERROR recheck=yes gcopy=yes;;
*:yes) col=$lgn res=XFAIL recheck=no gcopy=yes;;
*:*) col=$red res=FAIL recheck=yes gcopy=yes;;
esac
# Report the test outcome and exit status in the logs, so that one can
# know whether the test passed or failed simply by looking at the '.log'
# file, without the need of also peaking into the corresponding '.trs'
# file (automake bug#11814).
echo "$res $test_name (exit status: $estatus)" >>"$log_file"
# Report outcome to console.
echo "${col}${res}${std}: $test_name"
# Register the test result, and other relevant metadata.
echo ":test-result: $res" > $trs_file
echo ":global-test-result: $res" >> $trs_file
echo ":recheck: $recheck" >> $trs_file
echo ":copy-in-global-log: $gcopy" >> $trs_file
# Local Variables:
# mode: shell-script
# sh-indentation: 2
# eval: (add-hook 'before-save-hook 'time-stamp)
# time-stamp-start: "scriptversion="
# time-stamp-format: "%:y-%02m-%02d.%02H"
# time-stamp-time-zone: "UTC0"
# time-stamp-end: "; # UTC"
# End:
libXaw-1.0.16/specs/ 0000755 0001751 0000144 00000000000 14573370156 011153 5 0000000 0000000 libXaw-1.0.16/specs/Label.xml 0000644 0001751 0000144 00000020452 14573370144 012634 0000000 0000000
Label Widget
Label widget
Application header file <X11/Xaw/Label.h>
Label.h
Class header file <X11/Xaw/LabelP.h>
LabelP.h
Class labelWidgetClass
labelWidgetClass
Class Name Label
Label widgetclass name
Superclass Simple
A Label widget holds a graphic displayed within a
rectangular region of the screen. The graphic may be a
text string containing multiple lines of characters in an
8 bit or 16 bit character set (to be displayed with a
font), or in a multi-byte encoding (for use with a
fontset). The graphic may also be a bitmap or
pixmap. The Label widget will allow its graphic to be
left, right, or center justified. Normally, this widget
can be neither selected nor directly edited by the user.
It is intended for use as an output device only.
Resources
When creating a Label widget instance, the following resources are
retrieved from the argument list or from the resource database:
Label widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
bitmap
Bitmap
Pixmap
None
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
encoding
Encoding
UnsignedChar
XawTextEncoding8bit
font
Font
XFontStruct
XtDefaultFont
fontSet
FontSet
XFontSet
XtDefaultFontSet
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
graphic height + 2 * internalHeight
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
internalHeight
Height
Dimension
2
internalWidth
Width
Dimension
4
international
International
Boolean
C
False
justify
Justify
Justify
XtJustifyCenter (center)
label
Label
String
name of widget
leftBitmap
LeftBitmap
Bitmap
None
mappedWhenManaged
MappedWhenManaged
Boolean
True
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
resize
Resize
Boolean
True
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
See above
width
Width
Dimension
A
graphic width + 2 * internalWidth
x
Position
Position
0
y
Position
Position
0
libXaw-1.0.16/specs/Template.xml 0000644 0001751 0000144 00000027413 14573370144 013374 0000000 0000000
Widget Source File
The source code file implements the widget class itself. The unique
part of this file is the declaration and initialization of the
widget class record structure and the declaration of all resources and
action routines added by the widget class.
The contents of the Template implementation file,
,
are:
/* Copyright (c) X Consortium 1987, 1988
*/
#include <X11/IntrinsicP.h>
#include <X11/StringDefs.h>
#include "TemplateP.h"
static XtResource resources[] = {
#define offset(field) XtOffsetOf(TemplateRec, template.field)
/* {name, class, type, size, offset, default_type, default_addr}, */
{ XtNtemplateResource, XtCTemplateResource, XtRTemplateResource,
sizeof(char*), offset(resource), XtRString, (XtPointer) "default" },
#undef offset
};
static void TemplateAction(/* Widget, XEvent*, String*, Cardinal* */);
static XtActionsRec actions[] =
{
/* {name, procedure}, */
{"template", TemplateAction},
};
static char translations[] =
" <Key>: template( ) \\n\\
";
TemplateClassRec templateClassRec = {
{ /* core fields */
/* superclass */ (WidgetClass) &widgetClassRec,
/* class_name */ "Template",
/* widget_size */ sizeof(TemplateRec),
/* class_initialize */ NULL,
/* class_part_initialize */ NULL,
/* class_inited */ FALSE,
/* initialize */ NULL,
/* initialize_hook */ NULL,
/* realize */ XtInheritRealize,
/* actions */ actions,
/* num_actions */ XtNumber(actions),
/* resources */ resources,
/* num_resources */ XtNumber(resources),
/* xrm_class */ NULLQUARK,
/* compress_motion */ TRUE,
/* compress_exposure */ TRUE,
/* compress_enterleave */ TRUE,
/* visible_interest */ FALSE,
/* destroy */ NULL,
/* resize */ NULL,
/* expose */ NULL,
/* set_values */ NULL,
/* set_values_hook */ NULL,
/* set_values_almost */ XtInheritSetValuesAlmost,
/* get_values_hook */ NULL,
/* accept_focus */ NULL,
/* version */ XtVersion,
/* callback_private */ NULL,
/* tm_table */ translations,
/* query_geometry */ XtInheritQueryGeometry,
/* display_accelerator */ XtInheritDisplayAccelerator,
/* extension */ NULL
},
{ /* template fields */
/* empty */ 0
}
};
WidgetClass templateWidgetClass = (WidgetClass)&templateClassRec;
The resource list for the "WindowWidget" might look like the following:
static XtResource resources[] = {
#define offset(field) XtOffsetOf(WindowWidgetRec, window.field)
/* {name, class, type, size, offset, default_type, default_addr}, */
{ XtNdrawingColor1, XtCColor, XtRPixel, sizeof(Pixel),
offset(color_1), XtRString, XtDefaultForeground },
{ XtNdrawingColor2, XtCColor, XtRPixel, sizeof(Pixel),
offset(color_2), XtRString, XtDefaultForeground },
{ XtNfont, XtCFont, XtRFontStruct, sizeof(XFontStruct*),
offset(font), XtRString, XtDefaultFont },
{ XtNexposeCallback, XtCCallback, XtRCallback, sizeof(XtCallbackList),
offset(expose_callback), XtRCallback, NULL },
{ XtNcallback, XtCCallback, XtRCallback, sizeof(XtCallbackList),
offset(input_callback), XtRCallback, NULL },
#undef offset
};
The user input callback will be implemented by an action procedure which
passes the event pointer as call_data. The action procedure
is declared as:
/* ARGSUSED */
static void InputAction(w, event, params, num_params)
Widget w;
XEvent *event;
String *params; /* unused */
Cardinal *num_params; /* unused */
{
XtCallCallbacks(w, XtNcallback, (XtPointer)event);
}
static XtActionsRec actions[] =
{
/* {name, procedure}, */
{"input", InputAction},
};
and the default input binding will be to execute the input callbacks on
KeyPress and ButtonPress :
static char translations[] =
" <Key>: input( ) \\n\\
<BtnDown>: input( ) \\
";
In the class record declaration and initialization, the only field that
is different from the Template is the expose procedure:
/* ARGSUSED */
static void Redisplay(w, event, region)
Widget w;
XEvent *event; /* unused */
Region region;
{
XtCallCallbacks(w, XtNexposeCallback, (XtPointer)region);
}
WindowClassRec windowClassRec = {
...
/* expose */ Redisplay,
The "WindowWidget" will also declare three public procedures to return the
drawing colors and the font id, saving the application the effort of
constructing an argument list for a call to
XtGetValues :
Pixel WindowColor1(w)
Widget w;
{
return ((WindowWidget)w)->window.color_1;
}
Pixel WindowColor2(w)
Widget w;
{
return ((WindowWidget)w)->window.color_2;
}
Font WindowFont(w)
Widget w;
{
return ((WindowWidget)w)->window.font->fid;
}
The "WindowWidget" is now complete. The application can retrieve the two
drawing colors from the widget instance by calling either
XtGetValues,
or the WindowColor functions. The actual window created for the
"WindowWidget" is available by calling the
XtWindow function.
libXaw-1.0.16/specs/TextActions_default_translation_bindings.xml 0000644 0001751 0000144 00000007571 14573370144 022070 0000000 0000000
Default Translation Bindings
Text widgetdefault translations
The following translations are defaults built into every Text widget.
They can be overridden, or replaced by specifying a new value for the
Text widget's translations resource.
Ctrl<Key>A: beginning-of-line() \\n\\
Ctrl<Key>B: backward-character() \\n\\
Ctrl<Key>D: delete-next-character() \\n\\
Ctrl<Key>E: end-of-line() \\n\\
Ctrl<Key>F: forward-character() \\n\\
Ctrl<Key>G: multiply(Reset) \\n\\
Ctrl<Key>H: delete-previous-character() \\n\\
Ctrl<Key>J: newline-and-indent() \\n\\
Ctrl<Key>K: kill-to-end-of-line() \\n\\
Ctrl<Key>L: redraw-display() \\n\\
Ctrl<Key>M: newline() \\n\\
Ctrl<Key>N: next-line() \\n\\
Ctrl<Key>O: newline-and-backup() \\n\\
Ctrl<Key>P: previous-line() \\n\\
Ctrl<Key>R: search(backward) \\n\\
Ctrl<Key>S: search(forward) \\n\\
Ctrl<Key>T: transpose-characters() \\n\\
Ctrl<Key>U: multiply(4) \\n\\
Ctrl<Key>V: next-page() \\n\\
Ctrl<Key>W: kill-selection() \\n\\
Ctrl<Key>Y: insert-selection(CUT_BUFFER1) \\n\\
Ctrl<Key>Z: scroll-one-line-up() \\n\\
Ctrl<Key>\\: reconnect-im() \\n\\
Meta<Key>B: backward-word() \\n\\
Meta<Key>F: forward-word() \\n\\
Meta<Key>I: insert-file() \\n\\
Meta<Key>K: kill-to-end-of-paragraph() \\n\\
Meta<Key>Q: form-paragraph() \\n\\
Meta<Key>V: previous-page() \\n\\
Meta<Key>Y: insert-selection(PRIMARY, CUT_BUFFER0) \\n\\
Meta<Key>Z: scroll-one-line-down() \\n\\
:Meta<Key>d: delete-next-word() \\n\\
:Meta<Key>D: kill-word() \\n\\
:Meta<Key>h: delete-previous-word() \\n\\
:Meta<Key>H: backward-kill-word() \\n\\
:Meta<Key>\\<: beginning-of-file() \\n\\
:Meta<Key>\\>: end-of-file() \\n\\
:Meta<Key>]: forward-paragraph() \\n\\
:Meta<Key>[: backward-paragraph() \\n\\
~Shift Meta<Key>Delete: delete-previous-word() \\n\\
Shift Meta<Key>Delete: backward-kill-word() \\n\\
~Shift Meta<Key>Backspace: delete-previous-word() \\n\\
Shift Meta<Key>Backspace: backward-kill-word() \\n\\
<Key>Right: forward-character() \\n\\
<Key>Left: backward-character() \\n\\
<Key>Down: next-line() \\n\\
<Key>Up: previous-line() \\n\\
<Key>Delete: delete-previous-character() \\n\\
<Key>BackSpace: delete-previous-character() \\n\\
<Key>Linefeed: newline-and-indent() \\n\\
<Key>Return: newline() \\n\\
<Key>: insert-char() \\n\\
<Key>Kanji: reconnect-im() \\n\\
<FocusIn>: focus-in() \\n\\
<FocusOut>: focus-out() \\n\\
<Btn1Down>: select-start() \\n\\
<Btn1Motion>: extend-adjust() \\n\\
<Btn1Up>: extend-end(PRIMARY, CUT_BUFFER0) \\n\\
<Btn2Down>: insert-selection(PRIMARY, CUT_BUFFER0) \\n\\
<Btn3Down>: extend-start() \\n\\
<Btn3Motion>: extend-adjust() \\n\\
<Btn3Up>: extend-end(PRIMARY, CUT_BUFFER0) \\n
libXaw-1.0.16/specs/CH7.xml 0000644 0001751 0000144 00000013543 14573370144 012201 0000000 0000000
Creating New Widgets (Subclassing)
Although the task of creating a new widget may at first appear a little
daunting, there is a basic simple pattern that all widgets follow. The
Athena Widget library contains a special widget called the
Template widget that is intended to assist
the novice widget programmer in writing a custom widget.
Reasons for wishing to write a custom widget include:
Providing a graphical interface not currently supported by any existing
widget set.
Convenient access to resource management procedures to obtain fonts,
colors, etc., even if user customization is not desired.
Convenient access to user input dispatch and translation management procedures.
Access to callback mechanism for building higher-level application libraries.
Customizing the interface or behavior of an existing widget to suit a
special application need.
Desire to allow user customization of resources such as fonts, colors,
etc., or to allow convenient re-binding of keys and buttons to internal
functions.
Converting a non-Toolkit application to use the Toolkit.
In each of these cases, the operation needed to create a new widget is
to "subclass" an existing one. If the desired semantics of the new
widget are similar to an existing one, then the implementation of the
existing widget should be examined to see how much work would be
required to create a subclass that will then be
able to share the existing class methods. Much time will be saved in
writing the new widget if an existing widget class Expose, Resize and/or
GeometryManager method can be used by the subclass.
Note that some trivial uses of a bare-bones
widget may be achieved by
simply creating an instance of the Core
widget. The class variable to use when creating a Core widget is
widgetClass.
The geometry of the Core widget is determined entirely by the parent
widget.
It is very often the case than an application will have a special need
for a certain set of functions and that many copies of these functions
will be needed. For example, when converting an older application to use
the Toolkit, it may be desirable to have a "Window Widget" class that
might have the following semantics:
Allocate 2 drawing colors in addition to a background color.
Allocate a text font.
Execute an application-supplied function to handle exposure events.
Execute an application-supplied function to handle user input events.
It is obvious that a completely general-purpose WindowWidgetClass could
be constructed that would export all class methods as callbacks lists,
but such a widget would be very large and would have to choose some
arbitrary number of resources such as colors to allocate. An application
that used many instances of the general-purpose widget would therefore
un-necessarily waste many resources.
In this section, an outline will be given of the procedure to follow to
construct a special-purpose widget to address the items listed above.
The reader should refer to the appropriate sections of the
X Toolkit Intrinsics - C Language Interface
for complete details of the material outlined here.
Section 1.4 of the Intrinsics
should be read in
conjunction with this section.
All Athena widgets have three separate files associated with them:
A "public" header file containing declarations needed by applications programmers
A "private" header file containing additional declarations needed by the
widget and any subclasses
A source code file containing the implementation of the widget
This separation of functions into three files is suggested for all
widgets, but nothing in the Toolkit actually requires this format. In
particular, a private widget created for a single application may easily
combine the "public" and "private" header files into a single file, or
merge the contents into another application header file. Similarly, the
widget implementation can be merged into other application code.
In the following example, the public header file
,
the private header file
and the source code file
will be modified to produce the "WindowWidget" described above.
In each case, the files have been designed so that a global string
replacement of "Template" and "template"
with the name of your new widget, using
the appropriate case, can be done.
libXaw-1.0.16/specs/Template_private_header_file.xml 0000644 0001751 0000144 00000004341 14573370144 017430 0000000 0000000
libXaw-1.0.16/specs/Makefile.in 0000644 0001751 0000144 00000064021 14573370153 013140 0000000 0000000 # Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
@SET_MAKE@
#
# Generate output formats for a single DocBook/XML with/without chapters
#
# Variables set by the calling Makefile:
# shelfdir: the location where the docs/specs are installed. Typically $(docdir)
# docbook: the main DocBook/XML file, no chapters, appendix or image files
# chapters: all files pulled in by an XInclude statement and images.
#
#
# This makefile is intended for Users Documentation and Functional Specifications.
# Do not use for Developer Documentation which is not installed and does not require olink.
# Refer to http://www.x.org/releases/X11R7.6/doc/xorg-docs/ReleaseNotes.html#id2584393
# for an explanation on documents classification.
#
VPATH = @srcdir@
am__is_gnu_make = { \
if test -z '$(MAKELEVEL)'; then \
false; \
elif test -n '$(MAKE_HOST)'; then \
true; \
elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \
true; \
else \
false; \
fi; \
}
am__make_running_with_option = \
case $${target_option-} in \
?) ;; \
*) echo "am__make_running_with_option: internal error: invalid" \
"target option '$${target_option-}' specified" >&2; \
exit 1;; \
esac; \
has_opt=no; \
sane_makeflags=$$MAKEFLAGS; \
if $(am__is_gnu_make); then \
sane_makeflags=$$MFLAGS; \
else \
case $$MAKEFLAGS in \
*\\[\ \ ]*) \
bs=\\; \
sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \
| sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \
esac; \
fi; \
skip_next=no; \
strip_trailopt () \
{ \
flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \
}; \
for flg in $$sane_makeflags; do \
test $$skip_next = yes && { skip_next=no; continue; }; \
case $$flg in \
*=*|--*) continue;; \
-*I) strip_trailopt 'I'; skip_next=yes;; \
-*I?*) strip_trailopt 'I';; \
-*O) strip_trailopt 'O'; skip_next=yes;; \
-*O?*) strip_trailopt 'O';; \
-*l) strip_trailopt 'l'; skip_next=yes;; \
-*l?*) strip_trailopt 'l';; \
-[dEDm]) skip_next=yes;; \
-[JT]) skip_next=yes;; \
esac; \
case $$flg in \
*$$target_option*) has_opt=yes; break;; \
esac; \
done; \
test $$has_opt = yes
am__make_dryrun = (target_option=n; $(am__make_running_with_option))
am__make_keepgoing = (target_option=k; $(am__make_running_with_option))
pkgdatadir = $(datadir)/@PACKAGE@
pkgincludedir = $(includedir)/@PACKAGE@
pkglibdir = $(libdir)/@PACKAGE@
pkglibexecdir = $(libexecdir)/@PACKAGE@
am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
install_sh_DATA = $(install_sh) -c -m 644
install_sh_PROGRAM = $(install_sh) -c
install_sh_SCRIPT = $(install_sh) -c
INSTALL_HEADER = $(INSTALL_DATA)
transform = $(program_transform_name)
NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
build_triplet = @build@
host_triplet = @host@
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@am__append_1 = $(docbook:.xml=.html)
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TEXT_TRUE@@HAVE_XMLTO_TRUE@am__append_2 = $(docbook:.xml=.txt)
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@am__append_3 = $(docbook:.xml=.pdf) \
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(docbook:.xml=.ps)
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@am__append_4 = $(docbook:.xml=.html.db) \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(docbook:.xml=.pdf.db)
subdir = specs
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
$(top_srcdir)/m4/ltoptions.m4 $(top_srcdir)/m4/ltsugar.m4 \
$(top_srcdir)/m4/ltversion.m4 $(top_srcdir)/m4/lt~obsolete.m4 \
$(top_srcdir)/configure.ac
am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
$(ACLOCAL_M4)
DIST_COMMON = $(srcdir)/Makefile.am $(am__dist_shelf_DATA_DIST) \
$(am__DIST_COMMON)
mkinstalldirs = $(install_sh) -d
CONFIG_HEADER = $(top_builddir)/config.h
CONFIG_CLEAN_FILES = libXaw.ent
CONFIG_CLEAN_VPATH_FILES =
AM_V_P = $(am__v_P_@AM_V@)
am__v_P_ = $(am__v_P_@AM_DEFAULT_V@)
am__v_P_0 = false
am__v_P_1 = :
AM_V_GEN = $(am__v_GEN_@AM_V@)
am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@)
am__v_GEN_0 = @echo " GEN " $@;
am__v_GEN_1 =
AM_V_at = $(am__v_at_@AM_V@)
am__v_at_ = $(am__v_at_@AM_DEFAULT_V@)
am__v_at_0 = @
am__v_at_1 =
SOURCES =
DIST_SOURCES =
am__can_run_installinfo = \
case $$AM_UPDATE_INFO_DIR in \
n|no|NO) false;; \
*) (install-info --version) >/dev/null 2>&1;; \
esac
am__dist_shelf_DATA_DIST = libXaw.xml AsciiSink.xml AsciiSource.xml \
AsciiText.xml Box.xml CH1.xml CH2.xml CH3.xml CH4.xml CH5.xml \
CH6.xml CH7.xml Command.xml Dialog.xml Form.xml Grip.xml \
Label.xml List.xml MenuButton.xml Paned.xml Panner.xml \
Porthole.xml Repeater.xml Scrollbar.xml SimpleMenu.xml \
Simple.xml SmeBSB.xml SmeLine.xml Sme.xml StripChart.xml \
Template_private_header_file.xml \
Template_public_header_file.xml \
Template_widget_source_file.xml Template.xml \
TextActions_default_translation_bindings.xml \
TextActions_text_widget_actions.xml TextActions.xml \
TextCustom.xml TextFuncs.xml TextSink.xml TextSource.xml \
Text.xml Toggle.xml TPage_Credits.xml Tree.xml Viewport.xml
am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
am__vpath_adj = case $$p in \
$(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
*) f=$$p;; \
esac;
am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
am__install_max = 40
am__nobase_strip_setup = \
srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
am__nobase_strip = \
for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
am__nobase_list = $(am__nobase_strip_setup); \
for p in $$list; do echo "$$p $$p"; done | \
sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
$(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
if (++n[$$2] == $(am__install_max)) \
{ print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
END { for (dir in files) print dir, files[dir] }'
am__base_list = \
sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
am__uninstall_files_from_dir = { \
test -z "$$files" \
|| { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
|| { echo " ( cd '$$dir' && rm -f" $$files ")"; \
$(am__cd) "$$dir" && rm -f $$files; }; \
}
am__installdirs = "$(DESTDIR)$(shelfdir)" "$(DESTDIR)$(shelfdir)"
DATA = $(dist_shelf_DATA) $(shelf_DATA)
am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP)
am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/libXaw.ent.in \
$(top_srcdir)/docbook.am
DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
ACLOCAL = @ACLOCAL@
ADMIN_MAN_DIR = @ADMIN_MAN_DIR@
ADMIN_MAN_SUFFIX = @ADMIN_MAN_SUFFIX@
AMTAR = @AMTAR@
AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
APP_MAN_DIR = @APP_MAN_DIR@
APP_MAN_SUFFIX = @APP_MAN_SUFFIX@
AR = @AR@
AUTOCONF = @AUTOCONF@
AUTOHEADER = @AUTOHEADER@
AUTOMAKE = @AUTOMAKE@
AWK = @AWK@
BASE_CFLAGS = @BASE_CFLAGS@
CC = @CC@
CCDEPMODE = @CCDEPMODE@
CFLAGS = @CFLAGS@
CHANGELOG_CMD = @CHANGELOG_CMD@
CPPFLAGS = @CPPFLAGS@
CSCOPE = @CSCOPE@
CTAGS = @CTAGS@
CWARNFLAGS = @CWARNFLAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
DLLTOOL = @DLLTOOL@
DRIVER_MAN_DIR = @DRIVER_MAN_DIR@
DRIVER_MAN_SUFFIX = @DRIVER_MAN_SUFFIX@
DSYMUTIL = @DSYMUTIL@
DUMPBIN = @DUMPBIN@
ECHO_C = @ECHO_C@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
FILECMD = @FILECMD@
FILE_MAN_DIR = @FILE_MAN_DIR@
FILE_MAN_SUFFIX = @FILE_MAN_SUFFIX@
FOP = @FOP@
GREP = @GREP@
INSTALL = @INSTALL@
INSTALL_CMD = @INSTALL_CMD@
INSTALL_DATA = @INSTALL_DATA@
INSTALL_PROGRAM = @INSTALL_PROGRAM@
INSTALL_SCRIPT = @INSTALL_SCRIPT@
INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
LD = @LD@
LDFLAGS = @LDFLAGS@
LIBEXT = @LIBEXT@
LIBOBJS = @LIBOBJS@
LIBS = @LIBS@
LIBTOOL = @LIBTOOL@
LIB_MAN_DIR = @LIB_MAN_DIR@
LIB_MAN_SUFFIX = @LIB_MAN_SUFFIX@
LIPO = @LIPO@
LN_S = @LN_S@
LTLIBOBJS = @LTLIBOBJS@
LT_SYS_LIBRARY_PATH = @LT_SYS_LIBRARY_PATH@
MAKEINFO = @MAKEINFO@
MANIFEST_TOOL = @MANIFEST_TOOL@
MAN_SUBSTS = @MAN_SUBSTS@
MISC_MAN_DIR = @MISC_MAN_DIR@
MISC_MAN_SUFFIX = @MISC_MAN_SUFFIX@
MKDIR_P = @MKDIR_P@
NM = @NM@
NMEDIT = @NMEDIT@
OBJDUMP = @OBJDUMP@
OBJEXT = @OBJEXT@
OTOOL = @OTOOL@
OTOOL64 = @OTOOL64@
PACKAGE = @PACKAGE@
PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
PACKAGE_NAME = @PACKAGE_NAME@
PACKAGE_STRING = @PACKAGE_STRING@
PACKAGE_TARNAME = @PACKAGE_TARNAME@
PACKAGE_URL = @PACKAGE_URL@
PACKAGE_VERSION = @PACKAGE_VERSION@
PATH_SEPARATOR = @PATH_SEPARATOR@
PKG_CONFIG = @PKG_CONFIG@
PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@
PKG_CONFIG_PATH = @PKG_CONFIG_PATH@
RANLIB = @RANLIB@
SED = @SED@
SET_MAKE = @SET_MAKE@
SHELL = @SHELL@
STRICT_CFLAGS = @STRICT_CFLAGS@
STRIP = @STRIP@
STYLESHEET_SRCDIR = @STYLESHEET_SRCDIR@
VERSION = @VERSION@
XAW6_CFLAGS = @XAW6_CFLAGS@
XAW6_LIBS = @XAW6_LIBS@
XAW7_CFLAGS = @XAW7_CFLAGS@
XAW7_LIBS = @XAW7_LIBS@
XMLTO = @XMLTO@
XORG_MALLOC_DEBUG_ENV = @XORG_MALLOC_DEBUG_ENV@
XORG_MAN_PAGE = @XORG_MAN_PAGE@
XORG_SGML_PATH = @XORG_SGML_PATH@
XSLTPROC = @XSLTPROC@
XSL_STYLESHEET = @XSL_STYLESHEET@
abs_builddir = @abs_builddir@
abs_srcdir = @abs_srcdir@
abs_top_builddir = @abs_top_builddir@
abs_top_srcdir = @abs_top_srcdir@
ac_ct_AR = @ac_ct_AR@
ac_ct_CC = @ac_ct_CC@
ac_ct_DUMPBIN = @ac_ct_DUMPBIN@
am__include = @am__include@
am__leading_dot = @am__leading_dot@
am__quote = @am__quote@
am__tar = @am__tar@
am__untar = @am__untar@
bindir = @bindir@
build = @build@
build_alias = @build_alias@
build_cpu = @build_cpu@
build_os = @build_os@
build_vendor = @build_vendor@
builddir = @builddir@
datadir = @datadir@
datarootdir = @datarootdir@
docdir = @docdir@
dvidir = @dvidir@
exec_prefix = @exec_prefix@
host = @host@
host_alias = @host_alias@
host_cpu = @host_cpu@
host_os = @host_os@
host_vendor = @host_vendor@
htmldir = @htmldir@
includedir = @includedir@
infodir = @infodir@
install_sh = @install_sh@
libdir = @libdir@
libexecdir = @libexecdir@
localedir = @localedir@
localstatedir = @localstatedir@
mandir = @mandir@
mkdir_p = @mkdir_p@
oldincludedir = @oldincludedir@
pdfdir = @pdfdir@
prefix = @prefix@
program_transform_name = @program_transform_name@
psdir = @psdir@
runstatedir = @runstatedir@
sbindir = @sbindir@
sharedstatedir = @sharedstatedir@
srcdir = @srcdir@
sysconfdir = @sysconfdir@
target_alias = @target_alias@
top_build_prefix = @top_build_prefix@
top_builddir = @top_builddir@
top_srcdir = @top_srcdir@
# Main DocBook/XML files (DOCTYPE book)
@ENABLE_SPECS_TRUE@docbook = libXaw.xml
# Included chapters, appendix, images
@ENABLE_SPECS_TRUE@chapters = \
@ENABLE_SPECS_TRUE@ AsciiSink.xml \
@ENABLE_SPECS_TRUE@ AsciiSource.xml \
@ENABLE_SPECS_TRUE@ AsciiText.xml \
@ENABLE_SPECS_TRUE@ Box.xml \
@ENABLE_SPECS_TRUE@ CH1.xml \
@ENABLE_SPECS_TRUE@ CH2.xml \
@ENABLE_SPECS_TRUE@ CH3.xml \
@ENABLE_SPECS_TRUE@ CH4.xml \
@ENABLE_SPECS_TRUE@ CH5.xml \
@ENABLE_SPECS_TRUE@ CH6.xml \
@ENABLE_SPECS_TRUE@ CH7.xml \
@ENABLE_SPECS_TRUE@ Command.xml \
@ENABLE_SPECS_TRUE@ Dialog.xml \
@ENABLE_SPECS_TRUE@ Form.xml \
@ENABLE_SPECS_TRUE@ Grip.xml \
@ENABLE_SPECS_TRUE@ Label.xml \
@ENABLE_SPECS_TRUE@ List.xml \
@ENABLE_SPECS_TRUE@ MenuButton.xml \
@ENABLE_SPECS_TRUE@ Paned.xml \
@ENABLE_SPECS_TRUE@ Panner.xml \
@ENABLE_SPECS_TRUE@ Porthole.xml \
@ENABLE_SPECS_TRUE@ Repeater.xml \
@ENABLE_SPECS_TRUE@ Scrollbar.xml \
@ENABLE_SPECS_TRUE@ SimpleMenu.xml \
@ENABLE_SPECS_TRUE@ Simple.xml \
@ENABLE_SPECS_TRUE@ SmeBSB.xml \
@ENABLE_SPECS_TRUE@ SmeLine.xml \
@ENABLE_SPECS_TRUE@ Sme.xml \
@ENABLE_SPECS_TRUE@ StripChart.xml \
@ENABLE_SPECS_TRUE@ Template_private_header_file.xml \
@ENABLE_SPECS_TRUE@ Template_public_header_file.xml \
@ENABLE_SPECS_TRUE@ Template_widget_source_file.xml \
@ENABLE_SPECS_TRUE@ Template.xml \
@ENABLE_SPECS_TRUE@ TextActions_default_translation_bindings.xml \
@ENABLE_SPECS_TRUE@ TextActions_text_widget_actions.xml \
@ENABLE_SPECS_TRUE@ TextActions.xml \
@ENABLE_SPECS_TRUE@ TextCustom.xml \
@ENABLE_SPECS_TRUE@ TextFuncs.xml \
@ENABLE_SPECS_TRUE@ TextSink.xml \
@ENABLE_SPECS_TRUE@ TextSource.xml \
@ENABLE_SPECS_TRUE@ Text.xml \
@ENABLE_SPECS_TRUE@ Toggle.xml \
@ENABLE_SPECS_TRUE@ TPage_Credits.xml \
@ENABLE_SPECS_TRUE@ Tree.xml \
@ENABLE_SPECS_TRUE@ Viewport.xml
# The location where the DocBook/XML files and their generated formats are installed
@ENABLE_SPECS_TRUE@shelfdir = $(docdir)
# DocBook/XML generated output formats to be installed
@ENABLE_SPECS_TRUE@shelf_DATA = $(am__append_1) $(am__append_2) \
@ENABLE_SPECS_TRUE@ $(am__append_3) $(am__append_4)
# DocBook/XML file with chapters, appendix and images it includes
@ENABLE_SPECS_TRUE@dist_shelf_DATA = $(docbook) $(chapters)
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_SEARCHPATH_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ --searchpath "$(XORG_SGML_PATH)/X11" \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ --searchpath "$(abs_top_builddir)"
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_HTML_OLINK_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ --stringparam target.database.document=$(XORG_SGML_PATH)/X11/dbs/masterdb.html.xml \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ --stringparam current.docid="$(<:.xml=)"
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_HTML_STYLESHEET_FLAGS = -x $(STYLESHEET_SRCDIR)/xorg-xhtml.xsl
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_HTML_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(XMLTO_SEARCHPATH_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(XMLTO_HTML_STYLESHEET_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(XMLTO_HTML_OLINK_FLAGS)
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_FO_IMAGEPATH_FLAGS = --stringparam img.src.path=$(abs_builddir)/
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_PDF_OLINK_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ --stringparam target.database.document=$(XORG_SGML_PATH)/X11/dbs/masterdb.pdf.xml \
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ --stringparam current.docid="$(<:.xml=)"
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_FO_STYLESHEET_FLAGS = -x $(STYLESHEET_SRCDIR)/xorg-fo.xsl
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@XMLTO_FO_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(XMLTO_SEARCHPATH_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(XMLTO_FO_STYLESHEET_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(XMLTO_FO_IMAGEPATH_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(XMLTO_PDF_OLINK_FLAGS)
# Generate documents cross-reference target databases
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@XSLT_SEARCHPATH_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ --path "$(XORG_SGML_PATH)/X11" \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ --path "$(abs_top_builddir)"
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@XSLT_OLINK_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ --stringparam targets.filename "$@" \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ --stringparam collect.xref.targets "only" \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ --stringparam olink.base.uri "$(@:.db=)"
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@XSLT_HTML_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(XSLT_SEARCHPATH_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(XSLT_OLINK_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ --nonet --xinclude \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(STYLESHEET_SRCDIR)/xorg-xhtml.xsl
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@XSLT_PDF_FLAGS = \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(XSLT_SEARCHPATH_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(XSLT_OLINK_FLAGS) \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ --nonet --xinclude \
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(STYLESHEET_SRCDIR)/xorg-fo.xsl
@ENABLE_SPECS_TRUE@CLEANFILES = $(shelf_DATA)
all: all-am
.SUFFIXES:
$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(top_srcdir)/docbook.am $(am__configure_deps)
@for dep in $?; do \
case '$(am__configure_deps)' in \
*$$dep*) \
( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
&& { if test -f $@; then exit 0; else break; fi; }; \
exit 1;; \
esac; \
done; \
echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign specs/Makefile'; \
$(am__cd) $(top_srcdir) && \
$(AUTOMAKE) --foreign specs/Makefile
Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
@case '$?' in \
*config.status*) \
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
*) \
echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__maybe_remake_depfiles)'; \
cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__maybe_remake_depfiles);; \
esac;
$(top_srcdir)/docbook.am $(am__empty):
$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(top_srcdir)/configure: $(am__configure_deps)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(ACLOCAL_M4): $(am__aclocal_m4_deps)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(am__aclocal_m4_deps):
libXaw.ent: $(top_builddir)/config.status $(srcdir)/libXaw.ent.in
cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
mostlyclean-libtool:
-rm -f *.lo
clean-libtool:
-rm -rf .libs _libs
install-dist_shelfDATA: $(dist_shelf_DATA)
@$(NORMAL_INSTALL)
@list='$(dist_shelf_DATA)'; test -n "$(shelfdir)" || list=; \
if test -n "$$list"; then \
echo " $(MKDIR_P) '$(DESTDIR)$(shelfdir)'"; \
$(MKDIR_P) "$(DESTDIR)$(shelfdir)" || exit 1; \
fi; \
for p in $$list; do \
if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
echo "$$d$$p"; \
done | $(am__base_list) | \
while read files; do \
echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(shelfdir)'"; \
$(INSTALL_DATA) $$files "$(DESTDIR)$(shelfdir)" || exit $$?; \
done
uninstall-dist_shelfDATA:
@$(NORMAL_UNINSTALL)
@list='$(dist_shelf_DATA)'; test -n "$(shelfdir)" || list=; \
files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
dir='$(DESTDIR)$(shelfdir)'; $(am__uninstall_files_from_dir)
install-shelfDATA: $(shelf_DATA)
@$(NORMAL_INSTALL)
@list='$(shelf_DATA)'; test -n "$(shelfdir)" || list=; \
if test -n "$$list"; then \
echo " $(MKDIR_P) '$(DESTDIR)$(shelfdir)'"; \
$(MKDIR_P) "$(DESTDIR)$(shelfdir)" || exit 1; \
fi; \
for p in $$list; do \
if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
echo "$$d$$p"; \
done | $(am__base_list) | \
while read files; do \
echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(shelfdir)'"; \
$(INSTALL_DATA) $$files "$(DESTDIR)$(shelfdir)" || exit $$?; \
done
uninstall-shelfDATA:
@$(NORMAL_UNINSTALL)
@list='$(shelf_DATA)'; test -n "$(shelfdir)" || list=; \
files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
dir='$(DESTDIR)$(shelfdir)'; $(am__uninstall_files_from_dir)
tags TAGS:
ctags CTAGS:
cscope cscopelist:
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
distdir-am: $(DISTFILES)
@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
list='$(DISTFILES)'; \
dist_files=`for file in $$list; do echo $$file; done | \
sed -e "s|^$$srcdirstrip/||;t" \
-e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
case $$dist_files in \
*/*) $(MKDIR_P) `echo "$$dist_files" | \
sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
sort -u` ;; \
esac; \
for file in $$dist_files; do \
if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
if test -d $$d/$$file; then \
dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
if test -d "$(distdir)/$$file"; then \
find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
fi; \
if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
fi; \
cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
else \
test -f "$(distdir)/$$file" \
|| cp -p $$d/$$file "$(distdir)/$$file" \
|| exit 1; \
fi; \
done
check-am: all-am
check: check-am
all-am: Makefile $(DATA)
installdirs:
for dir in "$(DESTDIR)$(shelfdir)" "$(DESTDIR)$(shelfdir)"; do \
test -z "$$dir" || $(MKDIR_P) "$$dir"; \
done
install: install-am
install-exec: install-exec-am
install-data: install-data-am
uninstall: uninstall-am
install-am: all-am
@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
installcheck: installcheck-am
install-strip:
if test -z '$(STRIP)'; then \
$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
install; \
else \
$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
"INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \
fi
mostlyclean-generic:
clean-generic:
-test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
distclean-generic:
-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
maintainer-clean-generic:
@echo "This command is intended for maintainers to use"
@echo "it deletes files that may require special tools to rebuild."
clean: clean-am
clean-am: clean-generic clean-libtool mostlyclean-am
distclean: distclean-am
-rm -f Makefile
distclean-am: clean-am distclean-generic
dvi: dvi-am
dvi-am:
html: html-am
html-am:
info: info-am
info-am:
install-data-am: install-dist_shelfDATA install-shelfDATA
install-dvi: install-dvi-am
install-dvi-am:
install-exec-am:
install-html: install-html-am
install-html-am:
install-info: install-info-am
install-info-am:
install-man:
install-pdf: install-pdf-am
install-pdf-am:
install-ps: install-ps-am
install-ps-am:
installcheck-am:
maintainer-clean: maintainer-clean-am
-rm -f Makefile
maintainer-clean-am: distclean-am maintainer-clean-generic
mostlyclean: mostlyclean-am
mostlyclean-am: mostlyclean-generic mostlyclean-libtool
pdf: pdf-am
pdf-am:
ps: ps-am
ps-am:
uninstall-am: uninstall-dist_shelfDATA uninstall-shelfDATA
.MAKE: install-am install-strip
.PHONY: all all-am check check-am clean clean-generic clean-libtool \
cscopelist-am ctags-am distclean distclean-generic \
distclean-libtool distdir dvi dvi-am html html-am info info-am \
install install-am install-data install-data-am \
install-dist_shelfDATA install-dvi install-dvi-am install-exec \
install-exec-am install-html install-html-am install-info \
install-info-am install-man install-pdf install-pdf-am \
install-ps install-ps-am install-shelfDATA install-strip \
installcheck installcheck-am installdirs maintainer-clean \
maintainer-clean-generic mostlyclean mostlyclean-generic \
mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \
uninstall-am uninstall-dist_shelfDATA uninstall-shelfDATA
.PRECIOUS: Makefile
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@%.html: %.xml $(chapters)
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(AM_V_GEN)$(XMLTO) $(XMLTO_HTML_FLAGS) xhtml-nochunks $<
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TEXT_TRUE@@HAVE_XMLTO_TRUE@%.txt: %.xml $(chapters)
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TEXT_TRUE@@HAVE_XMLTO_TRUE@ $(AM_V_GEN)$(XMLTO) $(XMLTO_HTML_FLAGS) txt $<
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@%.pdf: %.xml $(chapters)
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(AM_V_GEN)$(XMLTO) $(XMLTO_FO_FLAGS) --with-fop pdf $<
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@%.ps: %.xml $(chapters)
@ENABLE_SPECS_TRUE@@HAVE_FOP_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@ $(AM_V_GEN)$(XMLTO) $(XMLTO_FO_FLAGS) --with-fop ps $<
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@%.html.db: %.xml $(chapters)
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(AM_V_GEN)$(XSLTPROC) $(XSLT_HTML_FLAGS) $<
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@%.pdf.db: %.xml $(chapters)
@ENABLE_SPECS_TRUE@@HAVE_STYLESHEETS_TRUE@@HAVE_XMLTO_TRUE@@HAVE_XSLTPROC_TRUE@ $(AM_V_GEN)$(XSLTPROC) $(XSLT_PDF_FLAGS) $<
# Generate DocBook/XML output formats with or without stylesheets
# Tell versions [3.59,3.63) of GNU make to not export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:
libXaw-1.0.16/specs/Repeater.xml 0000644 0001751 0000144 00000033061 14573370144 013364 0000000 0000000
Repeater Widget
Repeater widget
Application header file <X11/Xaw/Repeater.h>
Repeater.h
Class header file <X11/Xaw/RepeaterP.h>
RepeaterP.h
Class repeaterWidgetClass
repeaterWidgetClass
Class Name Repeater
Repeater widgetclass name
Superclass Command
The Repeater widget is a subclass of the Command widget; see the
Command documentation
for details. The difference is that the Repeater can call its
registered callbacks repeatedly, at an increasing rate. The default translation
does so for the duration the user holds down pointer button 1 while the pointer
is on the Repeater.
Resources
When creating a Repeater widget instance, the following resources are
retrieved from the argument list or from the resource database:
Repeater widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
bitmap
Bitmap
Pixmap
None
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
callback
Callback
XtCallbackList
NULL
colormap
Colormap
Colormap
Parent's Colormap
cornerRoundPercent
CornerRoundPercent
Dimension
25
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
decay
Decay
Int
5
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
encoding
Encoding
UnsignedChar
XawTextEncoding8bit
flash
Boolean
Boolean
False
font
Font
XFontStruct
XtDefaultFont
fontSet
FontSet
XFontSet
XtDefaultFontSet
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
graphic height + 2 * internalHeight
highlightThickness
Thickness
Dimension
A
2 (0 if Shaped)
initialDelay
Delay
Int
200
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
internalHeight
Height
Dimension
2
internalWidth
Width
Dimension
4
international
International
Boolean
C
False
justify
Justify
Justify
XtJustifyCenter (center)
label
Label
String
name of widget
leftBitmap
LeftBitmap
Bitmap
None
mappedWhenManaged
MappedWhenManaged
Boolean
True
minimumDelay
MinimumDelay
Int
10
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
repeatDelay
Delay
Int
50
resize
Resize
Boolean
True
screen
Screen
Pointer
R
Parent's Screen
sensitive
Sensitive
Boolean
True
shapeStyle
ShapeStyle
ShapeStyle
Rectangle
startCallback
StartCallback
Callback
NULL
stopCallback
StopCallback
Callback
NULL
translations
Translations
TranslationTable
See below
width
Width
Dimension
A
graphic width + 2 * internalWidth
x
Position
Position
0
y
Position
Position
0
\" Resource Descriptions
decay
The number of milliseconds that should be subtracted from each succeeding
interval while the Repeater button is being held down until the interval
has reached minimumDelay milliseconds.
flash
Whether or not to flash the Repeater button whenever the timer goes off.
initialDelay
The number of milliseconds between the beginning of the Repeater button
being held down and the first invocation of the callback function.
minimumDelay
The minimum time between callbacks in milliseconds.
repeatDelay
The number of milliseconds between each callback after the first (minus an
increasing number of decays).
startCallback
The list of functions to invoke by the start action (typically
when the Repeater button is first pressed). The callback data parameter
is set to NULL.
stopCallback
The list of functions to invoke by the stop action (typically
when the Repeater button is released). The callback data parameter
is set to NULL.
Repeater Actions
Repeater widgetactions
The Repeater widget supports the following actions beyond those of the Command
button:
start()
This invokes the functions on the startCallback and callback lists
and sets a timer to go off in initialDelay milliseconds. The timer
will cause the callback functions to be invoked with increasing
frequency until the stop action occurs.
stop()
This invokes the functions on the stopCallback list and prevents any
further timers from occurring until the next start action.
Repeater widgettranslation bindings
The following are the default translation bindings used by the
Repeater widget:
<EnterWindow>: highlight( )
<LeaveWindow>: unhighlight( )
<Btn1Down>: set( ) start( )
<Btn1Up>: stop( ) unset( )
libXaw-1.0.16/specs/TextSink.xml 0000644 0001751 0000144 00000063457 14573370144 013402 0000000 0000000
TextSink Object
TextSink object
Application Header file <X11/Xaw/TextSink.h>
TextSink.h
Class Header file <X11/Xaw/TextSinkP.h>
TextSinkP.h
Class textSinkObjectClass
textSinkObjectClass
Class Name TextSink
TextSink objectclass name
Superclass Object
The TextSink object is the root object for all text sinks. Any new text
sink objects should be subclasses of the TextSink Object. The TextSink
Class contains all methods that the Text widget expects a text sink to
export.
Since all text sinks will have some resources in common, the TextSink
defines a few new resources.
Resources
When creating an TextSink object instance, the following resources are
retrieved from the argument list or from the resource database:
AsciiSink objectresources
Name
Class
Type
Notes
Default Value
background
Background
Pixel
XtDefaultBackground
destroyCallback
Callback
XtCallbackList
NULL
foreground
Foreground
Pixel
XtDefaultForeground
_
Subclassing the TextSink
TextSink objectsubclassing
The only purpose of the TextSink Object is to be subclassed. It
contains the minimum set of class methods that all text sinks must have.
While all may be inherited, the direct descendant of TextSink must
specify some of them as TextSink does contain enough information to
be a valid text sink by itself. Do not try to use
the TextSink as a valid sink for the Text widget; it is not intended
to be used as a sink by itself.
Function
Inherit with
Public Interface
must specify
DisplayText
XtInheritDisplayText
XawTextSinkDisplayText
yes
InsertCursor
XtInheritInsertCursor
XawTextSinkInsertCursor
yes
ClearToBackground
XtInheritClearToBackground
XawTextSinkClearToBackground
no
FindPosition
XtInheritFindPosition
XawTextSinkFindPosition
yes
FindDistance
XtInheritFindDistance
XawTextSinkFindDistance
yes
Resolve
XtInheritResolve
XawTextSinkResolve
yes
MaxLines
XtInheritMaxLines
XawTextSinkMaxLines
no
MaxHeight
XtInheritMaxHeight
XawTextSinkMaxHeight
no
SetTabs
XtInheritSetTabs
XawTextSinkSetTabs
no
GetCursorBounds
XtInheritGetCursorBounds
XawTextSinkGetCursorBounds
yes
Displaying Text
To display a section of the text buffer contained in the text source
use the function :
TextSink objectDisplayText
void DisplayText
Widget w
Positionx, y
XawTextPositionpos1, pos2
Boolean highlight
w
Specifies the TextSink object.
x
Specifies the x location to start drawing the text.
y
Specifies the y location to start drawing text.
pos1
Specifies the location within the text source of the first character
to be printed.
pos2
Specifies the location within the text source of the last character
to be printed.
highlight
Specifies whether or not to paint the text region highlighted.
The Text widget will only pass one line at a time to the text sink, so
this function does not need to know how to line feed the text. It is
acceptable for this function to just ignore Carriage Returns. x
and y denote the upper left hand corner of the first character to
be displayed.
Displaying the Insert Point
The function that controls the display of the text cursor is
. This function will be called whenever the text
widget desires to change the state of, or move the insert point.
void InsertCursor
Widget w
Positionx, y
XawTextInsertState state
w
Specifies the TextSink object.
x
Specifies the x location of the cursor in Pixels.
y
Specifies the y location of the cursor in Pixels.
state
Specifies the state of the cursor, may be one of XawisOn or
XawisOff.
X and y denote the upper left hand corner of the insert point.
Clearing Portions of the Text window
To clear a portion of the Text window to its background color, the Text
widget will call . The TextSink object already
defines this function as calling
XClearArea
on the region passed.
This behavior will be used if you specify
XtInheritClearToBackground for this method.
XtInheritClearToBackground
TextSink objectClearToBackground
void ClearToBackground
Widget w
Positionx, y
Dimensionwidth, height
w
Specifies the TextSink object.
x
Specifies the x location, in pixels, of the Region to clear.
y
Specifies the y location, in pixels, of the Region to clear.
width
Specifies the width, in pixels, of the Region to clear.
height
Specifies the height, in pixels, of the Region to clear.
X and y denote the upper left hand corner of region to clear.
Finding a Text Position Given Pixel Values
To find the text character position that will be rendered at a given x
location the Text widget uses the function :
TextSink objectFindPosition
void FindPosition
Widget w
XawTextPosition fromPos
intfromX, width
Boolean stopAtWordBreak
XawTextPosition *pos_return
int*width_return, *height_return
w
Specifies the TextSink object.
fromPos
Specifies a reference position, usually the first character in this line.
This character is always to the left of the desired character location.
fromX
Specifies the distance that the left edge of fromPos is from the
left edge of the window. This is the reference x location for the
reference position.
width
Specifies the distance, in pixels, from the reference position to the
desired character position.
stopAtWordBreak
Specifies whether or not the position that is returned should be forced
to be on a word boundary.
pos_return
Returns the character position that corresponds to the location that has
been specified, or the work break immediately to the left of the
position if stopAtWordBreak is True.
width_return
Returns the actual distance between fromPos and pos_return.
height_return
Returns the maximum height of the text between fromPos and
pos_return.
This function need make no attempt to deal with line feeds. The text
widget will only call it one line at a time.
Another means of finding a text position is provided by the
function:
TextSink objectResolve
void Resolve
Widget w
XawTextPosition fromPos
intfromX, width
XawTextPosition *pos_return
w
Specifies the TextSink object.
fromPos
Specifies a reference position, usually the first character in this line.
This character is always to the left of the desired character location.
fromX
Specifies the distance that the left edge of fromPos is from the
left edge of the window. This is the reference x location for the
reference position.
width
Specifies the distance, in pixels, from the reference position to the
desired character position.
pos_return
Returns the character position that corresponds to the
location that has been specified, or the word break immediately to the left
if stopAtWordBreak is True.
This function need make no attempt to deal with line feeds. The text
widget will only call it one line at a time. This is a more convenient
interface to the function, and provides a subset of its
functionality.
FindPosition
Finding the Distance Between two Text Positions
To find the distance in pixels between two text positions on the same
line use the function .
TextSink objectFindDistance
void FindDistance
Widget w
XawTextPositionfromPos, toPos
int fromX
XawTextPosition *pos_return
int*width_return, *height_return
w
Specifies the TextSink object.
fromPos
Specifies the text buffer position, in characters, of the first position.
fromX
Specifies the distance that the left edge of fromPos is from the
left edge of the window. This is the reference x location for the
reference position.
toPos
Specifies the text buffer position, in characters, of the second position.
resWidth
Return the actual distance between fromPos
and pos_return.
resPos
Returns the character position that corresponds to the actual character
position used for toPos in the calculations. This may be
different than toPos, for example if fromPos and toPos
are on different lines in the file.
height_return
Returns the maximum height of the text between fromPos and
pos_return.
This function need make no attempt to deal with line feeds. The Text
widget will only call it one line at a time.
Finding the Size of the Drawing area
To find the maximum number of lines that will fit into the current Text
widget, use the function . The TextSink already defines
this function to compute the maximum number of lines by using the height
of font.
TextSink objectMaxLines
int MaxLines
Widget w
Dimension height
w
Specifies the TextSink object.
height
Specifies the height of the current drawing area.
Returns the maximum number of lines that will fit in height.
To find the height required for a given number of text lines, use
the function . The TextSink already defines this
function to compute the maximum height of the window by using the
height of font.
TextSink objectMaxHeight
int MaxHeight
Widget w
int lines
w
Specifies the TextSink object.
height
Specifies the height of the current drawing area.
Returns the height that will be taken up by the number of lines passed.
Setting the Tab Stops
To set the tab stops for a text sink use the function.
The TextSink already defines this function to set the tab x location in
pixels to be the number of characters times the figure width of
font.
TextSink objectSetTabs
void SetTabs
Widget w
inttab_count, *tabs
w
Specifies the TextSink object.
tab_count
Specifies the number of tabs passed in tabs.
tabs
Specifies the position, in characters, of the tab stops.
This function is responsible for the converting character positions passed
to it into whatever internal positions the TextSink uses for tab placement.
Getting the Insert Point's Size and Location
To get the size and location of the insert point use the
function.
TextSink objectGetCursorBounds
void GetCursorBounds
Widget w
XRectangle *rect_return
w
Specifies the TextSinkObject.
rect_return
Returns the location and size of the insert point.
Rect will be filled with the current size and location of the
insert point.
libXaw-1.0.16/specs/Simple.xml 0000644 0001751 0000144 00000013765 14573370144 013057 0000000 0000000
Simple Widget
Simple widget
Application Header file <Xaw/Simple.h>
Simple.h
Class Header file <Xaw/SimpleP.h>
SimpleP.h
Class simpleWidgetClass
simpleWidgetClass
Class Name Simple
Simple widgetclass name
Superclass Core
The Simple widget is not very useful by itself, as it has no semantics
of its own. It main purpose is to be used as a common superclass for
the other simple Athena widgets. This widget adds six resources
to the resource list provided by the Core widget and its superclasses.
Resources
When creating a Simple widget instance, the following resources are
retrieved from the argument list or from the resource database:
Simple widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
height
Height
Dimension
0
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
international
International
Boolean
C
False
mappedWhenManaged
MappedWhenManaged
Boolean
True
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
width
Width
Dimension
0
x
Position
Position
0
y
Position
Position
0
libXaw-1.0.16/specs/SimpleMenu.xml 0000644 0001751 0000144 00000054275 14573370144 013705 0000000 0000000
libXaw-1.0.16/specs/AsciiText.xml 0000644 0001751 0000144 00000026753 14573370144 013524 0000000 0000000
Ascii Text Widget
AsciiText widget
Application Header file <X11/Xaw/AsciiText.h>
AsciiText.h
ClassHeader file <X11/Xaw/AsciiTextP.h>
AsciiTextP.h
Class asciiTextWidgetClass
asciiTextWidgetClass
Class Name Text
AsciiText widgetclass name
Superclass Text
Sink Name textSink
Source Name textSource
For the ease of internationalization, the AsciiText widget class name has not
been changed, although it is actually able to support non-ASCII locales.
The AsciiText widget is really a collection of smaller parts. It
includes the Text widget itself, a Source
(which supports memory management),
and a Sink
(which handles the display). There are currently two supported
sources, the AsciiSrc and MultiSrc, and two supported sinks, the AsciiSink and
AsciiSrc object
AsciiSink object
MultiSrc object
MultiSink object
MultiSink. Some of
the resources listed below are not actually resources of the
AsciiText, but belong to the associated source or sink. This is
is noted in the explanation of each resource where it applies. When
specifying these resources in a resource file it is necessary to use
*AsciiText*resource_name instead of
*AsciiText.resource_name, since they actually belong to the
children of the AsciiText widget, and not the AsciiText widget itself.
However, these resources may be set directly on the AsciiText widget at
widget creation time, or via .
Resources
When creating an AsciiText widget instance, the following resources are
retrieved from the argument list or from the resource database:
AsciiText widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
autoFill
AutoFill
Boolean
False
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
bottomMargin
Margin
Position
2
callback
Callback
XtCallbackList
NULL
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
XC_xterm
cursorName
Cursor
String
NULL
dataCompression
DataCompression
Boolean
True
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
displayCaret
Output
Boolean
True
displayNonprinting
Output
Boolean
True
displayPosition
TextPosition
XawTextPosition
0
echo
Output
Boolean
True
editType
EditType
XawTextEditType
XawtextRead
font
Font
XFontStruct*
XtDefaultFont
fontSet
FontSet
XFontSet
XtDefaultFontSet
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
Font height + margins
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
insertPosition
TextPosition
int
0
international
International
Boolean
C
False
leftMargin
Margin
Dimension
2
length
Length
int
A
length of string
mappedWhenManaged
MappedWhenManaged
Boolean
True
pieceSize
PieceSize
XawTextPosition
BUFSIZ
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
resize
Resize
XawTextResizeMode
XawtextResizeNever
rightMargin
Margin
Position
2
screen
Screen
Screen
R
Parent's Screen
scrollHorizontal
Scroll
XawTextScrollMode
XawtextScrollNever
scrollVertical
Scroll
XawTextScrollMode
XawtextScrollNever
selectTypes
SelectTypes
XawTextSelectType*
See above
sensitive
Sensitive
Boolean
True
string
String
String
NULL
textSink
TextSink
Widget
An AsciiSink
textSource
TextSource
Widget
An AsciiSrc
topMargin
Margin
Position
2
translations
Translations
TranslationTable
See above
type
Type
XawAsciiType
XawAsciiString
useStringInPlace
UseStringInPlace
Boolean
False
width
Width
Dimension
100
wrap
Wrap
WrapMode
XawtextWrapNever
x
Position
Position
0
y
Position
Position
0
libXaw-1.0.16/specs/CH5.xml 0000644 0001751 0000144 00000035274 14573370144 012204 0000000 0000000
Text Widgets
The Text widget provides a window that will allow an application
to display and edit one or more lines of text. Options are provided to
allow the user to add Scrollbars to its window, search for a specific
string, and modify the text in the buffer.
The Text widget is made up of a number of pieces; it was modularized to
ease customization. The AsciiText widget class (actually not limited to
ASCII but so named for compatibility) is be general enough to most
needs. If more flexibility, special features, or extra functionality is
needed, they can be added by implementing a new TextSource or TextSink, or
by subclassing the Text Widget
(See Section 5.8
for customization details.)
The words insertion point are used in this chapter to refer to the text
caret. This is the symbol that is displayed between two characters in
the file. The insertion point marks the location where any new characters
will be added to the file. To avoid confusion the pointer cursor will
always be referred to as the pointer.
The text widget supports three edit modes, controlling the types of
modifications a user is allowed to make:
Append-only
Editable
Read-only
Read-only mode does not allow the user or the programmer to modify the text
in the widget. While the entire string may be reset in
read-only mode with , it cannot be modified via
with . Append-only and editable modes allow
the text at the insertion point to be modified. The only difference is
that text may only be added to or removed from the end of a buffer in
append-only mode.
Text Widget for Users
Text widgetUser's Guide to the Text widget
The Text widget provides many of the common keyboard editing commands.
These commands allow users to move around and edit the buffer. If an
illegal operation is attempted, (such as deleting characters in a
read-only text widget), the X server will beep.
Default Key Bindings
Text widgetdefault key bindings
The default key bindings are patterned after those in the EMACS text editor:
Ctrl-a Beginning Of Line Meta-b Backward Word
Ctrl-b Backward Character Meta-f Forward Word
Ctrl-d Delete Next Character Meta-i Insert File
Ctrl-e End Of Line Meta-k Kill To End Of Paragraph
Ctrl-f Forward Character Meta-q Form Paragraph
Ctrl-g Multiply Reset Meta-v Previous Page
Ctrl-h Delete Previous Character Meta-y Insert Current Selection
Ctrl-j Newline And Indent Meta-z Scroll One Line Down
Ctrl-k Kill To End Of Line Meta-d Delete Next Word
Ctrl-l Redraw Display Meta-D Kill Word
Ctrl-m Newline Meta-h Delete Previous Word
Ctrl-n Next Line Meta-H Backward Kill Word
Ctrl-o Newline And Backup Meta-< Beginning Of File
Ctrl-p Previous Line Meta-> End Of File
Ctrl-r Search/Replace Backward Meta-] Forward Paragraph
Ctrl-s Search/Replace Forward Meta-[ Backward Paragraph
Ctrl-t Transpose Characters
Ctrl-u Multiply by 4 Meta-Delete Delete Previous Word
Ctrl-v Next Page Meta-Shift Delete Kill Previous Word
Ctrl-w Kill Selection Meta-Backspace Delete Previous Word
Ctrl-y Unkill Meta-Shift Backspace Kill Previous Word
Ctrl-z Scroll One Line Up
Ctrl-\\ Reconnect to input method
Kanji Reconnect to input method
In addition, the pointer may be used to cut and paste text:
Button 1 Down Start Selection
Button 1 Motion Adjust Selection
Button 1 Up End Selection (cut)
Button 2 Down Insert Current Selection (paste)
Button 3 Down Extend Current Selection
Button 3 Motion Adjust Selection
Button 3 Up End Selection (cut)
Since all of these key and pointer bindings are set through the
translations and resource manager, the user and the application
programmer can modify them by changing the Text widget's
translations resource.
Search and Replace
Text widgetsearch
Text widgetquery replace
The Text widget provides a search popup that can be used to search for a
string within the current Text widget. The popup can be activated by
typing either Control-r or Control-s. If Control-s is
used the search will be forward in the file from the current location of the
insertion point; if Control-r is used the search will be backward. The
activated popup is placed under the pointer. It has a number of buttons
that allow both text searches and text replacements to be performed.
At the top of the search popup are two toggle buttons labeled
backward and forward. One of these buttons will always be
highlighted; this is the direction in which the search will be
performed. The user can change the direction at any time by clicking on
the appropriate button.
Directly under the buttons there are two text areas, one labeled
Search for: and the other labeled Replace with:. If this is
a read-only Text widget the Replace with: field will be insensitive
and no replacements will be allowed. After each of these labels will be
a text field. This field will allow the user to enter a string to
search for and the string to replace it with. Only one of these text
fields will have a window border around it; this is the active text
field. Any key presses that occur when the focus in in the search popup
will be directed to the active text field. There are also a few special
key sequences:
Carriage Return: Execute the action, and pop down the search widget.
Tab: Execute the action, then move to the next field.
Shift Carriage Return: Execute the action, then move to the next field.
Control-q Tab: Enter a Tab into a text field.
Control-c: Pop down the search popup.
Using these special key sequences should allow simple
searches without ever removing one's hands from the keyboard.
Near the bottom of the search popup is a row of buttons. These buttons
allow the same actions to to be performed as the key sequences, but the
buttons will leave the popup active. This can be quite useful if many
searches are being performed, as the popup will be left on the display.
Since the search popup is a transient window, it may be picked
up with the window manager and pulled off to the side for use
at a later time.
Search
Search for the specified string.
Replace
Replace the currently highlighted string with the string in the
Replace with text field, and move onto the next occurrence of the
Search for text field. The functionality is commonly referred to as
query-replace.
ReplaceAll
Replace all occurrences of the search string with the replace string from
the current insertion point position to the end (or beginning) of the
file. There is no key sequence to perform this action.
ReplaceAll
Remove the search popup from the screen.
Finally, when international resource is true, there may be a
pre-edit buffer below the button row, for composing input. Its presence
is determined by the X locale in use and the VendorShell's preeditType
resource.
The widget hierarchy for the search popup is show below, all widgets
are listed by class and instance name.
Text <name of Text widget>
TransientShell search
Form form
Label label1
Label label2
Toggle backwards
Toggle forwards
Label searchLabel
Text searchText
Label replaceLabel
Text replaceText
Command search
Command replaceOne
Command replaceAll
Command cancel
File Insertion
Text widgetfile insertion
To insert a file into a text widget, type the key sequence Meta-i,
which will activate the file insert popup. This popup will appear under
the pointer, and any text typed while the focus is in this popup will be
redirected to the text field used for the filename. When the desired
filename has been entered, click on Insert File, or type
Carriage Return. The named file will then be inserted in the text
widget beginning at the insertion point position. If an error occurs when
opening the file, an error message will be printed, prompting the user
to enter the filename again. The file insert may be aborted by clicking
on Cancel. If Meta-i is typed at a text widget that is
read-only, it will beep, as no file insertion is allowed.
The widget hierarchy for the file insert popup is show below; all widgets
are listed by class and instance name.
Text <name of Text widget>
TransientShell insertFile
Form form
Label label
Text text
Command insert
Command cancel
Text Selections for Users
Text widgetText Selections for Users
The text widgets have a text selection mechanism that allows
the user to copy pieces of the text into the PRIMARY selection,
and paste
into the text widget some text that another application (or text
widget) has put in the PRIMARY selection.
One method of selecting text is to press pointer button 1
on the beginning of the text to be selected, drag the pointer until all
of the desired text is highlighted, and then release the button to
activate the selection. Another method is to click pointer button 1 at
one end of the text to be selected, then click pointer button 3 at the
other end.
To modify a currently active selection, press pointer button 3 near
either the end of the selection that you want to
adjust. This end of the selection may be moved while holding down pointer
button 3. When the proper area has been highlighted release the pointer
button to activate the selection.
The selected text may now be pasted into another application, and
will remain active until some other client makes a selection.
To paste text that some other application has
put into the PRIMARY selection use pointer button 2.
First place the insertion point where you would like the text to be inserted,
then click and release pointer button 2.
Rapidly clicking pointer button 1 the following number of times will adjust
the selection as described.
Two
Select the word under the pointer. A word boundary is defined by the
Text widget to be a Space, Tab, or Carriage Return.
Three
Select the line under the pointer.
Four
Select the paragraph under the pointer. A paragraph boundary is
defined by the text widget as two Carriage Returns in a row with only
Spaces or Tabs between them.
Five
Select the entire text buffer.
To unset the text selection, click pointer button 1 without moving it.
libXaw-1.0.16/specs/TextFuncs.xml 0000644 0001751 0000144 00000060165 14573370144 013545 0000000 0000000
Text Functions
The following functions are provided as convenience routines for use with
the Text widget. Although many of these actions can be performed by
modifying resources, these interfaces are frequently more efficient.
These data structures are defined in the Text widget's public header file,
<X11/Xaw/Text.h>.
XawTextPosition
typedef long XawTextPosition;
Character positions in the Text widget begin at 0 and end at n, where
n is the number of characters in the Text source widget.
XawTextBlock
typedef struct {
int firstPos;
int length;
char *ptr;
unsigned long format;
} XawTextBlock, *XawTextBlockPtr;
XawTextBlockPtr
firstPos
The first position, or index, to use within the ptr field.
The value is commonly zero.
length
The number of characters to be used from the ptr field.
The number of characters used is commonly the number of characters
in ptr, and must not be greater than the length of the string
in ptr.
ptr
Contains the string to be referenced by the Text widget.
format
This flag indicates whether the data pointed to by ptr is char
or wchar_t. When the associated widget has international set
to false this field must be XawFmt8Bit. When the associated
widget has international set to true this field must be
either XawFmt8Bit or XawFmtWide.
Note: Previous versions of Xaw used
FMT8BIT,
which has been retained for backwards compatibility. FMT8BIT is
deprecated and will eventually be removed from the implementation.
Selecting Text
To select a piece of text, use
XawTextSetSelection :
XawTextSetSelection
void XawTextSetSelection
Widget w
XawTextPositionleft, right
w
Specifies the Text widget.
left
Specifies the character position at which the selection begins.
right
Specifies the character position at which the selection ends.
See section 5.4
for a description of XawTextPosition.
If redisplay is enabled, this function highlights the text and
makes it the PRIMARY selection. This function does not have any
effect on CUT_BUFFER0.
Unhighlighting Text
To unhighlight previously highlighted text in a widget, use
:
XawTextUnsetSelection
void XawTextUnsetSelection
Widget w
w
Specifies the Text widget.
Getting Current Text Selection
To retrieve the text that has been selected by this
text widget use :
XawTextGetSelectionPos
void XawTextGetSelectionPos
Widget w
XawTextPosition*begin_return, *end_return
w
Specifies the Text widget.
begin_return
Returns the beginning of the text selection.
end_return
Returns the end of the text selection.
See section 5.4
for a description of XawTextPosition.
If the returned values are equal, no text is currently selected.
Replacing Text
To modify the text in an editable Text widget use :
XawTextReplace
int XawTextReplace
Widget w
XawTextPositionstart, end
XawTextBlock *text
w
Specifies the Text widget.
start
Specifies the starting character position of the text replacement.
end
Specifies the ending character position of the text replacement.
text
Specifies the text to be inserted into the file.
This function will not
be able to replace text in read-only text widgets. It will also only
be able to append text to an append-only text widget.
See section 5.4
for a description of XawTextPosition and
XawTextBlock.
This function may return the following values:
XawEditDone
XawEditDone
The text replacement was successful.
XawPositionError
XawPositionError
The edit mode is XawtextAppend and start is not the position of
the last character of the source.
XawEditError
XawEditError
Either the Source was read-only or the range to be deleted is larger
than the length of the Source.
The arguments start and
end represent the text source character positions for the
existing text that is to be replaced by the text in the text block.
The characters from start up to
but not including end are deleted, and the characters
specified on the text block are inserted in their place. If
start and end are equal, no text is deleted and the new
text is inserted after start.
Searching for Text
To search for a string in the Text widget, use
:
XawTextSearch
XawTextPosition XawTextSearch
Widget w
XawTextScanDirection dir
XawTextBlock* text
w
Specifies the Text widget.
dir
Specifies the direction to search in. Legal values are
XawsdLeft and XawsdRight.
text
Specifies a text block structure that contains the text to search for.
See section 5.4 for a description of
XawTextPosition and XawTextBlock.
The function will begin at the insertion point
and search in the
direction specified for a string that matches the one passed in
text. If the string is found the location of the first
character in the string is returned. If the string could not be
found then the value XawTextSearchError is returned.
Redisplaying Text
To redisplay a range of characters, use :
XawTextInvalidate
void XawTextInvalidate
Widget w
XawTextPositionfrom, to
w
Specifies the Text widget.
from
Specifies the start of the text to redisplay.
to
Specifies the end of the text to redisplay.
See section 5.4
for a description of XawTextPosition.
The
function causes the specified range of characters to be redisplayed
immediately if redisplay is enabled or the next time that redisplay is
enabled.
To enable redisplay, use :
XawTextEnableRedisplay
void XawTextEnableRedisplay
Widget w
w
Specifies the Text widget.
The function flushes any changes due to
batched updates when
was called and allows future changes to be reflected immediately.
To disable redisplay while making several changes, use
.
XawTextDisableRedisplay
void XawTextDisableRedisplay
Widget w
w
Specifies the Text widget.
The function causes all changes to be
batched until either or
is called.
To display batched updates, use :
XawTextDisplay
void XawTextDisplay
Widget w
w
Specifies the Text widget.
The function forces any accumulated updates to be
displayed.
Resources Convenience Routines
To obtain the character position of the left-most character on the
first line displayed in the widget (the value of the
displayPosition resource), use .
XawTextTopPosition
XawTextPosition XawTextTopPosition
Widget w
w
Specifies the Text widget.
To assign a new selection array to a text widget use
:
XawTextSetSelectionArray
void XawTextSetSelectionArray
Widget w
XawTextSelectType* sarray
w
Specifies the Text widget.
sarray
Specifies a selection array as defined in
.
Calling this function is equivalent to setting the value of the
selectionTypes resource.
To move the insertion point to the specified source position, use
:
XawTextSetInsertionPoint
void XawTextSetInsertionPoint
Widget w
XawTextPosition position
w
Specifies the Text widget.
position
Specifies the new position for the insertion point.
See section 5.4
for a description of XawTextPosition.
The text will be scrolled vertically if necessary to make the line
containing the insertion point visible. Calling this function is
equivalent to setting the insertPosition resource.
To obtain the current position of the insertion point, use
:
XawTextGetInsertionPoint
XawTextPosition XawTextGetInsertionPoint
Widget w
w
Specifies the Text widget.
See section 5.4
for a description of XawTextPosition.
The result is equivalent to retrieving the value of the
insertPosition resource.
To replace the text source in the specified widget, use
:
XawTextSetSource
void XawTextSetSource
Widget w
Widget source
XawTextPosition position
w
Specifies the Text widget.
source
Specifies the text source object.
position
Specifies character position that will become the upper left hand corner
of the displayed text. This is usually set to zero.
See section 5.4
for a description of XawTextPosition.
A display update will be performed if redisplay is enabled.
To obtain the current text source for the specified widget, use
:
XawTextGetSource
Widget XawTextGetSource
Widget w
w
Specifies the Text widget.
This function returns the text source that this Text widget is currently
using.
To enable and disable the insertion point, use
:
XawTextDisplayCaret
void XawTextDisplayCaret
Widget w
Boolean visible
w
Specifies the Text widget.
visible
Specifies whether or not the caret should be displayed.
If visible is False the insertion point will be disabled.
The marker is re-enabled either by setting visible to True, by
calling , or by executing the display-caret
action routine.
libXaw-1.0.16/specs/Scrollbar.xml 0000644 0001751 0000144 00000057516 14573370144 013553 0000000 0000000
Scrollbar Widget
Application header file <X11/Xaw/Scrollbar.h>
Class header file <X11/Xaw/ScrollbarP.h>
Class scrollbarWidgetClass
Class Name Scrollbar
Superclass Simple
A Scrollbar widget is a rectangle, called the canvas,
on
which another rectangle, the thumb,
moves in one
dimension, either vertically or horizontally. A Scrollbar
can be used alone, as a value generator, or it can be used
within a composite widget (for example, a Viewport). When a
Scrollbar is used to move, or scroll,
the contents of
another widget, the size and the position of the thumb usually give
feedback as to what portion of the other widget's contents
are visible.
Each pointer button invokes a specific action. Pointer
buttons 1 and 3 do not move the thumb automatically.
Instead, they return the pixel position of the cursor on the
scroll region. When pointer button 2 is clicked, the thumb
moves to the current pointer position. When pointer button
2 is held down and the pointer is moved, the thumb follows
the pointer.
The pointer cursor in the scroll region changes depending on the current
action. When no pointer button is pressed, the cursor appears as a
double-headed arrow that points in the direction that scrolling can
occur. When pointer button 1 or 3 is pressed, the cursor appears as a
single-headed arrow that points in the logical direction that the thumb
will move. When pointer button 2 is pressed, the cursor
appears as an arrow that points to the top or the left of the thumb.
When the user scrolls, the application receives notification
through callback procedures. For both discrete scrolling actions, the
callback returns the Scrollbar widget, the client_data, and the pixel
position of the pointer when the button was released. For continuous
scrolling, the callback routine returns the scroll bar widget, the
client data, and the current relative position of the thumb. When the
thumb is moved using pointer button 2, the callback procedure is invoked
continuously. When either button 1 or 3 is pressed, the callback
procedure is invoked only when the button is released and the client
callback procedure is responsible for moving the thumb.
Resources
When creating a Scrollbar widget instance, the following resources are
retrieved from the argument list or from the resource database:
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
colormap
Colormap
Colormap
parent's Colormap
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
depth
Depth
int
C
parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
depends on orientation
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
international
International
Boolean
C
False
jumpProc
Callback
XtCallbackList
NULL
length
Length
Dimension
1
mappedWhenManaged
MappedWhenManaged
Boolean
True
minimumThumb
MinimumThumb
Dimension
7
orientation
Orientation
Orientation
XtorientVertical (vertical)
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
screen
Screen
Screen
R
parent's Screen
scrollDCursor
Cursor
Cursor
XC_sb_down_arrow
scrollHCursor
Cursor
Cursor
XC_sb_h_double_arrow
scrollLCursor
Cursor
Cursor
XC_sb_left_arrow
scrollProc
Callback
XtCallbackList
NULL
scrollRCursor
Cursor
Cursor
XC_sb_right_arrow
scrollUCursor
Cursor
Cursor
XC_sb_up_arrow
scrollVCursor
Cursor
Cursor
XC_sb_v_arrow
sensitive
Sensitive
Boolean
True
shown
Shown
Float
0.0
thickness
Thickness
Dimension
14
thumb
Thumb
Bitmap
GreyPixmap
thumbProc
Callback
XtCallbackList
NULL
topOfThumb
TopOfThumb
Float
0.0
translations
Translations
TranslationTable
See below
width
Width
Dimension
A
depends on orientation
x
Position
Position
0
y
Position
Position
0
foreground
A pixel value which indexes the widget's colormap to derive the color
used to draw the thumb.
jumpProc
All functions on this callback list are called when the
NotifyThumb action is invoked. See
for details.
length
The height of a vertical scrollbar or the width of a horizontal scrollbar.
minimumThumb
The smallest size, in pixels, to which the thumb can shrink.
orientation
The orientation is the direction that the thumb will be allowed to move.
This value can be either XtorientVertical or
XtorientHorizontal.
scrollDCursor
This cursor is used when scrolling backward in a vertical scrollbar.
scrollHCursor
This cursor is used when a horizontal scrollbar is inactive.
scrollLCursor
This cursor is used when scrolling forward in a horizontal scrollbar.
scrollProc
All functions on this callback list may be called when the
NotifyScroll action is invoked. See
for details.
scrollRCursor
This cursor is used when scrolling backward in a horizontal scrollbar,
or when thumbing a vertical scrollbar.
scrollUCursor
This cursor is used when scrolling forward in a vertical scrollbar, or when
thumbing a horizontal scrollbar.
scrollVCursor
This cursor is used when a vertical scrollbar is inactive.
shown
This is the size of the thumb, expressed as a percentage (0.0 - 1.0)
of the length of the scrollbar.
thickness
The width of a vertical scrollbar or the height of a horizontal scrollbar.
thumb
This pixmap is used to tile (or stipple) the thumb of the scrollbar. If
no tiling is desired, then set this resource to None. This
resource will accept either a bitmap or a pixmap that is the same depth
as the window. The resource converter for this resource constructs
bitmaps from the contents of files. (See Converting Bitmaps for
details.)
topOfThumb
The location of the top of the thumb, as a percentage (0.0 - 1.0)
of the length of the scrollbar. This resource was called top in
previous versions of the Athena widget set. The name collided with the
a Form widget constraint resource, and had to be changed.
Scrollbar Actions
The actions supported by the Scrollbar widget are:
StartScroll(value)
The possible values are Forward, Backward, or Continuous.
This must be the first action to begin a new movement.
NotifyScroll(value)
The possible values are Proportional or FullLength. If the
argument to StartScroll was Forward or Backward, NotifyScroll executes
the scrollProc callbacks and passes either; the position of the
pointer, if value is Proportional, or the full length of the
scroll bar, if value is FullLength. If the argument to
StartScroll was Continuous, NotifyScroll returns without executing any
callbacks.
EndScroll( )
This must be the last action after a movement is complete.
MoveThumb( )
Repositions the Scrollbar's thumb to the current pointer location.
NotifyThumb( )\
Calls the
callbacks and passes the relative position of the
pointer as a percentage of the scroll bar length.
The default bindings for Scrollbar are:
Scrollbar widgetdefault translation table
<Btn1Down>: StartScroll(Forward)
<Btn2Down>: StartScroll(Continuous) MoveThumb( ) NotifyThumb( )
<Btn3Down>: StartScroll(Backward)
<Btn2Motion>: MoveThumb( ) NotifyThumb( )
<BtnUp>: NotifyScroll(Proportional) EndScroll( )
Examples of additional bindings a user might wish to specify in a
resource file are:
*Scrollbar.Translations: \\
~Meta<Key>space: StartScroll(Forward) NotifyScroll(FullLength) \\n\\
Meta<Key>space: StartScroll(Backward) NotifyScroll(FullLength) \\n\\
EndScroll( )
Scrollbar Callbacks
Scrollbar widgetcallbacks
There are two callback lists provided by the Scrollbar widget.
The procedural interface for these functions is described here.
The calling interface to the scrollProc callback procedure is:
ScrollProc
void ScrollProc
Widget scrollbar
XtPointer client_data
XtPointer position
scrollbar
Specifies the Scrollbar widget.
client_data
Specifies the client data.
position
Specifies a pixel position in integer form.
The scrollProc callback is used for incremental scrolling
and is called by the NotifyScroll action.
The position argument is a signed quantity and should be cast to an int
when used. Using the default button bindings, button 1 returns a
positive value, and button 3 returns a negative value. In both cases,
the magnitude of the value is the distance of the pointer in
pixels from the top (or left) of the Scrollbar. The value will never
be greater than the length of the Scrollbar.
The calling interface to the jumpProc callback procedure is:
jumpProc
void JumpProc
Widget scrollbar
XtPointer client_data
XtPointer percent_ptr
scrollbar
Specifies the ID of the scroll bar widget.
client_data
Specifies the client data.
percent_ptr
Specifies the floating point position of the thumb (0.0 – 1.0).
The jumpProc callback is used to implement smooth scrolling and
is called by the NotifyThumb action. Percent_ptr must be cast
to a pointer to float before use; i.e.
float percent = *(float*)percent_ptr;
With the default button bindings, button 2 moves the thumb interactively,
and the jumpProc is called on each new position of the pointer,
while the pointer button remains down. The value specified by
percent_ptr is the current location of the thumb (from the top or
left of the Scrollbar) expressed as a percentage of the length of the
Scrollbar.
Convenience Routines
Scrollbar widgetsetting thumb values
To set the position and length of a Scrollbar thumb, use
XawScrollbarSetThumb
void XawScrollbarSetThumb
Widget w
float top
float shown
w
Specifies the Scrollbar widget.
top
Specifies the position of the top of the thumb as a fraction of the
length of the Scrollbar.
shown
Specifies the length of the thumb as a fraction of the total length
of the Scrollbar.
XawScrollbarThumb
moves the visible thumb to a new position (0.0 – 1.0) and length (0.0 – 1.0).
Either the top or shown arguments can be specified as -1.0,
in which case the current value is left unchanged.
Values greater than 1.0 are truncated to 1.0.
If called from jumpProc, has no effect.
Setting Float Resources
float resourcessetting
The shown and topOfThumb resources are of type
float. These resources can be difficult to get into an
argument list. The reason is that C performs an automatic cast of
the float value to an integer value, usually truncating the important
information. The following code fragment is one portable method of
getting a float into an argument list.
top = 0.5;
if (sizeof(float) > sizeof(XtArgVal)) {
/*
* If a float is larger than an XtArgVal then pass this
* resource value by reference.
*/
XtSetArg(args[0], XtNshown, &top);
}
else {
/*
* Convince C not to perform an automatic conversion, which
* would truncate 0.5 to 0.
*/
XtArgVal * l_top = (XtArgVal *) ⊤
XtSetArg(args[0], XtNshown, *l_top);
}
libXaw-1.0.16/specs/AsciiSource.xml 0000644 0001751 0000144 00000030161 14573370144 014024 0000000 0000000
Ascii Source Object and Multi Source Object
AsciiSrc object
Application Header file <X11/Xaw/AsciiSrc.h> or <X11/Xaw/MultiSrc.h>
AsciiSrc.h
Class Header file <X11/Xaw/AsciiSrcP.h> or <X11/Xaw/MultiSrcP.h>
AsciiSrcP.h
Class asciiSrcObjectClass or multiSrcObjectClass
asciiSrcObjectClass
Class Name AsciiSrc or MultiSrc
AsciiSrc objectclass name
Superclass TextSource
The AsciiSrc or MultiSrc object is used by a text widget to read the text from a
file or string in memory. Depending on its international resource, an
AsciiText widget will create one or the other of these when the AsciiText
itself is created. Both types are nearly identical; the following discussion
applies to both, with MultiSrc differences noted only as they occur.
The AsciiSrc understands all Latin1 characters plus Tab and Carriage Return.
The MultiSrc understands any set of character sets that
the underlying X implementation's internationalization handles.
The AsciiSrc can be either of two types: XawAsciiFile
or XawAsciiString.
AsciiSrc objects of type XawAsciiFile read the text from a file and
store it
into an internal buffer. This buffer may then be modified, provided the
text widget is in the correct edit mode, just as if it were a source of
type XawAsciiString. Unlike R3 and earlier versions of the AsciiSrc,
it is now possible to specify an editable disk source. The file is not
updated, however, until a call to is made. When the
source is in this mode the useStringInPlace resource is ignored.
AsciiSrc objects of type XawAsciiString have the text buffer
implemented as a string.
MultiSrc objects of type XawAsciiString
have the text buffer implemented as a wide character string.
The string owner is responsible for allocating and managing storage for the
string.
In the default case for AsciiSrc objects of type XawAsciiString,
the resource useStringInPlace is false,
and the widget owns the string. The initial value of the
string resource, and any update made by the application
programmer to the string resource with , is copied
into memory private to the widget, and managed internally by the widget.
The application writer
does not need to worry about running out of buffer space
(subject to the total memory available to the application).
The performance does not decay linearly as the buffer grows
large, as is necessarily the case when the text buffer is used
in place. The application writer must use to
determine the contents of the text buffer, which will return
a copy of the widget's text buffer as
it existed at the time of the call. This copy
is not affected by subsequent updates to the text buffer, i.e.,
it is not updated as the user types input into the text buffer.
This copy is freed upon the next call to XtGetValues to
retrieve the string resource; however, to conserve memory,
there is a convenience routine, , allowing the
application programmer to direct the widget to free the copy.
When the resource useStringInPlace is true and the AsciiSrc object
is of type XawAsciiString, the application
is the string owner. The widget will take the value
of the string resource as its own text buffer, and the length
resource indicates the buffer size. In this case
the buffer contents change as the user types at the widget;
it is not necessary to call on the string
resource to determine the contents of the buffer-it will
simply return the address of the application's implementation
of the text buffer.
Resources
When creating an AsciiSrc object instance, the following resources are
retrieved from the argument list or from the resource database:
AsciiSrc objectresources
Name
Class
Type
Notes
Default Value
callback
Callback
XtCallbackList
NULL
dataCompression
DataCompression
Boolean
True
destroyCallback
Callback
Callback
NULL
editType
EditType
EditMode
XawtextRead
length
Length
Int
A
length of string
pieceSize
PieceSize
Int
BUFSIZ
string
String
String
NULL
type
Type
AsciiType
XawAsciiString
useStringInPlace
UseStringInPlace
Boolean
False
_
Convenience Routines
The AsciiSrc has a few convenience routines that allow the
application programmer quicker or easier access to some of the
commonly used functionality of the AsciiSrc.
Conserving Memory
When the AsciiSrc widget is not in useStringInPlace mode
space must be allocated whenever the file is saved, or the string is
requested with a call to . This memory is allocated on the
fly, and remains valid until the next time a string needs to be allocated.
You may save memory by freeing this string as soon as you are done
with it by calling .
void XawAsciiSourceFreeString
Widget w
w
Specifies the AsciiSrc object.
This function will free the memory that contains the string pointer returned
by . This will normally happen automatically when
the next call to occurs, or when the widget is destroyed.
Saving Files
To save the changes made in the current text source into a file use
.
Boolean XawAsciiSave
Widget w
w
Specifies the AsciiSrc object.
returns True if the save was successful.
It will update the file named in the string resource.
If the buffer has not been changed, no action will be taken. This function
only works on an AsciiSrc of type XawAsciiFile.
To save the contents of the current text buffer into a named file use
.
Boolean XawAsciiSaveAsFile
Widget w
String name
w
Specifies the AsciiSrc object.
name
The name of the file to save the current buffer into.
This function returns True if the save was successful.
will work with a buffer of either type
XawAsciiString or type XawAsciiFile.
Seeing if the Source has Changed
To find out if the text buffer in an AsciiSrc object has changed
since the last time it was saved with or queried
XawAsciiSave
use .
Boolean XawAsciiSourceChanged
Widget w
w
Specifies the AsciiSrc object.
This function will return True if the source has changed since
the last time it was saved or queried. The internal change flag is
reset whenever the string is queried via or the
buffer is saved via .
libXaw-1.0.16/specs/TextActions_text_widget_actions.xml 0000644 0001751 0000144 00000064271 14573370144 020220 0000000 0000000
Text Widget Actions
Text widgetactions
Text widgetactions
All editing functions are performed by translation manager actions that may
be specified through the translations resource in the Text widget.
Insert Point Movement Delete
forward-character delete-next-character
backward-character delete-previous-character
forward-word delete-next-word
backward-word delete-previous-word
forward-paragraph delete-selection
backward-paragraph
beginning-of-line
end-of-line Selection
next-line select-word
previous-line select-all
next-page select-start
previous-page select-adjust
beginning-of-file select-end
end-of-file extend-start
scroll-one-line-up extend-adjust
scroll-one-line-down extend-end
insert-selection
Miscellaneous New Line
redraw-display newline-and-indent
insert-file newline-and-backup
insert-char newline
insert-string
display-caret
focus-in Kill
focus-in kill-word
search backward-kill-word
multiply kill-selection
form-paragraph kill-to-end-of-line
transpose-characters kill-paragraph
no-op kill-to-end-of-paragraph
XawWMProtocols
reconnect-im
Most of the actions take no arguments, and unless otherwise noted you
may assume this to be the case.
Cursor Movement Actions
forward-character()
backward-character()
These actions move the insert point forward or backward one character in
the buffer. If the insert point is at the end or beginning of a line
this action will move the insert point to the next (or previous) line.
forward-word()
backward-word()
These actions move the insert point to the next or previous word boundary.
A word boundary is defined as a Space, Tab or Carriage Return.
forward-paragraph()
backward-paragraph()
These actions move the insert point to the next or previous paragraph boundary.
A paragraph boundary is defined as two Carriage Returns in a row with only
Spaces or Tabs between them.
beginning-of-line()
end-of-line()
These actions move to the beginning or end of the current line. If the
insert point is already at the end or beginning of the line then no action is taken.
next-line()
previous-line()
These actions move the insert point up or down one line. If the insert
point is currently N characters from the beginning of the line then it
will be N characters from the beginning of the next or previous line.
If N is past the end of the line, the insert point is placed at the end
of the line.
next-page()
previous-page()
These actions move the insert point up or down one page in the file.
One page is defined as the current height of the text widget. The
insert point is always placed at the first character of the top line by
this action.
beginning-of-file()
end-of-file()
These actions place the insert point at the beginning or end of the
current text buffer. The text widget is then scrolled the minimum
amount necessary to make the new insert point location visible.
scroll-one-line-up()
scroll-one-line-down()
These actions scroll the current text field up or down by one line.
They do not move the insert point. Other than the scrollbars this is
the only way that the insert point may be moved off of the visible text
area. The widget will be scrolled so that the insert point is back on
the screen as soon as some other action is executed.
Delete Actions
delete-next-character()
delete-previous-character()
These actions remove the character immediately before or after the
insert point. If a Carriage Return is removed then the next line is
appended to the end of the current line.
delete-next-word()
delete-previous-word()
These actions remove all characters between the insert point location and
the next word boundary. A word boundary is defined as a Space, Tab or
Carriage Return.
delete-selection()
This action removes all characters in the current selection.
The selection can be set with the selection actions.
Selection Actions
select-word()
This action selects the word in which the insert point is currently located.
If the insert point is between words then it will select the previous word.
select-all()
This action selects the entire text buffer.
select-start()
This action sets the insert point to the current pointer location (if
triggered by a button event) or text cursor location (if triggered by
a key event). It
will then begin a selection at this location. If many of these
selection actions occur quickly in succession then the selection count
mechanism will be invoked (see
for details).
select-adjust()
This action allows a selection started with the select-start
action to be modified, as described above.
select-end(name[,name,...])
This action ends a text selection that began with the select-start
action, and asserts ownership of the selection or selections specified.
A name can be a selection (e.g., PRIMARY) or a cut buffer
(e.g., CUT_BUFFER0). Note that case is important. If no
names are specified, PRIMARY is asserted.
extend-start()
This action finds the nearest end of the current selection, and moves it
to the current pointer location (if triggered by a button event) or text
cursor location (if triggered by a key event).
extend-adjust()
This action allows a selection started with an extend-start action
to be modified.
extend-end(name[,name,...])
This action ends a text selection that began with the extend-start
action, and asserts ownership of the selection or selections specified.
A name can be a selection (e.g. PRIMARY) or a cut buffer
(e.g CUT_BUFFER0). Note that case is important. If no names are
given, PRIMARY is asserted.
insert-selection(name[,name,...])
This action retrieves the value of the first (left-most) named selection
that exists or the cut buffer that is not empty and inserts it into the
Text widget at the current insert point location. A name can be a
selection (e.g. PRIMARY) or a cut buffer (e.g CUT_BUFFER0).
Note that case is important.
The New Line Actions
newline-and-indent()
This action inserts a newline into the text and adds spaces to
that line to indent it to match the previous line.
newline-and-backup()
This action inserts a newline into the text after the insert point.
newline()
This action inserts a newline into the text before the insert point.
Kill and Actions
kill-word()
backward-kill-word()
These actions act exactly like the delete-next-word and
delete-previous-word actions, but they stuff the word that was
killed into the kill buffer (CUT_BUFFER_1).
kill-selection()
This action deletes the current selection and stuffs the deleted text into
the kill buffer (CUT_BUFFER_1).
kill-to-end-of-line()
This action deletes the entire line to the right of the insert point position,
and stuffs the deleted text into the kill buffer (CUT_BUFFER_1).
kill-paragraph()
This action deletes the current paragraph, if between paragraphs it deletes
the paragraph above the insert point, and stuffs the deleted text into
the kill buffer (CUT_BUFFER_1).
kill-to-end-of-paragraph()
This action deletes everything between the current insert point location and
the next paragraph boundary, and stuffs the deleted text into the kill
buffer (CUT_BUFFER_1).
Miscellaneous Actions
redraw-display()
This action recomputes the location of all the text lines on the
display, scrolls the text to vertically center the line containing the insert point
on the screen, clears the entire screen, and redisplays it.
insert-file([filename])
This action activates the insert file popup. The filename
option specifies the default filename to put in the filename buffer of
the popup. If no filename is specified the buffer is empty
at startup.
insert-char()
This action may only be attached to a key event. When the
international resource is false, this action
calls XLookupString to translate the event into a (rebindable) Latin-1
character (sequence) and inserts it into the text at the
insert point. When the international resource is true,
characters are passed to the input method via XwcLookupString, and any
committed string returned is inserted into the text at the insert point.
insert-string(string[,string,...])
This action inserts each string into the text
at the insert point location. Any string
beginning with the characters "0x" followed by an even
number of hexadecimal digits is
interpreted as a hexadecimal constant and the
corresponding string is inserted instead. This
hexadecimal string may represent up to 50 8-bit characters.
When theinternational resource is
true, a hexadecimal string is intrepeted as
being in a multi-byte encoding, and a hexadecimal
or regular string will result in an error message
if it is not legal in the current locale.
display-caret(state,when)
This action allows the insert point to be turned on and off.
The state argument specifies the desired state of the insert point.
This value may be any of the string
values accepted for Boolean resources (e.g. on, True,
off, False, etc.). If no arguments are specified, the
default value is True.
The when argument specifies, for EnterNotify or LeaveNotify
events whether or not the focus field in the event is to be examined.
If the second argument is not specified, or specified as something other
than always then if the action is bound to an EnterNotify
or LeaveNotify event, the action will be taken only if the focus
field is True. An augmented binding that might be useful is:
*Text.Translations: #override \\
<FocusIn>: display-caret(on) \\n\\
<FocusOut>: display-caret(off)
focus-in()
focus-out()
These actions do not currently do anything.
search(direction,[string])
This action activates the search popup. The direction must be
specified as either forward or backward. The string is
optional and is used as an initial value for the Search for: string.
For further explanation of the search widget see the section on
Text Searches.
multiply(value)
The multiply action allows the user to multiply the effects of many of
the text actions. Thus the following action sequence
multiply(10) delete-next-word() will delete 10 words. It does not
matter whether these actions take place in one event or many events.
Using the default translations the key sequence
Control-u, Control-d will delete 4 characters.
Multiply actions can be chained, thus
multiply(5) multiply(5) is the same as
multiply(25). If the string
reset is passed to the multiply action the effects of all previous
multiplies are removed and a beep is sent to the display.
form-paragraph()
This action removes all the Carriage Returns from the current
paragraph and reinserts them so that each line is as long as possible, while
still fitting on the current screen. Lines are broken at word boundaries if
at all possible. This action currently works only on Text widgets
that use ASCII text.
transpose-characters()
This action will swap the position of the character to the left of the
insert point with the character to the right of the insert point. The insert point will then
be advanced one character.
no-op([action])
The no-op action makes no change to the text widget, and is mainly used
to override translations. This action takes one optional argument. If
this argument is RingBell then a beep is sent to the display.
XawWMProtocols([wm_protocol_name])
XawWMProtocols
This action is written specifically for the file insertion and the search
and replace
dialog boxes. This action is attached to those shells by the Text widget,
in order to handle ClientMessage events with the WM_PROTOCOLS atom in the
detail field. This action supports WM_DELETE_WINDOW on the Text widget
popups, and may support other window manager protocols if necessary in
the future. The popup will be dismissed if the window manager sends
a WM_DELETE_WINDOW request and there are no parameters in the action
call, which is the default. The popup will also be dismissed if the
parameters include the string wm_delete_window,
and the event is a
ClientMessage event requesting dismissal or is not a ClientMessage event.
This action is not sensitive to the case of the strings passed as parameters.
reconnect-im()
Input Method
When the international resource is true,
input is usually passed to an input method, a separate
process, for composing. Sometimes the connection to
this process gets severed; this action will attempt to
reconnect it. Causes for severage include network
trouble, and the user explicitly killing one input
method and starting a new one. This action may also
establish first connection when the application is
started before the input method.
Text Selections for Application Programmers
Text widgetText Selections for Application Programmers
The default behavior of the text selection array is described in the
section called Text Selections for Users. To modify the selections
a programmer must construct a XawTextSelectType array (called the
selection array), containing the selections desired, and pass this as
the new value for the selectionTypes resource. The selection
array may also be modified using the
XawTextSetSelectionArray
function. All selection arrays must end with the value
XawselectNull. The selectionTypes resource has no converter
registered and cannot be modified through the resource manager.
The array contains a list of entries that will be called when the user
attempts to select text in rapid succession with the select-start
action (usually by clicking a pointer button). The first entry in the
selection array will be used when the select-start action is
initially called. The next entry will be used when select-start
is called again, and so on. If a timeout value (1/10 of a second) is
exceeded, the the next select-start action will begin at the top
of the selection array. When XawselectNull is reached the array
is recycled beginning with the first element.
XawselectAll
Selects the contents of the entire buffer.
XawselectChar
Selects text characters as the pointer moves over them.
XawselectLine
Selects the entire line.
XawselectNull
Indicates the end of the selection array.
XawselectParagraph
Selects the entire paragraph.
XawselectPosition
Selects the current pointer position.
XawselectWord
Selects whole words as the pointer moves onto them.
The default selectType array is:
{XawselectPosition, XawselectWord, XawselectLine, XawselectParagraph, XawselectAll, XawselectNull}
The selection array is not copied by the text widgets. The
application must allocate space for the array and cannot deallocate or
change it until the text widget is destroyed or until a new selection
array is set.
libXaw-1.0.16/specs/Grip.xml 0000644 0001751 0000144 00000022734 14573370144 012523 0000000 0000000
Grip Widget
Grip widget
Application header file <X11/Xaw/Grip.h>
Grip.h
Class header file <X11/Xaw/GripP.h>
GripP.h
Class gripWidgetClass
gripWidgetClass
Class Name Grip
Grip widgetclass name
Superclass Simple
The Grip widget provides a small rectangular region in which user input
events (such as ButtonPress or ButtonRelease) may be handled. The most
common use for the Grip widget is as an attachment point for visually
repositioning an object, such as the pane border in a Paned widget.
Resources
When creating a Grip widget instance, the following resources are
retrieved from the argument list or from the resource database:
Grip widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
0
callback
Callback
Callback
NULL
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
8
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
international
International
Boolean
C
False
mappedWhenManaged
MappedWhenManaged
Boolean
True
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
width
Width
Dimension
8
x
Position
Position
0
y
Position
Position
0
callback
All routines on this list are called whenever the GripAction
action routine is invoked. The call_data contains all
information passed to the action routine. A detailed description
is given below in the Grip Actions section.
foreground
A pixel value which indexes the widget's colormap to derive the color
used to flood fill the entire Grip widget.
Grip Actions
Grip widgetactions
The Grip widget does not declare any default event translation bindings,
but it does declare a single action routine named GripAction. The
Grip widgetGripAction routine
client specifies an arbitrary event translation table, optionally giving
parameters to the GripAction routine.
The GripAction routine executes the callbacks on the
callback list, passing as call_data a pointer to a
XawGripCallData structure, defined in the Grip widget's application
header file.
XawGripCallData
XawGripCallDataRec
typedef struct _XawGripCallData {
XEvent *event;
String *params;
Cardinal num_params;
} XawGripCallDataRec, *XawGripCallData,
GripCallDataRec, *GripCallData; /* supported for R4 compatibility */
XawGripCallDataRec
XawGripCallData
GripCallData
In this structure, the event is a pointer to the input event that
triggered the action. params and num_params give the string
parameters specified in the translation table for the particular event
binding.
Grip widgetGripAction table
The following is an example of a translation table that uses the GripAction:
<Btn1Down>: GripAction(press)
<Btn1Motion>: GripAction(move)
<Btn1Up>: GripAction(release)
For a complete description of the format of translation tables, see the
X Toolkit Intrinsics - C Language Interface.
libXaw-1.0.16/specs/CH2.xml 0000644 0001751 0000144 00000173274 14573370144 012204 0000000 0000000 Using Widgets
Using Widgets
Widgets serve as the primary tools for building a user interface or
application environment. The Athena widget set consists of primitive
widgets that contain no children (for example, a command button) and
composite widgets which may contain one or more widget children (for
example, a Box widget).
The remaining chapters explain the widgets that are provided
by the Athena widget set.
These user-interface components serve as an interface for
application programmers who do not want to implement their own widgets.
In addition, they serve as a starting point
for those widget programmers who, using the Intrinsics mechanisms,
want to implement alternative application programming interfaces.
This chapter is a brief introduction to widget programming. The
examples provided use the Athena widgets, though most of the concepts
will apply to all widget sets. Although there are several programming
interfaces to the X Toolkit, only one is described here. A full
description of the programming interface is provided in the document
X Toolkit Intrinsics - C Language Interface.
Setting the Locale
If it is desirable that the application take advantage of
internationalization (i18n), you must establish locale with
XtSetLanguageProc
prior to calling
,
XtOpenDisplay,
XtDisplayInitialize,
or
XtAppInitialize.
For full details, please refer to the document
X Toolkit Intrinsics - C Language Interface,
section 2.2. However, the following simplest-case
call is sufficient in many or most applications.
internationalization
XtSetLanguageProc
locale
XtSetLanguageProc(NULL, NULL, NULL);
Most notably, this will affect the Standard C locale, determine which
resource files will be loaded, and what fonts will be required of FontSet
specifications. In many cases, the addition of this line is the only source change
required to internationalize Xaw programs, and will not disturb the function
of programs in the default "C" locale.
Initializing the Toolkit
You must call a toolkit initialization function before invoking any
other toolkit routines (besides locale setting, above).
,
opens the X server connection, parses the command line,
and creates an initial widget that will serve as the root of
a tree of widgets created by this application.
initialization
toolkit initialization
XtOpenApplication
fallback resources
Widget XtOpenApplication
XtAppContext *app_context_return
String application_class
XrmOptionDescList options
Cardinal num_options
int *argc_in_out
String *argv_in_out
String *fallback_resources
WidgetClass widget_class
ArgList args
Cardinal num_args
app_context_return
Returns the application context of this application, if non-NULL.
application_class
Specifies the class name of this application,
which is usually the generic name for all instances of this application.
A useful convention is to form the class name by capitalizing the
first letter of the application name. For example, the application named
xman
has a class name of Xman
.
options
Specifies how to parse the command line for any application-specific
resources.
The options argument is passed as a parameter to
XrmParseCommand.
For further information,
see Xlib - C Language Interface.
num_options
Specifies the number of entries in the options list.
argc_in_out
Specifies a pointer to the number of command line parameters.
argv_in_out
Specifies the command line parameters.
fallback_resources
Specifies resource values to be used if the site-wide application class
defaults file cannot be opened, or NULL.
widget_class
Specifies the class of the widget to be created. Must be shellWidgetClass
or a subclass.
args
Specifies the argument list to use when creating the Application shell.
num_args
Specifies the number of arguments in args.
This function will remove the command line arguments that the toolkit
reads from argc_in_out, and argv_in_out. It will then
attempt to open the display. If the display cannot be opened, an error
message is issued and XtAppInitialize terminates the application. Once
the display is opened, all resources are read from the locations
specified by the Intrinsics. This function returns an ApplicationShell
widget to be used as the root of the application's widget tree.
Creating a Widget
widget creation
creating widgets
XtRealizeWidget
Creating a widget is a three-step process. First, the widget instance
is allocated, and various instance-specific attributes are set by
using XtCreateWidget. Second, the widget's parent is informed
of the new child by using XtManageChild. Finally, X windows are
created for the parent and all its children by using
and specifying the top-most widget. The first two steps can be
combined by using . In addition,
is automatically called when the child becomes
managed if the parent is already realized.
To allocate, initialize, and manage a widget, use
XtCreateManagedWidget.
XtCreateManagedWidget
Widget XtCreateManagedWidget
String name
WidgetClass widget_class
Widget parent
ArgList args
Cardinal num_args
name
Specifies the instance name for the created widget that is used for retrieving
widget resources.
widget_class
Specifies the widget class pointer for the created widget.
parent
Specifies the parent widget ID.
args
Specifies the argument list. The argument list is a variable-length
list composed of name and value pairs that contain information
pertaining to the specific widget instance being created. For further
information, see Section 2.7.2.
num_args
Specifies the number of arguments in the argument list.
If the num_args is zero, the argument list is never referenced.
When a widget instance is successfully created, the widget identifier
is returned to the application. If an error is encountered, the
XtError
routine is invoked to inform the user of the error.
XtError
For further information, see
X Toolkit Intrinsics - C Language Interface.
Common Resources
resource
Although a widget can have unique arguments that it understands, all
widgets have common arguments that provide some regularity of operation.
The common arguments allow arbitrary widgets to be managed by
higher-level components without regard for the individual widget type.
Widgets will ignore any argument that they do not understand.
The following resources are retrieved from the argument list
or from the resource database by all of the Athena widgets:
Name
Class
Type
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
colormap
Colormap
Colormap
Parent's Colormap
depth
Depth
int
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
height
Height
Dimension
widget dependent
mappedWhenManaged
MappedWhenManaged
Boolean
True
screen
Screen
Screen
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
widget dependent
width
Width
Dimension
widget dependent
x
Position
Position
0
y
Position
Position
0
XtDefaultForeground
XtDefaultBackground
The following additional resources are retrieved from the argument list
or from the resource database by many of the Athena widgets:
Name
Class
Type
Default Value
callback
Callback
XtCallbackList
NULL
cursor
Cursor
Cursor
widget dependent
foreground
Foreground
Pixel
XtDefaultForeground
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
XtDefaultForeground
Resource Conversions
conversions
string conversions
type conversions
Most resources in the Athena widget set have a converter registered that
will translate the string in a resource file to the correct internal
representation. While some are obvious (string to integer, for example),
others need specific mention of the allowable values. Three general
converters are described here:
Cursor
Pixel
Bitmap
Many widgets have defined special converters that apply only to that
widget. When these occur, the documentation section for that widget
will describe the converter.
Cursor Conversion
conversionsColorCursor
conversionsCursor
cursor
The value for the cursorName resource is specified in the resource
database as a string, and is of the following forms:
A standard X cursor name from .
The names in cursorfont.h each describe a specific cursor. The
resource names for these cursors are exactly like the names in this file
except the XC_ is not used. The cursor definition XC_gumby
has a resource name of gumby.
Glyphs, as in FONT font-name glyph-index [[ font-name ] glyph-index ].
The first font and glyph specify the cursor source pixmap.
The second font and glyph specify the cursor mask pixmap.
The mask font defaults to the source font,
and the mask glyph index defaults to the source glyph index.
A relative or absolute file name.
If a relative or absolute file name is specified, that file is used to
create the source pixmap. Then the string "Mask" is appended to
locate the cursor mask pixmap. If the "Mask" file does not exist, the
suffix "msk" is tried. If "msk" fails, no cursor mask will be used.
If the filename does not start with '/' or './' the the bitmap
file path is used (see section 2.4.3).
Pixel Conversion
conversionsPixel
pixel
rgb.txt
XtDefaultForeground
XtDefaultBackground
The string-to-pixel converter takes any name that is acceptable to
XParseColor (see Xlib - C Language Interface). In addition this routine understands
the special toolkit symbols `XtDefaultForeground' and
`XtDefaultBackground', described in
X Toolkit Intrinsics - C Language Interface. In short the acceptable
pixel names are:
Any color name for the rgb.txt file (typically in the directory
/usr/share/X11 on POSIX systems).
A numeric specification of the form #<red><green><blue> where these
numeric values are hexadecimal digits (both upper and lower case).
The special strings `XtDefaultForeground' and `XtDefaultBackground'
Bitmap Conversion
bitmap conversions
conversionsBitmap
bitmapFilePath
BitmapFilePath
/usr/include/X11/bitmaps
The string-to-bitmap converter attempts to locate a file containing
bitmap data whose name is specified by the input string. If the file
name is relative (i.e. does not begin with / or ./), the directories to
be searched are specified in the bitmapFilePath resource--class
BitmapFilePath. This resource specifies a colon (:) separated
list of directories that will be searched for the named bitmap or
cursor glyph (see section 2.4.1). The bitmapFilePath resource is
global to the application, and may not be specified differently
for each widget that wishes to convert a cursor to bitmap. In addition
to the directories specified in the bitmapFilePath resource a
default directory is searched. When using POSIX the default
directory is
/usr/include/X11/bitmaps.
Realizing a Widget
realizing widgets
The
function performs two tasks:
Calculates the geometry constraints of all managed descendants
of this widget. The actual calculation is put off until realize time
for performance reasons.
Creates an X window for the widget and, if it is a composite widget,
realizes each of its managed children.
XtRealizeWidget
void XtRealizeWidget
Widget w
Specifies the widget.
For further information about this function,
see the X Toolkit Intrinsics - C Language Interface.
Processing Events
events
XtAppInitialize
Now that the application has created, managed and realized its
widgets, it is ready to process the events that will be delivered by the
X Server to this client. A function call that will process the
events is .
XtAppMainLoop
void XtAppMainLoop
XtAppContext app_context
app_context
Specifies the application context of this application. The value is
normally returned by .
This function never returns: it is an infinite loop that processes the
X events. User input can be handled through callback procedures and
application defined action routines. More details are provided in
X Toolkit Intrinsics - C Language Interface.
Standard Widget Manipulation Functions
After a widget has been created, a client can interact with that
widget by calling one of the standard widget manipulation routines
provided by the Intrinsics, or a widget class-specific manipulation routine.
The Intrinsics provide generic routines to give the application programmer
access to a set of standard widget functions. The common widget
routines let an application or composite widget perform the following
operations on widgets without requiring explicit knowledge of the widget
type.
Control the mapping of widget windows
Destroy a widget instance
Obtain an argument value
Set an argument value
Mapping Widgets
By default,
widget windows are mapped (made viewable) automatically by
. This behavior can be disabled by using
, making the client responsible for calling
to make the widget viewable.
XtSetMappedWhenManaged
XtMapWidget
XtRealizeWidget
void XtSetMappedWhenManaged
Widget w
Boolean map_when_managed
w
Specifies the widget.
map_when_managed
Specifies the new value.
If map_when_managed is True, the widget is mapped automatically
when it is realized. If map_when_managed is False, the client
must call
or make a second call to
to cause the child window to be mapped.
The definition for
is:
XtMapWidget
void XtMapWidget
Widget w
w
Specifies the widget.
When you are creating several children in sequence for a previously
realized common parent it is generally more efficient to construct a
list of children as they are created (using XtCreateWidget) and
then use to request that their parent managed
them all at once. By managing a list of children at one time, the
parent can avoid wasteful duplication of geometry processing and the
associated screen flash
.
XtManageChildren
XtCreateWidget
void XtManageChildren
WidgetList children
Cardinal num_children
children
Specifies a list of children to add.
num_children
Specifies the number of children to add.
If the parent is already visible on the screen, it is especially
important to batch updates so that the minimum amount of visible window
reconfiguration is performed.
For further information about these functions,
see the X Toolkit Intrinsics - C Language Interface.
Destroying Widgets
To destroy a widget instance of any type, use
XtDestroyWidget
void XtDestroyWidget
Widget w
w
Specifies the widget.
destroys the widget and recursively destroys any children that it may have,
including the windows created by its children.
After calling
XtDestroyWidget,
no further references should be made to the widget or any children
that the destroyed widget may have had.
Retrieving Widget Resource Values
To retrieve the current value of a resource attribute associated
with a widget instance, use
XtGetValues.
XtGetValues
void XtGetValues
Widget w
ArgList args
Cardinal num_args
w
Specifies the widget.
args
Specifies a variable-length argument list of name and address
pairs that contain the resource name and the address into which the
resource value is stored.
num_args
Specifies the number of arguments in the argument list.
The arguments and values passed in the argument list are dependent on
the widget. Note that the caller is responsible for providing space
into which the returned resource value is copied; the ArgList
contains a pointer to this storage (e.g. x and y must be
allocated as Position). For further information, see the
X Toolkit Intrinsics - C Language Interface.
Modifying Widget Resource Values
To modify the current value of a resource attribute associated with a
widget instance, use
XtSetValues.
XtSetValues
void XtSetValues
Widget w
ArgList args
Cardinal num_args
w
Specifies the widget.
args
Specifies an array of name and value pairs that contain the
arguments to be modified and their new values.
num_args
Specifies the number of arguments in the argument list.
The arguments and values that are passed will depend on the widget
being modified. Some widgets may not allow certain resources to be
modified after the widget instance has been created or realized.
No notification is given if any part of a request is
ignored.
For further information about these functions, see the
X Toolkit Intrinsics - C Language Interface.
XtGetValues
XtSetValues
The argument list entry for
specifies the address to which the caller wants the value copied. The
argument list entry for
XtSetValues,
however, contains the new value itself, if the size of value is less than
sizeof(XtArgVal) (architecture dependent, but at least sizeof(long));
otherwise, it is a pointer to the value. String resources are always
passed as pointers, regardless of the length of the string.
Using the Client Callback Interface
callbacks
Widgets can communicate changes in their state to their clients
by means of a callback facility.
The format for a client's callback handler is:
CallbackProc
void CallbackProc
Widget w
XtPointer client_data
XtPointer call_data
w
Specifies widget for which the callback is registered.
client_data
Specifies arbitrary client-supplied data that the widget should pass
back to the client when the widget executes the client's callback
procedure. This is a way for the client registering the callback to
also register client-specific data: a pointer to additional information
about the widget, a reason for invoking the callback, and so on. If no
additional information is necessary, NULL may be passed as this argument.
This field is also frequently known as the closure.
call_data
Specifies any callback-specific data the widget wants to pass to the client.
For example, when Scrollbar executes its jumpProc callback list,
it passes the current position of the thumb in call_data.
Callbacks can be registered either by creating an argument containing
the callback list described below or by using the special convenience
routines and XtAddCallbacks. When the widget
is created, a pointer to a list of callback procedure and data pairs can
be passed in the argument list to
XtCreateWidget.
The list is of type
XtCallbackList :
XtCallbackProc
XtAddCallbacks
XtAddCallback
XtCallbackList
XtCallbackRec
typedef struct {
XtCallbackProc callback;
XtPointer closure;
} XtCallbackRec, *XtCallbackList;
The callback list must be allocated and initialized before calling
XtCreateWidget.
XtCreateWidget
The end of the list is identified by an entry containing NULL in
callback and closure. Once the widget is created, the client can change
or de-allocate this list; the widget itself makes no further reference
to it. The closure field contains the client_data passed to the
callback when the callback list is executed.
The second method for registering callbacks is to use
after the widget has been created.
XtAddCallback
void XtAddCallback
Widget w
String callback_name
XtCallbackProc callback
XtPointer client_data
w
Specifies the widget to add the callback to.
callback_name
Specifies the callback list within the widget to append to.
callback
Specifies the callback procedure to add.
client_data
Specifies the data to be passed to the callback when it is invoked.
adds the specified callback to the list for the named widget.
All widgets provide a callback list named
destroyCallback
destroyCallback
where clients can register procedures that are to be executed when the
widget is destroyed. The destroy callbacks are executed when the widget
or an ancestor is destroyed. The call_data argument is unused for
destroy callbacks.
Programming Considerations
This section provides some guidelines on how to set up an application
program that uses the X Toolkit.
Writing Applications
writing applications
StringDefs.h
Intrinsic.h
When writing an application that uses the X Toolkit,
you should make sure that your application performs the following:
Include
in your application programs.
This header file automatically includes
,
so all Xlib functions also are defined.
It may also be necessary to include when setting
up argument lists, as many of the XtNsomething definitions are
only defined in this file.
Include the widget-specific header files for each widget type
that you need to use.
For example,
and
.
Call the
XtOpenApplication
function before invoking any other toolkit or Xlib functions.
For further information,
see Section 2.1 and the
X Toolkit Intrinsics - C Language Interface.
To pass attributes to the widget creation routines that will override
any site or user customizations, set up argument lists. In this
document, a list of valid argument names is provided in the discussion
of each widget. The names each have a global symbol defined that begins
with XtN to help catch spelling errors. For example,
XtNlabel is defined for the label resource of many widgets.
XtN
For further information, see Section 2.9.2.2.
When the argument list is set up, create the widget with the
function. For further information, see
Section 2.2 and the
X Toolkit Intrinsics - C Language Interface.
XtCreateManagedWidget
If the widget has any callback routines, set by the
XtNcallback
argument or the
function, declare these routines within the application.
XtAddCallback
After creating the initial widget hierarchy, windows must be created
for each widget by calling
on the top level widget.
XtRealizeWidget
Most applications now sit in a loop processing events using
XtAppMainLoop,
for example:
XtAppMainLoop
XtCreateManagedWidget(name, class, parent, args, num_args);
XtRealizeWidget(shell);
XtAppMainLoop(app_context);
For information about this function, see the
X Toolkit Intrinsics - C Language Interface.
Link your application with
libXaw
(the Athena widgets),
libXmu
(miscellaneous utilities),
libXt
(the X Toolkit Intrinsics),
libSM
(Session Management),
libICE
(Inter-Client Exchange),
libXext
(the extension library needed for the shape extension code which allows
rounded Command buttons), and
libX11
(the core X library).
The following provides a sample command line:
libXaw
libXmu
libXt
libSM
libICE
libXext
libX11
linking applications
compiling applications
cc -o application application.c -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11
Changing Resource Values
resource
The Intrinsics support two methods of changing the default resource
values; the resource manager, and an argument list passed into
XtCreateWidget. While resources values will get updated no matter
which method you use, the two methods provide slightly different
functionality.
Resource Manager
This method picks up resource definitions described in
Xlib - C Language Interface from
many different locations at run time. The locations most important to
the application programmer are the fallback resources and the
app-defaults file, (see
X Toolkit Intrinsics - C Language Interface
for the complete list).
Since these resource are loaded at run time, they can be overridden by
the user, allowing an application to be customized to fit the
particular needs of each individual user. These values can also be
modified without the need to rebuild the application, allowing rapid
prototyping of user interfaces. Application programmers should use
resources in preference to hard-coded values whenever possible.
Argument Lists
The values passed into the widget at creation time via an argument list
cannot be modified by the user, and allow no opportunity for
customization. It is used to set resources that cannot be specified as
strings (e.g. callback lists) or resources that should not be
overridden (e.g. window depth) by the user.
Specifying Resources
It is important for all X Toolkit application programmers to
understand how to use the X Resource Manager to specify resources for
widgets in an X application. This section will describe the most common
methods used to specify these resources, and how to use the X Resource
manager.
xrdb
Xrdb
The xrdb utility may be used to load a file containing
resources into the X server. Once the resources are loaded, the
resources will affect any new applications started on the display that
they were loaded onto.
application defaults
app-defaults
/usr/share/X11/app-defaults
Application Defaults
The application defaults (app-defaults) file (normally in
/usr/share/X11/app-defaults/classname) for an application is loaded
whenever the application is started.
The resource specification has two colon-separated parts, a name, and
a value. The value is a string whose format is dependent on the
resource specified by name. Name is constructed by
appending a resource name to a full widget name.
The full widget name is a list of the name of every ancestor of the
desired widget separated by periods (.). Each widget also has a class
associated with it. A class is a type of widget (e.g. Label or
Scrollbar or Box). Notice that class names, by convention, begin with
capital letters and instance names begin with lower case letters. The
class of any widget may be used in place of its name in a resource
specification. Here are a few examples:
xman.form.button1
This is a fully specified resource name, and will affect only widgets
called button1 that are children of widgets called form that are
children of
applications named xman. (Note that while typically two widgets that
are siblings will have different names, it is not prohibited.)
Xman.Form.Command
This will match any Command widget that is a child of a Form widget
that is itself a child of an application of class Xman.
Xman.Form.button1
This is a mixed resource name with both widget names and classes specified.
This syntax allows an application programmer to specify any widget
in the widget tree. To match more than one widget (for example a user
may want to make all Command buttons blue), use an asterisk (*)
instead of a period. When an asterisk is used, any number of widgets
(including zero) may exist between the two widget names. For example:
Xman*Command
This matches all Command widgets in the Xman application.
Foo*button1
This matches any widget in the Foo application that is named button1.
The root of all application widget trees is the widget returned by
. Even though this is actually an
ApplicationShell widget, the toolkit replaces its widget class with the
class name of the application. The name of this widget is either
the name used to invoke the application (argv[0]) or the name of
the application specified using the standard -name command line
option supported by the Intrinsics.
The last step in constructing the resource name is to append the name of
the resource with either a period or asterisk to the full or partial
widget name already constructed.
*foreground:Blue
Specifies that all widgets in all applications will have a foreground
color of blue.
Xman*borderWidth:10
Specifies that all widgets in an application whose class is Xman will
have a border width of 10 (pixels).
xman.form.button1.label:Testing
Specifies that a particular widget in the xman application will have a
label named Testing.
An exclamation point (!) in the first column of a line indicates
that the rest of the line should be treated as a comment.
Final Words
The Resource manager is a powerful tool that can be used very
effectively to customize X Toolkit applications at run time by either the
application programmer or the user. Some final points to note:
An application programmer may add new resources to their
application. These resources are associated with the global
application, and not any particular widget. The X Toolkit function used for
adding the application resources is XtGetApplicationResources.
XtGetApplicationResources
Be careful when creating resource files. Since widgets will
ignore resources that they do not understand, any spelling
errors will cause a resource to have no effect.
Only one resource line will match any given resource. There is a set
of precedence rules, which take the following general stance.
More specific overrides less specific, thus period always overrides asterisk.
Names on the left are more specific and override names on the right.
When resource specifications are exactly the same, user defaults
will override program defaults.
For a complete explanation of the rules of precedence, and
other specific topics see
X Toolkit Intrinsics - C Language Interface and Xlib - C Language Interface.
Creating Argument Lists
argument lists
To set up an argument list for the inline specification of widget attributes,
you may use any of the four approaches discussed in this section.
Each resource name has a global symbol associated with it. This
global symbol has the form XtNresource name. For example, the
symbol for foreground
is XtNforeground. For further information,
see the X Toolkit Intrinsics - C Language Interface.
Argument are specified by using the following structure:
ArgList
Arg
typedef struct {
String name;
XtArgVal value;
} Arg, *ArgList;
The first approach is to statically initialize the argument list.
For example:
static Arg arglist[] = {
{XtNwidth, (XtArgVal) 400},
{XtNheight, (XtArgVal) 300},
};
This approach is convenient for lists that do not need to be computed
at runtime and makes adding or deleting new elements easy.
The
XtNumber
XtNumber
macro is used to compute the number of elements in the argument list,
preventing simple programming errors:
XtCreateWidget(name, class, parent, arglist, XtNumber(arglist));
XtSetArg
The second approach is to use the
XtSetArg
macro.
For example:
Arg arglist[10];
XtSetArg(arglist[1], XtNwidth, 400);
XtSetArg(arglist[2], XtNheight, 300);
To make it easier to insert and delete entries,
you also can use a variable index:
Arg arglist[10];
Cardinal i=0;
XtSetArg(arglist[i], XtNwidth, 400); i++;
XtSetArg(arglist[i], XtNheight, 300); i++;
The i variable can then be used as the argument list count in the widget
create function.
In this example,
XtNumber
XtNumber
would return 10, not 2, and therefore is not useful.
You should not use auto-increment or auto-decrement
within the first argument to
XtSetArg.
As it is currently implemented,
XtSetArg
is a macro that dereferences the first argument twice.
The third approach is to individually set the elements of the
argument list array:
Arg arglist[10];
arglist[0].name = XtNwidth;
arglist[0].value = (XtArgVal) 400;
arglist[1].name = XtNheight;
arglist[1].value = (XtArgVal) 300;
Note that in this example, as in the previous example,
XtNumber
XtNumber
would return 10, not 2, and therefore would not be useful.
The fourth approach is to use a mixture of the first and third approaches:
you can statically define the argument list but modify some entries at runtime.
For example:
static Arg arglist[] = {
{XtNwidth, (XtArgVal) 400},
{XtNheight, (XtArgVal) NULL},
};
arglist[1].value = (XtArgVal) 300;
In this example,
XtNumber
XtNumber
can be used, as in the first approach, for easier code maintenance.
Example Programs
examples
The best way to understand how to use any programming library is by
trying some simple examples. A collection of example programs that
introduces each of the widgets in that Athena widget set, as well as many
important toolkit programming concepts, is available in the X11R5 contrib
release as distributed by the X Consortium. It can be found in the
directory contrib/examples/Xaw in the archive
at
See the README file from that directory for a guide
to the examples.
libXaw-1.0.16/specs/Toggle.xml 0000644 0001751 0000144 00000054667 14573370144 013055 0000000 0000000
Toggle Widget
Application Header file <Xaw/Toggle.h>
Class Header file <Xaw/ToggleP.h>
Class toggleWidgetClass
Class Name Toggle
Superclass Command
The Toggle widget is an area, often rectangular,
that displays a graphic. The graphic may be a text
string containing multiple lines of characters in an 8
bit or 16 bit character set (to be displayed with a
font), or in a multi-byte encoding (for use with
a fontset). The graphic may also be a bitmap or
pixmap.
This widget maintains a Boolean state (e.g.
True/False or On/Off) and changes state whenever it is selected. When
the pointer is on the Toggle widget, the Toggle widget may become highlighted by
drawing a rectangle around its perimeter. This highlighting indicates
that the Toggle widget is ready for selection. When pointer button 1 is
pressed and released, the Toggle widget indicates that it has changed
state by reversing its foreground and background colors, and its
notify action is invoked, calling all functions on its callback
list. If the pointer is moved off of the widget before the pointer button is
released, the Toggle widget reverts to its previous foreground and background
colors, and releasing the pointer button has no effect. This behavior allows
the user to cancel the operation.
Toggle widgets may also be part of a radio group.
A radio group is a
list of at least two Toggle widgets in which no more than one Toggle may
be set at
any time. A radio group is identified by the widget ID of any one of
its members. The convenience routine will
return information about the Toggle widget in the radio group.
Toggle widget state is preserved across changes in sensitivity.
Resources
When creating a Toggle widget instance, the following resources are
retrieved from the argument list or from the resource database:
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
bitmap
Bitmap
Pixmap
None
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
callback
Callback
XtCallbackList
NULL
colormap
Colormap
Colormap
Parent's Colormap
cornerRoundPercent
CornerRoundPercent
Dimension
25
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
encoding
Encoding
UnsignedChar
XawTextEncoding8bit
font
Font
XFontStruct
XtDefaultFont
fontSet
FontSet
XFontSet
XtDefaultFontSet
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
graphic height + 2 * internalHeight
highlightThickness
Thickness
Dimension
A
2 (0 if Shaped)
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
internalHeight
Height
Dimension
2
internalWidth
Width
Dimension
4
international
International
Boolean
C
False
justify
Justify
Justify
XtJustifyCenter (center)
label
Label
String
name of widget
leftBitmap
LeftBitmap
Bitmap
None
mappedWhenManaged
MappedWhenManaged
Boolean
True
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
radioData
RadioData
Pointer
Name of widget
radioGroup
Widget
Widget
No radio group
resize
Resize
Boolean
True
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
shapeStype
ShapeStyle
ShapeStyle
Rectangle
state
State
Boolean
Off
translations
Translations
TranslationTable
See below
width
Width
Dimension
A
graphic width + 2 * internalWidth
x
Position
Position
0
y
Position
Position
0
radioData
Specifies the data that will be returned by
when this is the currently set widget in the radio group. This
value is also used to identify the Toggle that will be set by a call to
. The value NULL will be returned by
if no widget in a radio group is currently
set. Programmers must not specify NULL (or Zero) as radioData.
radioGroup
Specifies another Toggle widget that is in the radio group to which this
Toggle widget should be added. A radio group is a group of at least two Toggle
widgets, only one of which may be set at a time. If this value is
NULL (the default) then the Toggle will not be part of any radio group
and can change state without affecting any other Toggle widgets. If the
widget specified in this resource is not already in a radio group then a
new radio group will be created containing these two Toggle widgets. No
Toggle widget can be in multiple radio groups. The behavior of a radio
group of one toggle is undefined. A converter is registered which will
convert widget names to widgets without caching.
state
Specifies whether the Toggle widget is set (True) or unset
(False).
Toggle Actions
The Toggle widget supports the following actions:
Switching the Toggle widget between the foreground and background
colors with set and unset and toggle
Processing application callbacks with notify
Switching the internal border between highlighted
and unhighlighted states with highlight and unhighlight
The following are the default translation bindings used by the
Toggle widget:
<EnterWindow>: highlight(Always)
<LeaveWindow>: unhighlight()
<Btn1Down>,<Btn1Up>: toggle() notify()
Toggle Actions
The full list of actions supported by Toggle is:
highlight(condition)
Displays the internal highlight border in the color (foreground
or background ) that contrasts with the interior color of the
Toggle widget. The conditions WhenUnset and Always are
understood by this action procedure. If no argument is passed then
WhenUnset is assumed.
unhighlight()
Displays the internal highlight border in the color (foreground
or background ) that matches the interior color of the
Toggle widget.
set()
Enters the set state, in which notify is possible. This
action causes the Toggle widget to display its interior in the
foreground color. The label or bitmap is displayed in the
background color.
unset()
Cancels the set state and displays the interior of the Toggle widget in the
background color. The label or bitmap is displayed in the
foreground color.
toggle()
Changes the current state of the Toggle widget, causing to be set
if it was previously unset, and unset if it was previously set.
If the widget is to be set, and is in a radio group then this procedure may
unset another Toggle widget causing all routines on its callback list
to be invoked. The callback routines for the Toggle that
is to be unset will be called before the one that is to be set.
reset()
Cancels any set or highlight and displays the interior of the
Toggle widget in the background color, with the label displayed in the
foreground color.
notify()
When the Toggle widget is in the set state this action calls all functions in
the callback list named by the callback resource. The value of
the call_data argument in these callback functions is undefined.
When a bitmap of depth greater that one (1) is specified the
set(), unset(), and reset() actions have no effect,
since there are no foreground and background colors used in a
multi-plane pixmap.
Radio Groups
There are typically two types of radio groups desired by applications.
The default translations for the Toggle widget implement a "zero or one
Radio groupszero or one of many
of many" radio group. This means that there may be no more than one
Toggle widget active, but there need not be any Toggle widgets active.
The other type of radio group is "one of many" and has the more strict
policy that there will always be exactly one radio button active.
Toggle widgets can be used to provide this interface with a slight
modification to the translation table of each Toggle in the group.
<EnterWindow>: highlight(Always)
<LeaveWindow>: unhighlight()
<Btn1Down>,<Btn1Up>: set() notify()
This translation table will not allow any Toggle to be unset
except as a result of another Toggle becoming set. It is
the application programmer's responsibility to choose an initial
state for the radio group by setting the state resource of one of
its member widgets to True.
Convenience Routines
The following functions allow easy access to the Toggle widget's radio
group functionality.
Changing the Toggle's Radio Group.
To enable an application to change the Toggle's radio group, add
the Toggle to a radio group, or remove the Toggle from a radio group, use
.
void XawToggleChangeRadioGroup
Widgetw, radio_group
w
Specifies the Toggle widget.
radio_group
Specifies any Toggle in the new radio group. If NULL then the Toggle
will be removed from any radio group of which it is a member.
If a Toggle is already set in the new radio group,
and the Toggle to be added is also set then the previously
set Toggle in the radio group is unset and its callback
procedures are invoked.
Finding the Currently selected Toggle in a radio group of Toggles
To find the currently selected Toggle in a radio group of Toggle widgets
use .
XtPointer XawToggleGetCurrent
XtPointer XawToggleGetCurrent(radio_group)
Widget radio_group
radio_group
Specifies any Toggle widget in the radio group.
The value returned by this function is the
radioData
of the Toggle in this radio group that is currently set. The default
value for radioData
is the name of that Toggle widget. If no Toggle is set in the radio
group specified then NULL is returned.
Changing the Toggle that is set in a radio group.
To change the Toggle that is currently set in a radio group use
.
void XawToggleSetCurrent
voidXawToggleSetCurrent(radio_group, radio_data)
Widget radio_group
XtPointer radio_data
radio_group
Specifies any Toggle widget in the radio group.
radio_data
Specifies the
radioData
identifying the Toggle that should be set in the radio group specified
by the radio_group argument.
locates the Toggle widget to be set by
matching radio_data against the radioData for each Toggle in
the radio group. If none match, returns
without making any changes. If more than one Toggle matches,
will choose a Toggle to set arbitrarily. If
this causes any Toggle widgets to change state, all routines in their
callback lists will be invoked. The callback routines for a Toggle that
is to be unset will be called before the one that is to be set.
Unsetting all Toggles in a radio group.
To unset all Toggle widgets in a radio group use
.
void XawToggleUnsetCurrent
void XawToggleUnsetCurrent(radio_group)
Widget radio_group
radio_group
Specifies any Toggle widget in the radio group.
If this causes a Toggle widget to change state, all routines on its
callback list will be invoked.
libXaw-1.0.16/specs/libXaw.xml 0000644 0001751 0000144 00000007230 14573370144 013042 0000000 0000000
%defs;
%xawdefs;
]>
Athena Widget Set - C Language Interface
X Consortium Standard
libXaw Version &xawvers;
ChrisD.Peterson
formerly MIT X Consortium
1985198619871988
198919911994
X Consortium
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files
(the “Software”), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
Except as contained in this notice, the name of the X Consortium shall not
be used in advertising or otherwise to promote the sale, use or other dealings
in this Software without prior written authorization from the X Consortium.
X Window System is a trademark of The OpenGroup.
Copyright © 1985, 1986, 1987, 1988, 1989, 1991
Digital Equipment Corporation, Maynard, Massachusetts.
Permission to use, copy, modify and distribute this documentation for any
purpose and without fee is hereby granted, provided that the above copyright
notice appears in all copies and that both that copyright notice and this
permission notice appear in supporting documentation, and that the name of
Digital not be used in in advertising or publicity pertaining
to distribution of the software without specific, written prior permission.
Digital makes no representations about the suitability of the
software described herein for any purpose.
It is provided “as is” without express or implied warranty.
libXaw-1.0.16/specs/Sme.xml 0000644 0001751 0000144 00000013636 14573370144 012347 0000000 0000000
Sme Object
Sme object
Application Header file <X11/Xaw/Sme.h>
Sme.h
Class Header file <X11/Xaw/SmeP.h>
SmeP.h
Class smeObjectClass
smeObjectClass
Class Name Sme
Sme objectclass name
Superclass RectObj
The Sme object is the base class for all menu entries. While this
object is mainly intended to be subclassed, it may be used in a menu to
add blank space between menu entries.
Resources
SmeLine objectresources
The resources associated with the SmeLine object are defined in this
section, and affect only the single menu entry specified by this object.
There are no new resources added for this class, as it picks up all its
resources from the RectObj class.
Name
Class
Type
Notes
Default Value
ancestorSensitive
AncestorSensitive
Boolean
True
callback
Callback
XtCallbackList
NULL
destroyCallback
Callback
XtCallbackList
NULL
height
Height
Dimension
0
international
International
Boolean
C
False
sensitive
Sensitive
Boolean
True
width
Width
Dimension
1
Keep in mind that the SimpleMenu widget will force all menu items to
be the width of the widest entry.
Subclassing the Sme Object
Sme objectsubclassing
To Create a new Sme object class you will need to define three class methods.
These methods allow the SimpleMenu to highlight and unhighlight the
menu entry as the pointer cursor moves over it, as well as notify the
entry when the user has selected it. All of
these methods may be inherited from the Sme object, although the default
semantics are not very interesting.
Highlight( )
Sme objectHighlight method
Called to put the menu entry into the highlighted state.
Unhighlight( )
Sme objectUnhighlight method
Called to return the widget to its normal (unhighlighted) state.
Notify( )
Sme objectNotify method
Called when the user selects this menu entry.
Other then these methods, creating a new object
is straight forward. Here is some information that may help you
avoid some common mistakes.
Objects can be zero pixels high.
Objects draw on their parent's window, therefore the Drawing dimensions
are different from those of widgets. For instance, y locations vary
from y to y + height, not 0 to height.
XtSetValues calls may come from the application while the Sme is highlighted,
and if the SetValues method returns True, will result in an expose event.
The SimpleMenu may later call the menu entry's unhighlight
procedure. However, due to the asynchronous nature of
X, the expose event generated by will come after
this unhighlight.
Remember that your subclass of the Sme does not own the
window. Share the space with other menu entries, and refrain
from drawing outside the subclass's own section of the menu.
libXaw-1.0.16/specs/Panner.xml 0000644 0001751 0000144 00000044265 14573370144 013050 0000000 0000000
Panner Widget
Panner widget
Application header file <X11/Xaw/Panner.h>
Panner.h
Class header file <X11/Xaw/PannerP.h>
PannerP.h
Class pannerWidgetClass
pannerWidgetClass
Class Name Panner
Panner widgetclass name
Superclass Simple
A Panner widget is a rectangle, called the
canvas,
on which another rectangle, the slider,
moves in two
dimensions. It is often used with a Porthole widget to move, or
scroll,
a third widget in two dimensions, in which case the
slider's size and position gives feedback as to what portion of
the third widget is visible.
The slider may be scrolled around the canvas by pressing,
dragging, and releasing Button1; the default translation also
enables scrolling via arrow keys and some other keys. While
scrolling is in progress, the application receives notification
through callback procedures. Notification may be done either
continuously whenever the slider moves or discretely whenever the
slider has been given a new location.
Resources
When creating a Panner widget instance, the following resources are
retrieved from the argument list or from the resource database:
Panner widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
allowOff
AllowOff
Boolean
False
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
backgroundStipple
BackgroundStipple
String
NULL
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
canvasHeight
CanvasHeight
Dimension
0
canvasWidth
CanvasWidth
Dimension
0
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
defaultScale
DefaultScale
Dimension
8
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
depends on orientation
internalSpace
InternalSpace
Dimension
4
international
International
Boolean
C
False
lineWidth
LineWidth
Dimension
0
mappedWhenManaged
MappedWhenManaged
Boolean
True
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
reportCallback
ReportCallback
Callback
NULL
resize
Resize
Boolean
True
rubberBand
RubberBand
Boolean
False
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
shadowColor
ShadowColor
Pixel
XtDefaultForeground
shadowThickness
ShadowThickness
Dimension
2
sliderX
SliderX
Position
0
sliderY
SliderY
Position
0
sliderHeight
SliderHeight
Dimension
0
sliderWidth
SliderWidth
Dimension
0
translations
Translations
TranslationTable
See below
width
Width
Dimension
A
depends on orientation
x
Position
Position
0
y
Position
Position
0
allowOff
Whether to allow the edges of the slider to go off the edges of the canvas.
backgroundStipple
The name of a bitmap pattern to be used as the background for
the area representing the canvas.
canvasHeight
canvasWidth
The size of the canvas.
defaultScale
The percentage size that the Panner widget should have relative
to the size of the canvas.
foreground
A pixel value which indexes the widget's colormap to derive the color
used to draw the slider.
internalSpace
The width of internal border in pixels between a slider representing the
full size of the canvas
and the edge of the Panner widget.
lineWidth
The width of the lines in the rubberbanding rectangle when rubberbanding
is in effect instead of continuous scrolling. The default is 0.
reportCallback
All functions on this callback list are called when the
notify action is invoked. See the Panner Actions section
for details.
resize
Whether or not to resize the panner whenever the canvas size is changed so
that the defaultScale is maintained.
rubberBand
Whether or not scrolling should be discrete (only moving a rubberbanded
rectangle until the scrolling is done) or continuous (moving the slider
itself). This controls whether or not the move action procedure also
invokes the notify action procedure.
shadowColor
The color of the shadow underneath the slider.
shadowThickness
The width of the shadow underneath the slider.
sliderX
sliderY
The location of the slider in the coordinates of the canvas.
sliderHeight
sliderWidth
The size of the slider.
Panner Actions
Panner widgetactions
The actions supported by the Panner widget are:
start()
This action begins movement of the slider.
stop()
This action ends movement of the slider.
abort()
This action ends movement of the slider and restores it to the position it
held when the start action was invoked.
move()
This action moves the outline of the slider (if the rubberBand resource
is True) or the slider itself (by invoking the notify
action procedure).
page(xamount,yamount)
This action moves the slider by the specified amounts. The format
for the amounts is a signed or unsigned floating-point number (e.g., +1.0
or -.5) followed
by either p indicating pages (slider sizes), or c indicating
canvas sizes. Thus, page(+0,+.5p) represents vertical movement down
one-half the height of the slider and page(0,0) represents moving to
the upper left corner of the canvas.
notify()
This action informs the application of the slider's current position by
invoking the reportCallback functions registered by the application.
set(what,value)
This action changes the behavior of the Panner. The what argument
must currently be the string rubberband and controls the value of
the rubberBand resource. The value argument
may have one of the values on, off, or toggle.
The default bindings for Panner are:
Panner widgetdefault translation table
<Btn1Down>: start( )
<Btn1Motion>: move( )
<Btn1Up>: notify( ) stop( )
<Btn2Down>: abort( )
<Key>KP_Enter: set(rubberband,toggle)
<Key>space: page(+1p,+1p)
<Key>Delete: page(-1p,-1p)
<Key>BackSpace: page(-1p,-1p)
<Key>Left: page(-.5p,+0)
<Key>Right: page(+.5p,+0)
<Key>Up: page(+0,-.5p)
<Key>Down: page(+0,+.5p)
<Key>Home: page(0,0)
Panner Callbacks
Panner widgetcallbacks
The functions registered on the reportCallback list are invoked by
the notify action as follows:
ReportProc
void ReportProc
Widget panner
XtPointer client_data
XtPointer report
panner
Specifies the Panner widget.
panner
Specifies the client data.
panner
Specifies a pointer to an XawPannerReport structure containing
the location and size of the slider and the size of the canvas.
libXaw-1.0.16/specs/TextActions.xml 0000644 0001751 0000144 00000074062 14573370144 014070 0000000 0000000
Text Widget Actions
Text widgetactions
Text widgetactions
All editing functions are performed by translation manager actions that may
be specified through the translations resource in the Text widget.
Insert Point Movement Delete
forward-character delete-next-character
backward-character delete-previous-character
forward-word delete-next-word
backward-word delete-previous-word
forward-paragraph delete-selection
backward-paragraph
beginning-of-line
end-of-line Selection
next-line select-word
previous-line select-all
next-page select-start
previous-page select-adjust
beginning-of-file select-end
end-of-file extend-start
scroll-one-line-up extend-adjust
scroll-one-line-down extend-end
insert-selection
Miscellaneous New Line
redraw-display newline-and-indent
insert-file newline-and-backup
insert-char newline
insert-string
display-caret
focus-in Kill
focus-in kill-word
search backward-kill-word
multiply kill-selection
form-paragraph kill-to-end-of-line
transpose-characters kill-paragraph
no-op kill-to-end-of-paragraph
XawWMProtocols
reconnect-im
Most of the actions take no arguments, and unless otherwise noted you
may assume this to be the case.
Cursor Movement Actions
forward-character()
backward-character()
These actions move the insert point forward or backward one character in
the buffer. If the insert point is at the end or beginning of a line
this action will move the insert point to the next (or previous) line.
forward-word()
backward-word()
These actions move the insert point to the next or previous word boundary.
A word boundary is defined as a Space, Tab or Carriage Return.
forward-paragraph()
backward-paragraph()
These actions move the insert point to the next or previous paragraph boundary.
A paragraph boundary is defined as two Carriage Returns in a row with only
Spaces or Tabs between them.
beginning-of-line()
end-of-line()
These actions move to the beginning or end of the current line. If the
insert point is already at the end or beginning of the line then no action is taken.
next-line()
previous-line()
These actions move the insert point up or down one line. If the insert
point is currently N characters from the beginning of the line then it
will be N characters from the beginning of the next or previous line.
If N is past the end of the line, the insert point is placed at the end
of the line.
next-page()
previous-page()
These actions move the insert point up or down one page in the file.
One page is defined as the current height of the text widget. The
insert point is always placed at the first character of the top line by
this action.
beginning-of-file()
end-of-file()
These actions place the insert point at the beginning or end of the
current text buffer. The text widget is then scrolled the minimum
amount necessary to make the new insert point location visible.
scroll-one-line-up()
scroll-one-line-down()
These actions scroll the current text field up or down by one line.
They do not move the insert point. Other than the scrollbars this is
the only way that the insert point may be moved off of the visible text
area. The widget will be scrolled so that the insert point is back on
the screen as soon as some other action is executed.
Delete Actions
delete-next-character()
delete-previous-character()
These actions remove the character immediately before or after the
insert point. If a Carriage Return is removed then the next line is
appended to the end of the current line.
delete-next-word()
delete-previous-word()
These actions remove all characters between the insert point location and
the next word boundary. A word boundary is defined as a Space, Tab or
Carriage Return.
delete-selection()
This action removes all characters in the current selection.
The selection can be set with the selection actions.
Selection Actions
select-word()
This action selects the word in which the insert point is currently located.
If the insert point is between words then it will select the previous word.
select-all()
This action selects the entire text buffer.
select-start()
This action sets the insert point to the current pointer location (if
triggered by a button event) or text cursor location (if triggered by
a key event). It
will then begin a selection at this location. If many of these
selection actions occur quickly in succession then the selection count
mechanism will be invoked (see
for details).
select-adjust()
This action allows a selection started with the select-start
action to be modified, as described above.
select-end(name[,name,...])
This action ends a text selection that began with the select-start
action, and asserts ownership of the selection or selections specified.
A name can be a selection (e.g., PRIMARY) or a cut buffer
(e.g., CUT_BUFFER0). Note that case is important. If no
names are specified, PRIMARY is asserted.
extend-start()
This action finds the nearest end of the current selection, and moves it
to the current pointer location (if triggered by a button event) or text
cursor location (if triggered by a key event).
extend-adjust()
This action allows a selection started with an extend-start action
to be modified.
extend-end(name[,name,...])
This action ends a text selection that began with the extend-start
action, and asserts ownership of the selection or selections specified.
A name can be a selection (e.g. PRIMARY) or a cut buffer
(e.g CUT_BUFFER0). Note that case is important. If no names are
given, PRIMARY is asserted.
insert-selection(name[,name,...])
This action retrieves the value of the first (left-most) named selection
that exists or the cut buffer that is not empty and inserts it into the
Text widget at the current insert point location. A name can be a
selection (e.g. PRIMARY) or a cut buffer (e.g CUT_BUFFER0).
Note that case is important.
The New Line Actions
newline-and-indent()
This action inserts a newline into the text and adds spaces to
that line to indent it to match the previous line.
newline-and-backup()
This action inserts a newline into the text after the insert point.
newline()
This action inserts a newline into the text before the insert point.
Kill and Actions
kill-word()
backward-kill-word()
These actions act exactly like the delete-next-word and
delete-previous-word actions, but they stuff the word that was
killed into the kill buffer (CUT_BUFFER_1).
kill-selection()
This action deletes the current selection and stuffs the deleted text into
the kill buffer (CUT_BUFFER_1).
kill-to-end-of-line()
This action deletes the entire line to the right of the insert point position,
and stuffs the deleted text into the kill buffer (CUT_BUFFER_1).
kill-paragraph()
This action deletes the current paragraph, if between paragraphs it deletes
the paragraph above the insert point, and stuffs the deleted text into
the kill buffer (CUT_BUFFER_1).
kill-to-end-of-paragraph()
This action deletes everything between the current insert point location and
the next paragraph boundary, and stuffs the deleted text into the kill
buffer (CUT_BUFFER_1).
Miscellaneous Actions
redraw-display()
This action recomputes the location of all the text lines on the
display, scrolls the text to vertically center the line containing the insert point
on the screen, clears the entire screen, and redisplays it.
insert-file([filename])
This action activates the insert file popup. The filename
option specifies the default filename to put in the filename buffer of
the popup. If no filename is specified the buffer is empty
at startup.
insert-char()
This action may only be attached to a key event. When the
international resource is false, this action
calls XLookupString to translate the event into a (rebindable) Latin-1
character (sequence) and inserts it into the text at the
insert point. When the international resource is true,
characters are passed to the input method via XwcLookupString, and any
committed string returned is inserted into the text at the insert point.
insert-string(string[,string,...])
This action inserts each string into the text
at the insert point location. Any string
beginning with the characters "0x" followed by an even
number of hexadecimal digits is
interpreted as a hexadecimal constant and the
corresponding string is inserted instead. This
hexadecimal string may represent up to 50 8-bit characters.
When theinternational resource is
true, a hexadecimal string is intrepeted as
being in a multi-byte encoding, and a hexadecimal
or regular string will result in an error message
if it is not legal in the current locale.
display-caret(state,when)
This action allows the insert point to be turned on and off.
The state argument specifies the desired state of the insert point.
This value may be any of the string
values accepted for Boolean resources (e.g. on, True,
off, False, etc.). If no arguments are specified, the
default value is True.
The when argument specifies, for EnterNotify or LeaveNotify
events whether or not the focus field in the event is to be examined.
If the second argument is not specified, or specified as something other
than always then if the action is bound to an EnterNotify
or LeaveNotify event, the action will be taken only if the focus
field is True. An augmented binding that might be useful is:
*Text.Translations: #override \\
<FocusIn>: display-caret(on) \\n\\
<FocusOut>: display-caret(off)
focus-in()
focus-out()
These actions do not currently do anything.
search(direction,[string])
This action activates the search popup. The direction must be
specified as either forward or backward. The string is
optional and is used as an initial value for the Search for: string.
For further explanation of the search widget see the section on
Text Searches.
multiply(value)
The multiply action allows the user to multiply the effects of many of
the text actions. Thus the following action sequence
multiply(10) delete-next-word() will delete 10 words. It does not
matter whether these actions take place in one event or many events.
Using the default translations the key sequence
Control-u, Control-d will delete 4 characters.
Multiply actions can be chained, thus
multiply(5) multiply(5) is the same as
multiply(25). If the string
reset is passed to the multiply action the effects of all previous
multiplies are removed and a beep is sent to the display.
form-paragraph()
This action removes all the Carriage Returns from the current
paragraph and reinserts them so that each line is as long as possible, while
still fitting on the current screen. Lines are broken at word boundaries if
at all possible. This action currently works only on Text widgets
that use ASCII text.
transpose-characters()
This action will swap the position of the character to the left of the
insert point with the character to the right of the insert point. The insert point will then
be advanced one character.
no-op([action])
The no-op action makes no change to the text widget, and is mainly used
to override translations. This action takes one optional argument. If
this argument is RingBell then a beep is sent to the display.
XawWMProtocols([wm_protocol_name])
XawWMProtocols
This action is written specifically for the file insertion and the search
and replace
dialog boxes. This action is attached to those shells by the Text widget,
in order to handle ClientMessage events with the WM_PROTOCOLS atom in the
detail field. This action supports WM_DELETE_WINDOW on the Text widget
popups, and may support other window manager protocols if necessary in
the future. The popup will be dismissed if the window manager sends
a WM_DELETE_WINDOW request and there are no parameters in the action
call, which is the default. The popup will also be dismissed if the
parameters include the string wm_delete_window,
and the event is a
ClientMessage event requesting dismissal or is not a ClientMessage event.
This action is not sensitive to the case of the strings passed as parameters.
reconnect-im()
Input Method
When the international resource is true,
input is usually passed to an input method, a separate
process, for composing. Sometimes the connection to
this process gets severed; this action will attempt to
reconnect it. Causes for severage include network
trouble, and the user explicitly killing one input
method and starting a new one. This action may also
establish first connection when the application is
started before the input method.
Text Selections for Application Programmers
Text widgetText Selections for Application Programmers
The default behavior of the text selection array is described in the
section called Text Selections for Users. To modify the selections
a programmer must construct a XawTextSelectType array (called the
selection array), containing the selections desired, and pass this as
the new value for the selectionTypes resource. The selection
array may also be modified using the
XawTextSetSelectionArray
function. All selection arrays must end with the value
XawselectNull. The selectionTypes resource has no converter
registered and cannot be modified through the resource manager.
The array contains a list of entries that will be called when the user
attempts to select text in rapid succession with the select-start
action (usually by clicking a pointer button). The first entry in the
selection array will be used when the select-start action is
initially called. The next entry will be used when select-start
is called again, and so on. If a timeout value (1/10 of a second) is
exceeded, the the next select-start action will begin at the top
of the selection array. When XawselectNull is reached the array
is recycled beginning with the first element.
XawselectAll
Selects the contents of the entire buffer.
XawselectChar
Selects text characters as the pointer moves over them.
XawselectLine
Selects the entire line.
XawselectNull
Indicates the end of the selection array.
XawselectParagraph
Selects the entire paragraph.
XawselectPosition
Selects the current pointer position.
XawselectWord
Selects whole words as the pointer moves onto them.
The default selectType array is:
{XawselectPosition, XawselectWord, XawselectLine, XawselectParagraph, XawselectAll, XawselectNull}
The selection array is not copied by the text widgets. The
application must allocate space for the array and cannot deallocate or
change it until the text widget is destroyed or until a new selection
array is set.
Default Translation Bindings
Text widgetdefault translations
The following translations are defaults built into every Text widget.
They can be overridden, or replaced by specifying a new value for the
Text widget's translations resource.
Ctrl<Key>A: beginning-of-line() \\n\\
Ctrl<Key>B: backward-character() \\n\\
Ctrl<Key>D: delete-next-character() \\n\\
Ctrl<Key>E: end-of-line() \\n\\
Ctrl<Key>F: forward-character() \\n\\
Ctrl<Key>G: multiply(Reset) \\n\\
Ctrl<Key>H: delete-previous-character() \\n\\
Ctrl<Key>J: newline-and-indent() \\n\\
Ctrl<Key>K: kill-to-end-of-line() \\n\\
Ctrl<Key>L: redraw-display() \\n\\
Ctrl<Key>M: newline() \\n\\
Ctrl<Key>N: next-line() \\n\\
Ctrl<Key>O: newline-and-backup() \\n\\
Ctrl<Key>P: previous-line() \\n\\
Ctrl<Key>R: search(backward) \\n\\
Ctrl<Key>S: search(forward) \\n\\
Ctrl<Key>T: transpose-characters() \\n\\
Ctrl<Key>U: multiply(4) \\n\\
Ctrl<Key>V: next-page() \\n\\
Ctrl<Key>W: kill-selection() \\n\\
Ctrl<Key>Y: insert-selection(CUT_BUFFER1) \\n\\
Ctrl<Key>Z: scroll-one-line-up() \\n\\
Ctrl<Key>\\: reconnect-im() \\n\\
Meta<Key>B: backward-word() \\n\\
Meta<Key>F: forward-word() \\n\\
Meta<Key>I: insert-file() \\n\\
Meta<Key>K: kill-to-end-of-paragraph() \\n\\
Meta<Key>Q: form-paragraph() \\n\\
Meta<Key>V: previous-page() \\n\\
Meta<Key>Y: insert-selection(PRIMARY, CUT_BUFFER0) \\n\\
Meta<Key>Z: scroll-one-line-down() \\n\\
:Meta<Key>d: delete-next-word() \\n\\
:Meta<Key>D: kill-word() \\n\\
:Meta<Key>h: delete-previous-word() \\n\\
:Meta<Key>H: backward-kill-word() \\n\\
:Meta<Key>\\<: beginning-of-file() \\n\\
:Meta<Key>\\>: end-of-file() \\n\\
:Meta<Key>]: forward-paragraph() \\n\\
:Meta<Key>[: backward-paragraph() \\n\\
~Shift Meta<Key>Delete: delete-previous-word() \\n\\
Shift Meta<Key>Delete: backward-kill-word() \\n\\
~Shift Meta<Key>Backspace: delete-previous-word() \\n\\
Shift Meta<Key>Backspace: backward-kill-word() \\n\\
<Key>Right: forward-character() \\n\\
<Key>Left: backward-character() \\n\\
<Key>Down: next-line() \\n\\
<Key>Up: previous-line() \\n\\
<Key>Delete: delete-previous-character() \\n\\
<Key>BackSpace: delete-previous-character() \\n\\
<Key>Linefeed: newline-and-indent() \\n\\
<Key>Return: newline() \\n\\
<Key>: insert-char() \\n\\
<Key>Kanji: reconnect-im() \\n\\
<FocusIn>: focus-in() \\n\\
<FocusOut>: focus-out() \\n\\
<Btn1Down>: select-start() \\n\\
<Btn1Motion>: extend-adjust() \\n\\
<Btn1Up>: extend-end(PRIMARY, CUT_BUFFER0) \\n\\
<Btn2Down>: insert-selection(PRIMARY, CUT_BUFFER0) \\n\\
<Btn3Down>: extend-start() \\n\\
<Btn3Motion>: extend-adjust() \\n\\
<Btn3Up>: extend-end(PRIMARY, CUT_BUFFER0) \\n
libXaw-1.0.16/specs/Form.xml 0000644 0001751 0000144 00000035516 14573370144 012527 0000000 0000000
Form Widget
Form widget
Application Header file <X11/Xaw/Form.h>
Form.h
Class Header file <X11/Xaw/FormP.h>
FormP.h
Class formWidgetClass
formWidgetClass
Class Name Form
Form widgetclass name
Superclass Constraint
The Form widget can contain an arbitrary number of children or
subwidgets. The Form provides geometry management for its children,
which allows individual control of the position of each child. Any
combination of children can be added to a Form. The initial positions
of the children may be computed relative to the positions of previously
created children. When the Form is resized, it computes new positions and
sizes for its children. This computation is based upon information
provided when a child is added to the Form.
The default width of the Form is the minimum width needed to
enclose the children after computing their initial layout, with a
margin of defaultDistance
at the right and bottom edges. If a width and height is assigned
to the Form that is too small for the layout, the children will
be clipped by the right and bottom edges of the Form.
Resources
When creating a Form widget instance, the following resources are
retrieved from the argument list or from the resource database:
Form widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
children
ReadOnly
WidgetList
R
NULL
colormap
Colormap
Colormap
Parent's Colormap
defaultDistance
Thickness
int
4
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
height
Height
Dimension
A
Enough space to contain all children
mappedWhenManaged
MappedWhenManaged
Boolean
True
numChildren
ReadOnly
Cardinal
R
0
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
width
Width
Dimension
A
Enough space to contain all children
x
Position
Position
0
y
Position
Position
0
_
Constraint Resources
Form widgetconstraint resources
Each child of the Form widget may request special layout resources
be applied to it. These constraint resources allow the Form
widget's children to specify individual layout requirements.
Name
Class
Type
Notes
Default Value
bottom
Edge
XawEdgeType
XawRubber
fromHoriz
Widget
Widget
NULL (left edge of Form)
fromVert
Widget
Widget
NULL (top edge of Form)
horizDistance
Thickness
int
defaultDistance resource
left
Edge
XawEdgeType
XawRubber
resizable
Boolean
Boolean
FALSE
right
Edge
XawEdgeType
XawRubber
top
Edge
XawEdgeType
XawRubber
vertDistance
Thickness
int
defaultDistance resource
bottom
left
right
top What to do with this edge of the child when
the parent is resized. This resource may be
any edgeType. See Layout Semantics for
details.
fromHoriz
fromVert Which widget this child should be placed
underneath (or to the right of). If a value
of NULL is specified then this widget will be
positioned relative to the edge of the par-
ent.
horizDistance
vertDistance The amount of space, in pixels, between this
child and its left or upper neighbor.
resizable If this resource is False then the parent
widget will ignore all geometry request made
by this child. The parent may still resize
this child itself, however.
Layout Semantics
The Form widget uses two different sets of layout semantics.
One is used when initially laying out the children. The
other is used when the Form is resized.
The first layout method uses the fromVert
and fromHoriz
resources to place the children of the Form. A single pass
is made through the Form widget's children in the order that
they were created. Each child is then placed in the Form
widget below or to the right of the widget specified by the
fromVert and fromHoriz
resources. The distance the new
child is placed from its left or upper neighbor is deter-
mined by the horizDistance and
vertDistance resources. This
implies some things about how the order of creation affects
the possible placement of the children. The Form widget
registers a string to widget converter which does not post-
pone conversion and does not cache conversion results.
The second layout method is used when the Form is resized.
It does not matter what causes this resize, and it is possi-
ble for a resize to happen before the widget becomes visible
(due to constraints imposed by the parent of the Form).
This layout method uses the bottom,
top, left, and
right
resources. These resources are used to determine what will
happen to each edge of the child when the Form is resized.
If a value of XawChain
<something> is specified, the the edge
of the child will remain a fixed distance from the
chain
edge of the Form. For example if XawChainLeft is specified
for the right resource of a child then the right edge of
that child will remain a fixed distance from the left edge
of the Form widget. If a value of XawRubber is specified,
that edge will grow by the same percentage that the Form
grew. For instance if the Form grows by 50% the left edge
of the child (if specified as XawRubber will be 50% farther
from the left edge of the Form). One must be very careful
when specifying these resources, for when they are specified
incorrectly children may overlap or completely occlude other
children when the Form widget is resized.
Edge Type
Resource Name
Description
XawChainBottom
ChainBottom
Edge remains a fixed distance from bottom of Form
XawChainLeft
ChainLeft
Edge remains a fixed distance from left of Form
XawChainRight
ChainRight
Edge remains a fixed distance from right of Form
XawChainTop
ChainTop
Edge remains a fixed distance from top of Form
XawRubber
Rubber
Edges will move a proportional distance
Example
If you wish to force the Form to never resize one or more of its
children, then set left and right to XawChainLeft and
top and bottom to XawChainTop. This will cause the
child to remain a fixed distance from the top and left edges of the
Form, and never to resize.
Convenience Routines
To force or defer a re-layout of the Form, use
Form widgetre-layout
XawFormDoLayout
void XawFormDoLayout
Widget w
Boolean do_layout
w
Specifies the Form widget.
do_layout
Specifies whether the layout of the Form widget is enabled (True)
or disabled (False).
When making several changes to the children of a Form widget
after the Form has been realized, it is a good idea to disable
relayout until after all changes have been made.
libXaw-1.0.16/specs/CH4.xml 0000644 0001751 0000144 00000010062 14573370144 012167 0000000 0000000
libXaw-1.0.16/specs/TextSource.xml 0000644 0001751 0000144 00000043607 14573370144 013731 0000000 0000000
TextSrc Object
Application Header file <X11/Xaw/TextSrc.h>
Class Header file <X11/Xaw/TextSrcP.h>
Class textSrcObjectClass
Class Name TextSrc
Superclass Object
The TextSrc object is the root object for all text sources. Any new text
source objects should be subclasses of the TextSrc Object. The
TextSrc Class contains all methods the Text widget expects a text
source to export.
Since all text sources will have some resources in common the
TextSrc defines a few new resources.
Resources
When creating an TextSrc object instance, the following resources are
retrieved from the argument list or from the resource database:
Name
Class
Type
Notes
Default Value
destroyCallback
Callback
XtCallbackList
NULL
editType
EditType
EditMode
NULL
Subclassing the TextSrc
The only purpose of the TextSrc Object is to be subclassed. It contains
the minimum set of class methods that all text sources must have. All
class methods of the TextSrc must be defined, as the Text widget uses
them all. While all may be inherited, the direct descendant of TextSrc
must specify some of them as TextSrc does not contain enough
information to be a valid text source by itself. Do not try to use the
TextSrc as a valid source for the Text widget; it is not intended to be
used as a source by itself and bad things will probably happen.
Function
Inherit with
Public Interface
must specify
Read
XtInheritRead
XawTextSourceRead
yes
Replace
XtInheritReplace
XawTextSourceReplace
no
Scan
XtInheritScan
XawTextSourceScan
yes
Search
XtInheritSearch
XawTextSourceSearch
no
SetSelection
XtInheritSetSelection
XawTextSourceSetSelection
no
ConvertSelection
XtInheritConvertSelection
XawTextSourceConvertSelection
no
Reading Text.
To read the text in a text source use the function:
TextSrc objectRead
XawTextPosition Read
Widget w
XawTextPosition pos
XawTextBlock *text_return
int length
w
Specifies the TextSrc object.
pos
Specifies the position of the first character to be read from the text buffer.
text
Returns the text read from the source.
length
Specifies the maximum number of characters the TextSrc should
return to the application in text_return.
This function returns the text position immediately after the
characters read from the
text buffer. The function is not required to read length
characters if that many characters are in the file, it may break at
any point that is convenient to the internal structure of the
source. It may take several calls to before the desired
portion of the text buffer is fully retrieved.
Replacing Text.
To replace or edit the text in a text buffer use the function:
XawTextPosition Replace
Widget w
XawTextPositionstart, end
XawTextBlock *text
w
Specifies the TextSrc object.
start
Specifies the position of the first character to be removed from the text
buffer. This is also the location to begin inserting the new text.
end
Specifies the position immediately after the last character to be
removed from the text buffer.
text
Specifies the text to be added to the text source.
This function can return any of the following values:
XawEditDone
The text replacement was successful.
XawPositionError
XawPositionError
The edit mode is XawtextAppend and start is not the last
character of the source.
XawEditError
XawEditError
Either the Source was read-only or the range to be deleted is larger
than the length of the Source.
The arguments start and end represent the
text source character positions for the existing text that is to be
replaced by the text in the text block. The characters from
start up to but not including end are deleted, and the
buffer specified by the text block is inserted in their
place. If start and end are equal, no text is deleted and
the new text is inserted after start.
Scanning the TextSrc
To search the text source for one of the predefined boundary types use
the function:
XawTextPosition Scan
Widget w
XawTextPosition position
XawTextScanType type
XawTextScanDirection dir
int count
Boolean include
w
Specifies the TextSrc object.
position
Specifies the position to begin scanning the source.
type
Specifies the type of boundary to scan for, may be one of:
XawstPosition, XawstWhiteSpace, XawstEOL,
XawstParagraph, XawstAll. The exact meaning of these
boundaries is left up to the individual text source.
dir
Specifies the direction to scan, may be either XawsdLeft to search
XawsdLeft
backward, or XawsdRight to search forward.
XawsdRight
count
Specifies the number of boundaries to scan for.
include
Specifies whether the boundary itself should be included in the scan.
The function returns the position in the text source of the desired
boundary. It is expected to return a valid address for
all calls made to it, thus if a particular request is made that would take
the text widget beyond the end of the source it must return the
position of that end.
Searching through a TextSrc
To search for a particular string use the function.
XawTextPosition Search
Widget w
XawTextPosition position
XawTextScanDirection dir
XawTextBlock *text
w
Specifies the TextSrc object.
position
Specifies the position to begin the search.
dir
Specifies the direction to search, may be either XawsdLeft to search
XawsdLeft
backward, or XawsdRight to search forward.
XawsdRight
text
Specifies a text block containing the text to search for.
This function will search through the text buffer attempting to find a
match for the string in the text block. If a match is found in the
direction specified, then the character location of the first character
in the string is returned. If no text was found then
XawTextSearchError is returned.
Text Selections
While many selection types are handled by the Text widget, text sources
may have selection types unknown to the Text widget. When a selection
conversion is requested by the X server the Text widget will first call
the ConvertSelection function, to attempt the selection
conversion.
Boolean ConvertSelections
Widget w
Atom*selection,*target, *type
caddr_t *value_return
unsignedlong *length_return
int *format_return
w
Specifies the TextSrc object.
selection
Specifies the type of selection that was requested (e.g. PRIMARY).
target
Specifies the type of the selection that has been requested, which
indicates the desired information about the selection (e.g. Filename,
Text, Window).
type
Specifies a pointer to the atom into which the property type of the converted
value of the selection is to be stored. For instance, either file
name or text might have property type XA_STRING.
value_return
Returns a pointer into which a pointer to the converted value of the
selection
is to be stored. The selection owner is responsible for allocating
this storage. The memory is considered owned by the toolkit, and is
freed by XtFree when the Intrinsics selection mechanism is done with it.
length_return
Returns a pointer into which the number of elements in value is to be stored.
The size of each element is determined by format.
format_return
Returns a pointer into which the size in bits of the data elements of the
selection value is to be stored.
If this function returns True then the Text widget will assume
that the source has taken care of converting the selection, Otherwise the
Text widget will attempt to convert the selection itself.
If the source needs to know when the text selection is modified it
should define a procedure:
void SetSelection
Widget w
XawTextPositionstart, end
Atom selection
w
Specifies the TextSrc object.
start
Specifies the character position of the beginning of the new text selection.
end
Specifies the character position of the end of the new text selection.
selection
Specifies the type of selection that was requested (e.g. PRIMARY).
libXaw-1.0.16/specs/CH6.xml 0000644 0001751 0000144 00000010335 14573370144 012174 0000000 0000000
Composite and Constraint Widgets
These widgets may contain arbitrary widget children. They implement a
policy for the size and location of their children.
Box
This widget will pack its children as tightly as possible in non-overlapping rows.
Dialog
An implementation of a commonly used interaction semantic to prompt for
auxiliary input from the user, such as a filename.
Form
A more sophisticated layout widget that allows the children to specify
their positions relative to the other children, or to the edges of the Form.
Paned
Allows children to be tiled vertically or horizontally. Controls are
also provided to allow the user to dynamically resize the individual panes.
Porthole
Allows viewing of a managed child which is as large as, or larger than its
parent, typically under control of a Panner widget.
Tree
Provides geometry management of widgets arranged in a directed, acyclic graph.
Viewport
Consists of a frame, one or two scrollbars, and an inner window. The
inner window can contain all the data that is to be displayed. This inner
window will be clipped by the frame with the scrollbars controlling
which section of the inner window is currently visible.
The geometry management semantics provided by the X Toolkit give full
control of the size and position of a widget to the parent of that
widget. While the children are allowed to request a certain size or
location, it is the parent who makes the final decision. Many of the
composite widgets here will deny any geometry request from their
children by default. If a child widget is not getting the expected size
or location, it is most likely the parent disallowing a request, or
implementing semantics slightly different than those expected by the
application programmer.
If the application wishes to change the size or location of
any widget it should make a call to . This will
XtSetValues
allow the widget to ask its parent for the new size or location.
As noted above the parent is allowed to refuse this request,
and the child must live with the result. If the
application is unable to achieve the desired semantics, then perhaps it
should use a different composite widget. Under no circumstances
should an application programmer resort to XtMoveWidget or
XtMoveWidget
XtResizeWidget; these functions are exclusively for the use of
XtResizeWidget
Composite widget implementors.
For more information on geometry management consult the
X Toolkit Intrinsics - C Language Interface.
libXaw-1.0.16/specs/Box.xml 0000644 0001751 0000144 00000022066 14573370144 012350 0000000 0000000
Box Widget
Box widget
Application Header file <X11/Xaw/Box.h>
Box.h
Class Header file <X11/Xaw/BoxP.h>
BoxP.h
Class boxWidgetClass
boxWidgetClass
Class Name Box
Box widgetclass name
Superclass Composite
The Box widget provides geometry management of arbitrary widgets in a
box of a specified dimension. The children are rearranged when
resizing events occur either on the Box or its children, or when
children are managed or unmanaged. The Box widget always attempts to
pack its children as tightly as possible within the geometry allowed by
its parent.
Box widgets are commonly used to manage a related set of buttons and
are often called ButtonBox widgets, but the children are not
limited to buttons. The Box's children are arranged on a background that
has its own specified dimensions and color.
Resources
When creating a Box widget instance, the following resources are
retrieved from the argument list or from the resource database:
Box widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
children
ReadOnly
WidgetList
R
NULL
colormap
Colormap
Colormap
Parent's Colormap
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
height
Height
Dimension
A
see Layout Semantics
hSpace
HSpace
Dimension
4
mappedWhenManaged
MappedWhenManaged
Boolean
True
numChildren
ReadOnly
Cardinal
R
0
orientation
Orientation
Orientation
XtorientVertical
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
vSpace
VSpace
Dimension
4
translations
Translations
TranslationTable
NULL
width
Width
Dimension
A
see Layout Semantics
x
Position
Position
0
y
Position
Position
0
_
hSpace
vSpace
The amount of space, in pixels, to leave between the children. This
resource specifies the amount of space left between the outermost
children and the edge of the box.
orientation
Specifies whether the preferred shape of the box (i.e. the result
returned by the query_geometry class method) is tall and narrow
XtorientVertical or short and wide XtorientHorizontal.
XtorientVertical
XtorientHorizontal
conversionsOrientation
When the Box is a child of a parent which enforces width constraints, it
is usually better to specify XtorientVertical (the default).
When the parent enforces height constraints, it is usually better to
specify XtorientHorizontal.
Layout Semantics
Box widgetlayout semantics
Each time a child is managed or unmanaged, the Box widget will attempt
to reposition the remaining children to compact the box. Children are
positioned in order left to right, top to bottom. The packing
algorithm used depends on the orientation of the Box.
XtorientVertical
XtorientVertical
When the next child does not fit on the current row, a new row is
started. If a child is wider than the width of the box, the box will
request a larger width from its parent and will begin the layout
process from the beginning if a new width is granted.
XtorientHorizontal
XtorientHorizontal
When the next child does not fit on the current row, the Box widens if
possible (so as to keep children on a single row); otherwise a new row is
started.
After positioning all children, the Box widget attempts to shrink its
own size to the minimum dimensions required for the layout.
libXaw-1.0.16/specs/CH1.xml 0000644 0001751 0000144 00000052457 14573370144 012202 0000000 0000000
Athena Widgets and The Intrinsics
The X Toolkit is made up of two distinct pieces, the Xt Intrinsics and a
widget set. The Athena widget set is a sample implementation of a
widget set built upon the Intrinsics. In the X Toolkit, a widget is the
combination of an X window or subwindow and its associated input and
output semantics.
Because the Intrinsics 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 Intrinsics. Since widget sets may also
implement private protocols, all functionality may not be available when
mixing and matching widget sets. For information about the Intrinsics, see
the X Toolkit Intrinsics - C Language Interface.
The Athena widget set is a library package layered on top of the Intrinsics
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
Intrinsics are a Consortium standard, there is no standard widget set.
To the extent possible, the Intrinsics are "policy-free". The application
environment and widget set, not the Intrinsics, define, implement, and
enforce:
Policy
Consistency
Style
Each individual widget implementation defines its own policy. The X Toolkit
design allows for, but does not necessarily encourage, the free mixing
of radically differing widget implementations.
Introduction to the X Toolkit
introduction
The X Toolkit 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 X Toolkit in their applications, programmers can present a similar
user interface across applications to all workstation users.
The X Toolkit consists of:
A set of Intrinsics functions for building widgets
An architectural model for constructing widgets
A widget set for application programming
While the majority of the Intrinsics functions are intended
for the widget programmer,
a subset of the Intrinsics functions are to be used by application programmers
(see X Toolkit Intrinsics - C Language Interface).
The architectural model lets the widget programmer design new widgets
by using the Intrinsics and by combining other widgets.
The application interface layers built on top of the X Toolkit 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
applications.
The remainder of this chapter discusses the X Toolkit and Athena widget set:
Terminology
Model
Conventions used in this manual
Format of the Widget Reference Chapters
Terminology
In addition to the terms already defined for X programming (see
Xlib - C Language Interface),
the following terms are specific to the Intrinsics and Athena widget set
and used throughout this document.
Application programmer
application programmer
A programmer who uses the X Toolkit to produce an application user interface.
Child
child
A widget that is contained within another "parent" widget.
Class
class
The general group to which a specific object belongs.
Client
client
A function that uses a widget in an application or for composing
other widgets.
FullName
FullName
The name of a widget instance appended to the full name of its parent.
Instance
instance
A specific widget object as opposed to a general widget class.
Method
method
A function or procedure implemented by a widget class.
Name
namewidget
The name that is specific to an instance of a widget for a given client.
This name is specified at creation time and cannot be modified.
Object
object
A data abstraction consisting of private data and private and public
functions that operate on the private data.
Users of the abstraction can interact with the object only through calls
to the object's public functions.
In the X Toolkit,
some of the object's public functions are called directly by the application,
while others are called indirectly when the application calls the common
Intrinsics functions.
In general, if a function is common to all widgets,
an application uses a single Intrinsics function to invoke the function for all
types of widgets.
If a function is unique to a single widget type,
the widget exports the function.
Parent
parent
A widget that contains at least one other ("child") widget.
A parent widget is also known as a composite widget.
Resource
resource
A named piece of data in a widget that can be set by a client,
by an application, or by user defaults.
Superclass
superclass
A larger class of which a specific class is a member.
All members of a class are also members of the superclass.
User
user
A person interacting with a workstation.
Widget
widget
An object providing a user-interface abstraction (for example, a Scrollbar
widget).
Widget class
widget class
The general group to which a specific widget belongs,
otherwise known as the type of the widget.
Widget programmer
widget programmer
A programmer who adds new widgets to the X Toolkit.
Underlying Model
underlying model
The underlying architectural model is based on the following premises:
Widgets are X windows
Every user-interface widget is associated with an X window.
The X window ID for a widget is readily available from the widget.
Standard Xlib calls can be used by widgets for many of their input and
output operations.
Information hiding
The data for every widget is private to the widget and its subclasses.
That is, the data is neither directly accessible
nor visible outside of the module implementing the widget.
All program interaction with the widget is performed by a set of operations
(methods) that are defined for the widget.
Widget semantics and widget layout geometry
Widget semantics are clearly separated from widget layout geometry.
Widgets are concerned with implementing specific user-interface
semantics. They have little control over issues such as their size or
placement relative to other widget peers. Mechanisms are provided for
associating geometric managers with widgets and for widgets to make
suggestions about their own geometry.
Conventions Used in this Manual
conventionsused in manual
All resources available to the widgets are listed with each widget. Many
of these are available to more than one widget class due to the object
oriented nature of the Intrinsics. The new resources for each widget are
listed in bold text, and the inherited resources are listed in plain text.
Global symbols are printed in bold and can be function names,
symbols defined in include files, or structure names. Arguments 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. Where
applicable, the last paragraph of the explanation lists the return values
of the function.
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. The explanations for all arguments that you can pass
and are returned start with the words specifies and returns.
Any pointer to a structure that is used to return a value is
designated as such by the _return suffix as part of its name.
All other pointers passed to these functions are used for reading
only. A few arguments use pointers to structures that are used for
both input and output and are indicated by using the _in_out
suffix.
_return
_in_out
Format of the Widget Reference Chapters
conventionschapter format
chapter format
The majority of this document is a reference guide for the Athena
widget set. Chapters three through six give the programmer all
information necessary to use the widgets. The layout of the chapters
follows a specific pattern to allow the programmer to easily find the
desired information.
The first few pages of every chapter give an overview of the widgets
in that section. Widgets are grouped into chapters by functionality.
Following the introduction will be a description of each widget in that
chapter. When no functional grouping is obvious the widgets are listed
in alphabetical order, such as in chapters three and six.
The first section of each widget's description is a table that
contains general information about this widget class. Here is the
table for the Box widget, and an explanation of all the entries.
Application Header file <X11/Xaw/Box.h>
Class Header file <X11/Xaw/BoxP.h>
Class boxWidgetClass
Class Name Box
Superclass Composite
Application Header File
application header file
This file must be included when an application uses this widget.
It usually contains the class definition, and some resource macros.
This is often called the public
header file.
class header file
Class Header File
This file will only be used by widget programmers. It will need to be
included by any widget that subclasses this widget. This is often
called the private
header file.
class
Class
This is the widget class of this widget. This global symbol is passed to
XtCreateWidget so that the Intrinsics will know which type of widget
to create.
class name
Class Name
This is the resource name of this class. This name can be used in
a resource file to match any widget of this class.
superclass
Superclass
This is the superclass that this widget class is descended from. If
you understand how the superclass works it will allow you to more quickly
understand what this widget does, since much of its functionality may be
inherited from its superclass.
After this table follows a general description of the default behavior of
this widget, as seen by the user. In many cases this functionality
may be overridden by the application programmer, or by the user.
The next section is a table showing the
name, class, type and default value of each resource that is available
to this widget. There is also a column containing notes describing
special restrictions placed upon individual resources.
notes
A, note
D, note
C, note
R, note
A
This resource may be automatically adjusted when another
resource is changed.
C
This resource is only settable at widget creation time, and may not
be modified with .
D
Do not modify this resource. While setting this resource will
work, it can cause unexpected behavior. When this symbol appears
there is another, preferred, interface provided by the X Toolkit.
R
This resource is READ-ONLY, and may not be modified.
After the resource table is a detailed description of every resource
available to that widget. Many of these are redundant, but printing
them with each widget saves page flipping. The names of the resources
that are inherited are printed in plain text, while the names of the
resources that are new to this class are printed in bold.
If you have already read the description of the superclass you need
only pay attention to the resources printed in bold.
For each composite widget there is a section on layout semantics that
follows the resource description. This section will describe the
effect of constraint resources on the layout of the children, as well
as a general description of where it prefers to place its children.
Descriptions of default translations and action routines come next, for
widgets to which they apply. The last item in each widget's
documentation is the description of all convenience routines provided by
the widget.
Input Focus
input focus
input
XtNinput
The Intrinsics define a resource on all Shell widgets that interact with
the window manager called input. This resource requests the
assistance of window manager in acquiring the input focus. The
resource defaults to False in the Intrinsics, but is redefined to
default to True when an application is using the Athena widget
set. An application programmer may override this default and set the
resource back to False if the application does not need the window
manager to give it the input focus. See the
X Toolkit Intrinsics - C Language Interface for details
on the input resource.
libXaw-1.0.16/specs/Template_public_header_file.xml 0000644 0001751 0000144 00000007211 14573370144 017233 0000000 0000000
libXaw-1.0.16/specs/StripChart.xml 0000644 0001751 0000144 00000025777 14573370144 013717 0000000 0000000
StripChart Widget
StripChart widget
Application Header file <Xaw/StripChart.h>
StripChart.h
Class Header file <Xaw/StripCharP.h>
StripCharP.h
Class stripChartWidgetClass
stripChartWidgetClass
Class Name StripChart
StripChart widgetclass name
Superclass Simple
The StripChart widget is used to provide a roughly real
time graphical chart of a single value. For example,
it is used by the common client program xload
to provide a graph of processor load. The StripChart
reads data from an application, and updates the chart
at the update interval specified.
Resources
When creating a StripChart widget instance, the following resources are
retrieved from the argument list or from the resource database:
StripChart widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
foreground
Foreground
Pixel
XtDefaultForeground
getValue
Callback
XtCallbackList
NULL
height
Height
Dimension
120
highlight
Foreground
Pixel
XtDefaultForeground
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
international
International
Boolean
C
False
jumpScroll
JumpScroll
int
A
half the width of the widget
mappedWhenManaged
MappedWhenManaged
Boolean
True
minScale
Scale
int
1
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
screen
Screen
Pointer
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
update
Interval
int
10
width
Width
Dimension
120
x
Position
Position
0
y
Position
Position
0
foreground
A pixel value which indexes the widget's colormap to derive the color
that will be used to draw the graph.
getValue
A list of callback functions to call every update seconds.
This list should contain one function, which returns the
value to be graphed by the StripChart widget. The following
section describes the procedural interface. Behavior when this list has
more than one function is undefined.
highlight
A pixel value which indexes the widget's colormap to derive the color
that will be used to draw the scale lines on the graph.
jumpScroll
When the graph reaches the right edge of the window it must be
scrolled to the left. This resource specifies the number of pixels
it will jump. Smooth scrolling can be achieved by setting this resource
to 1.
minScale
The minimum scale for the graph. The number of divisions on the graph
will always be greater than or equal to this value.
update
The number of seconds between graph updates. Each update is
represented on the graph as a 1 pixel wide line. Every update seconds
the getValue procedure will be used to get a new graph point,
and this point will be added to the right end of the StripChart.
Getting the StripChart Value
StripChart widgetgetting the value
The StripChart widget will call the application routine passed to it
as the getValue callback function every update seconds to
obtain another point for the StripChart graph.
The calling interface for the getValue callback is:
StripChart widgetgetValue callback
void(*getValueProc)
Widget w
XtPointer client_data
XtPointer value
w
Specifies the StripChart widget.
client_data
Specifies the client data.
value
Returns a pointer to a double. The application should set the address
pointed to by this argument to a double containing the value to be
graphed on the StripChart.
This function is used by the StripChart to call an application routine.
The routine will pass the value to be graphed back to the the StripChart
in the value field of this routine.
libXaw-1.0.16/specs/Text.xml 0000644 0001751 0000144 00000017227 14573370144 012547 0000000 0000000
Text Widget
Application Header file <X11/Xaw/Text.h>
Class Header file <X11/Xaw/TextP.h>
Class textWidgetClass
Class Name Text
Superclass Simple
The Text widget is the glue that binds all the other pieces together, it
maintains the internal state of the displayed text, and acts as a
mediator between the source and sink.
This section lists the resources that are actually part of the
Text widget, and explains the functionality provided by each.
Resources
When creating a Text widget instance, the following resources are
retrieved from the argument list or from the resource database:
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
autoFill
AutoFill
Boolean
False
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
bottomMargin
Margin
Position
2
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
XC_xterm
cursorName
Cursor
String
NULL
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
displayCaret
Output
Boolean
True
displayPosition
TextPosition
XawTextPosition
0
height
Height
Dimension
A
Font height + margins
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
insertPosition
TextPosition
int
0
leftMargin
Margin
Position
2
mappedWhenManaged
MappedWhenManaged
Boolean
True
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
resize
Resize
XawTextResizeMode
XawtextResizeNever
rightMargin
Margin
Position
4
screen
Screen
Pointer
R
Parent's Screen
scrollHorizontal
Scroll
ScrollMode
XawtextScrollNever
scrollVertical
Scroll
XawTextScrollMode
XawtextScrollNever
selectTypes
SelectTypes
XawTextSelectType*
See above
sensitive
Sensitive
Boolean
True
textSink
TextSink
Widget
NULL
textSource
TextSource
Widget
NULL
topMargin
Margin
Position
2
translations
Translations
TranslationTable
See above
unrealizeCallback
Callback
XtCallbackList
NULL
width
Width
Dimension
100
wrap
Wrap
WrapMode
XawtextWrapNever
x
Position
Position
0
y
Position
Position
0
libXaw-1.0.16/specs/SmeLine.xml 0000644 0001751 0000144 00000007775 14573370144 013166 0000000 0000000
SmeLine Object
SmeLine object
Application Header file <X11/Xaw/SmeLine.h>
SmeLine.h
Class Header file <X11/Xaw/SmeLineP.h>
SmeLineP.h
Class smeLineObjectClass
smeLineObjectClass
Class Name SmeLine
SmeLine objectclass name
Superclass Sme
The SmeLine object is used to add a horizontal line or menu separator to
a menu. Since each SmeLine is an independent object, the application
is able to change the color, height, and other attributes of the SmeLine
objects on an entry by entry basis. This object is not selectable, and
will not highlight when the pointer cursor is over it.
Resources
SmeLine objectresources
The resources associated with the SmeLine object are defined in this section,
and affect only the single menu entry specified by this object.
Name
Class
Type
Notes
Default Value
destroyCallback
Callback
XtCallbackList
NULL
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
lineWidth
international
International
Boolean
C
False
lineWidth
LineWidth
Dimension
1
stipple
Stipple
Pixmap
XtUnspecifiedPixmap
width
Width
Dimension
1
foreground
A pixel value which indexes the SimpleMenu's colormap to derive the
foreground color used to draw the separator line.
Keep in mind that the SimpleMenu widget will force all menu items to
be the width of the widest entry. Thus, setting the width is generally not
very important.
lineWidth
The width of the horizontal line that is to be displayed.
stipple
If a bitmap is specified for this resource, the line will be stippled
through it. This allows the menu separator to be rendered as something
more exciting than just a line. For instance, if you define a stipple
that is a chain link, then your menu separators will look like chains.
libXaw-1.0.16/specs/Command.xml 0000644 0001751 0000144 00000033451 14573370144 013176 0000000 0000000
Command Widget
Command widget
Application header file <X11/Xaw/Command.h>
Command.h
Class header file <X11/Xaw/CommandP.h>
CommandP.h
Class commandWidgetClass
commandWidgetClass
Class Name Command
Command widgetclass name
Superclass Label
The Command widget is an area, often rectangular, that contains text
or a graphical image. Command widgets are often referred to as
push buttons.
When the pointer is over a Command widget, the
widget becomes highlighted by drawing a rectangle around its perimeter.
This highlighting indicates that the widget is ready for selection.
When mouse button 1 is pressed, the Command widget indicates that
it has been selected by reversing its foreground and background colors.
When the mouse button is released, the Command widget's notify
action is invoked, calling all functions on its callback list. If
the pointer is moved off of the widget before the pointer button is
released, the widget reverts to its normal foreground and background
colors, and releasing the pointer button has no effect. This behavior
allows the user to cancel an action.
Resources
When creating a Command widget instance, the following resources are
retrieved from the argument list or from the resource database:
Command widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
bitmap
Bitmap
Pixmap
None
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
callback
Callback
XtCallbackList
NULL
colormap
Colormap
Colormap
Parent's Colormap
cornerRoundPercent
CornerRoundPercent
Dimension
25
cursor
Cursor
Cursor
None
cursorName
Cursor
String
NULL
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
encoding
Encoding
UnsignedChar
XawTextEncoding8bit
font
Font
XFontStruct
XtDefaultFont
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
graphic height + 2 * internalHeight
highlightThickness
Thickness
Dimension
A
2 (0 if Shaped)
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
internalHeight
Height
Dimension
2
internalWidth
Width
Dimension
4
international
International
Boolean
C
False
justify
Justify
Justify
XtJustifyCenter (center)
label
Label
String
name of widget
leftBitmap
LeftBitmap
Bitmap
None
mappedWhenManaged
MappedWhenManaged
Boolean
True
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
resize
Resize
Boolean
True
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
shapeStyle
ShapeStyle
ShapeStyle
Rectangle
translations
Translations
TranslationTable
See below
width
Width
Dimension
A
graphic width + 2 * internalWidth
x
Position
Position
0
y
Position
Position
0
_
Command Actions
Command widgetactions
The Command widget supports the following actions:
Switching the button's interior between the foreground and background
colors with set, unset, and reset.
Processing application callbacks with notify
Switching the internal border between highlighted
and unhighlighted states with highlight and unhighlight
Command widgettranslation bindings
The following are the default translation bindings used by the
Command widget:
<EnterWindow>: highlight( )
<LeaveWindow>: reset( )
<Btn1Down>: set( )
<Btn1Up>: notify( ) unset( )
The full list of actions supported by Command is:
highlight(condition)
Displays the internal highlight border in the color (foreground
or background ) that contrasts with the interior color of the
Command widget. The conditions WhenUnset and Always are
understood by this action procedure. If no argument is passed,
WhenUnset is assumed.
unhighlight( )
Displays the internal highlight border in the color (foreground
or background ) that matches the interior color of the
Command widget.
set( )
Enters the set state, in which notify is possible. This
action causes the button to display its interior in the
foreground color. The label or bitmap is displayed in the
background color.
unset( )
Cancels the set state and displays the interior of the button in the
background color. The label or bitmap is displayed in the
foreground color.
reset( )
Cancels any set or highlight and displays the interior of the
button in the background color, with the label or bitmap displayed
in the foreground color.
notify( )
When the button is in the set state this action calls all functions in
the callback list named by the callback resource. The value of
the call_data argument passed to these functions is undefined.
A very common alternative to registering callbacks is to augment a
Command's translations with an action performing the desired
function. This often takes the form of:
*Myapp*save.translations: #augment <Btn1Down>,<Btn1Up>: Save()
When a bitmap of depth greater that one (1) is specified the
set(), unset(), and reset() actions have no effect,
since there are no foreground and background colors used in a
multi-plane pixmap.
libXaw-1.0.16/specs/Makefile.am 0000644 0001751 0000144 00000002432 14573370144 013125 0000000 0000000
if ENABLE_SPECS
# Main DocBook/XML files (DOCTYPE book)
docbook = libXaw.xml
# Included chapters, appendix, images
chapters = \
AsciiSink.xml \
AsciiSource.xml \
AsciiText.xml \
Box.xml \
CH1.xml \
CH2.xml \
CH3.xml \
CH4.xml \
CH5.xml \
CH6.xml \
CH7.xml \
Command.xml \
Dialog.xml \
Form.xml \
Grip.xml \
Label.xml \
List.xml \
MenuButton.xml \
Paned.xml \
Panner.xml \
Porthole.xml \
Repeater.xml \
Scrollbar.xml \
SimpleMenu.xml \
Simple.xml \
SmeBSB.xml \
SmeLine.xml \
Sme.xml \
StripChart.xml \
Template_private_header_file.xml \
Template_public_header_file.xml \
Template_widget_source_file.xml \
Template.xml \
TextActions_default_translation_bindings.xml \
TextActions_text_widget_actions.xml \
TextActions.xml \
TextCustom.xml \
TextFuncs.xml \
TextSink.xml \
TextSource.xml \
Text.xml \
Toggle.xml \
TPage_Credits.xml \
Tree.xml \
Viewport.xml
# The location where the DocBook/XML files and their generated formats are installed
shelfdir = $(docdir)
# Generate DocBook/XML output formats with or without stylesheets
include $(top_srcdir)/docbook.am
endif ENABLE_SPECS
libXaw-1.0.16/specs/SmeBSB.xml 0000644 0001751 0000144 00000021170 14573370144 012666 0000000 0000000
SmeBSB Object
SmeBSB object
Application Header file <X11/Xaw/SmeBSB.h>
SmeBSB.h
Class Header file <X11/Xaw/SmeBSBP.h>
SmeBSBP.h
Class smeBSBObjectClass
smeBSBObjectClass
Class Name SmeBSB
SmeBSB objectclass name
Superclass Sme
The SmeBSB object is used to create a menu entry that contains a string,
and optional bitmaps in its left and right margins. Since each menu
entry is an independent object, the application is able to change the
font, color, height, and other attributes of the menu entries, on an
entry by entry basis. The format of the string may either be the encoding
of the 8 bit font utilized, or in a multi-byte encoding for use with a
fontSet.
Resources
SmeBSB objectresources
The resources associated with the SmeBSB object are defined in this section,
and affect only the single menu entry specified by this object.
Name
Class
Type
Notes
Default Value
ancestorSensitive
AncestorSensitive
Boolean
D
True
callback
Callback
Callback
NULL
destroyCallback
Callback
XtCallbackList
NULL
font
Font
FontStruct
XtDefaultFont
fontSet
FontSet
XFontSet
XtDefaultFontSet
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
Font height + vertSpace
international
International
Boolean
C
False
justify
Justify
Justify
XtjustifyLeft
label
Label
String
NULL
leftBitmap
LeftBitmap
Pixmap
XtUnspecifiedPixmap
leftMargin
leftMargin
Dimension
4
rightBitmap
RightBitmap
Pixmap
XtUnspecifiedPixmap
rightMargin
rightMargin
Dimension
4
sensitive
Sensitive
Boolean
True
vertSpace
VertSpace
int
25
width
Width
Dimension
A
TextWidth + margins
callback
All callback functions on this list are called when the SimpleMenu
notifies this entry that the user has selected it.
font
The text font to use when displaying the label, when the
international resource is false.
fontSet
The text font set to use when displaying the label, when the
international resource is true.
foreground
A pixel value which indexes the SimpleMenu's colormap to derive the
foreground color of the menu entry's window. This color is also
used to render all 1's in the left and right bitmaps.
Keep in mind that the SimpleMenu widget will force the width of all
menu entries to be the width of the longest entry.
justify
How the label is to be rendered between the left and right margins when
the space is wider than the actual text. This resource may be
specified with the values XtJustifyLeft, XtJustifyCenter,
or XtJustifyRight. When specifying the justification from a
resource file the values left, center, or right may be
used.
label
This is a the string that will be displayed in the menu entry. The
exact location of this string within the bounds of the menu entry is
controlled by the leftMargin, rightMargin, vertSpace,
and justify resources.
leftBitmap
rightBitmap
This is a name of a bitmap to display in the left or right margin of the
menu entry. All 1's in the bitmap will be rendered in the foreground
color, and all 0's will be drawn in the background color of the
SimpleMenu widget. It is the
programmers' responsibility to make sure that the menu entry is tall
enough, and the appropriate margin wide enough to accept the bitmap.
If care is not taken the bitmap may extend into another menu entry, or
into this entry's label.
leftMargin
rightMargin
This is the amount of space (in pixels) that will be left between the
edge of the menu entry and the label string.
vertSpace
This is the amount of vertical padding, expressed as a percentage of
the height of the font, that is to be placed around the label of a
menu entry.. The label and bitmaps are always centered vertically
within the menu. The default value for this
resource (25) causes the default height to be 125% of the height of the
font.
libXaw-1.0.16/specs/Dialog.xml 0000644 0001751 0000144 00000050247 14573370144 013021 0000000 0000000
Dialog Widget
Dialog widget
Application Header file <X11/Xaw/Dialog.h>
Dialog.h
Class Header file <X11/Xaw/DialogP.h>
DialogP.h
Class dialogWidgetClass
dialogWidgetClass
Class Name Dialog
Dialog widgetclass name
Superclass Form
The Dialog widget implements a commonly used interaction semantic to
prompt for auxiliary input from a user. For example, you can use a
Dialog widget when an application requires a small piece of information,
such as a filename, from the user. A Dialog widget, which is simply a
special case of the Form widget, provides a convenient way to create a
preconfigured form.
The typical Dialog widget contains three areas. The first line
contains a description of the function of the Dialog widget, for
example, the string Filename:. The second line contains an area
into which the user types input. The third line can contain buttons
that let the user confirm or cancel the Dialog input. Any of these
areas may be omitted by the application.
Resources
When creating a Dialog widget instance, the following resources are
retrieved from the argument list or the resource database:
Dialog widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
children
ReadOnly
WidgetList
R
NULL
colormap
Colormap
Colormap
Parent's Colormap
defaultDistance
Thickness
int
4
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
height
Height
Dimension
A
Enough space to contain all children
icon
Icon
Bitmap
None
label
Label
String
"label"
mappedWhenManaged
MappedWhenManaged
Boolean
True
numChildren
ReadOnly
Cardinal
R
0
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
value
Value
String
no value widget
width
Width
Dimension
A
Enough space to contain all children
x
Position
Position
0
y
Position
Position
0
_
icon
A pixmap image to be displayed immediately to the left of the
Dialog widget's label.
label
A string to be displayed at the top of the Dialog widget.
value
An initial value for the string field that the user will enter text
into. By default, no text entry field is available to the user.
Specifying an initial value for value activates the text entry
field. If string input is desired, but no initial value is to be
specified then set this resource to "" (empty string).
Constraint Resources
Dialog widgetconstraint resources
Each child of the Dialog widget may request special layout resources
be applied to it. These constraint resources allow the Dialog
widget's children to specify individual layout requirements.
Name
Class
Type
Notes
Default Value
bottom
Edge
XawEdgeType
XawRubber
fromHoriz
Widget
Widget
NULL (left edge of Dialog)
fromVert
Widget
Widget
NULL (top edge of Dialog)
horizDistance
Thickness
int
defaultDistance resource
left
Edge
XawEdgeType
XawRubber
resizable
Boolean
Boolean
FALSE
right
Edge
XawEdgeType
XawRubber
top
Edge
XawEdgeType
XawRubber
vertDistance
Thickness
int
defaultDistance resource
bottom
left
right
top What to do with this edge of the child when
the parent is resized. This resource may be
any edgeType. See Layout Semantics for
details.
fromHoriz
fromVert Which widget this child should be placed
underneath (or to the right of). If a value
of NULL is specified then this widget will be
positioned relative to the edge of the par-
ent.
horizDistance
vertDistance The amount of space, in pixels, between this
child and its left or upper neighbor.
resizable If this resource is False then the parent
widget will ignore all geometry request made
by this child. The parent may still resize
this child itself, however.
Layout Semantics
Dialog widgetlayout semantics
The Dialog widget uses two different sets of layout seman-
tics. One is used when initially laying out the children.
The other is used when the Dialog is resized.
The first layout method uses the fromVert mand fromHoriz
resources to place the children of the Dialog. A single
pass is made through the Dialog widget's children in the
order that they were created. Each child is then placed in
the Dialog widget below or to the right of the widget specified by the
fromVert and fromHoriz resources.
The distance the new child is placed from its left or upper neighbor is
determined by the horizDistance and
vertDistance resources.
This implies some things about how the order of creation
affects the possible placement of the children. The Form
widget registers a string to widget converter which does not
postpone conversion and does not cache conversion results.
The second layout method is used when the Dialog is resized.
It does not matter what causes this resize, and it is possi-
ble for a resize to happen before the widget becomes visible
(due to constraints imposed by the parent of the Dialog).
This layout method uses the bottom ,
top , left , and
right
resources. These resources are used to determine what will
happen to each edge of the child when the Dialog is resized.
If a value of XawChain
<something>
is specified, the the edge
of the child will remain a fixed distance from the chain
edge of the Dialog. For example if XawChainLeft
mis specified for the right mresource of a child
then the right edge
of that child will remain a fixed distance from the left
edge of the Dialog widget. If a value of XawRubber mis spec-
ified, that edge will grow by the same percentage that the
Dialog grew. For instance if the Dialog grows by 50% the
left edge of the child (if specified as XawRubber mwill be
50% farther from the left edge of the Dialog). One must be
very careful when specifying these resources, for when they
are specified incorrectly children may overlap or completely
occlude other children when the Dialog widget is resized.
Edge Type
Resource Name
Description
XawChainBottom
ChainBottom
Edge remains a fixed distance from bottom of Dialog
XawChainLeft
ChainLeft
Edge remains a fixed distance from left of Dialog
XawChainRight
ChainRight
Edge remains a fixed distance from right of Dialog
XawChainTop
ChainTop
Edge remains a fixed distance from top of Dialog
XawRubber
Rubber
Edges will move a proportional distance
Example
If you wish to force the Dialog to never resize one or more of its children
then set left and right to XawChainLeft and
top and bottom to XawChainTop. This will cause
the child to remain a fixed distance from the top and left
edges of the Dialog, and to never resize.
Special Considerations
Dialog widgetspecial considerations
The Dialog widget automatically sets the top and bottom
resources for all Children that are subclasses of the Command widget,
as well as the widget children that are used to contain the label,
value, and icon. This policy allows the buttons at the
bottom of the Dialog to interact correctly with the predefined children,
and makes it possible for a client to simply create and manage a new
Command button without having to specify its constraints.
The Dialog will also set fromLeft to the last button in the
fromLeft
Dialog for each new button added to the Dialog widget.
The automatically added constraints cannot be overridden, as they are
policy decisions of the Dialog widget. If a more flexible Dialog is
desired, the application is free to use the Form widget to create its
own Dialog policy.
Automatically Created Children.
Dialog widgetautomatically created children
The Dialog uses Label widgets to contain the label and icon.
These widgets are named label and icon respectively. The
Dialog value is contained in an AsciiText widget whose name is
value. Using XtNameToWidget the application can change
XtNameToWidget
those resources associated with each of these widgets that are not
available through the Dialog widget itself.
Convenience Routines
To return the character string in the text field, use
XawDialogGetValueString
String XawDialogGetValueString
Widget w
w
Specifies the Dialog widget.
This function returns a copy of the value string of the Dialog
widget. This string is allocated by the AsciiText widget and will
remain valid and unchanged until another call to
or an call on the
value widget, when the string will be automatically freed, and
a new string is returned. This string may be freed earlier by calling
the function .
XawAsciiSourceFreeString
To add a new button to the Dialog widget use
.
XawDialogAddButton
void XawDialogAddButton
Widget w
String name
XtCallbackProc func
XtPointer client_data
w
Specifies the Dialog widget.
name
Specifies the name of the new Command button to be added to the Dialog.
func
Specifies a callback function to be called when this button is activated. If
NULL is specified then no callback is added.
client_data
Specifies the client_data to be passed to the func.
This function is merely a shorthand for the code sequence:
{
Widget button = XtCreateManagedWidget(name, commandWidgetClass, w, NULL, ZERO);
XtAddCallback(button, XtNcallback, func, client_data);
}
libXaw-1.0.16/specs/TextCustom.xml 0000644 0001751 0000144 00000010102 14573370144 013723 0000000 0000000
Customizing the Text Widget
Text widgetcustomizing
The remainder of this chapter will describe customizing the Text
widget. The Text widget may be customized by subclassing, or by
creating new sources and sinks. Subclassing is described in
detail in Chapter 7; this section will describe only those things that
are specific to the Text widget. Attributes of the Text widget base
class and creating new sources and sinks will be discussed.
The Text widget is made up of a number of different pieces, with the
Text widget as the base widget class. It and the AsciiText widget are
the only true "widgets" in the Text widget family. The other pieces
(sources and sinks) are X Toolkit objects and have no window
associated with them. No source or sink is useful unless assigned to
a Text widget.
Each of the following pieces of the Text widget has a specific purpose,
and will be, or has been, discussed in detail in this chapter:
Text widget
Text
This is the glue that binds everything else together. This widget reads
the text data from the source, and displays the information in the sink.
All translations and actions are handled in the Text widget itself.
TextSink
TextSink object
This object is responsible for displaying and clearing the drawing area.
It also reports the configuration of the window that contains the
drawing area. The TextSink does not have its own window; instead it does
its drawing on the Text widget's window.
TextSrc
TextSrc object
This object is responsible for reading, editing and searching through the
text buffer.
AsciiSink
AsciiSink object
This object is a subclass of the TextSink and knows how to display
ASCII text. Support has been added to display any 8-bit character set, given
the font.
MultiSink
MultiSink object
This object is a subclass of the TextSink and knows how to display
font sets.
AsciiSrc
AsciiSrc object
This object is a subclass of the TextSrc and knows how to read strings
and files.
MultiSrc
MultiSrc object
This object is a subclass of the TextSrc and knows how to read strings
and multibyte files, converting them to wide characters based on locale.
AsciiText
AsciiText widget
This widget is a subclass of the Text widget. When created, the AsciiText
automatically creates and attaches either an AsciiSrc and AsciiSink, or a
MultiSrc and MultiSink, to itself. The AsciiText provides the simplest
interface to the Athena Text widgets.
libXaw-1.0.16/specs/Template_widget_source_file.xml 0000644 0001751 0000144 00000013245 14573370144 017314 0000000 0000000
Widget Source File
The source code file implements the widget class itself. The unique
part of this file is the declaration and initialization of the
widget class record structure and the declaration of all resources and
action routines added by the widget class.
The contents of the Template implementation file,
,
are:
/* Copyright (c) X Consortium 1987, 1988
*/
#include <X11/IntrinsicP.h>
#include <X11/StringDefs.h>
#include "TemplateP.h"
static XtResource resources[] = {
#define offset(field) XtOffsetOf(TemplateRec, template.field)
/* {name, class, type, size, offset, default_type, default_addr}, */
{ XtNtemplateResource, XtCTemplateResource, XtRTemplateResource,
sizeof(char*), offset(resource), XtRString, (XtPointer) "default" },
#undef offset
};
static void TemplateAction(/* Widget, XEvent*, String*, Cardinal* */);
static XtActionsRec actions[] =
{
/* {name, procedure}, */
{"template", TemplateAction},
};
static char translations[] =
" <Key>: template( ) \\n\\
";
TemplateClassRec templateClassRec = {
{ /* core fields */
/* superclass */ (WidgetClass) &widgetClassRec,
/* class_name */ "Template",
/* widget_size */ sizeof(TemplateRec),
/* class_initialize */ NULL,
/* class_part_initialize */ NULL,
/* class_inited */ FALSE,
/* initialize */ NULL,
/* initialize_hook */ NULL,
/* realize */ XtInheritRealize,
/* actions */ actions,
/* num_actions */ XtNumber(actions),
/* resources */ resources,
/* num_resources */ XtNumber(resources),
/* xrm_class */ NULLQUARK,
/* compress_motion */ TRUE,
/* compress_exposure */ TRUE,
/* compress_enterleave */ TRUE,
/* visible_interest */ FALSE,
/* destroy */ NULL,
/* resize */ NULL,
/* expose */ NULL,
/* set_values */ NULL,
/* set_values_hook */ NULL,
/* set_values_almost */ XtInheritSetValuesAlmost,
/* get_values_hook */ NULL,
/* accept_focus */ NULL,
/* version */ XtVersion,
/* callback_private */ NULL,
/* tm_table */ translations,
/* query_geometry */ XtInheritQueryGeometry,
/* display_accelerator */ XtInheritDisplayAccelerator,
/* extension */ NULL
},
{ /* template fields */
/* empty */ 0
}
};
WidgetClass templateWidgetClass = (WidgetClass)&templateClassRec;
The resource list for the "WindowWidget" might look like the following:
static XtResource resources[] = {
#define offset(field) XtOffsetOf(WindowWidgetRec, window.field)
/* {name, class, type, size, offset, default_type, default_addr}, */
{ XtNdrawingColor1, XtCColor, XtRPixel, sizeof(Pixel),
offset(color_1), XtRString, XtDefaultForeground },
{ XtNdrawingColor2, XtCColor, XtRPixel, sizeof(Pixel),
offset(color_2), XtRString, XtDefaultForeground },
{ XtNfont, XtCFont, XtRFontStruct, sizeof(XFontStruct*),
offset(font), XtRString, XtDefaultFont },
{ XtNexposeCallback, XtCCallback, XtRCallback, sizeof(XtCallbackList),
offset(expose_callback), XtRCallback, NULL },
{ XtNcallback, XtCCallback, XtRCallback, sizeof(XtCallbackList),
offset(input_callback), XtRCallback, NULL },
#undef offset
};
The user input callback will be implemented by an action procedure which
passes the event pointer as call_data. The action procedure
is declared as:
/* ARGSUSED */
static void InputAction(w, event, params, num_params)
Widget w;
XEvent *event;
String *params; /* unused */
Cardinal *num_params; /* unused */
{
XtCallCallbacks(w, XtNcallback, (XtPointer)event);
}
static XtActionsRec actions[] =
{
/* {name, procedure}, */
{"input", InputAction},
};
and the default input binding will be to execute the input callbacks on
KeyPress and ButtonPress :
static char translations[] =
" <Key>: input( ) \\n\\
<BtnDown>: input( ) \\
";
In the class record declaration and initialization, the only field that
is different from the Template is the expose procedure:
/* ARGSUSED */
static void Redisplay(w, event, region)
Widget w;
XEvent *event; /* unused */
Region region;
{
XtCallCallbacks(w, XtNexposeCallback, (XtPointer)region);
}
WindowClassRec windowClassRec = {
...
/* expose */ Redisplay,
The "WindowWidget" will also declare three public procedures to return the
drawing colors and the font id, saving the application the effort of
constructing an argument list for a call to
XtGetValues :
Pixel WindowColor1(w)
Widget w;
{
return ((WindowWidget)w)->window.color_1;
}
Pixel WindowColor2(w)
Widget w;
{
return ((WindowWidget)w)->window.color_2;
}
Font WindowFont(w)
Widget w;
{
return ((WindowWidget)w)->window.font->fid;
}
The "WindowWidget" is now complete. The application can retrieve the two
drawing colors from the widget instance by calling either
XtGetValues,
or the WindowColor functions. The actual window created for the
"WindowWidget" is available by calling the
XtWindow function.
libXaw-1.0.16/specs/Viewport.xml 0000644 0001751 0000144 00000025125 14573370144 013436 0000000 0000000
Viewport Widget
Viewport widget
Application Header file <X11/Xaw/Viewport.h>
Viewport.h
Class Header file <X11/Xaw/ViewportP.h>
ViewportP.h
Class viewportWidgetClass
viewportWidgetClass
Class Name Viewport
Viewport widgetclass name
Superclass Form
The Viewport widget consists of a frame window, one or two Scrollbars,
and an inner window. The size of the frame window is determined by the
viewing size of the data that is to be displayed and the dimensions to
which the Viewport is created. The inner window is the full size of the
data that is to be displayed and is clipped by the frame window. The
Viewport widget controls the scrolling of the data directly. No
application callbacks are required for scrolling.
When the geometry of the frame window is equal in size to the inner
window, or when the data does not require scrolling, the Viewport widget
automatically removes any scrollbars. The forceBars option causes
the Viewport widget to display all scrollbars permanently.
Resources
When creating a Viewport widget instance, the following resources are
retrieved from the argument list or the resource database:
Viewport widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
allowHoriz
Boolean
Boolean
False
allowVert
Boolean
Boolean
False
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
children
ReadOnly
WidgetList
R
NULL
colormap
Colormap
Colormap
Parent's Colormap
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
forceBars
Boolean
Boolean
False
height
Height
Dimension
height of the child
mappedWhenManaged
MappedWhenManaged
Boolean
True
numChildren
ReadOnly
Cardinal
R
0
reportCallback
ReportCallback
XtCallbackList
NULL
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
useBottom
Boolean
Boolean
False
useRight
Boolean
Boolean
False
width
Width
Dimension
width of the child
x
Position
Position
0
y
Position
Position
0
_
allowHoriz
allowVert
If these resources are False then the Viewport will never create
a scrollbar in this direction. If it is True then the scrollbar will
only appear when it is needed, unless forceBars is True.
forceBars
When True the scrollbars that have been allowed will always be
visible on the screen. If False the scrollbars will be visible only
when the inner window is larger than the frame.
reportCallback
These callbacks will be executed whenever the Viewport adjusts the viewed
area of the child. The call_data parameter is a pointer to an XawPannerReport
structure.
useBottom
useRight
By default the scrollbars appear on the left and top of the screen.
These resources allow the vertical scrollbar to be placed on the right
edge of the Viewport, and the horizontal scrollbar on the bottom edge of
the Viewport.
Layout Semantics
Viewport widgetlayout semantics
The Viewport widget manages a single child widget. When the size of the
child is larger than the size of the Viewport, the user can interactively
move the child within the Viewport by repositioning the scrollbars.
The default size of the Viewport before it is realized is the width and/or
height of the child. After it is realized, the Viewport will allow its
child to grow vertically or horizontally if allowVert or
allowHoriz are set, respectively. If the corresponding vertical
or horizontal scrollbar is not enabled, the Viewport will propagate the
geometry request to its own parent and the child will be allowed to change
size only if the Viewport's parent allows it. Regardless of whether or not
scrollbars are enabled in the corresponding direction, if the child requests
a new size smaller than the Viewport size, the change will be allowed only
if the parent of the Viewport allows the Viewport to shrink to the
appropriate dimension.
The scrollbar children of the Viewport are named horizontal and
vertical. By using these names the programmer can specify resources
for the individual scrollbars. can be used to modify
the resources dynamically once the widget ID has been obtained with
XtNameToWidget.
XtNameToWidget
Although the Viewport is a Subclass of the Form, no resources for the Form
may be supplied for any of the children of the Viewport. These constraints
are managed internally and are not meant for public consumption.
libXaw-1.0.16/specs/TPage_Credits.xml 0000644 0001751 0000144 00000006134 14573370144 014273 0000000 0000000
Acknowledgments
Many thanks go to Ralph Swick (Project Athena / Digital) who has
contributed much time and effort to this widget set. Previous
versions of the widget set are largely due to his time and effort.
Many of the improvements that I have been able to make are because he
provided a solid foundation to build upon. While much of the effort
has been Ralph's, many other people have contributed to the code.
Mark Ackerman (formerly Project Athena)
Donna Converse (MIT X Consortium)
Jim Fulton (formerly MIT X Consortium)
Loretta Guarino-Reid (Digital WSL)
Charles Haynes (Digital WSL)
Rich Hyde (Digital WSL)
Mary Larson (Digital UEG)
Joel McCormack (Digital WSL)
Ron Newman (formerly Project Athena)
Jeanne Rich (Digital WSL)
Terry Weissman (formerly Digital WSL)
While not much remains of the X10 toolkit, many of the ideas for this
widget set come from that original version. The design and
implementation of the X10 toolkit were done by:
Mike Gancarz (formerly Digital UEG)
Charles Haynes (Digital WSL)
Phil Karlton (formerly Digital WSL)
Kathleen Langone (Digital UEG)
Mary Larson (Digital UEG)
Ram Rao (Digital UEG)
Smokey Wallace (formerly Digital WSL)
Terry Weissman (formerly Digital WSL)
I have used the formatting ideas, and some of the words from previous
versions of this document. The X11R3 Athena widget document was written by:
Ralph R. Swick (Project Athena/ Digital)
Terry Weissman (formerly Digital WSL)
Al Mento (Digital UEG)
Putting this manual together was a major task in and of itself. I
would like to thank Ralph Swick, Donna Converse, and Jim Fulton for
taking the time to help convert my technical knowledge into legible
text. A special thanks to Jean Diaz (O'Reilly and Associates) for
spending nearly a month with me working out all the annoying little
details.
Chris D. Peterson
MIT X Consortium 1989
The R5 edition of this document has been edited by the research staff of
the MIT X Consortium, with significant contributions by Jim Fulton (NCD).
Donna Converse
MIT X Consortium 1991
The R6 edition of this document has been edited to reflect changes
brought about by research staff of the Omron Corporation, with special
recognition to Li Yuhong, Seiji Kuwari, and Hiroshi Kuribayashi for
the X11R5/contrib/lib/Xaw internationalization that inspired this version.
Frank Sheeran
Omron Corporation 1994
This document is made available to you in modern formats such as HTML and PDF
thanks to the efforts of Matt Dew, who converted the original troff sources to
DocBook/XML and edited them into shape; along with Gaetan Nadon and
Alan Coopersmith, who set up the formatting machinery in the libXaw builds and
performed further editing of the DocBook markup.
libXaw-1.0.16/specs/Paned.xml 0000644 0001751 0000144 00000102434 14573370144 012645 0000000 0000000
Paned Widget
Paned widget
Application Header file <X11/Xaw/Paned.h>
Paned.h
Class Header file <X11/Xaw/PanedP.h>
PanedP.h
Class panedWidgetClass
panedWidgetClass
Class Name Paned
Paned widgetclass name
Superclass Constraint
The Paned widget manages children in a vertically or horizontally
tiled fashion. The panes may be dynamically resized by the user by
using the grips that appear near the right or bottom edge of the
border between two panes.
The Paned widget may accept any widget class as a pane except
Grip. Grip widgets have a special meaning for the Paned widget, and
adding a Grip as its own pane will confuse the Paned widget.
Using the Paned Widget
Paned widgetusing
The grips allow the panes to be resized by the user. The semantics of
how these panes resize is somewhat complicated, and warrants further
explanation here. When the mouse pointer is positioned on a grip and
pressed, an arrow is displayed that indicates the pane that is to be to
be resized. While keeping the mouse button down, the user can move the
grip up and down (or left and right). This, in turn, changes the size
of the pane. The size of the Paned widget will not change. Instead,
it chooses another pane (or panes) to resize. For more details on which
pane it chooses to resize, see Layout Semantics.
One pointer binding allows the border between two panes to be moved,
without affecting any of the other panes. When this occurs the pointer
will change to an arrow that points along the pane border.
The default bindings for the Paned widget's grips are:
Mouse button
Pane to Resize - Vertical
Pane to Resize - Horizontal
1 (left)
above the grip
left of the grip
2 (middle)
adjust border
adjust border
3 (right)
below the grip
right of the grip
_
Resources
When creating a Paned widget instance, the following resources are
retrieved from the argument list or the resource database:
Paned widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
betweenCursor
Cursor
Cursor
A
Depends on orientation
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
children
ReadOnly
WidgetList
R
NULL
colormap
Colormap
Colormap
Parent's Colormap
cursor
Cursor
Cursor
None
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
gripCursor
Cursor
Cursor
A
Depends on orientation
gripIndent
GripIndent
Position
10
gripTranslations
Translations
TranslationTable
see below
height
Height
Dimension
A
Depends on orientation
horizontalBetweenCursor
Cursor
Cursor
sb_up_arrow
horizontalGripCursor
Cursor
Cursor
sb_h_double_arrow
internalBorderColor
BorderColor
Pixel
XtDefaultForeground
internalBorderWidth
BorderWidth
Dimension
1
leftCursor
Cursor
Cursor
sb_left_arrow
lowerCursor
Cursor
Cursor
sb_down_arrow
mappedWhenManaged
MappedWhenManaged
Boolean
True
numChildren
ReadOnly
Cardinal
R
0
orientation
Orientation
Orientation
XtorientVertical
refigureMode
Boolean
Boolean
True
rightCursor
Cursor
Cursor
sb_right_arrow
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
upperCursor
Cursor
Cursor
sb_up_arrow
verticalBetweenCursor
Cursor
Cursor
sb_left_arrow
verticalGripCursor
Cursor
Cursor
sb_v_double_arrow
width
Width
Dimension
A
Depends on orientation
x
Paned
Position
0
y
Paned
Position
0
_
cursor
The cursor to use when the mouse pointer is over the Paned widget, but
not in any of its children (children may also inherit this cursor). It
should be noted that the internal borders are actually part of the Paned
widget, not the children.
gripCursor
The cursor to use when the grips are not active. The default value is
verticalGripCursor or horizontalGripCursor depending on
the orientation of the Paned widget.
gripIndent
The amount of space left between the right (or bottom) edge of the
Paned widget and all the grips.
gripTranslation
Translation table that will be applied to all grips.
horizontalBetweenCursor
verticalBetweenCursor
The cursor to be used for the grip when changing the boundary between
two panes. These resources allow the cursors to be different
depending on the orientation of the Paned widget.
horizontalGripCursor
verticalGripCursor
The cursor to be used for the grips when they are not active. These
resources allow the cursors to be different depending on the
orientation of the Paned widget.
internalBorderColor
A pixel value which indexes the widget's colormap to derive the internal
border color of the widget's window. The class name of this resource
allows Paned*BorderColor: blue to set the internal border color
for the Paned widget. An optimization is invoked if
internalBorderColor and background are the same, and the
internal borders are not drawn. internalBorderWidth is still left
between the panes, however.
internalBorderWidth
The width of the internal borders. This is the amount of space left
between the panes. The class name of this resource allows
Paned*BorderWidth: 3 to set the internal border width for the
Paned widget.
leftCursor
rightCursor
The cursor used to indicate which is the important pane to resize
when the Paned widget is oriented horizontally.
lowerCursor
upperCursor
The cursor used to indicate which is the important pane to resize
when the Paned widget is oriented vertically.
This is not the same as the number of panes, since this also contains a
grip for some of the panes, use to retrieve the
number of panes.
orientation
The orientation to stack the panes. This value can be either
XtorientVertical or XtorientHorizontal.
XtorientVertical
XtorientHorizontal
conversionsOrientation
refigureMode
This resource allows pane layout to be suspended. If this value is
False, then no layout actions will be taken. This may improve
efficiency when adding or removing more than one pane from the Paned
widget.
Constraint Resources
Paned widgetconstraint resources
Each child of the Paned widget may request special layout resources
be applied to it. These constraint resources allow the Paned
widget's children to specify individual layout requirements.
Name
Class
Type
Notes
Default Value
allowResize
Boolean
Boolean
False
max
Max
Dimension
Infinity
min
Min
Dimension
Height of Grips
preferredPaneSize
PreferredPaneSize
Dimension
ask child
resizeToPreferred
Boolean
Boolean
False
showGrip
ShowGrip
Boolean
True
skipAdjust
Boolean
Boolean
False
_
allowResize
If this value is False the the Paned widget will disallow all
geometry requests from this child.
max
min
The absolute maximum or minimum size for this pane. These values will
never be overridden by the Paned widget. This may cause some panes to be
pushed off the bottom (or right) edge of the paned widget.
preferredPaneSize
Normally the paned widget makes a QueryGeometry call on a child to
determine the preferred size of the child's pane. There are times
when the application programmer or the user has a better idea of the
preferred size of a pane. Setting this resource causes the value
passed to be interpreted as the preferred size, in pixels, of this pane.
resizeToPreferred
Determines whether or not to resize each pane to its preferred size
when the Paned widget is resized. See Layout Semantics for details.
showGrip
If True then a grip will be shown for this pane. The grip
associated with a pane is either below or to the right of the pane. No
grip is ever shown for the last pane.
skipAdjust
This resource is used to determine which pane is forced to be resized.
Setting this value to True makes this pane less likely to be
forced to be resized. See Layout Semantics for details.
Layout Semantics
Paned widgetlayout semantics
In order to make effective use of the Paned widget it is helpful to know
the rules it uses to determine which child will be resized in any given
situation. There are three rules used to determine which child is
resized. While these rules are always the same, the panes that are
searched can change depending upon what caused the relayout.
Layout Rules
1
Do not let a pane grow larger than its max or smaller than its
min.
2
Do not adjust panes with skipAdjust set.
3
Do not adjust panes away from their preferred size, although moving one
closer to its preferred size is fine.
When searching the children the Paned widget looks for panes that
satisfy all the rules, and if unsuccessful then it eliminates rule 3
and then 2. Rule 1 is always enforced.
If the relayout is due to a resize or change in management then the
panes are searched from bottom to top. If the relayout is due to grip
movement then they are searched from the grip selected in the direction
opposite the pane selected.
Resizing Panes from a Grip Action
The pane above the grip is resized by invoking the GripAction with
UpLeftPane specified. The panes below the grip are each checked
against all rules, then rules 2 and 1 and finally against rule 1 only.
No pane above the chosen pane will ever be resized.
The pane below the grip is resized by invoking the GripAction with
LowRightPane specified. The panes above the grip are each
checked in this case. No pane below the chosen pane will ever be resized.
Invoking GripAction with ThisBorderOnly specified just moves the
border between the panes. No other panes are ever resized.
Resizing Panes after the Paned widget is resized.
When the Pane widget is resized it must determine a new size for each
pane. There are two methods of doing this. The Paned widget can either
give each pane its preferred size and then resize the panes to fit, or
it can use the current sizes and then resize the panes to fit. The
resizeToPreferred resource allows the application to tell the
Paned widget whether to query the child about its preferred size
(subject to the the preferredPaneSize) or to use the current size
when refiguring the pane locations after the pane has been resized.
There is one special case. All panes assume they should resize to
their preferred size until the Paned widget becomes visible to the user.
Managing Children and Geometry Management
The Paned widget always resizes its children to their preferred sizes when
a new child is managed, or a geometry management request is honored.
The Paned widget will first attempt to resize itself to contain its
panes exactly. If this is not possible then it will hunt through the
children, from bottom to top (right to left), for a pane to resize.
Special Considerations
When a user resizes a pane with the grips, the Paned widget assumes that
this new size is the preferred size of the pane.
Grip Translations
The Paned widget has no action routines of its own, as all actions are
handled through the grips. The grips are each assigned a default
Translation table.
<Btn1Down>: GripAction(Start, UpLeftPane)
GripAction
<Btn2Down>: GripAction(Start, ThisBorderOnly)
<Btn3Down>: GripAction(Start, LowRightPane)
<Btn1Motion>: GripAction(Move, UpLeftPane)
<Btn2Motion>: GripAction(Move, ThisBorderOnly)
<Btn3Motion>: GripAction(Move, LowRightPane)
Any<BtnUp>: GripAction(Commit)
The Paned widget interprets the GripAction as taking two arguments.
GripAction
The first argument may be any of the following:
Start
Sets up the Paned widget for resizing and changes the cursor of the
grip. The second argument determines which pane will be resized, and
can take on any of the three values shown above.
Move
The internal borders are drawn over the current pane locations to
animate where the borders would actually be placed if you were to move
this border as shown. The second argument must match the second argument
that was passed to the Start action, that began this process. If
these arguments are not passed, the behavior is undefined.
Commit
This argument causes the Paned widget to commit the changes selected
by the previously started action. The cursor is changed back to the
grip's inactive cursor. No second argument is needed in this case.
Convenience Routines
Paned widgetenable pane resizing
Paned widgetdisable pane resizing
To enable or disable a child's request for pane resizing,
use
XawPanedAllowResize :
XawPanedAllowResize
void XawPanedAllowResize
Widget w
Boolean allow_resize
w
Specifies the child pane.
allow_resize
Specifies whether or not resizing requests for this child will be
granted by the Paned widget.
If allow_resize is True, the Paned widget allows geometry
requests from the child to change the pane's height. If allow_resize
is False, the Paned widget ignores geometry requests from the
child to change the pane's height. The default state is True
before the Pane is realized and False after it is realized.
This procedure is equivalent to changing the allowResize
constraint resource for the child.
Paned widgetchange height settings
To change the minimum and maximum height settings for a pane, use
XawPanedSetMinMax :
XawPanedSetMinMax
void XawPanedSetMinMax
Widget w
intmin, max
w
Specifies the child pane.
min
Specifies the new minimum height of the child, expressed in pixels.
max
Specifies new maximum height of the child, expressed in pixels.
This procedure is equivalent to setting the min and max
constraint resources for the child.
Paned widgetget height settings
To retrieve the minimum and maximum height settings for a pane, use
XawPanedGetMinMax :
XawPanedGetMinMax
void XawPanedGetMinMax
Widget w
int*min_return, *max_return
w
Specifies the child pane.
min_return
Returns the minimum height of the child, expressed in pixels.
max_return
Returns the maximum height of the child, expressed in pixels.
This procedure is equivalent to getting the min and max
resources for this child child.
Paned widgetenable auto-reconfiguring
Paned widgetdisable auto-reconfiguring
To enable or disable automatic recalculation of pane sizes and positions,
use
XawPanedSetRefigureMode :
XawPanedSetRefigureMode
void XawPanedSetRefigureMode
Widget w
Boolean mode
w
Specifies the Paned widget.
mode
Specifies whether the layout of the Paned widget is enabled (True)
or disabled (False).
When making several changes to the children of a Paned widget
after the Paned has been realized, it is a good idea to disable
relayout until after all changes have been made.
Paned widgetgetting the number of children
To retrieve the number of panes in a paned widget use
:
XawPanedGetNumSub
int XawPanedGetNumSub
Widget w
w
Specifies the Paned widget.
This function returns the number of panes in the Paned widget. This is
not the same as the number of children, since the grips are also
children of the Paned widget.
libXaw-1.0.16/specs/libXaw.ent.in 0000644 0001751 0000144 00000000157 14573370144 013436 0000000 0000000
libXaw-1.0.16/specs/Porthole.xml 0000644 0001751 0000144 00000017423 14573370144 013415 0000000 0000000
Porthole Widget
Porthole widget
Application Header file <X11/Xaw/Porthole.h>
Porthole.h
Class Header file <X11/Xaw/PortholeP.h>
PortholeP.h
Class portholeWidgetClass
portholeWidgetClass
Class Name Porthole
Porthole widgetclass name
Superclass Composite
The Porthole widget provides geometry management of a list of arbitrary
widgets, only one of which may be managed at any particular time.
The managed child widget is reparented within the porthole and is moved around
by the application (typically under the control of a Panner widget).
Resources
When creating a Porthole widget instance, the following resources are
retrieved from the argument list or from the resource database:
Porthole widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
children
ReadOnly
WidgetList
R
NULL
colormap
Colormap
Colormap
Parent's Colormap
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
height
Height
Dimension
A
see Layout Semantics
mappedWhenManaged
MappedWhenManaged
Boolean
True
numChildren
ReadOnly
Cardinal
R
0
reportCallback
ReportCallback
Callback
NULL
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
NULL
width
Width
Dimension
A
see Layout Semantics
x
Position
Position
0
y
Position
Position
0
_
reportCallback
A list of functions to invoke whenever the managed child widget changes
size or position.
Layout Semantics
Porthole widgetlayout semantics
The Porthole widget allows its managed child to request any size
that is as large
or larger than the Porthole itself and any location so long as the child
still obscures all of the Porthole. This widget typically is used with a
Panner widget.
Porthole Callbacks
Porthole widgetcallbacks
The functions registered on the reportCallback list are invoked whenever
the managed child changes size or position:
ReportProc
void ReportProc
Widget porthole
XtPointer client_data
XtPointer report
porthole
Specifies the Porthole widget.
client_data
Specifies the client data.
report
Specifies a pointer to an XawPannerReport structure containing
the location and size of the slider and the size of the canvas.
libXaw-1.0.16/specs/CH3.xml 0000644 0001751 0000144 00000007721 14573370144 012176 0000000 0000000
Simple Widgets
Each of these widgets performs a specific user interface function. They
are simple because they cannot have widget
children—they may only
be used as leaves of the widget tree. These widgets display information or
take user input.
Command
A push button that, when selected, may cause a specific action
to take place. This widget can display a multi-line string or a bitmap or pixmap image.
Grip
A rectangle that, when selected, will cause an action to take place.
Label
A rectangle that can display a multi-line string or a bitmap or pixmap image.
List
A list of text strings presented in row column format that may be
individually selected. When an element is selected an action may take
place.
Panner
A rectangular area containing a slider that may be moved in two
dimensions. Notification of movement may be continuous or discrete.
Repeater
A push button that triggers an action at an increasing rate when selected.
This widget can display a multi-line string or a bitmap or pixmap image.
Scrollbar
A rectangular area containing a thumb that when slid along one
dimension may cause a specific action to take place. The Scrollbar may
be oriented horizontally or vertically.
Simple
The base class for most of the simple widgets. Provides a rectangular
area with a settable mouse cursor and special border.
StripChart
A real time data graph that will automatically update and scroll.
Toggle
A push button that contains state information. Toggles
may also be used as "radio buttons" to implement a "one of many" or
"zero or one of many" group
of buttons. This widget can display a multi-line string or a bitmap or pixmap image.
libXaw-1.0.16/specs/List.xml 0000644 0001751 0000144 00000056251 14573370144 012536 0000000 0000000
List Widget
List widget
Application header file <X11/Xaw/List.h>
List.h
Class header file <X11/Xaw/ListP.h>
ListP.h
Class listWidgetClass
listWidgetClass
Class Name List
List widgetclass name
Superclass Simple
The List widget contains a list of strings formatted into rows and
columns. When one of the strings is selected, it is highlighted, and the
List widget's Notify action is invoked, calling all routines on
its callback list. Only one string may be selected at a time.
Resources
When creating a List widget instance, the following resources are
retrieved from the argument list or from the resource database:
List widgetresources
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
callback
Callback
Callback
NULL
colormap
Colormap
Colormap
Parent's Colormap
columnSpacing
Spacing
Dimension
6
cursor
Cursor
Cursor
XC_left_ptr
cursorName
Cursor
String
NULL
defaultColumns
Columns
int
2
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
font
Font
FontStruct
XtDefaultFont
fontSet
FontSet
XFontSet
XtDefaultFontSet
forceColumns
Columns
Boolean
False
foreground
Foreground
Pixel
XtDefaultForeground
height
Height
Dimension
A
Enough space to contain the list
insensitiveBorder
Insensitive
Pixmap
GreyPixmap
internalHeight
Height
Dimension
2
internalWidth
Width
Dimension
4
international
International
Boolean
C
False
list
List
Pointer
name of widget
longest
Longest
int
A
0
mappedWhenManaged
MappedWhenManaged
Boolean
True
numberStrings
NumberStrings
int
A
computed for NULL terminated list
pasteBuffer
Boolean
Boolean
False
pointerColor
Foreground
Pixel
XtDefaultForeground
pointerColorBackground
Background
Pixel
XtDefaultBackground
rowSpacing
Spacing
Dimension
2
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
translations
Translations
TranslationTable
See below
verticalList
Boolean
Boolean
False
width
Width
Dimension
A
Enough space to contain the list
x
Position
Position
0
y
Position
Position
0
_
callback
All functions on this list are called whenever the notify action is
invoked. The call_data argument contains information about the element
selected and is described in detail in the List Callbacks section.
columnSpacing
rowSpacing
The amount of space, in pixels, between each of the rows and columns
in the list.
defaultColumns
The default number of columns. This value is used when neither the
width nor the height of the List widget is specified or when
forceColumns is True.
font
The text font to use when displaying the list, when the
international resource is false.
fontSet
The text font set to use when displaying the list, when the
international resource is true.
forceColumns
Forces the default number of columns to be used regardless of the
List widget's current size.
foreground
A pixel value which indexes the widget's colormap to derive the color
used to paint the text of the list elements.
internalHeight
internalWidth
The margin, in pixels, between the edges of the list and the
corresponding edge of the List widget's window.
list
An array of text strings displayed in the List widget. If
numberStrings is zero (the default) then the list must be
NULL terminated. If a value is not specified for the list, then
numberStrings is set to 1, and the name of the widget is used as
the list, and longest is set to the length of the name of the
widget. The list is used in place, and must be available
to the List widget for the lifetime of this widget, or until it is
changed with or .
longest
Specifies the width, in pixels, of the longest string in the current
list. The List widget will compute this value if zero (the default)
is specified. If this resource is set by hand, entries longer than this
will be clipped to fit.
numberStrings
The number of strings in the current list. If a value of zero (the
default) is specified, the List widget will compute it. When computing
the number of strings the List widget assumes that the list is NULL
terminated.
pasteBuffer
If this resource is set to True then the name of the currently
selected list element will be put into CUT_BUFFER_0.
verticalList
If this resource is set to True then the list elements will be
presented in column major order.
List Actions
List widgetactions
The List widget supports the following actions:
Highlighting and unhighlighting the list element under the
pointer with Set and Unset
Processing application callbacks with Notify
The following is the default translation table used by the List Widget:
List widgetdefault translation table
<Btn1Down>,<Btn1Up>: Set( ) Notify( )
The full list of actions supported by List widget is:
Set( )
Sets the list element that is currently under the pointer. To
inform the user that this element is currently set, it is drawn with
foreground and background colors reversed. If this action is called when
there is no list element under the cursor, the currently set
element will be unset.
Unset( )
Cancels the set state of the element under the pointer,
and redraws it with normal foreground and background colors.
Notify( )
Calls all callbacks on the List widget's callback list. Information
about the currently selected list element is passed in the
call_data argument (see List Callbacks below).
List Callbacks
List widgetcallbacks
All procedures on the List widget's callback list will have a
XawListReturnStruct passed to them as call_data. The
structure is defined in the List widget's application header file.
XawListReturnStruct
typedef struct _XawListReturnStruct {
String string; /* string shown in the list. */
int list_index; /* index of the item selected. */
} XawListReturnStruct;
XawListReturnStruct
The list_index item used to be called simply index.
Unfortunately, this name collided with a global name defined on some
operating systems, and had to be changed.
Changing the List
To change the list that is displayed, use
XawListChange.
XawListChange
void XawListChange
Widget w
String* list
intnitems, longest
Boolean resize
w
Specifies the List widget.
list
Specifies the new list for the List widget to display.
nitems
Specifies the number of items in the list. If a value less than 1
is specified, list must be NULL terminated, and the number of
items will be calculated by the List widget.
longest
Specifies the length of the longest item in the list in pixels.
If a value less than 1 is specified, the List widget will calculate the
value.
resize
Specifies a Boolean value that if True indicates that the
List widget should try to resize itself after making the change.
The constraints of the List widget's parent are always enforced,
regardless of the value specified here.
will unset all list elements that are currently set before
the list is actually changed. The list is used in place, and must
remain usable for the lifetime of the List widget, or until list
has been changed again with this function or with .
Highlighting an Item
To highlight an item in the list, use
XawListHighlight.
XawListHighlight
void XawListHighlight
Widget w
int item
w
Specifies the List widget.
item
Specifies an index into the current list that indicates the item to be
highlighted.
Only one item can be highlighted at a time.
If an item is already highlighted when
is called,
the highlighted item is unhighlighted before the new item is highlighted.
Unhighlighting an Item
To unhighlight the currently highlighted item in the list, use
XawListUnhighlight.
XawListUnhighlight
void XawListUnhighlight
Widget w
w
Specifies the List widget.
Retrieving the Currently Selected Item
To retrieve the list element that is currently set, use
XawListShowCurrent.
XawListShowCurrent
XawListReturnStruct *XawListShowCurrent
Widget w
w
Specifies the List widget.
XawListShowCurrent
returns a pointer to an
XawListReturnStruct
structure,
containing the currently highlighted item.
If the value of the index member is XAW_LIST_NONE,
XAW_LIST_NONE
the string member is undefined, and no item is currently selected.
Restrictions
Many programmers create a scrolled list
by putting a List
widget with many entries as a child of a Viewport widget. The
List continues to create a window as big as its contents, but
that big window is only visible where it intersects the parent
Viewport's window. (I.e., it is clipped.
)
While this is a useful technique, there is a serious drawback.
X does not support windows above 32,767 pixels in width or
height, but this height limit will be exceeded by a List's
window when the List has many entries (i.e., with a 12 point
font, about 3000 entries would be too many.)
libXaw-1.0.16/specs/Tree.xml 0000644 0001751 0000144 00000024162 14573370144 012516 0000000 0000000
Tree Widget
Application Header file <X11/Xaw/Tree.h>
Class Header file <X11/Xaw/TreeP.h>
Class treeWidgetClass
Class Name Tree
Superclass Constraint
The Tree widget provides geometry management of arbitrary widgets arranged
in a directed, acyclic graph (i.e., a tree). The hierarchy is constructed
by attaching a constraint resource called treeParent to each widget
indicating which other node in the tree should be treated as the widget's
superior. The structure of the tree is shown by laying out the nodes
in the standard format for tree diagrams with lines drawn connecting each
node with its children.
The Tree sizes itself according to the needs of its children and is not
intended to be resized by its parent. Instead, it should be placed inside
another composite widget (such as the Porthole or Viewport)
that can be used to scroll around in the tree.
Resources
When creating a Tree widget instance, the following resources are
retrieved from the argument list or from the resource database:
Name
Class
Type
Notes
Default Value
accelerators
Accelerators
AcceleratorTable
NULL
ancestorSensitive
AncestorSensitive
Boolean
D
True
autoReconfigure
AutoReconfigure
Boolean
False
background
Background
Pixel
XtDefaultBackground
backgroundPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderColor
BorderColor
Pixel
XtDefaultForeground
borderPixmap
Pixmap
Pixmap
XtUnspecifiedPixmap
borderWidth
BorderWidth
Dimension
1
children
ReadOnly
WidgetList
R
NULL
colormap
Colormap
Colormap
Parent's Colormap
depth
Depth
int
C
Parent's Depth
destroyCallback
Callback
XtCallbackList
NULL
foreground
Foreground
Pixel
XtDefaultForeground
gravity
Gravity
XtGravity
WestGravity
height
Height
Dimension
A
see
hSpace
HSpace
Dimension
4
lineWidth
LineWidth
Dimension
0
mappedWhenManaged
MappedWhenManaged
Boolean
True
numChildren
ReadOnly
Cardinal
R
0
screen
Screen
Screen
R
Parent's Screen
sensitive
Sensitive
Boolean
True
vSpace
VSpace
Dimension
4
translations
Translations
TranslationTable
NULL
width
Width
Dimension
A
see
x
Position
Position
0
y
Position
Position
0
autoReconfigure
Whether or not to layout the tree every time a node is added or removed.
gravity
Specifies the side of the widget from which the tree should grow. Valid
values include WestGravity, NorthGravity, EastGravity, and
SouthGravity.
hSpace
vSpace
The amount of space, in pixels, to leave between the children. This
resource specifies the amount of space left between the outermost
children and the edge of the box.
lineWidth
The width of the lines from nodes that do not have a treeGC
constraint resource to their children.
Constraint Resources
Each child of the Tree widget must specify its superior node in the tree. In
addition, it may specify a GC to use when drawing a line between it and its
inferior nodes.
Name
Class
Type
Notes
Default Value
treeGC
TreeGC
GC
NULL
treeParent
TreeParent
Widget
NULL
treeGC
This specifies the GC to use when drawing lines between this widget and its
inferiors in the tree. If this resource is not specified, the Tree's
foreground and lineWidth will be used.
treeParent
This specifies the superior node in the tree for this widget. The default is
for the node to have no superior (and to therefore be at the top of the tree).
Layout Semantics
Each time a child is managed or unmanaged, the Tree widget will attempt
to reposition the remaining children to fix the shape of the tree if the
resource is set. Children at the top (most superior) of the tree are
drawn at the side specified by the resource.
After positioning all children, the Tree widget attempts to shrink its
own size to the minimum dimensions required for the layout.
Convenience Routines
The most efficient way to layout a tree is to set
autoReconfigure
to False and then use the
routine to arrange the children.
void XawTreeForceLayout
Widget w
w
Specifies the Tree widget.
libXaw-1.0.16/specs/AsciiSink.xml 0000644 0001751 0000144 00000010106 14573370144 013465 0000000 0000000
Ascii Sink Object and Multi Sink Object
AsciiSink object
Application Header file <X11/Xaw/AsciiSink.h>
AsciiSink.h
Class Header file <X11/Xaw/AsciiSinkP.h>
AsciiSinkP.h
Class asciiSinkObjectClass
asciiSinkObjectClass
Class Name AsciiSink
AsciiSink objectclass name
Superclass TextSink
The AsciiSink or MultiSink object is used by a text widget to render the text.
Depending on its international resource, a
AsciiText widget will create one or the other of these when the AsciiText
itself is created. Both types are nearly identical; the following discussion
applies to both, with MultiSink differences noted only as they occur.
The AsciiSink
will display all printing characters in an 8 bit font, along with handling Tab
and Carriage Return. The name has been left as AsciiSink
for compatibility.
The MultiSink will display all printing characters in a
font set, along with handling Tab and Carriage Return.
The source object also reports the text window metrics to the
text widgets.
Resources
When creating an AsciiSink object instance, the following resources are
retrieved from the argument list or from the resource database:
AsciiSink objectresources
Name
Class
Type
Notes
Default Value
background
Background
Pixel
XtDefaultBackground
destroyCallback
Callback
XtCallbackList
NULL
displayNonprinting
Output
Boolean
True
echo
Output
Boolean
True
font
Font
XFontStruct*
XtDefaultFont
fontSet
FontSet
XFontSet
XtDefaultFontSet
foreground
Foreground
Pixel
XtDefaultForeground
_
This resource is retrieved by the AsciiSink instead of being copied
from the Text widget.
The text font to use when displaying the string.
(This resource is present in the AsciiSink, but not the MultiSink.)
The text font set to use when displaying the string.
(This resource is present in the MultiSink, but not the AsciiSink.)
libXaw-1.0.16/specs/MenuButton.xml 0000644 0001751 0000144 00000035416 14573370144 013723 0000000 0000000
libXaw-1.0.16/Makefile.in 0000644 0001751 0000144 00000073537 14573370153 012037 0000000 0000000 # Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
@SET_MAKE@
VPATH = @srcdir@
am__is_gnu_make = { \
if test -z '$(MAKELEVEL)'; then \
false; \
elif test -n '$(MAKE_HOST)'; then \
true; \
elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \
true; \
else \
false; \
fi; \
}
am__make_running_with_option = \
case $${target_option-} in \
?) ;; \
*) echo "am__make_running_with_option: internal error: invalid" \
"target option '$${target_option-}' specified" >&2; \
exit 1;; \
esac; \
has_opt=no; \
sane_makeflags=$$MAKEFLAGS; \
if $(am__is_gnu_make); then \
sane_makeflags=$$MFLAGS; \
else \
case $$MAKEFLAGS in \
*\\[\ \ ]*) \
bs=\\; \
sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \
| sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \
esac; \
fi; \
skip_next=no; \
strip_trailopt () \
{ \
flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \
}; \
for flg in $$sane_makeflags; do \
test $$skip_next = yes && { skip_next=no; continue; }; \
case $$flg in \
*=*|--*) continue;; \
-*I) strip_trailopt 'I'; skip_next=yes;; \
-*I?*) strip_trailopt 'I';; \
-*O) strip_trailopt 'O'; skip_next=yes;; \
-*O?*) strip_trailopt 'O';; \
-*l) strip_trailopt 'l'; skip_next=yes;; \
-*l?*) strip_trailopt 'l';; \
-[dEDm]) skip_next=yes;; \
-[JT]) skip_next=yes;; \
esac; \
case $$flg in \
*$$target_option*) has_opt=yes; break;; \
esac; \
done; \
test $$has_opt = yes
am__make_dryrun = (target_option=n; $(am__make_running_with_option))
am__make_keepgoing = (target_option=k; $(am__make_running_with_option))
pkgdatadir = $(datadir)/@PACKAGE@
pkgincludedir = $(includedir)/@PACKAGE@
pkglibdir = $(libdir)/@PACKAGE@
pkglibexecdir = $(libexecdir)/@PACKAGE@
am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
install_sh_DATA = $(install_sh) -c -m 644
install_sh_PROGRAM = $(install_sh) -c
install_sh_SCRIPT = $(install_sh) -c
INSTALL_HEADER = $(INSTALL_DATA)
transform = $(program_transform_name)
NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
build_triplet = @build@
host_triplet = @host@
@BUILD_XAW6_TRUE@am__append_1 = xaw6.pc
@BUILD_XAW7_TRUE@am__append_2 = xaw7.pc
subdir = .
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
$(top_srcdir)/m4/ltoptions.m4 $(top_srcdir)/m4/ltsugar.m4 \
$(top_srcdir)/m4/ltversion.m4 $(top_srcdir)/m4/lt~obsolete.m4 \
$(top_srcdir)/configure.ac
am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
$(ACLOCAL_M4)
DIST_COMMON = $(srcdir)/Makefile.am $(top_srcdir)/configure \
$(am__configure_deps) $(am__DIST_COMMON)
am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
configure.lineno config.status.lineno
mkinstalldirs = $(install_sh) -d
CONFIG_HEADER = config.h
CONFIG_CLEAN_FILES = xaw6.pc xaw7.pc
CONFIG_CLEAN_VPATH_FILES =
AM_V_P = $(am__v_P_@AM_V@)
am__v_P_ = $(am__v_P_@AM_DEFAULT_V@)
am__v_P_0 = false
am__v_P_1 = :
AM_V_GEN = $(am__v_GEN_@AM_V@)
am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@)
am__v_GEN_0 = @echo " GEN " $@;
am__v_GEN_1 =
AM_V_at = $(am__v_at_@AM_V@)
am__v_at_ = $(am__v_at_@AM_DEFAULT_V@)
am__v_at_0 = @
am__v_at_1 =
SOURCES =
DIST_SOURCES =
RECURSIVE_TARGETS = all-recursive check-recursive cscopelist-recursive \
ctags-recursive dvi-recursive html-recursive info-recursive \
install-data-recursive install-dvi-recursive \
install-exec-recursive install-html-recursive \
install-info-recursive install-pdf-recursive \
install-ps-recursive install-recursive installcheck-recursive \
installdirs-recursive pdf-recursive ps-recursive \
tags-recursive uninstall-recursive
am__can_run_installinfo = \
case $$AM_UPDATE_INFO_DIR in \
n|no|NO) false;; \
*) (install-info --version) >/dev/null 2>&1;; \
esac
am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
am__vpath_adj = case $$p in \
$(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
*) f=$$p;; \
esac;
am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
am__install_max = 40
am__nobase_strip_setup = \
srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
am__nobase_strip = \
for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
am__nobase_list = $(am__nobase_strip_setup); \
for p in $$list; do echo "$$p $$p"; done | \
sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
$(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
if (++n[$$2] == $(am__install_max)) \
{ print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
END { for (dir in files) print dir, files[dir] }'
am__base_list = \
sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
am__uninstall_files_from_dir = { \
test -z "$$files" \
|| { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
|| { echo " ( cd '$$dir' && rm -f" $$files ")"; \
$(am__cd) "$$dir" && rm -f $$files; }; \
}
am__installdirs = "$(DESTDIR)$(pkgconfigdir)"
DATA = $(pkgconfig_DATA)
RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \
distclean-recursive maintainer-clean-recursive
am__recursive_targets = \
$(RECURSIVE_TARGETS) \
$(RECURSIVE_CLEAN_TARGETS) \
$(am__extra_recursive_targets)
AM_RECURSIVE_TARGETS = $(am__recursive_targets:-recursive=) TAGS CTAGS \
cscope distdir distdir-am dist dist-all distcheck
am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) \
config.h.in
# Read a list of newline-separated strings from the standard input,
# and print each of them once, without duplicates. Input order is
# *not* preserved.
am__uniquify_input = $(AWK) '\
BEGIN { nonempty = 0; } \
{ items[$$0] = 1; nonempty = 1; } \
END { if (nonempty) { for (i in items) print i; }; } \
'
# Make sure the list of sources is unique. This is necessary because,
# e.g., the same source file might be shared among _SOURCES variables
# for different programs/libraries.
am__define_uniq_tagged_files = \
list='$(am__tagged_files)'; \
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
DIST_SUBDIRS = $(SUBDIRS)
am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/config.h.in \
$(srcdir)/xaw6.pc.in $(srcdir)/xaw7.pc.in COPYING ChangeLog \
INSTALL README.md compile config.guess config.sub install-sh \
ltmain.sh missing
DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
distdir = $(PACKAGE)-$(VERSION)
top_distdir = $(distdir)
am__remove_distdir = \
if test -d "$(distdir)"; then \
find "$(distdir)" -type d ! -perm -200 -exec chmod u+w {} ';' \
&& rm -rf "$(distdir)" \
|| { sleep 5 && rm -rf "$(distdir)"; }; \
else :; fi
am__post_remove_distdir = $(am__remove_distdir)
am__relativize = \
dir0=`pwd`; \
sed_first='s,^\([^/]*\)/.*$$,\1,'; \
sed_rest='s,^[^/]*/*,,'; \
sed_last='s,^.*/\([^/]*\)$$,\1,'; \
sed_butlast='s,/*[^/]*$$,,'; \
while test -n "$$dir1"; do \
first=`echo "$$dir1" | sed -e "$$sed_first"`; \
if test "$$first" != "."; then \
if test "$$first" = ".."; then \
dir2=`echo "$$dir0" | sed -e "$$sed_last"`/"$$dir2"; \
dir0=`echo "$$dir0" | sed -e "$$sed_butlast"`; \
else \
first2=`echo "$$dir2" | sed -e "$$sed_first"`; \
if test "$$first2" = "$$first"; then \
dir2=`echo "$$dir2" | sed -e "$$sed_rest"`; \
else \
dir2="../$$dir2"; \
fi; \
dir0="$$dir0"/"$$first"; \
fi; \
fi; \
dir1=`echo "$$dir1" | sed -e "$$sed_rest"`; \
done; \
reldir="$$dir2"
DIST_ARCHIVES = $(distdir).tar.gz $(distdir).tar.xz
GZIP_ENV = --best
DIST_TARGETS = dist-xz dist-gzip
# Exists only to be overridden by the user if desired.
AM_DISTCHECK_DVI_TARGET = dvi
distuninstallcheck_listfiles = find . -type f -print
am__distuninstallcheck_listfiles = $(distuninstallcheck_listfiles) \
| sed 's|^\./|$(prefix)/|' | grep -v '$(infodir)/dir$$'
distcleancheck_listfiles = find . -type f -print
ACLOCAL = @ACLOCAL@
ADMIN_MAN_DIR = @ADMIN_MAN_DIR@
ADMIN_MAN_SUFFIX = @ADMIN_MAN_SUFFIX@
AMTAR = @AMTAR@
AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
APP_MAN_DIR = @APP_MAN_DIR@
APP_MAN_SUFFIX = @APP_MAN_SUFFIX@
AR = @AR@
AUTOCONF = @AUTOCONF@
AUTOHEADER = @AUTOHEADER@
AUTOMAKE = @AUTOMAKE@
AWK = @AWK@
BASE_CFLAGS = @BASE_CFLAGS@
CC = @CC@
CCDEPMODE = @CCDEPMODE@
CFLAGS = @CFLAGS@
CHANGELOG_CMD = @CHANGELOG_CMD@
CPPFLAGS = @CPPFLAGS@
CSCOPE = @CSCOPE@
CTAGS = @CTAGS@
CWARNFLAGS = @CWARNFLAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
DLLTOOL = @DLLTOOL@
DRIVER_MAN_DIR = @DRIVER_MAN_DIR@
DRIVER_MAN_SUFFIX = @DRIVER_MAN_SUFFIX@
DSYMUTIL = @DSYMUTIL@
DUMPBIN = @DUMPBIN@
ECHO_C = @ECHO_C@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
FILECMD = @FILECMD@
FILE_MAN_DIR = @FILE_MAN_DIR@
FILE_MAN_SUFFIX = @FILE_MAN_SUFFIX@
FOP = @FOP@
GREP = @GREP@
INSTALL = @INSTALL@
INSTALL_CMD = @INSTALL_CMD@
INSTALL_DATA = @INSTALL_DATA@
INSTALL_PROGRAM = @INSTALL_PROGRAM@
INSTALL_SCRIPT = @INSTALL_SCRIPT@
INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
LD = @LD@
LDFLAGS = @LDFLAGS@
LIBEXT = @LIBEXT@
LIBOBJS = @LIBOBJS@
LIBS = @LIBS@
LIBTOOL = @LIBTOOL@
LIB_MAN_DIR = @LIB_MAN_DIR@
LIB_MAN_SUFFIX = @LIB_MAN_SUFFIX@
LIPO = @LIPO@
LN_S = @LN_S@
LTLIBOBJS = @LTLIBOBJS@
LT_SYS_LIBRARY_PATH = @LT_SYS_LIBRARY_PATH@
MAKEINFO = @MAKEINFO@
MANIFEST_TOOL = @MANIFEST_TOOL@
MAN_SUBSTS = @MAN_SUBSTS@
MISC_MAN_DIR = @MISC_MAN_DIR@
MISC_MAN_SUFFIX = @MISC_MAN_SUFFIX@
MKDIR_P = @MKDIR_P@
NM = @NM@
NMEDIT = @NMEDIT@
OBJDUMP = @OBJDUMP@
OBJEXT = @OBJEXT@
OTOOL = @OTOOL@
OTOOL64 = @OTOOL64@
PACKAGE = @PACKAGE@
PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
PACKAGE_NAME = @PACKAGE_NAME@
PACKAGE_STRING = @PACKAGE_STRING@
PACKAGE_TARNAME = @PACKAGE_TARNAME@
PACKAGE_URL = @PACKAGE_URL@
PACKAGE_VERSION = @PACKAGE_VERSION@
PATH_SEPARATOR = @PATH_SEPARATOR@
PKG_CONFIG = @PKG_CONFIG@
PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@
PKG_CONFIG_PATH = @PKG_CONFIG_PATH@
RANLIB = @RANLIB@
SED = @SED@
SET_MAKE = @SET_MAKE@
SHELL = @SHELL@
STRICT_CFLAGS = @STRICT_CFLAGS@
STRIP = @STRIP@
STYLESHEET_SRCDIR = @STYLESHEET_SRCDIR@
VERSION = @VERSION@
XAW6_CFLAGS = @XAW6_CFLAGS@
XAW6_LIBS = @XAW6_LIBS@
XAW7_CFLAGS = @XAW7_CFLAGS@
XAW7_LIBS = @XAW7_LIBS@
XMLTO = @XMLTO@
XORG_MALLOC_DEBUG_ENV = @XORG_MALLOC_DEBUG_ENV@
XORG_MAN_PAGE = @XORG_MAN_PAGE@
XORG_SGML_PATH = @XORG_SGML_PATH@
XSLTPROC = @XSLTPROC@
XSL_STYLESHEET = @XSL_STYLESHEET@
abs_builddir = @abs_builddir@
abs_srcdir = @abs_srcdir@
abs_top_builddir = @abs_top_builddir@
abs_top_srcdir = @abs_top_srcdir@
ac_ct_AR = @ac_ct_AR@
ac_ct_CC = @ac_ct_CC@
ac_ct_DUMPBIN = @ac_ct_DUMPBIN@
am__include = @am__include@
am__leading_dot = @am__leading_dot@
am__quote = @am__quote@
am__tar = @am__tar@
am__untar = @am__untar@
bindir = @bindir@
build = @build@
build_alias = @build_alias@
build_cpu = @build_cpu@
build_os = @build_os@
build_vendor = @build_vendor@
builddir = @builddir@
datadir = @datadir@
datarootdir = @datarootdir@
docdir = @docdir@
dvidir = @dvidir@
exec_prefix = @exec_prefix@
host = @host@
host_alias = @host_alias@
host_cpu = @host_cpu@
host_os = @host_os@
host_vendor = @host_vendor@
htmldir = @htmldir@
includedir = @includedir@
infodir = @infodir@
install_sh = @install_sh@
libdir = @libdir@
libexecdir = @libexecdir@
localedir = @localedir@
localstatedir = @localstatedir@
mandir = @mandir@
mkdir_p = @mkdir_p@
oldincludedir = @oldincludedir@
pdfdir = @pdfdir@
prefix = @prefix@
program_transform_name = @program_transform_name@
psdir = @psdir@
runstatedir = @runstatedir@
sbindir = @sbindir@
sharedstatedir = @sharedstatedir@
srcdir = @srcdir@
sysconfdir = @sysconfdir@
target_alias = @target_alias@
top_build_prefix = @top_build_prefix@
top_builddir = @top_builddir@
top_srcdir = @top_srcdir@
SUBDIRS = include src examples man specs
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = $(am__append_1) $(am__append_2)
@BUILD_XAW6_TRUE@@PLATFORM_DARWIN_FALSE@DEFAULT_LIB = libXaw6.@LIBEXT@
@BUILD_XAW6_TRUE@@PLATFORM_DARWIN_TRUE@DEFAULT_LIB = libXaw.6.@LIBEXT@
@BUILD_XAW7_TRUE@@PLATFORM_DARWIN_FALSE@DEFAULT_LIB = libXaw7.@LIBEXT@
@BUILD_XAW7_TRUE@@PLATFORM_DARWIN_TRUE@DEFAULT_LIB = libXaw.7.@LIBEXT@
MAINTAINERCLEANFILES = ChangeLog INSTALL
EXTRA_DIST = \
README.md \
autogen.sh \
old-doc/Changelog \
old-doc/CHANGES
all: config.h
$(MAKE) $(AM_MAKEFLAGS) all-recursive
.SUFFIXES:
am--refresh: Makefile
@:
$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps)
@for dep in $?; do \
case '$(am__configure_deps)' in \
*$$dep*) \
echo ' cd $(srcdir) && $(AUTOMAKE) --foreign'; \
$(am__cd) $(srcdir) && $(AUTOMAKE) --foreign \
&& exit 0; \
exit 1;; \
esac; \
done; \
echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign Makefile'; \
$(am__cd) $(top_srcdir) && \
$(AUTOMAKE) --foreign Makefile
Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
@case '$?' in \
*config.status*) \
echo ' $(SHELL) ./config.status'; \
$(SHELL) ./config.status;; \
*) \
echo ' cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__maybe_remake_depfiles)'; \
cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__maybe_remake_depfiles);; \
esac;
$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
$(SHELL) ./config.status --recheck
$(top_srcdir)/configure: $(am__configure_deps)
$(am__cd) $(srcdir) && $(AUTOCONF)
$(ACLOCAL_M4): $(am__aclocal_m4_deps)
$(am__cd) $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
$(am__aclocal_m4_deps):
config.h: stamp-h1
@test -f $@ || rm -f stamp-h1
@test -f $@ || $(MAKE) $(AM_MAKEFLAGS) stamp-h1
stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status
@rm -f stamp-h1
cd $(top_builddir) && $(SHELL) ./config.status config.h
$(srcdir)/config.h.in: $(am__configure_deps)
($(am__cd) $(top_srcdir) && $(AUTOHEADER))
rm -f stamp-h1
touch $@
distclean-hdr:
-rm -f config.h stamp-h1
xaw6.pc: $(top_builddir)/config.status $(srcdir)/xaw6.pc.in
cd $(top_builddir) && $(SHELL) ./config.status $@
xaw7.pc: $(top_builddir)/config.status $(srcdir)/xaw7.pc.in
cd $(top_builddir) && $(SHELL) ./config.status $@
mostlyclean-libtool:
-rm -f *.lo
clean-libtool:
-rm -rf .libs _libs
distclean-libtool:
-rm -f libtool config.lt
install-pkgconfigDATA: $(pkgconfig_DATA)
@$(NORMAL_INSTALL)
@list='$(pkgconfig_DATA)'; test -n "$(pkgconfigdir)" || list=; \
if test -n "$$list"; then \
echo " $(MKDIR_P) '$(DESTDIR)$(pkgconfigdir)'"; \
$(MKDIR_P) "$(DESTDIR)$(pkgconfigdir)" || exit 1; \
fi; \
for p in $$list; do \
if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
echo "$$d$$p"; \
done | $(am__base_list) | \
while read files; do \
echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(pkgconfigdir)'"; \
$(INSTALL_DATA) $$files "$(DESTDIR)$(pkgconfigdir)" || exit $$?; \
done
uninstall-pkgconfigDATA:
@$(NORMAL_UNINSTALL)
@list='$(pkgconfig_DATA)'; test -n "$(pkgconfigdir)" || list=; \
files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
dir='$(DESTDIR)$(pkgconfigdir)'; $(am__uninstall_files_from_dir)
# This directory's subdirectories are mostly independent; you can cd
# into them and run 'make' without going through this Makefile.
# To change the values of 'make' variables: instead of editing Makefiles,
# (1) if the variable is set in 'config.status', edit 'config.status'
# (which will cause the Makefiles to be regenerated when you run 'make');
# (2) otherwise, pass the desired values on the 'make' command line.
$(am__recursive_targets):
@fail=; \
if $(am__make_keepgoing); then \
failcom='fail=yes'; \
else \
failcom='exit 1'; \
fi; \
dot_seen=no; \
target=`echo $@ | sed s/-recursive//`; \
case "$@" in \
distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
*) list='$(SUBDIRS)' ;; \
esac; \
for subdir in $$list; do \
echo "Making $$target in $$subdir"; \
if test "$$subdir" = "."; then \
dot_seen=yes; \
local_target="$$target-am"; \
else \
local_target="$$target"; \
fi; \
($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
|| eval $$failcom; \
done; \
if test "$$dot_seen" = "no"; then \
$(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
fi; test -z "$$fail"
ID: $(am__tagged_files)
$(am__define_uniq_tagged_files); mkid -fID $$unique
tags: tags-recursive
TAGS: tags
tags-am: $(TAGS_DEPENDENCIES) $(am__tagged_files)
set x; \
here=`pwd`; \
if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
include_option=--etags-include; \
empty_fix=.; \
else \
include_option=--include; \
empty_fix=; \
fi; \
list='$(SUBDIRS)'; for subdir in $$list; do \
if test "$$subdir" = .; then :; else \
test ! -f $$subdir/TAGS || \
set "$$@" "$$include_option=$$here/$$subdir/TAGS"; \
fi; \
done; \
$(am__define_uniq_tagged_files); \
shift; \
if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \
test -n "$$unique" || unique=$$empty_fix; \
if test $$# -gt 0; then \
$(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
"$$@" $$unique; \
else \
$(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
$$unique; \
fi; \
fi
ctags: ctags-recursive
CTAGS: ctags
ctags-am: $(TAGS_DEPENDENCIES) $(am__tagged_files)
$(am__define_uniq_tagged_files); \
test -z "$(CTAGS_ARGS)$$unique" \
|| $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
$$unique
GTAGS:
here=`$(am__cd) $(top_builddir) && pwd` \
&& $(am__cd) $(top_srcdir) \
&& gtags -i $(GTAGS_ARGS) "$$here"
cscope: cscope.files
test ! -s cscope.files \
|| $(CSCOPE) -b -q $(AM_CSCOPEFLAGS) $(CSCOPEFLAGS) -i cscope.files $(CSCOPE_ARGS)
clean-cscope:
-rm -f cscope.files
cscope.files: clean-cscope cscopelist
cscopelist: cscopelist-recursive
cscopelist-am: $(am__tagged_files)
list='$(am__tagged_files)'; \
case "$(srcdir)" in \
[\\/]* | ?:[\\/]*) sdir="$(srcdir)" ;; \
*) sdir=$(subdir)/$(srcdir) ;; \
esac; \
for i in $$list; do \
if test -f "$$i"; then \
echo "$(subdir)/$$i"; \
else \
echo "$$sdir/$$i"; \
fi; \
done >> $(top_builddir)/cscope.files
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-rm -f cscope.out cscope.in.out cscope.po.out cscope.files
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
distdir-am: $(DISTFILES)
$(am__remove_distdir)
test -d "$(distdir)" || mkdir "$(distdir)"
@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
list='$(DISTFILES)'; \
dist_files=`for file in $$list; do echo $$file; done | \
sed -e "s|^$$srcdirstrip/||;t" \
-e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
case $$dist_files in \
*/*) $(MKDIR_P) `echo "$$dist_files" | \
sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
sort -u` ;; \
esac; \
for file in $$dist_files; do \
if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
if test -d $$d/$$file; then \
dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
if test -d "$(distdir)/$$file"; then \
find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
fi; \
if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
fi; \
cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
else \
test -f "$(distdir)/$$file" \
|| cp -p $$d/$$file "$(distdir)/$$file" \
|| exit 1; \
fi; \
done
@list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
if test "$$subdir" = .; then :; else \
$(am__make_dryrun) \
|| test -d "$(distdir)/$$subdir" \
|| $(MKDIR_P) "$(distdir)/$$subdir" \
|| exit 1; \
dir1=$$subdir; dir2="$(distdir)/$$subdir"; \
$(am__relativize); \
new_distdir=$$reldir; \
dir1=$$subdir; dir2="$(top_distdir)"; \
$(am__relativize); \
new_top_distdir=$$reldir; \
echo " (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) top_distdir="$$new_top_distdir" distdir="$$new_distdir" \\"; \
echo " am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)"; \
($(am__cd) $$subdir && \
$(MAKE) $(AM_MAKEFLAGS) \
top_distdir="$$new_top_distdir" \
distdir="$$new_distdir" \
am__remove_distdir=: \
am__skip_length_check=: \
am__skip_mode_fix=: \
distdir) \
|| exit 1; \
fi; \
done
$(MAKE) $(AM_MAKEFLAGS) \
top_distdir="$(top_distdir)" distdir="$(distdir)" \
dist-hook
-test -n "$(am__skip_mode_fix)" \
|| find "$(distdir)" -type d ! -perm -755 \
-exec chmod u+rwx,go+rx {} \; -o \
! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
! -type d ! -perm -400 -exec chmod a+r {} \; -o \
! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \
|| chmod -R a+r "$(distdir)"
dist-gzip: distdir
tardir=$(distdir) && $(am__tar) | eval GZIP= gzip $(GZIP_ENV) -c >$(distdir).tar.gz
$(am__post_remove_distdir)
dist-bzip2: distdir
tardir=$(distdir) && $(am__tar) | BZIP2=$${BZIP2--9} bzip2 -c >$(distdir).tar.bz2
$(am__post_remove_distdir)
dist-lzip: distdir
tardir=$(distdir) && $(am__tar) | lzip -c $${LZIP_OPT--9} >$(distdir).tar.lz
$(am__post_remove_distdir)
dist-xz: distdir
tardir=$(distdir) && $(am__tar) | XZ_OPT=$${XZ_OPT--e} xz -c >$(distdir).tar.xz
$(am__post_remove_distdir)
dist-zstd: distdir
tardir=$(distdir) && $(am__tar) | zstd -c $${ZSTD_CLEVEL-$${ZSTD_OPT--19}} >$(distdir).tar.zst
$(am__post_remove_distdir)
dist-tarZ: distdir
@echo WARNING: "Support for distribution archives compressed with" \
"legacy program 'compress' is deprecated." >&2
@echo WARNING: "It will be removed altogether in Automake 2.0" >&2
tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z
$(am__post_remove_distdir)
dist-shar: distdir
@echo WARNING: "Support for shar distribution archives is" \
"deprecated." >&2
@echo WARNING: "It will be removed altogether in Automake 2.0" >&2
shar $(distdir) | eval GZIP= gzip $(GZIP_ENV) -c >$(distdir).shar.gz
$(am__post_remove_distdir)
dist-zip: distdir
-rm -f $(distdir).zip
zip -rq $(distdir).zip $(distdir)
$(am__post_remove_distdir)
dist dist-all:
$(MAKE) $(AM_MAKEFLAGS) $(DIST_TARGETS) am__post_remove_distdir='@:'
$(am__post_remove_distdir)
# This target untars the dist file and tries a VPATH configuration. Then
# it guarantees that the distribution is self-contained by making another
# tarfile.
distcheck: dist
case '$(DIST_ARCHIVES)' in \
*.tar.gz*) \
eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).tar.gz | $(am__untar) ;;\
*.tar.bz2*) \
bzip2 -dc $(distdir).tar.bz2 | $(am__untar) ;;\
*.tar.lz*) \
lzip -dc $(distdir).tar.lz | $(am__untar) ;;\
*.tar.xz*) \
xz -dc $(distdir).tar.xz | $(am__untar) ;;\
*.tar.Z*) \
uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
*.shar.gz*) \
eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).shar.gz | unshar ;;\
*.zip*) \
unzip $(distdir).zip ;;\
*.tar.zst*) \
zstd -dc $(distdir).tar.zst | $(am__untar) ;;\
esac
chmod -R a-w $(distdir)
chmod u+w $(distdir)
mkdir $(distdir)/_build $(distdir)/_build/sub $(distdir)/_inst
chmod a-w $(distdir)
test -d $(distdir)/_build || exit 0; \
dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \
&& dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \
&& am__cwd=`pwd` \
&& $(am__cd) $(distdir)/_build/sub \
&& ../../configure \
$(AM_DISTCHECK_CONFIGURE_FLAGS) \
$(DISTCHECK_CONFIGURE_FLAGS) \
--srcdir=../.. --prefix="$$dc_install_base" \
&& $(MAKE) $(AM_MAKEFLAGS) \
&& $(MAKE) $(AM_MAKEFLAGS) $(AM_DISTCHECK_DVI_TARGET) \
&& $(MAKE) $(AM_MAKEFLAGS) check \
&& $(MAKE) $(AM_MAKEFLAGS) install \
&& $(MAKE) $(AM_MAKEFLAGS) installcheck \
&& $(MAKE) $(AM_MAKEFLAGS) uninstall \
&& $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \
distuninstallcheck \
&& chmod -R a-w "$$dc_install_base" \
&& ({ \
(cd ../.. && umask 077 && mkdir "$$dc_destdir") \
&& $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \
&& $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \
&& $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \
distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \
} || { rm -rf "$$dc_destdir"; exit 1; }) \
&& rm -rf "$$dc_destdir" \
&& $(MAKE) $(AM_MAKEFLAGS) dist \
&& rm -rf $(DIST_ARCHIVES) \
&& $(MAKE) $(AM_MAKEFLAGS) distcleancheck \
&& cd "$$am__cwd" \
|| exit 1
$(am__post_remove_distdir)
@(echo "$(distdir) archives ready for distribution: "; \
list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \
sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x'
distuninstallcheck:
@test -n '$(distuninstallcheck_dir)' || { \
echo 'ERROR: trying to run $@ with an empty' \
'$$(distuninstallcheck_dir)' >&2; \
exit 1; \
}; \
$(am__cd) '$(distuninstallcheck_dir)' || { \
echo 'ERROR: cannot chdir into $(distuninstallcheck_dir)' >&2; \
exit 1; \
}; \
test `$(am__distuninstallcheck_listfiles) | wc -l` -eq 0 \
|| { echo "ERROR: files left after uninstall:" ; \
if test -n "$(DESTDIR)"; then \
echo " (check DESTDIR support)"; \
fi ; \
$(distuninstallcheck_listfiles) ; \
exit 1; } >&2
distcleancheck: distclean
@if test '$(srcdir)' = . ; then \
echo "ERROR: distcleancheck can only run from a VPATH build" ; \
exit 1 ; \
fi
@test `$(distcleancheck_listfiles) | wc -l` -eq 0 \
|| { echo "ERROR: files left in build directory after distclean:" ; \
$(distcleancheck_listfiles) ; \
exit 1; } >&2
check-am: all-am
check: check-recursive
all-am: Makefile $(DATA) config.h
installdirs: installdirs-recursive
installdirs-am:
for dir in "$(DESTDIR)$(pkgconfigdir)"; do \
test -z "$$dir" || $(MKDIR_P) "$$dir"; \
done
install: install-recursive
install-exec: install-exec-recursive
install-data: install-data-recursive
uninstall: uninstall-recursive
install-am: all-am
@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
installcheck: installcheck-recursive
install-strip:
if test -z '$(STRIP)'; then \
$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
install; \
else \
$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
"INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \
fi
mostlyclean-generic:
clean-generic:
distclean-generic:
-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
maintainer-clean-generic:
@echo "This command is intended for maintainers to use"
@echo "it deletes files that may require special tools to rebuild."
-test -z "$(MAINTAINERCLEANFILES)" || rm -f $(MAINTAINERCLEANFILES)
clean: clean-recursive
clean-am: clean-generic clean-libtool mostlyclean-am
distclean: distclean-recursive
-rm -f $(am__CONFIG_DISTCLEAN_FILES)
-rm -f Makefile
distclean-am: clean-am distclean-generic distclean-hdr \
distclean-libtool distclean-tags
dvi: dvi-recursive
dvi-am:
html: html-recursive
html-am:
info: info-recursive
info-am:
install-data-am: install-pkgconfigDATA
install-dvi: install-dvi-recursive
install-dvi-am:
install-exec-am:
@$(NORMAL_INSTALL)
$(MAKE) $(AM_MAKEFLAGS) install-exec-hook
install-html: install-html-recursive
install-html-am:
install-info: install-info-recursive
install-info-am:
install-man:
install-pdf: install-pdf-recursive
install-pdf-am:
install-ps: install-ps-recursive
install-ps-am:
installcheck-am:
maintainer-clean: maintainer-clean-recursive
-rm -f $(am__CONFIG_DISTCLEAN_FILES)
-rm -rf $(top_srcdir)/autom4te.cache
-rm -f Makefile
maintainer-clean-am: distclean-am maintainer-clean-generic
mostlyclean: mostlyclean-recursive
mostlyclean-am: mostlyclean-generic mostlyclean-libtool
pdf: pdf-recursive
pdf-am:
ps: ps-recursive
ps-am:
uninstall-am: uninstall-local uninstall-pkgconfigDATA
.MAKE: $(am__recursive_targets) all install-am install-exec-am \
install-strip
.PHONY: $(am__recursive_targets) CTAGS GTAGS TAGS all all-am \
am--refresh check check-am clean clean-cscope clean-generic \
clean-libtool cscope cscopelist-am ctags ctags-am dist \
dist-all dist-bzip2 dist-gzip dist-hook dist-lzip dist-shar \
dist-tarZ dist-xz dist-zip dist-zstd distcheck distclean \
distclean-generic distclean-hdr distclean-libtool \
distclean-tags distcleancheck distdir distuninstallcheck dvi \
dvi-am html html-am info info-am install install-am \
install-data install-data-am install-dvi install-dvi-am \
install-exec install-exec-am install-exec-hook install-html \
install-html-am install-info install-info-am install-man \
install-pdf install-pdf-am install-pkgconfigDATA install-ps \
install-ps-am install-strip installcheck installcheck-am \
installdirs installdirs-am maintainer-clean \
maintainer-clean-generic mostlyclean mostlyclean-generic \
mostlyclean-libtool pdf pdf-am ps ps-am tags tags-am uninstall \
uninstall-am uninstall-local uninstall-pkgconfigDATA
.PRECIOUS: Makefile
install-exec-hook:
cd $(DESTDIR)$(libdir) && rm -f libXaw.@LIBEXT@ && $(LN_S) $(DEFAULT_LIB) libXaw.@LIBEXT@
uninstall-local:
-rm -f $(DESTDIR)$(libdir)/libXaw.@LIBEXT@
.PHONY: ChangeLog INSTALL
INSTALL:
$(INSTALL_CMD)
ChangeLog:
$(CHANGELOG_CMD)
dist-hook: ChangeLog INSTALL
# Tell versions [3.59,3.63) of GNU make to not export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:
libXaw-1.0.16/README.md 0000644 0001751 0000144 00000001001 14573370144 011222 0000000 0000000 Xaw is the X Athena Widget Set.
Xaw is a widget set based on the X Toolkit Intrinsics (Xt) Library.
All questions regarding this software should be directed at the
Xorg mailing list:
https://lists.x.org/mailman/listinfo/xorg
The primary development code repository can be found at:
https://gitlab.freedesktop.org/xorg/lib/libXaw
Please submit bug reports and requests to merge patches there.
For patch submission instructions, see:
https://www.x.org/wiki/Development/Documentation/SubmittingPatches
libXaw-1.0.16/xaw6.pc.in 0000644 0001751 0000144 00000000420 14573370144 011565 0000000 0000000 prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@
Name: Xaw
Description: X Athena Widgets Library, version 6
Version: @PACKAGE_VERSION@
Requires: xproto xt
Requires.private: x11 xext xt xmu
Cflags: -I${includedir}
Libs: -L${libdir} -lXaw6
libXaw-1.0.16/config.guess 0000755 0001751 0000144 00000140512 14573370153 012276 0000000 0000000 #! /bin/sh
# Attempt to guess a canonical system name.
# Copyright 1992-2022 Free Software Foundation, Inc.
# shellcheck disable=SC2006,SC2268 # see below for rationale
timestamp='2022-01-09'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, see .
#
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that
# program. This Exception is an additional permission under section 7
# of the GNU General Public License, version 3 ("GPLv3").
#
# Originally written by Per Bothner; maintained since 2000 by Ben Elliston.
#
# You can get the latest version of this script from:
# https://git.savannah.gnu.org/cgit/config.git/plain/config.guess
#
# Please send patches to .
# The "shellcheck disable" line above the timestamp inhibits complaints
# about features and limitations of the classic Bourne shell that were
# superseded or lifted in POSIX. However, this script identifies a wide
# variety of pre-POSIX systems that do not have POSIX shells at all, and
# even some reasonably current systems (Solaris 10 as case-in-point) still
# have a pre-POSIX /bin/sh.
me=`echo "$0" | sed -e 's,.*/,,'`
usage="\
Usage: $0 [OPTION]
Output the configuration name of the system \`$me' is run on.
Options:
-h, --help print this help, then exit
-t, --time-stamp print date of last modification, then exit
-v, --version print version number, then exit
Report bugs and patches to ."
version="\
GNU config.guess ($timestamp)
Originally written by Per Bothner.
Copyright 1992-2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
help="
Try \`$me --help' for more information."
# Parse command line
while test $# -gt 0 ; do
case $1 in
--time-stamp | --time* | -t )
echo "$timestamp" ; exit ;;
--version | -v )
echo "$version" ; exit ;;
--help | --h* | -h )
echo "$usage"; exit ;;
-- ) # Stop option processing
shift; break ;;
- ) # Use stdin as input.
break ;;
-* )
echo "$me: invalid option $1$help" >&2
exit 1 ;;
* )
break ;;
esac
done
if test $# != 0; then
echo "$me: too many arguments$help" >&2
exit 1
fi
# Just in case it came from the environment.
GUESS=
# CC_FOR_BUILD -- compiler used by this script. Note that the use of a
# compiler to aid in system detection is discouraged as it requires
# temporary files to be created and, as you can see below, it is a
# headache to deal with in a portable fashion.
# Historically, `CC_FOR_BUILD' used to be named `HOST_CC'. We still
# use `HOST_CC' if defined, but it is deprecated.
# Portable tmp directory creation inspired by the Autoconf team.
tmp=
# shellcheck disable=SC2172
trap 'test -z "$tmp" || rm -fr "$tmp"' 0 1 2 13 15
set_cc_for_build() {
# prevent multiple calls if $tmp is already set
test "$tmp" && return 0
: "${TMPDIR=/tmp}"
# shellcheck disable=SC2039,SC3028
{ tmp=`(umask 077 && mktemp -d "$TMPDIR/cgXXXXXX") 2>/dev/null` && test -n "$tmp" && test -d "$tmp" ; } ||
{ test -n "$RANDOM" && tmp=$TMPDIR/cg$$-$RANDOM && (umask 077 && mkdir "$tmp" 2>/dev/null) ; } ||
{ tmp=$TMPDIR/cg-$$ && (umask 077 && mkdir "$tmp" 2>/dev/null) && echo "Warning: creating insecure temp directory" >&2 ; } ||
{ echo "$me: cannot create a temporary directory in $TMPDIR" >&2 ; exit 1 ; }
dummy=$tmp/dummy
case ${CC_FOR_BUILD-},${HOST_CC-},${CC-} in
,,) echo "int x;" > "$dummy.c"
for driver in cc gcc c89 c99 ; do
if ($driver -c -o "$dummy.o" "$dummy.c") >/dev/null 2>&1 ; then
CC_FOR_BUILD=$driver
break
fi
done
if test x"$CC_FOR_BUILD" = x ; then
CC_FOR_BUILD=no_compiler_found
fi
;;
,,*) CC_FOR_BUILD=$CC ;;
,*,*) CC_FOR_BUILD=$HOST_CC ;;
esac
}
# This is needed to find uname on a Pyramid OSx when run in the BSD universe.
# (ghazi@noc.rutgers.edu 1994-08-24)
if test -f /.attbin/uname ; then
PATH=$PATH:/.attbin ; export PATH
fi
UNAME_MACHINE=`(uname -m) 2>/dev/null` || UNAME_MACHINE=unknown
UNAME_RELEASE=`(uname -r) 2>/dev/null` || UNAME_RELEASE=unknown
UNAME_SYSTEM=`(uname -s) 2>/dev/null` || UNAME_SYSTEM=unknown
UNAME_VERSION=`(uname -v) 2>/dev/null` || UNAME_VERSION=unknown
case $UNAME_SYSTEM in
Linux|GNU|GNU/*)
LIBC=unknown
set_cc_for_build
cat <<-EOF > "$dummy.c"
#include
#if defined(__UCLIBC__)
LIBC=uclibc
#elif defined(__dietlibc__)
LIBC=dietlibc
#elif defined(__GLIBC__)
LIBC=gnu
#else
#include
/* First heuristic to detect musl libc. */
#ifdef __DEFINED_va_list
LIBC=musl
#endif
#endif
EOF
cc_set_libc=`$CC_FOR_BUILD -E "$dummy.c" 2>/dev/null | grep '^LIBC' | sed 's, ,,g'`
eval "$cc_set_libc"
# Second heuristic to detect musl libc.
if [ "$LIBC" = unknown ] &&
command -v ldd >/dev/null &&
ldd --version 2>&1 | grep -q ^musl; then
LIBC=musl
fi
# If the system lacks a compiler, then just pick glibc.
# We could probably try harder.
if [ "$LIBC" = unknown ]; then
LIBC=gnu
fi
;;
esac
# Note: order is significant - the case branches are not exclusive.
case $UNAME_MACHINE:$UNAME_SYSTEM:$UNAME_RELEASE:$UNAME_VERSION in
*:NetBSD:*:*)
# NetBSD (nbsd) targets should (where applicable) match one or
# more of the tuples: *-*-netbsdelf*, *-*-netbsdaout*,
# *-*-netbsdecoff* and *-*-netbsd*. For targets that recently
# switched to ELF, *-*-netbsd* would select the old
# object file format. This provides both forward
# compatibility and a consistent mechanism for selecting the
# object file format.
#
# Note: NetBSD doesn't particularly care about the vendor
# portion of the name. We always set it to "unknown".
UNAME_MACHINE_ARCH=`(uname -p 2>/dev/null || \
/sbin/sysctl -n hw.machine_arch 2>/dev/null || \
/usr/sbin/sysctl -n hw.machine_arch 2>/dev/null || \
echo unknown)`
case $UNAME_MACHINE_ARCH in
aarch64eb) machine=aarch64_be-unknown ;;
armeb) machine=armeb-unknown ;;
arm*) machine=arm-unknown ;;
sh3el) machine=shl-unknown ;;
sh3eb) machine=sh-unknown ;;
sh5el) machine=sh5le-unknown ;;
earmv*)
arch=`echo "$UNAME_MACHINE_ARCH" | sed -e 's,^e\(armv[0-9]\).*$,\1,'`
endian=`echo "$UNAME_MACHINE_ARCH" | sed -ne 's,^.*\(eb\)$,\1,p'`
machine=${arch}${endian}-unknown
;;
*) machine=$UNAME_MACHINE_ARCH-unknown ;;
esac
# The Operating System including object format, if it has switched
# to ELF recently (or will in the future) and ABI.
case $UNAME_MACHINE_ARCH in
earm*)
os=netbsdelf
;;
arm*|i386|m68k|ns32k|sh3*|sparc|vax)
set_cc_for_build
if echo __ELF__ | $CC_FOR_BUILD -E - 2>/dev/null \
| grep -q __ELF__
then
# Once all utilities can be ECOFF (netbsdecoff) or a.out (netbsdaout).
# Return netbsd for either. FIX?
os=netbsd
else
os=netbsdelf
fi
;;
*)
os=netbsd
;;
esac
# Determine ABI tags.
case $UNAME_MACHINE_ARCH in
earm*)
expr='s/^earmv[0-9]/-eabi/;s/eb$//'
abi=`echo "$UNAME_MACHINE_ARCH" | sed -e "$expr"`
;;
esac
# The OS release
# Debian GNU/NetBSD machines have a different userland, and
# thus, need a distinct triplet. However, they do not need
# kernel version information, so it can be replaced with a
# suitable tag, in the style of linux-gnu.
case $UNAME_VERSION in
Debian*)
release='-gnu'
;;
*)
release=`echo "$UNAME_RELEASE" | sed -e 's/[-_].*//' | cut -d. -f1,2`
;;
esac
# Since CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM:
# contains redundant information, the shorter form:
# CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM is used.
GUESS=$machine-${os}${release}${abi-}
;;
*:Bitrig:*:*)
UNAME_MACHINE_ARCH=`arch | sed 's/Bitrig.//'`
GUESS=$UNAME_MACHINE_ARCH-unknown-bitrig$UNAME_RELEASE
;;
*:OpenBSD:*:*)
UNAME_MACHINE_ARCH=`arch | sed 's/OpenBSD.//'`
GUESS=$UNAME_MACHINE_ARCH-unknown-openbsd$UNAME_RELEASE
;;
*:SecBSD:*:*)
UNAME_MACHINE_ARCH=`arch | sed 's/SecBSD.//'`
GUESS=$UNAME_MACHINE_ARCH-unknown-secbsd$UNAME_RELEASE
;;
*:LibertyBSD:*:*)
UNAME_MACHINE_ARCH=`arch | sed 's/^.*BSD\.//'`
GUESS=$UNAME_MACHINE_ARCH-unknown-libertybsd$UNAME_RELEASE
;;
*:MidnightBSD:*:*)
GUESS=$UNAME_MACHINE-unknown-midnightbsd$UNAME_RELEASE
;;
*:ekkoBSD:*:*)
GUESS=$UNAME_MACHINE-unknown-ekkobsd$UNAME_RELEASE
;;
*:SolidBSD:*:*)
GUESS=$UNAME_MACHINE-unknown-solidbsd$UNAME_RELEASE
;;
*:OS108:*:*)
GUESS=$UNAME_MACHINE-unknown-os108_$UNAME_RELEASE
;;
macppc:MirBSD:*:*)
GUESS=powerpc-unknown-mirbsd$UNAME_RELEASE
;;
*:MirBSD:*:*)
GUESS=$UNAME_MACHINE-unknown-mirbsd$UNAME_RELEASE
;;
*:Sortix:*:*)
GUESS=$UNAME_MACHINE-unknown-sortix
;;
*:Twizzler:*:*)
GUESS=$UNAME_MACHINE-unknown-twizzler
;;
*:Redox:*:*)
GUESS=$UNAME_MACHINE-unknown-redox
;;
mips:OSF1:*.*)
GUESS=mips-dec-osf1
;;
alpha:OSF1:*:*)
# Reset EXIT trap before exiting to avoid spurious non-zero exit code.
trap '' 0
case $UNAME_RELEASE in
*4.0)
UNAME_RELEASE=`/usr/sbin/sizer -v | awk '{print $3}'`
;;
*5.*)
UNAME_RELEASE=`/usr/sbin/sizer -v | awk '{print $4}'`
;;
esac
# According to Compaq, /usr/sbin/psrinfo has been available on
# OSF/1 and Tru64 systems produced since 1995. I hope that
# covers most systems running today. This code pipes the CPU
# types through head -n 1, so we only detect the type of CPU 0.
ALPHA_CPU_TYPE=`/usr/sbin/psrinfo -v | sed -n -e 's/^ The alpha \(.*\) processor.*$/\1/p' | head -n 1`
case $ALPHA_CPU_TYPE in
"EV4 (21064)")
UNAME_MACHINE=alpha ;;
"EV4.5 (21064)")
UNAME_MACHINE=alpha ;;
"LCA4 (21066/21068)")
UNAME_MACHINE=alpha ;;
"EV5 (21164)")
UNAME_MACHINE=alphaev5 ;;
"EV5.6 (21164A)")
UNAME_MACHINE=alphaev56 ;;
"EV5.6 (21164PC)")
UNAME_MACHINE=alphapca56 ;;
"EV5.7 (21164PC)")
UNAME_MACHINE=alphapca57 ;;
"EV6 (21264)")
UNAME_MACHINE=alphaev6 ;;
"EV6.7 (21264A)")
UNAME_MACHINE=alphaev67 ;;
"EV6.8CB (21264C)")
UNAME_MACHINE=alphaev68 ;;
"EV6.8AL (21264B)")
UNAME_MACHINE=alphaev68 ;;
"EV6.8CX (21264D)")
UNAME_MACHINE=alphaev68 ;;
"EV6.9A (21264/EV69A)")
UNAME_MACHINE=alphaev69 ;;
"EV7 (21364)")
UNAME_MACHINE=alphaev7 ;;
"EV7.9 (21364A)")
UNAME_MACHINE=alphaev79 ;;
esac
# A Pn.n version is a patched version.
# A Vn.n version is a released version.
# A Tn.n version is a released field test version.
# A Xn.n version is an unreleased experimental baselevel.
# 1.2 uses "1.2" for uname -r.
OSF_REL=`echo "$UNAME_RELEASE" | sed -e 's/^[PVTX]//' | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz`
GUESS=$UNAME_MACHINE-dec-osf$OSF_REL
;;
Amiga*:UNIX_System_V:4.0:*)
GUESS=m68k-unknown-sysv4
;;
*:[Aa]miga[Oo][Ss]:*:*)
GUESS=$UNAME_MACHINE-unknown-amigaos
;;
*:[Mm]orph[Oo][Ss]:*:*)
GUESS=$UNAME_MACHINE-unknown-morphos
;;
*:OS/390:*:*)
GUESS=i370-ibm-openedition
;;
*:z/VM:*:*)
GUESS=s390-ibm-zvmoe
;;
*:OS400:*:*)
GUESS=powerpc-ibm-os400
;;
arm:RISC*:1.[012]*:*|arm:riscix:1.[012]*:*)
GUESS=arm-acorn-riscix$UNAME_RELEASE
;;
arm*:riscos:*:*|arm*:RISCOS:*:*)
GUESS=arm-unknown-riscos
;;
SR2?01:HI-UX/MPP:*:* | SR8000:HI-UX/MPP:*:*)
GUESS=hppa1.1-hitachi-hiuxmpp
;;
Pyramid*:OSx*:*:* | MIS*:OSx*:*:* | MIS*:SMP_DC-OSx*:*:*)
# akee@wpdis03.wpafb.af.mil (Earle F. Ake) contributed MIS and NILE.
case `(/bin/universe) 2>/dev/null` in
att) GUESS=pyramid-pyramid-sysv3 ;;
*) GUESS=pyramid-pyramid-bsd ;;
esac
;;
NILE*:*:*:dcosx)
GUESS=pyramid-pyramid-svr4
;;
DRS?6000:unix:4.0:6*)
GUESS=sparc-icl-nx6
;;
DRS?6000:UNIX_SV:4.2*:7* | DRS?6000:isis:4.2*:7*)
case `/usr/bin/uname -p` in
sparc) GUESS=sparc-icl-nx7 ;;
esac
;;
s390x:SunOS:*:*)
SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*//'`
GUESS=$UNAME_MACHINE-ibm-solaris2$SUN_REL
;;
sun4H:SunOS:5.*:*)
SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*//'`
GUESS=sparc-hal-solaris2$SUN_REL
;;
sun4*:SunOS:5.*:* | tadpole*:SunOS:5.*:*)
SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*//'`
GUESS=sparc-sun-solaris2$SUN_REL
;;
i86pc:AuroraUX:5.*:* | i86xen:AuroraUX:5.*:*)
GUESS=i386-pc-auroraux$UNAME_RELEASE
;;
i86pc:SunOS:5.*:* | i86xen:SunOS:5.*:*)
set_cc_for_build
SUN_ARCH=i386
# If there is a compiler, see if it is configured for 64-bit objects.
# Note that the Sun cc does not turn __LP64__ into 1 like gcc does.
# This test works for both compilers.
if test "$CC_FOR_BUILD" != no_compiler_found; then
if (echo '#ifdef __amd64'; echo IS_64BIT_ARCH; echo '#endif') | \
(CCOPTS="" $CC_FOR_BUILD -m64 -E - 2>/dev/null) | \
grep IS_64BIT_ARCH >/dev/null
then
SUN_ARCH=x86_64
fi
fi
SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*//'`
GUESS=$SUN_ARCH-pc-solaris2$SUN_REL
;;
sun4*:SunOS:6*:*)
# According to config.sub, this is the proper way to canonicalize
# SunOS6. Hard to guess exactly what SunOS6 will be like, but
# it's likely to be more like Solaris than SunOS4.
SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*//'`
GUESS=sparc-sun-solaris3$SUN_REL
;;
sun4*:SunOS:*:*)
case `/usr/bin/arch -k` in
Series*|S4*)
UNAME_RELEASE=`uname -v`
;;
esac
# Japanese Language versions have a version number like `4.1.3-JL'.
SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/-/_/'`
GUESS=sparc-sun-sunos$SUN_REL
;;
sun3*:SunOS:*:*)
GUESS=m68k-sun-sunos$UNAME_RELEASE
;;
sun*:*:4.2BSD:*)
UNAME_RELEASE=`(sed 1q /etc/motd | awk '{print substr($5,1,3)}') 2>/dev/null`
test "x$UNAME_RELEASE" = x && UNAME_RELEASE=3
case `/bin/arch` in
sun3)
GUESS=m68k-sun-sunos$UNAME_RELEASE
;;
sun4)
GUESS=sparc-sun-sunos$UNAME_RELEASE
;;
esac
;;
aushp:SunOS:*:*)
GUESS=sparc-auspex-sunos$UNAME_RELEASE
;;
# The situation for MiNT is a little confusing. The machine name
# can be virtually everything (everything which is not
# "atarist" or "atariste" at least should have a processor
# > m68000). The system name ranges from "MiNT" over "FreeMiNT"
# to the lowercase version "mint" (or "freemint"). Finally
# the system name "TOS" denotes a system which is actually not
# MiNT. But MiNT is downward compatible to TOS, so this should
# be no problem.
atarist[e]:*MiNT:*:* | atarist[e]:*mint:*:* | atarist[e]:*TOS:*:*)
GUESS=m68k-atari-mint$UNAME_RELEASE
;;
atari*:*MiNT:*:* | atari*:*mint:*:* | atarist[e]:*TOS:*:*)
GUESS=m68k-atari-mint$UNAME_RELEASE
;;
*falcon*:*MiNT:*:* | *falcon*:*mint:*:* | *falcon*:*TOS:*:*)
GUESS=m68k-atari-mint$UNAME_RELEASE
;;
milan*:*MiNT:*:* | milan*:*mint:*:* | *milan*:*TOS:*:*)
GUESS=m68k-milan-mint$UNAME_RELEASE
;;
hades*:*MiNT:*:* | hades*:*mint:*:* | *hades*:*TOS:*:*)
GUESS=m68k-hades-mint$UNAME_RELEASE
;;
*:*MiNT:*:* | *:*mint:*:* | *:*TOS:*:*)
GUESS=m68k-unknown-mint$UNAME_RELEASE
;;
m68k:machten:*:*)
GUESS=m68k-apple-machten$UNAME_RELEASE
;;
powerpc:machten:*:*)
GUESS=powerpc-apple-machten$UNAME_RELEASE
;;
RISC*:Mach:*:*)
GUESS=mips-dec-mach_bsd4.3
;;
RISC*:ULTRIX:*:*)
GUESS=mips-dec-ultrix$UNAME_RELEASE
;;
VAX*:ULTRIX*:*:*)
GUESS=vax-dec-ultrix$UNAME_RELEASE
;;
2020:CLIX:*:* | 2430:CLIX:*:*)
GUESS=clipper-intergraph-clix$UNAME_RELEASE
;;
mips:*:*:UMIPS | mips:*:*:RISCos)
set_cc_for_build
sed 's/^ //' << EOF > "$dummy.c"
#ifdef __cplusplus
#include /* for printf() prototype */
int main (int argc, char *argv[]) {
#else
int main (argc, argv) int argc; char *argv[]; {
#endif
#if defined (host_mips) && defined (MIPSEB)
#if defined (SYSTYPE_SYSV)
printf ("mips-mips-riscos%ssysv\\n", argv[1]); exit (0);
#endif
#if defined (SYSTYPE_SVR4)
printf ("mips-mips-riscos%ssvr4\\n", argv[1]); exit (0);
#endif
#if defined (SYSTYPE_BSD43) || defined(SYSTYPE_BSD)
printf ("mips-mips-riscos%sbsd\\n", argv[1]); exit (0);
#endif
#endif
exit (-1);
}
EOF
$CC_FOR_BUILD -o "$dummy" "$dummy.c" &&
dummyarg=`echo "$UNAME_RELEASE" | sed -n 's/\([0-9]*\).*/\1/p'` &&
SYSTEM_NAME=`"$dummy" "$dummyarg"` &&
{ echo "$SYSTEM_NAME"; exit; }
GUESS=mips-mips-riscos$UNAME_RELEASE
;;
Motorola:PowerMAX_OS:*:*)
GUESS=powerpc-motorola-powermax
;;
Motorola:*:4.3:PL8-*)
GUESS=powerpc-harris-powermax
;;
Night_Hawk:*:*:PowerMAX_OS | Synergy:PowerMAX_OS:*:*)
GUESS=powerpc-harris-powermax
;;
Night_Hawk:Power_UNIX:*:*)
GUESS=powerpc-harris-powerunix
;;
m88k:CX/UX:7*:*)
GUESS=m88k-harris-cxux7
;;
m88k:*:4*:R4*)
GUESS=m88k-motorola-sysv4
;;
m88k:*:3*:R3*)
GUESS=m88k-motorola-sysv3
;;
AViiON:dgux:*:*)
# DG/UX returns AViiON for all architectures
UNAME_PROCESSOR=`/usr/bin/uname -p`
if test "$UNAME_PROCESSOR" = mc88100 || test "$UNAME_PROCESSOR" = mc88110
then
if test "$TARGET_BINARY_INTERFACE"x = m88kdguxelfx || \
test "$TARGET_BINARY_INTERFACE"x = x
then
GUESS=m88k-dg-dgux$UNAME_RELEASE
else
GUESS=m88k-dg-dguxbcs$UNAME_RELEASE
fi
else
GUESS=i586-dg-dgux$UNAME_RELEASE
fi
;;
M88*:DolphinOS:*:*) # DolphinOS (SVR3)
GUESS=m88k-dolphin-sysv3
;;
M88*:*:R3*:*)
# Delta 88k system running SVR3
GUESS=m88k-motorola-sysv3
;;
XD88*:*:*:*) # Tektronix XD88 system running UTekV (SVR3)
GUESS=m88k-tektronix-sysv3
;;
Tek43[0-9][0-9]:UTek:*:*) # Tektronix 4300 system running UTek (BSD)
GUESS=m68k-tektronix-bsd
;;
*:IRIX*:*:*)
IRIX_REL=`echo "$UNAME_RELEASE" | sed -e 's/-/_/g'`
GUESS=mips-sgi-irix$IRIX_REL
;;
????????:AIX?:[12].1:2) # AIX 2.2.1 or AIX 2.1.1 is RT/PC AIX.
GUESS=romp-ibm-aix # uname -m gives an 8 hex-code CPU id
;; # Note that: echo "'`uname -s`'" gives 'AIX '
i*86:AIX:*:*)
GUESS=i386-ibm-aix
;;
ia64:AIX:*:*)
if test -x /usr/bin/oslevel ; then
IBM_REV=`/usr/bin/oslevel`
else
IBM_REV=$UNAME_VERSION.$UNAME_RELEASE
fi
GUESS=$UNAME_MACHINE-ibm-aix$IBM_REV
;;
*:AIX:2:3)
if grep bos325 /usr/include/stdio.h >/dev/null 2>&1; then
set_cc_for_build
sed 's/^ //' << EOF > "$dummy.c"
#include
main()
{
if (!__power_pc())
exit(1);
puts("powerpc-ibm-aix3.2.5");
exit(0);
}
EOF
if $CC_FOR_BUILD -o "$dummy" "$dummy.c" && SYSTEM_NAME=`"$dummy"`
then
GUESS=$SYSTEM_NAME
else
GUESS=rs6000-ibm-aix3.2.5
fi
elif grep bos324 /usr/include/stdio.h >/dev/null 2>&1; then
GUESS=rs6000-ibm-aix3.2.4
else
GUESS=rs6000-ibm-aix3.2
fi
;;
*:AIX:*:[4567])
IBM_CPU_ID=`/usr/sbin/lsdev -C -c processor -S available | sed 1q | awk '{ print $1 }'`
if /usr/sbin/lsattr -El "$IBM_CPU_ID" | grep ' POWER' >/dev/null 2>&1; then
IBM_ARCH=rs6000
else
IBM_ARCH=powerpc
fi
if test -x /usr/bin/lslpp ; then
IBM_REV=`/usr/bin/lslpp -Lqc bos.rte.libc | \
awk -F: '{ print $3 }' | sed s/[0-9]*$/0/`
else
IBM_REV=$UNAME_VERSION.$UNAME_RELEASE
fi
GUESS=$IBM_ARCH-ibm-aix$IBM_REV
;;
*:AIX:*:*)
GUESS=rs6000-ibm-aix
;;
ibmrt:4.4BSD:*|romp-ibm:4.4BSD:*)
GUESS=romp-ibm-bsd4.4
;;
ibmrt:*BSD:*|romp-ibm:BSD:*) # covers RT/PC BSD and
GUESS=romp-ibm-bsd$UNAME_RELEASE # 4.3 with uname added to
;; # report: romp-ibm BSD 4.3
*:BOSX:*:*)
GUESS=rs6000-bull-bosx
;;
DPX/2?00:B.O.S.:*:*)
GUESS=m68k-bull-sysv3
;;
9000/[34]??:4.3bsd:1.*:*)
GUESS=m68k-hp-bsd
;;
hp300:4.4BSD:*:* | 9000/[34]??:4.3bsd:2.*:*)
GUESS=m68k-hp-bsd4.4
;;
9000/[34678]??:HP-UX:*:*)
HPUX_REV=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*.[0B]*//'`
case $UNAME_MACHINE in
9000/31?) HP_ARCH=m68000 ;;
9000/[34]??) HP_ARCH=m68k ;;
9000/[678][0-9][0-9])
if test -x /usr/bin/getconf; then
sc_cpu_version=`/usr/bin/getconf SC_CPU_VERSION 2>/dev/null`
sc_kernel_bits=`/usr/bin/getconf SC_KERNEL_BITS 2>/dev/null`
case $sc_cpu_version in
523) HP_ARCH=hppa1.0 ;; # CPU_PA_RISC1_0
528) HP_ARCH=hppa1.1 ;; # CPU_PA_RISC1_1
532) # CPU_PA_RISC2_0
case $sc_kernel_bits in
32) HP_ARCH=hppa2.0n ;;
64) HP_ARCH=hppa2.0w ;;
'') HP_ARCH=hppa2.0 ;; # HP-UX 10.20
esac ;;
esac
fi
if test "$HP_ARCH" = ""; then
set_cc_for_build
sed 's/^ //' << EOF > "$dummy.c"
#define _HPUX_SOURCE
#include
#include
int main ()
{
#if defined(_SC_KERNEL_BITS)
long bits = sysconf(_SC_KERNEL_BITS);
#endif
long cpu = sysconf (_SC_CPU_VERSION);
switch (cpu)
{
case CPU_PA_RISC1_0: puts ("hppa1.0"); break;
case CPU_PA_RISC1_1: puts ("hppa1.1"); break;
case CPU_PA_RISC2_0:
#if defined(_SC_KERNEL_BITS)
switch (bits)
{
case 64: puts ("hppa2.0w"); break;
case 32: puts ("hppa2.0n"); break;
default: puts ("hppa2.0"); break;
} break;
#else /* !defined(_SC_KERNEL_BITS) */
puts ("hppa2.0"); break;
#endif
default: puts ("hppa1.0"); break;
}
exit (0);
}
EOF
(CCOPTS="" $CC_FOR_BUILD -o "$dummy" "$dummy.c" 2>/dev/null) && HP_ARCH=`"$dummy"`
test -z "$HP_ARCH" && HP_ARCH=hppa
fi ;;
esac
if test "$HP_ARCH" = hppa2.0w
then
set_cc_for_build
# hppa2.0w-hp-hpux* has a 64-bit kernel and a compiler generating
# 32-bit code. hppa64-hp-hpux* has the same kernel and a compiler
# generating 64-bit code. GNU and HP use different nomenclature:
#
# $ CC_FOR_BUILD=cc ./config.guess
# => hppa2.0w-hp-hpux11.23
# $ CC_FOR_BUILD="cc +DA2.0w" ./config.guess
# => hppa64-hp-hpux11.23
if echo __LP64__ | (CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) |
grep -q __LP64__
then
HP_ARCH=hppa2.0w
else
HP_ARCH=hppa64
fi
fi
GUESS=$HP_ARCH-hp-hpux$HPUX_REV
;;
ia64:HP-UX:*:*)
HPUX_REV=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*.[0B]*//'`
GUESS=ia64-hp-hpux$HPUX_REV
;;
3050*:HI-UX:*:*)
set_cc_for_build
sed 's/^ //' << EOF > "$dummy.c"
#include
int
main ()
{
long cpu = sysconf (_SC_CPU_VERSION);
/* The order matters, because CPU_IS_HP_MC68K erroneously returns
true for CPU_PA_RISC1_0. CPU_IS_PA_RISC returns correct
results, however. */
if (CPU_IS_PA_RISC (cpu))
{
switch (cpu)
{
case CPU_PA_RISC1_0: puts ("hppa1.0-hitachi-hiuxwe2"); break;
case CPU_PA_RISC1_1: puts ("hppa1.1-hitachi-hiuxwe2"); break;
case CPU_PA_RISC2_0: puts ("hppa2.0-hitachi-hiuxwe2"); break;
default: puts ("hppa-hitachi-hiuxwe2"); break;
}
}
else if (CPU_IS_HP_MC68K (cpu))
puts ("m68k-hitachi-hiuxwe2");
else puts ("unknown-hitachi-hiuxwe2");
exit (0);
}
EOF
$CC_FOR_BUILD -o "$dummy" "$dummy.c" && SYSTEM_NAME=`"$dummy"` &&
{ echo "$SYSTEM_NAME"; exit; }
GUESS=unknown-hitachi-hiuxwe2
;;
9000/7??:4.3bsd:*:* | 9000/8?[79]:4.3bsd:*:*)
GUESS=hppa1.1-hp-bsd
;;
9000/8??:4.3bsd:*:*)
GUESS=hppa1.0-hp-bsd
;;
*9??*:MPE/iX:*:* | *3000*:MPE/iX:*:*)
GUESS=hppa1.0-hp-mpeix
;;
hp7??:OSF1:*:* | hp8?[79]:OSF1:*:*)
GUESS=hppa1.1-hp-osf
;;
hp8??:OSF1:*:*)
GUESS=hppa1.0-hp-osf
;;
i*86:OSF1:*:*)
if test -x /usr/sbin/sysversion ; then
GUESS=$UNAME_MACHINE-unknown-osf1mk
else
GUESS=$UNAME_MACHINE-unknown-osf1
fi
;;
parisc*:Lites*:*:*)
GUESS=hppa1.1-hp-lites
;;
C1*:ConvexOS:*:* | convex:ConvexOS:C1*:*)
GUESS=c1-convex-bsd
;;
C2*:ConvexOS:*:* | convex:ConvexOS:C2*:*)
if getsysinfo -f scalar_acc
then echo c32-convex-bsd
else echo c2-convex-bsd
fi
exit ;;
C34*:ConvexOS:*:* | convex:ConvexOS:C34*:*)
GUESS=c34-convex-bsd
;;
C38*:ConvexOS:*:* | convex:ConvexOS:C38*:*)
GUESS=c38-convex-bsd
;;
C4*:ConvexOS:*:* | convex:ConvexOS:C4*:*)
GUESS=c4-convex-bsd
;;
CRAY*Y-MP:*:*:*)
CRAY_REL=`echo "$UNAME_RELEASE" | sed -e 's/\.[^.]*$/.X/'`
GUESS=ymp-cray-unicos$CRAY_REL
;;
CRAY*[A-Z]90:*:*:*)
echo "$UNAME_MACHINE"-cray-unicos"$UNAME_RELEASE" \
| sed -e 's/CRAY.*\([A-Z]90\)/\1/' \
-e y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/ \
-e 's/\.[^.]*$/.X/'
exit ;;
CRAY*TS:*:*:*)
CRAY_REL=`echo "$UNAME_RELEASE" | sed -e 's/\.[^.]*$/.X/'`
GUESS=t90-cray-unicos$CRAY_REL
;;
CRAY*T3E:*:*:*)
CRAY_REL=`echo "$UNAME_RELEASE" | sed -e 's/\.[^.]*$/.X/'`
GUESS=alphaev5-cray-unicosmk$CRAY_REL
;;
CRAY*SV1:*:*:*)
CRAY_REL=`echo "$UNAME_RELEASE" | sed -e 's/\.[^.]*$/.X/'`
GUESS=sv1-cray-unicos$CRAY_REL
;;
*:UNICOS/mp:*:*)
CRAY_REL=`echo "$UNAME_RELEASE" | sed -e 's/\.[^.]*$/.X/'`
GUESS=craynv-cray-unicosmp$CRAY_REL
;;
F30[01]:UNIX_System_V:*:* | F700:UNIX_System_V:*:*)
FUJITSU_PROC=`uname -m | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz`
FUJITSU_SYS=`uname -p | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz | sed -e 's/\///'`
FUJITSU_REL=`echo "$UNAME_RELEASE" | sed -e 's/ /_/'`
GUESS=${FUJITSU_PROC}-fujitsu-${FUJITSU_SYS}${FUJITSU_REL}
;;
5000:UNIX_System_V:4.*:*)
FUJITSU_SYS=`uname -p | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz | sed -e 's/\///'`
FUJITSU_REL=`echo "$UNAME_RELEASE" | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz | sed -e 's/ /_/'`
GUESS=sparc-fujitsu-${FUJITSU_SYS}${FUJITSU_REL}
;;
i*86:BSD/386:*:* | i*86:BSD/OS:*:* | *:Ascend\ Embedded/OS:*:*)
GUESS=$UNAME_MACHINE-pc-bsdi$UNAME_RELEASE
;;
sparc*:BSD/OS:*:*)
GUESS=sparc-unknown-bsdi$UNAME_RELEASE
;;
*:BSD/OS:*:*)
GUESS=$UNAME_MACHINE-unknown-bsdi$UNAME_RELEASE
;;
arm:FreeBSD:*:*)
UNAME_PROCESSOR=`uname -p`
set_cc_for_build
if echo __ARM_PCS_VFP | $CC_FOR_BUILD -E - 2>/dev/null \
| grep -q __ARM_PCS_VFP
then
FREEBSD_REL=`echo "$UNAME_RELEASE" | sed -e 's/[-(].*//'`
GUESS=$UNAME_PROCESSOR-unknown-freebsd$FREEBSD_REL-gnueabi
else
FREEBSD_REL=`echo "$UNAME_RELEASE" | sed -e 's/[-(].*//'`
GUESS=$UNAME_PROCESSOR-unknown-freebsd$FREEBSD_REL-gnueabihf
fi
;;
*:FreeBSD:*:*)
UNAME_PROCESSOR=`/usr/bin/uname -p`
case $UNAME_PROCESSOR in
amd64)
UNAME_PROCESSOR=x86_64 ;;
i386)
UNAME_PROCESSOR=i586 ;;
esac
FREEBSD_REL=`echo "$UNAME_RELEASE" | sed -e 's/[-(].*//'`
GUESS=$UNAME_PROCESSOR-unknown-freebsd$FREEBSD_REL
;;
i*:CYGWIN*:*)
GUESS=$UNAME_MACHINE-pc-cygwin
;;
*:MINGW64*:*)
GUESS=$UNAME_MACHINE-pc-mingw64
;;
*:MINGW*:*)
GUESS=$UNAME_MACHINE-pc-mingw32
;;
*:MSYS*:*)
GUESS=$UNAME_MACHINE-pc-msys
;;
i*:PW*:*)
GUESS=$UNAME_MACHINE-pc-pw32
;;
*:SerenityOS:*:*)
GUESS=$UNAME_MACHINE-pc-serenity
;;
*:Interix*:*)
case $UNAME_MACHINE in
x86)
GUESS=i586-pc-interix$UNAME_RELEASE
;;
authenticamd | genuineintel | EM64T)
GUESS=x86_64-unknown-interix$UNAME_RELEASE
;;
IA64)
GUESS=ia64-unknown-interix$UNAME_RELEASE
;;
esac ;;
i*:UWIN*:*)
GUESS=$UNAME_MACHINE-pc-uwin
;;
amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
GUESS=x86_64-pc-cygwin
;;
prep*:SunOS:5.*:*)
SUN_REL=`echo "$UNAME_RELEASE" | sed -e 's/[^.]*//'`
GUESS=powerpcle-unknown-solaris2$SUN_REL
;;
*:GNU:*:*)
# the GNU system
GNU_ARCH=`echo "$UNAME_MACHINE" | sed -e 's,[-/].*$,,'`
GNU_REL=`echo "$UNAME_RELEASE" | sed -e 's,/.*$,,'`
GUESS=$GNU_ARCH-unknown-$LIBC$GNU_REL
;;
*:GNU/*:*:*)
# other systems with GNU libc and userland
GNU_SYS=`echo "$UNAME_SYSTEM" | sed 's,^[^/]*/,,' | tr "[:upper:]" "[:lower:]"`
GNU_REL=`echo "$UNAME_RELEASE" | sed -e 's/[-(].*//'`
GUESS=$UNAME_MACHINE-unknown-$GNU_SYS$GNU_REL-$LIBC
;;
*:Minix:*:*)
GUESS=$UNAME_MACHINE-unknown-minix
;;
aarch64:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
aarch64_be:Linux:*:*)
UNAME_MACHINE=aarch64_be
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
alpha:Linux:*:*)
case `sed -n '/^cpu model/s/^.*: \(.*\)/\1/p' /proc/cpuinfo 2>/dev/null` in
EV5) UNAME_MACHINE=alphaev5 ;;
EV56) UNAME_MACHINE=alphaev56 ;;
PCA56) UNAME_MACHINE=alphapca56 ;;
PCA57) UNAME_MACHINE=alphapca56 ;;
EV6) UNAME_MACHINE=alphaev6 ;;
EV67) UNAME_MACHINE=alphaev67 ;;
EV68*) UNAME_MACHINE=alphaev68 ;;
esac
objdump --private-headers /bin/sh | grep -q ld.so.1
if test "$?" = 0 ; then LIBC=gnulibc1 ; fi
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
arc:Linux:*:* | arceb:Linux:*:* | arc32:Linux:*:* | arc64:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
arm*:Linux:*:*)
set_cc_for_build
if echo __ARM_EABI__ | $CC_FOR_BUILD -E - 2>/dev/null \
| grep -q __ARM_EABI__
then
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
else
if echo __ARM_PCS_VFP | $CC_FOR_BUILD -E - 2>/dev/null \
| grep -q __ARM_PCS_VFP
then
GUESS=$UNAME_MACHINE-unknown-linux-${LIBC}eabi
else
GUESS=$UNAME_MACHINE-unknown-linux-${LIBC}eabihf
fi
fi
;;
avr32*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
cris:Linux:*:*)
GUESS=$UNAME_MACHINE-axis-linux-$LIBC
;;
crisv32:Linux:*:*)
GUESS=$UNAME_MACHINE-axis-linux-$LIBC
;;
e2k:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
frv:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
hexagon:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
i*86:Linux:*:*)
GUESS=$UNAME_MACHINE-pc-linux-$LIBC
;;
ia64:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
k1om:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
loongarch32:Linux:*:* | loongarch64:Linux:*:* | loongarchx32:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
m32r*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
m68*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
mips:Linux:*:* | mips64:Linux:*:*)
set_cc_for_build
IS_GLIBC=0
test x"${LIBC}" = xgnu && IS_GLIBC=1
sed 's/^ //' << EOF > "$dummy.c"
#undef CPU
#undef mips
#undef mipsel
#undef mips64
#undef mips64el
#if ${IS_GLIBC} && defined(_ABI64)
LIBCABI=gnuabi64
#else
#if ${IS_GLIBC} && defined(_ABIN32)
LIBCABI=gnuabin32
#else
LIBCABI=${LIBC}
#endif
#endif
#if ${IS_GLIBC} && defined(__mips64) && defined(__mips_isa_rev) && __mips_isa_rev>=6
CPU=mipsisa64r6
#else
#if ${IS_GLIBC} && !defined(__mips64) && defined(__mips_isa_rev) && __mips_isa_rev>=6
CPU=mipsisa32r6
#else
#if defined(__mips64)
CPU=mips64
#else
CPU=mips
#endif
#endif
#endif
#if defined(__MIPSEL__) || defined(__MIPSEL) || defined(_MIPSEL) || defined(MIPSEL)
MIPS_ENDIAN=el
#else
#if defined(__MIPSEB__) || defined(__MIPSEB) || defined(_MIPSEB) || defined(MIPSEB)
MIPS_ENDIAN=
#else
MIPS_ENDIAN=
#endif
#endif
EOF
cc_set_vars=`$CC_FOR_BUILD -E "$dummy.c" 2>/dev/null | grep '^CPU\|^MIPS_ENDIAN\|^LIBCABI'`
eval "$cc_set_vars"
test "x$CPU" != x && { echo "$CPU${MIPS_ENDIAN}-unknown-linux-$LIBCABI"; exit; }
;;
mips64el:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
openrisc*:Linux:*:*)
GUESS=or1k-unknown-linux-$LIBC
;;
or32:Linux:*:* | or1k*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
padre:Linux:*:*)
GUESS=sparc-unknown-linux-$LIBC
;;
parisc64:Linux:*:* | hppa64:Linux:*:*)
GUESS=hppa64-unknown-linux-$LIBC
;;
parisc:Linux:*:* | hppa:Linux:*:*)
# Look for CPU level
case `grep '^cpu[^a-z]*:' /proc/cpuinfo 2>/dev/null | cut -d' ' -f2` in
PA7*) GUESS=hppa1.1-unknown-linux-$LIBC ;;
PA8*) GUESS=hppa2.0-unknown-linux-$LIBC ;;
*) GUESS=hppa-unknown-linux-$LIBC ;;
esac
;;
ppc64:Linux:*:*)
GUESS=powerpc64-unknown-linux-$LIBC
;;
ppc:Linux:*:*)
GUESS=powerpc-unknown-linux-$LIBC
;;
ppc64le:Linux:*:*)
GUESS=powerpc64le-unknown-linux-$LIBC
;;
ppcle:Linux:*:*)
GUESS=powerpcle-unknown-linux-$LIBC
;;
riscv32:Linux:*:* | riscv32be:Linux:*:* | riscv64:Linux:*:* | riscv64be:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
s390:Linux:*:* | s390x:Linux:*:*)
GUESS=$UNAME_MACHINE-ibm-linux-$LIBC
;;
sh64*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
sh*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
sparc:Linux:*:* | sparc64:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
tile*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
vax:Linux:*:*)
GUESS=$UNAME_MACHINE-dec-linux-$LIBC
;;
x86_64:Linux:*:*)
set_cc_for_build
LIBCABI=$LIBC
if test "$CC_FOR_BUILD" != no_compiler_found; then
if (echo '#ifdef __ILP32__'; echo IS_X32; echo '#endif') | \
(CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) | \
grep IS_X32 >/dev/null
then
LIBCABI=${LIBC}x32
fi
fi
GUESS=$UNAME_MACHINE-pc-linux-$LIBCABI
;;
xtensa*:Linux:*:*)
GUESS=$UNAME_MACHINE-unknown-linux-$LIBC
;;
i*86:DYNIX/ptx:4*:*)
# ptx 4.0 does uname -s correctly, with DYNIX/ptx in there.
# earlier versions are messed up and put the nodename in both
# sysname and nodename.
GUESS=i386-sequent-sysv4
;;
i*86:UNIX_SV:4.2MP:2.*)
# Unixware is an offshoot of SVR4, but it has its own version
# number series starting with 2...
# I am not positive that other SVR4 systems won't match this,
# I just have to hope. -- rms.
# Use sysv4.2uw... so that sysv4* matches it.
GUESS=$UNAME_MACHINE-pc-sysv4.2uw$UNAME_VERSION
;;
i*86:OS/2:*:*)
# If we were able to find `uname', then EMX Unix compatibility
# is probably installed.
GUESS=$UNAME_MACHINE-pc-os2-emx
;;
i*86:XTS-300:*:STOP)
GUESS=$UNAME_MACHINE-unknown-stop
;;
i*86:atheos:*:*)
GUESS=$UNAME_MACHINE-unknown-atheos
;;
i*86:syllable:*:*)
GUESS=$UNAME_MACHINE-pc-syllable
;;
i*86:LynxOS:2.*:* | i*86:LynxOS:3.[01]*:* | i*86:LynxOS:4.[02]*:*)
GUESS=i386-unknown-lynxos$UNAME_RELEASE
;;
i*86:*DOS:*:*)
GUESS=$UNAME_MACHINE-pc-msdosdjgpp
;;
i*86:*:4.*:*)
UNAME_REL=`echo "$UNAME_RELEASE" | sed 's/\/MP$//'`
if grep Novell /usr/include/link.h >/dev/null 2>/dev/null; then
GUESS=$UNAME_MACHINE-univel-sysv$UNAME_REL
else
GUESS=$UNAME_MACHINE-pc-sysv$UNAME_REL
fi
;;
i*86:*:5:[678]*)
# UnixWare 7.x, OpenUNIX and OpenServer 6.
case `/bin/uname -X | grep "^Machine"` in
*486*) UNAME_MACHINE=i486 ;;
*Pentium) UNAME_MACHINE=i586 ;;
*Pent*|*Celeron) UNAME_MACHINE=i686 ;;
esac
GUESS=$UNAME_MACHINE-unknown-sysv${UNAME_RELEASE}${UNAME_SYSTEM}${UNAME_VERSION}
;;
i*86:*:3.2:*)
if test -f /usr/options/cb.name; then
UNAME_REL=`sed -n 's/.*Version //p' /dev/null >/dev/null ; then
UNAME_REL=`(/bin/uname -X|grep Release|sed -e 's/.*= //')`
(/bin/uname -X|grep i80486 >/dev/null) && UNAME_MACHINE=i486
(/bin/uname -X|grep '^Machine.*Pentium' >/dev/null) \
&& UNAME_MACHINE=i586
(/bin/uname -X|grep '^Machine.*Pent *II' >/dev/null) \
&& UNAME_MACHINE=i686
(/bin/uname -X|grep '^Machine.*Pentium Pro' >/dev/null) \
&& UNAME_MACHINE=i686
GUESS=$UNAME_MACHINE-pc-sco$UNAME_REL
else
GUESS=$UNAME_MACHINE-pc-sysv32
fi
;;
pc:*:*:*)
# Left here for compatibility:
# uname -m prints for DJGPP always 'pc', but it prints nothing about
# the processor, so we play safe by assuming i586.
# Note: whatever this is, it MUST be the same as what config.sub
# prints for the "djgpp" host, or else GDB configure will decide that
# this is a cross-build.
GUESS=i586-pc-msdosdjgpp
;;
Intel:Mach:3*:*)
GUESS=i386-pc-mach3
;;
paragon:*:*:*)
GUESS=i860-intel-osf1
;;
i860:*:4.*:*) # i860-SVR4
if grep Stardent /usr/include/sys/uadmin.h >/dev/null 2>&1 ; then
GUESS=i860-stardent-sysv$UNAME_RELEASE # Stardent Vistra i860-SVR4
else # Add other i860-SVR4 vendors below as they are discovered.
GUESS=i860-unknown-sysv$UNAME_RELEASE # Unknown i860-SVR4
fi
;;
mini*:CTIX:SYS*5:*)
# "miniframe"
GUESS=m68010-convergent-sysv
;;
mc68k:UNIX:SYSTEM5:3.51m)
GUESS=m68k-convergent-sysv
;;
M680?0:D-NIX:5.3:*)
GUESS=m68k-diab-dnix
;;
M68*:*:R3V[5678]*:*)
test -r /sysV68 && { echo 'm68k-motorola-sysv'; exit; } ;;
3[345]??:*:4.0:3.0 | 3[34]??A:*:4.0:3.0 | 3[34]??,*:*:4.0:3.0 | 3[34]??/*:*:4.0:3.0 | 4400:*:4.0:3.0 | 4850:*:4.0:3.0 | SKA40:*:4.0:3.0 | SDS2:*:4.0:3.0 | SHG2:*:4.0:3.0 | S7501*:*:4.0:3.0)
OS_REL=''
test -r /etc/.relid \
&& OS_REL=.`sed -n 's/[^ ]* [^ ]* \([0-9][0-9]\).*/\1/p' < /etc/.relid`
/bin/uname -p 2>/dev/null | grep 86 >/dev/null \
&& { echo i486-ncr-sysv4.3"$OS_REL"; exit; }
/bin/uname -p 2>/dev/null | /bin/grep entium >/dev/null \
&& { echo i586-ncr-sysv4.3"$OS_REL"; exit; } ;;
3[34]??:*:4.0:* | 3[34]??,*:*:4.0:*)
/bin/uname -p 2>/dev/null | grep 86 >/dev/null \
&& { echo i486-ncr-sysv4; exit; } ;;
NCR*:*:4.2:* | MPRAS*:*:4.2:*)
OS_REL='.3'
test -r /etc/.relid \
&& OS_REL=.`sed -n 's/[^ ]* [^ ]* \([0-9][0-9]\).*/\1/p' < /etc/.relid`
/bin/uname -p 2>/dev/null | grep 86 >/dev/null \
&& { echo i486-ncr-sysv4.3"$OS_REL"; exit; }
/bin/uname -p 2>/dev/null | /bin/grep entium >/dev/null \
&& { echo i586-ncr-sysv4.3"$OS_REL"; exit; }
/bin/uname -p 2>/dev/null | /bin/grep pteron >/dev/null \
&& { echo i586-ncr-sysv4.3"$OS_REL"; exit; } ;;
m68*:LynxOS:2.*:* | m68*:LynxOS:3.0*:*)
GUESS=m68k-unknown-lynxos$UNAME_RELEASE
;;
mc68030:UNIX_System_V:4.*:*)
GUESS=m68k-atari-sysv4
;;
TSUNAMI:LynxOS:2.*:*)
GUESS=sparc-unknown-lynxos$UNAME_RELEASE
;;
rs6000:LynxOS:2.*:*)
GUESS=rs6000-unknown-lynxos$UNAME_RELEASE
;;
PowerPC:LynxOS:2.*:* | PowerPC:LynxOS:3.[01]*:* | PowerPC:LynxOS:4.[02]*:*)
GUESS=powerpc-unknown-lynxos$UNAME_RELEASE
;;
SM[BE]S:UNIX_SV:*:*)
GUESS=mips-dde-sysv$UNAME_RELEASE
;;
RM*:ReliantUNIX-*:*:*)
GUESS=mips-sni-sysv4
;;
RM*:SINIX-*:*:*)
GUESS=mips-sni-sysv4
;;
*:SINIX-*:*:*)
if uname -p 2>/dev/null >/dev/null ; then
UNAME_MACHINE=`(uname -p) 2>/dev/null`
GUESS=$UNAME_MACHINE-sni-sysv4
else
GUESS=ns32k-sni-sysv
fi
;;
PENTIUM:*:4.0*:*) # Unisys `ClearPath HMP IX 4000' SVR4/MP effort
# says
GUESS=i586-unisys-sysv4
;;
*:UNIX_System_V:4*:FTX*)
# From Gerald Hewes .
# How about differentiating between stratus architectures? -djm
GUESS=hppa1.1-stratus-sysv4
;;
*:*:*:FTX*)
# From seanf@swdc.stratus.com.
GUESS=i860-stratus-sysv4
;;
i*86:VOS:*:*)
# From Paul.Green@stratus.com.
GUESS=$UNAME_MACHINE-stratus-vos
;;
*:VOS:*:*)
# From Paul.Green@stratus.com.
GUESS=hppa1.1-stratus-vos
;;
mc68*:A/UX:*:*)
GUESS=m68k-apple-aux$UNAME_RELEASE
;;
news*:NEWS-OS:6*:*)
GUESS=mips-sony-newsos6
;;
R[34]000:*System_V*:*:* | R4000:UNIX_SYSV:*:* | R*000:UNIX_SV:*:*)
if test -d /usr/nec; then
GUESS=mips-nec-sysv$UNAME_RELEASE
else
GUESS=mips-unknown-sysv$UNAME_RELEASE
fi
;;
BeBox:BeOS:*:*) # BeOS running on hardware made by Be, PPC only.
GUESS=powerpc-be-beos
;;
BeMac:BeOS:*:*) # BeOS running on Mac or Mac clone, PPC only.
GUESS=powerpc-apple-beos
;;
BePC:BeOS:*:*) # BeOS running on Intel PC compatible.
GUESS=i586-pc-beos
;;
BePC:Haiku:*:*) # Haiku running on Intel PC compatible.
GUESS=i586-pc-haiku
;;
x86_64:Haiku:*:*)
GUESS=x86_64-unknown-haiku
;;
SX-4:SUPER-UX:*:*)
GUESS=sx4-nec-superux$UNAME_RELEASE
;;
SX-5:SUPER-UX:*:*)
GUESS=sx5-nec-superux$UNAME_RELEASE
;;
SX-6:SUPER-UX:*:*)
GUESS=sx6-nec-superux$UNAME_RELEASE
;;
SX-7:SUPER-UX:*:*)
GUESS=sx7-nec-superux$UNAME_RELEASE
;;
SX-8:SUPER-UX:*:*)
GUESS=sx8-nec-superux$UNAME_RELEASE
;;
SX-8R:SUPER-UX:*:*)
GUESS=sx8r-nec-superux$UNAME_RELEASE
;;
SX-ACE:SUPER-UX:*:*)
GUESS=sxace-nec-superux$UNAME_RELEASE
;;
Power*:Rhapsody:*:*)
GUESS=powerpc-apple-rhapsody$UNAME_RELEASE
;;
*:Rhapsody:*:*)
GUESS=$UNAME_MACHINE-apple-rhapsody$UNAME_RELEASE
;;
arm64:Darwin:*:*)
GUESS=aarch64-apple-darwin$UNAME_RELEASE
;;
*:Darwin:*:*)
UNAME_PROCESSOR=`uname -p`
case $UNAME_PROCESSOR in
unknown) UNAME_PROCESSOR=powerpc ;;
esac
if command -v xcode-select > /dev/null 2> /dev/null && \
! xcode-select --print-path > /dev/null 2> /dev/null ; then
# Avoid executing cc if there is no toolchain installed as
# cc will be a stub that puts up a graphical alert
# prompting the user to install developer tools.
CC_FOR_BUILD=no_compiler_found
else
set_cc_for_build
fi
if test "$CC_FOR_BUILD" != no_compiler_found; then
if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \
(CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) | \
grep IS_64BIT_ARCH >/dev/null
then
case $UNAME_PROCESSOR in
i386) UNAME_PROCESSOR=x86_64 ;;
powerpc) UNAME_PROCESSOR=powerpc64 ;;
esac
fi
# On 10.4-10.6 one might compile for PowerPC via gcc -arch ppc
if (echo '#ifdef __POWERPC__'; echo IS_PPC; echo '#endif') | \
(CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) | \
grep IS_PPC >/dev/null
then
UNAME_PROCESSOR=powerpc
fi
elif test "$UNAME_PROCESSOR" = i386 ; then
# uname -m returns i386 or x86_64
UNAME_PROCESSOR=$UNAME_MACHINE
fi
GUESS=$UNAME_PROCESSOR-apple-darwin$UNAME_RELEASE
;;
*:procnto*:*:* | *:QNX:[0123456789]*:*)
UNAME_PROCESSOR=`uname -p`
if test "$UNAME_PROCESSOR" = x86; then
UNAME_PROCESSOR=i386
UNAME_MACHINE=pc
fi
GUESS=$UNAME_PROCESSOR-$UNAME_MACHINE-nto-qnx$UNAME_RELEASE
;;
*:QNX:*:4*)
GUESS=i386-pc-qnx
;;
NEO-*:NONSTOP_KERNEL:*:*)
GUESS=neo-tandem-nsk$UNAME_RELEASE
;;
NSE-*:NONSTOP_KERNEL:*:*)
GUESS=nse-tandem-nsk$UNAME_RELEASE
;;
NSR-*:NONSTOP_KERNEL:*:*)
GUESS=nsr-tandem-nsk$UNAME_RELEASE
;;
NSV-*:NONSTOP_KERNEL:*:*)
GUESS=nsv-tandem-nsk$UNAME_RELEASE
;;
NSX-*:NONSTOP_KERNEL:*:*)
GUESS=nsx-tandem-nsk$UNAME_RELEASE
;;
*:NonStop-UX:*:*)
GUESS=mips-compaq-nonstopux
;;
BS2000:POSIX*:*:*)
GUESS=bs2000-siemens-sysv
;;
DS/*:UNIX_System_V:*:*)
GUESS=$UNAME_MACHINE-$UNAME_SYSTEM-$UNAME_RELEASE
;;
*:Plan9:*:*)
# "uname -m" is not consistent, so use $cputype instead. 386
# is converted to i386 for consistency with other x86
# operating systems.
if test "${cputype-}" = 386; then
UNAME_MACHINE=i386
elif test "x${cputype-}" != x; then
UNAME_MACHINE=$cputype
fi
GUESS=$UNAME_MACHINE-unknown-plan9
;;
*:TOPS-10:*:*)
GUESS=pdp10-unknown-tops10
;;
*:TENEX:*:*)
GUESS=pdp10-unknown-tenex
;;
KS10:TOPS-20:*:* | KL10:TOPS-20:*:* | TYPE4:TOPS-20:*:*)
GUESS=pdp10-dec-tops20
;;
XKL-1:TOPS-20:*:* | TYPE5:TOPS-20:*:*)
GUESS=pdp10-xkl-tops20
;;
*:TOPS-20:*:*)
GUESS=pdp10-unknown-tops20
;;
*:ITS:*:*)
GUESS=pdp10-unknown-its
;;
SEI:*:*:SEIUX)
GUESS=mips-sei-seiux$UNAME_RELEASE
;;
*:DragonFly:*:*)
DRAGONFLY_REL=`echo "$UNAME_RELEASE" | sed -e 's/[-(].*//'`
GUESS=$UNAME_MACHINE-unknown-dragonfly$DRAGONFLY_REL
;;
*:*VMS:*:*)
UNAME_MACHINE=`(uname -p) 2>/dev/null`
case $UNAME_MACHINE in
A*) GUESS=alpha-dec-vms ;;
I*) GUESS=ia64-dec-vms ;;
V*) GUESS=vax-dec-vms ;;
esac ;;
*:XENIX:*:SysV)
GUESS=i386-pc-xenix
;;
i*86:skyos:*:*)
SKYOS_REL=`echo "$UNAME_RELEASE" | sed -e 's/ .*$//'`
GUESS=$UNAME_MACHINE-pc-skyos$SKYOS_REL
;;
i*86:rdos:*:*)
GUESS=$UNAME_MACHINE-pc-rdos
;;
i*86:Fiwix:*:*)
GUESS=$UNAME_MACHINE-pc-fiwix
;;
*:AROS:*:*)
GUESS=$UNAME_MACHINE-unknown-aros
;;
x86_64:VMkernel:*:*)
GUESS=$UNAME_MACHINE-unknown-esx
;;
amd64:Isilon\ OneFS:*:*)
GUESS=x86_64-unknown-onefs
;;
*:Unleashed:*:*)
GUESS=$UNAME_MACHINE-unknown-unleashed$UNAME_RELEASE
;;
esac
# Do we have a guess based on uname results?
if test "x$GUESS" != x; then
echo "$GUESS"
exit
fi
# No uname command or uname output not recognized.
set_cc_for_build
cat > "$dummy.c" <
#include
#endif
#if defined(ultrix) || defined(_ultrix) || defined(__ultrix) || defined(__ultrix__)
#if defined (vax) || defined (__vax) || defined (__vax__) || defined(mips) || defined(__mips) || defined(__mips__) || defined(MIPS) || defined(__MIPS__)
#include
#if defined(_SIZE_T_) || defined(SIGLOST)
#include
#endif
#endif
#endif
main ()
{
#if defined (sony)
#if defined (MIPSEB)
/* BFD wants "bsd" instead of "newsos". Perhaps BFD should be changed,
I don't know.... */
printf ("mips-sony-bsd\n"); exit (0);
#else
#include
printf ("m68k-sony-newsos%s\n",
#ifdef NEWSOS4
"4"
#else
""
#endif
); exit (0);
#endif
#endif
#if defined (NeXT)
#if !defined (__ARCHITECTURE__)
#define __ARCHITECTURE__ "m68k"
#endif
int version;
version=`(hostinfo | sed -n 's/.*NeXT Mach \([0-9]*\).*/\1/p') 2>/dev/null`;
if (version < 4)
printf ("%s-next-nextstep%d\n", __ARCHITECTURE__, version);
else
printf ("%s-next-openstep%d\n", __ARCHITECTURE__, version);
exit (0);
#endif
#if defined (MULTIMAX) || defined (n16)
#if defined (UMAXV)
printf ("ns32k-encore-sysv\n"); exit (0);
#else
#if defined (CMU)
printf ("ns32k-encore-mach\n"); exit (0);
#else
printf ("ns32k-encore-bsd\n"); exit (0);
#endif
#endif
#endif
#if defined (__386BSD__)
printf ("i386-pc-bsd\n"); exit (0);
#endif
#if defined (sequent)
#if defined (i386)
printf ("i386-sequent-dynix\n"); exit (0);
#endif
#if defined (ns32000)
printf ("ns32k-sequent-dynix\n"); exit (0);
#endif
#endif
#if defined (_SEQUENT_)
struct utsname un;
uname(&un);
if (strncmp(un.version, "V2", 2) == 0) {
printf ("i386-sequent-ptx2\n"); exit (0);
}
if (strncmp(un.version, "V1", 2) == 0) { /* XXX is V1 correct? */
printf ("i386-sequent-ptx1\n"); exit (0);
}
printf ("i386-sequent-ptx\n"); exit (0);
#endif
#if defined (vax)
#if !defined (ultrix)
#include
#if defined (BSD)
#if BSD == 43
printf ("vax-dec-bsd4.3\n"); exit (0);
#else
#if BSD == 199006
printf ("vax-dec-bsd4.3reno\n"); exit (0);
#else
printf ("vax-dec-bsd\n"); exit (0);
#endif
#endif
#else
printf ("vax-dec-bsd\n"); exit (0);
#endif
#else
#if defined(_SIZE_T_) || defined(SIGLOST)
struct utsname un;
uname (&un);
printf ("vax-dec-ultrix%s\n", un.release); exit (0);
#else
printf ("vax-dec-ultrix\n"); exit (0);
#endif
#endif
#endif
#if defined(ultrix) || defined(_ultrix) || defined(__ultrix) || defined(__ultrix__)
#if defined(mips) || defined(__mips) || defined(__mips__) || defined(MIPS) || defined(__MIPS__)
#if defined(_SIZE_T_) || defined(SIGLOST)
struct utsname *un;
uname (&un);
printf ("mips-dec-ultrix%s\n", un.release); exit (0);
#else
printf ("mips-dec-ultrix\n"); exit (0);
#endif
#endif
#endif
#if defined (alliant) && defined (i860)
printf ("i860-alliant-bsd\n"); exit (0);
#endif
exit (1);
}
EOF
$CC_FOR_BUILD -o "$dummy" "$dummy.c" 2>/dev/null && SYSTEM_NAME=`"$dummy"` &&
{ echo "$SYSTEM_NAME"; exit; }
# Apollos put the system type in the environment.
test -d /usr/apollo && { echo "$ISP-apollo-$SYSTYPE"; exit; }
echo "$0: unable to guess system type" >&2
case $UNAME_MACHINE:$UNAME_SYSTEM in
mips:Linux | mips64:Linux)
# If we got here on MIPS GNU/Linux, output extra information.
cat >&2 <&2 <&2 </dev/null || echo unknown`
uname -r = `(uname -r) 2>/dev/null || echo unknown`
uname -s = `(uname -s) 2>/dev/null || echo unknown`
uname -v = `(uname -v) 2>/dev/null || echo unknown`
/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null`
/bin/uname -X = `(/bin/uname -X) 2>/dev/null`
hostinfo = `(hostinfo) 2>/dev/null`
/bin/universe = `(/bin/universe) 2>/dev/null`
/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null`
/bin/arch = `(/bin/arch) 2>/dev/null`
/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null`
/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null`
UNAME_MACHINE = "$UNAME_MACHINE"
UNAME_RELEASE = "$UNAME_RELEASE"
UNAME_SYSTEM = "$UNAME_SYSTEM"
UNAME_VERSION = "$UNAME_VERSION"
EOF
fi
exit 1
# Local variables:
# eval: (add-hook 'before-save-hook 'time-stamp)
# time-stamp-start: "timestamp='"
# time-stamp-format: "%:y-%02m-%02d"
# time-stamp-end: "'"
# End:
libXaw-1.0.16/missing 0000755 0001751 0000144 00000015336 14573370153 011362 0000000 0000000 #! /bin/sh
# Common wrapper for a few potentially missing GNU programs.
scriptversion=2018-03-07.03; # UTC
# Copyright (C) 1996-2021 Free Software Foundation, Inc.
# Originally written by Fran,cois Pinard , 1996.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program. If not, see .
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that program.
if test $# -eq 0; then
echo 1>&2 "Try '$0 --help' for more information"
exit 1
fi
case $1 in
--is-lightweight)
# Used by our autoconf macros to check whether the available missing
# script is modern enough.
exit 0
;;
--run)
# Back-compat with the calling convention used by older automake.
shift
;;
-h|--h|--he|--hel|--help)
echo "\
$0 [OPTION]... PROGRAM [ARGUMENT]...
Run 'PROGRAM [ARGUMENT]...', returning a proper advice when this fails due
to PROGRAM being missing or too old.
Options:
-h, --help display this help and exit
-v, --version output version information and exit
Supported PROGRAM values:
aclocal autoconf autoheader autom4te automake makeinfo
bison yacc flex lex help2man
Version suffixes to PROGRAM as well as the prefixes 'gnu-', 'gnu', and
'g' are ignored when checking the name.
Send bug reports to ."
exit $?
;;
-v|--v|--ve|--ver|--vers|--versi|--versio|--version)
echo "missing $scriptversion (GNU Automake)"
exit $?
;;
-*)
echo 1>&2 "$0: unknown '$1' option"
echo 1>&2 "Try '$0 --help' for more information"
exit 1
;;
esac
# Run the given program, remember its exit status.
"$@"; st=$?
# If it succeeded, we are done.
test $st -eq 0 && exit 0
# Also exit now if we it failed (or wasn't found), and '--version' was
# passed; such an option is passed most likely to detect whether the
# program is present and works.
case $2 in --version|--help) exit $st;; esac
# Exit code 63 means version mismatch. This often happens when the user
# tries to use an ancient version of a tool on a file that requires a
# minimum version.
if test $st -eq 63; then
msg="probably too old"
elif test $st -eq 127; then
# Program was missing.
msg="missing on your system"
else
# Program was found and executed, but failed. Give up.
exit $st
fi
perl_URL=https://www.perl.org/
flex_URL=https://github.com/westes/flex
gnu_software_URL=https://www.gnu.org/software
program_details ()
{
case $1 in
aclocal|automake)
echo "The '$1' program is part of the GNU Automake package:"
echo "<$gnu_software_URL/automake>"
echo "It also requires GNU Autoconf, GNU m4 and Perl in order to run:"
echo "<$gnu_software_URL/autoconf>"
echo "<$gnu_software_URL/m4/>"
echo "<$perl_URL>"
;;
autoconf|autom4te|autoheader)
echo "The '$1' program is part of the GNU Autoconf package:"
echo "<$gnu_software_URL/autoconf/>"
echo "It also requires GNU m4 and Perl in order to run:"
echo "<$gnu_software_URL/m4/>"
echo "<$perl_URL>"
;;
esac
}
give_advice ()
{
# Normalize program name to check for.
normalized_program=`echo "$1" | sed '
s/^gnu-//; t
s/^gnu//; t
s/^g//; t'`
printf '%s\n' "'$1' is $msg."
configure_deps="'configure.ac' or m4 files included by 'configure.ac'"
case $normalized_program in
autoconf*)
echo "You should only need it if you modified 'configure.ac',"
echo "or m4 files included by it."
program_details 'autoconf'
;;
autoheader*)
echo "You should only need it if you modified 'acconfig.h' or"
echo "$configure_deps."
program_details 'autoheader'
;;
automake*)
echo "You should only need it if you modified 'Makefile.am' or"
echo "$configure_deps."
program_details 'automake'
;;
aclocal*)
echo "You should only need it if you modified 'acinclude.m4' or"
echo "$configure_deps."
program_details 'aclocal'
;;
autom4te*)
echo "You might have modified some maintainer files that require"
echo "the 'autom4te' program to be rebuilt."
program_details 'autom4te'
;;
bison*|yacc*)
echo "You should only need it if you modified a '.y' file."
echo "You may want to install the GNU Bison package:"
echo "<$gnu_software_URL/bison/>"
;;
lex*|flex*)
echo "You should only need it if you modified a '.l' file."
echo "You may want to install the Fast Lexical Analyzer package:"
echo "<$flex_URL>"
;;
help2man*)
echo "You should only need it if you modified a dependency" \
"of a man page."
echo "You may want to install the GNU Help2man package:"
echo "<$gnu_software_URL/help2man/>"
;;
makeinfo*)
echo "You should only need it if you modified a '.texi' file, or"
echo "any other file indirectly affecting the aspect of the manual."
echo "You might want to install the Texinfo package:"
echo "<$gnu_software_URL/texinfo/>"
echo "The spurious makeinfo call might also be the consequence of"
echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might"
echo "want to install GNU make:"
echo "<$gnu_software_URL/make/>"
;;
*)
echo "You might have modified some files without having the proper"
echo "tools for further handling them. Check the 'README' file, it"
echo "often tells you about the needed prerequisites for installing"
echo "this package. You may also peek at any GNU archive site, in"
echo "case some other package contains this missing '$1' program."
;;
esac
}
give_advice "$1" | sed -e '1s/^/WARNING: /' \
-e '2,$s/^/ /' >&2
# Propagate the correct exit status (expected to be 127 for a program
# not found, 63 for a program that failed due to version mismatch).
exit $st
# Local variables:
# eval: (add-hook 'before-save-hook 'time-stamp)
# time-stamp-start: "scriptversion="
# time-stamp-format: "%:y-%02m-%02d.%02H"
# time-stamp-time-zone: "UTC0"
# time-stamp-end: "; # UTC"
# End:
libXaw-1.0.16/compile 0000755 0001751 0000144 00000016350 14573370153 011336 0000000 0000000 #! /bin/sh
# Wrapper for compilers which do not understand '-c -o'.
scriptversion=2018-03-07.03; # UTC
# Copyright (C) 1999-2021 Free Software Foundation, Inc.
# Written by Tom Tromey .
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see .
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that program.
# This file is maintained in Automake, please report
# bugs to or send patches to
# .
nl='
'
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent tools from complaining about whitespace usage.
IFS=" "" $nl"
file_conv=
# func_file_conv build_file lazy
# Convert a $build file to $host form and store it in $file
# Currently only supports Windows hosts. If the determined conversion
# type is listed in (the comma separated) LAZY, no conversion will
# take place.
func_file_conv ()
{
file=$1
case $file in
/ | /[!/]*) # absolute file, and not a UNC file
if test -z "$file_conv"; then
# lazily determine how to convert abs files
case `uname -s` in
MINGW*)
file_conv=mingw
;;
CYGWIN* | MSYS*)
file_conv=cygwin
;;
*)
file_conv=wine
;;
esac
fi
case $file_conv/,$2, in
*,$file_conv,*)
;;
mingw/*)
file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'`
;;
cygwin/* | msys/*)
file=`cygpath -m "$file" || echo "$file"`
;;
wine/*)
file=`winepath -w "$file" || echo "$file"`
;;
esac
;;
esac
}
# func_cl_dashL linkdir
# Make cl look for libraries in LINKDIR
func_cl_dashL ()
{
func_file_conv "$1"
if test -z "$lib_path"; then
lib_path=$file
else
lib_path="$lib_path;$file"
fi
linker_opts="$linker_opts -LIBPATH:$file"
}
# func_cl_dashl library
# Do a library search-path lookup for cl
func_cl_dashl ()
{
lib=$1
found=no
save_IFS=$IFS
IFS=';'
for dir in $lib_path $LIB
do
IFS=$save_IFS
if $shared && test -f "$dir/$lib.dll.lib"; then
found=yes
lib=$dir/$lib.dll.lib
break
fi
if test -f "$dir/$lib.lib"; then
found=yes
lib=$dir/$lib.lib
break
fi
if test -f "$dir/lib$lib.a"; then
found=yes
lib=$dir/lib$lib.a
break
fi
done
IFS=$save_IFS
if test "$found" != yes; then
lib=$lib.lib
fi
}
# func_cl_wrapper cl arg...
# Adjust compile command to suit cl
func_cl_wrapper ()
{
# Assume a capable shell
lib_path=
shared=:
linker_opts=
for arg
do
if test -n "$eat"; then
eat=
else
case $1 in
-o)
# configure might choose to run compile as 'compile cc -o foo foo.c'.
eat=1
case $2 in
*.o | *.[oO][bB][jJ])
func_file_conv "$2"
set x "$@" -Fo"$file"
shift
;;
*)
func_file_conv "$2"
set x "$@" -Fe"$file"
shift
;;
esac
;;
-I)
eat=1
func_file_conv "$2" mingw
set x "$@" -I"$file"
shift
;;
-I*)
func_file_conv "${1#-I}" mingw
set x "$@" -I"$file"
shift
;;
-l)
eat=1
func_cl_dashl "$2"
set x "$@" "$lib"
shift
;;
-l*)
func_cl_dashl "${1#-l}"
set x "$@" "$lib"
shift
;;
-L)
eat=1
func_cl_dashL "$2"
;;
-L*)
func_cl_dashL "${1#-L}"
;;
-static)
shared=false
;;
-Wl,*)
arg=${1#-Wl,}
save_ifs="$IFS"; IFS=','
for flag in $arg; do
IFS="$save_ifs"
linker_opts="$linker_opts $flag"
done
IFS="$save_ifs"
;;
-Xlinker)
eat=1
linker_opts="$linker_opts $2"
;;
-*)
set x "$@" "$1"
shift
;;
*.cc | *.CC | *.cxx | *.CXX | *.[cC]++)
func_file_conv "$1"
set x "$@" -Tp"$file"
shift
;;
*.c | *.cpp | *.CPP | *.lib | *.LIB | *.Lib | *.OBJ | *.obj | *.[oO])
func_file_conv "$1" mingw
set x "$@" "$file"
shift
;;
*)
set x "$@" "$1"
shift
;;
esac
fi
shift
done
if test -n "$linker_opts"; then
linker_opts="-link$linker_opts"
fi
exec "$@" $linker_opts
exit 1
}
eat=
case $1 in
'')
echo "$0: No command. Try '$0 --help' for more information." 1>&2
exit 1;
;;
-h | --h*)
cat <<\EOF
Usage: compile [--help] [--version] PROGRAM [ARGS]
Wrapper for compilers which do not understand '-c -o'.
Remove '-o dest.o' from ARGS, run PROGRAM with the remaining
arguments, and rename the output as expected.
If you are trying to build a whole package this is not the
right script to run: please start by reading the file 'INSTALL'.
Report bugs to .
EOF
exit $?
;;
-v | --v*)
echo "compile $scriptversion"
exit $?
;;
cl | *[/\\]cl | cl.exe | *[/\\]cl.exe | \
icl | *[/\\]icl | icl.exe | *[/\\]icl.exe )
func_cl_wrapper "$@" # Doesn't return...
;;
esac
ofile=
cfile=
for arg
do
if test -n "$eat"; then
eat=
else
case $1 in
-o)
# configure might choose to run compile as 'compile cc -o foo foo.c'.
# So we strip '-o arg' only if arg is an object.
eat=1
case $2 in
*.o | *.obj)
ofile=$2
;;
*)
set x "$@" -o "$2"
shift
;;
esac
;;
*.c)
cfile=$1
set x "$@" "$1"
shift
;;
*)
set x "$@" "$1"
shift
;;
esac
fi
shift
done
if test -z "$ofile" || test -z "$cfile"; then
# If no '-o' option was seen then we might have been invoked from a
# pattern rule where we don't need one. That is ok -- this is a
# normal compilation that the losing compiler can handle. If no
# '.c' file was seen then we are probably linking. That is also
# ok.
exec "$@"
fi
# Name of file we expect compiler to create.
cofile=`echo "$cfile" | sed 's|^.*[\\/]||; s|^[a-zA-Z]:||; s/\.c$/.o/'`
# Create the lock directory.
# Note: use '[/\\:.-]' here to ensure that we don't use the same name
# that we are using for the .o file. Also, base the name on the expected
# object file name, since that is what matters with a parallel build.
lockdir=`echo "$cofile" | sed -e 's|[/\\:.-]|_|g'`.d
while true; do
if mkdir "$lockdir" >/dev/null 2>&1; then
break
fi
sleep 1
done
# FIXME: race condition here if user kills between mkdir and trap.
trap "rmdir '$lockdir'; exit 1" 1 2 15
# Run the compile.
"$@"
ret=$?
if test -f "$cofile"; then
test "$cofile" = "$ofile" || mv "$cofile" "$ofile"
elif test -f "${cofile}bj"; then
test "${cofile}bj" = "$ofile" || mv "${cofile}bj" "$ofile"
fi
rmdir "$lockdir"
exit $ret
# Local Variables:
# mode: shell-script
# sh-indentation: 2
# eval: (add-hook 'before-save-hook 'time-stamp)
# time-stamp-start: "scriptversion="
# time-stamp-format: "%:y-%02m-%02d.%02H"
# time-stamp-time-zone: "UTC0"
# time-stamp-end: "; # UTC"
# End:
libXaw-1.0.16/old-doc/ 0000755 0001751 0000144 00000000000 14573370156 011357 5 0000000 0000000 libXaw-1.0.16/old-doc/CHANGES 0000644 0001751 0000144 00000010171 14573370144 012267 0000000 0000000
These changes have been made to Xaw since X11R4.
Documentation:
Fixed definition of XtAppInitialize().
Changed all references to XawOrient* and XtOrient* to Xtorient*.
Many other corrections and clarifications.
Everywhere:
Function prototypes for public interfaces.
Many bugs not mentioned here have been fixed.
AllWidgets:
Add WidgetNode table for use with listres and viewres.
AsciiSrc (Text):
No warning message is printed when the file can not be
written to, the return value should be enough info.
GetValues on the string resource was failing when
"useStringInPlace" was set to true.
Memory leak when freeing pieces in a source of type "ascii String"
has been plugged.
Buffer is now updated whenever the "string" resource is set using
XtSetValues(). If type is file then the file is read in again.
Box:
The public header file now includes Xmu/Converters.h for the
orientation resources.
Clock:
Made subclass of simple instead of Core
Command:
Fixed bug in changing shape style to Rectangular.
Dialog:
Resource Type of Icon changed from Pixmap -> Bitmap.
Form:
The geometry handler now will now disallow geometry management
requests that will force the child outside the Form's window.
Fixed missing parens typo in PreferredGeometry.
Fixed EdgeTypes to be Xaw* instead of Xt*, but left the
old definitions around with #define so that code will still work.
StringToWidget converter no longer caches resources.
Logo:
Made subclass of simple instead of Core.
Fixed reverse video.
Mailbox:
Made subclass of simple instead of Core.
Fixed reverse video and many other bugs.
MenuButton:
* The MenuButton widget no longer places a server grab on itself.
Instead, PopupMenu is registered as a grab action. As a result
of this, clients which popped up menus without using XtMenuPopup
or MenuPopup or PopupMenu in the menu button translations will
fail to have a grab active. They should make a call to
XtRegisterGrabAction on the appropriate action in the application
initialization routine, or use a different translation.
Paned:
The public header file now includes Xmu/Converters.h for the
orientation resources.
Panner: This widget is new in R5.
Porthole:
New for R5.
Scrollbar:
Fixed bug that could call XtReleaseGC() with garbage
Made subclass of simple instead of Core
Type of thumb resource is XtRBitmap; it used to be XtRPixmap.
However, if applications provide the resource conversion, the
Scrollbar's SetValues can still handle pixmaps of correct depth.
Simple:
Added a color cursor converter. and the new resource types:
XtNpointerColor
XtNpointerColorBackground
XtNcursorName
SmeBSB:
Right bitmaps are now painted in the correct location.
Right and Left Bitmaps can be specified in resource files, and
at startup time.
Text:
If there is no current selection the the selection extends
from the insert point, rather than some random location.
Forward (Backward) Paragraph works at the paragraph boundaries now.
Selecting a word now transitions correctly at BOTH end points.
Infinite loop when using fill paragraph in a read only text widget
has been found and fixed.
When the "resize" resource is set the text will start up with
exactly enough space to contain the text in the widget.
Fixed a bug that could cause an infinite loop when Meta-Q was used
to invoke the form-paragraph function on a read-only text widget.
Exposures fixed.
TextP.h:
Symbolic constants private to the Text widget should not conflict
with operating system headers files. The names of these symbolic
constants have each had the prefix Xaw added to them:
#define XawLF 0x0a
#define XawCR 0x0d
#define XawTAB 0x09
#define XawBS 0x08
#define XawSP 0x20
#define XawDEL 0x7f
#define XawBSLASH '\\'
Toggle:
* Toggle widget state is preserved across changes in sensitivity.
A string to widget converter is regisetered for radio groups.
Tree:
New for R5.
Paned:
Fixed bug that caused XtGeometryYes returns to have bogus values,
causes panes to get random sizes.
Vendor:
Added support for the Resource Editor.
Fixed bug causing Shell to ignore all but first child.
Viewport:
Added XawPannerReport support.
libXaw-1.0.16/old-doc/Changelog 0000644 0001751 0000144 00000204234 14573370144 013113 0000000 0000000 Patch 1 (#1655) 15 April 1998
Description of the actions system:
--------------------------------------------------------------------
All the actions have the syntax:
action-name(boolean-expression, args)
Where:
action-name:
Any string with a translation binding in the binary for the widget.
boolean-expression:
[{~}]variable-name|resource-name|constant-name[{&|^}[[{~}]variable-name|resource-name|constant-name]]...
variable-name:
Any string starting with a '$' character (actually it's not possible
to mask this character; I'll fix it). Variables are actually created
with the translations 'declare' and 'get-values'. Example:
get-values(1, $x, x)
declare(1, $armed, true)
resource-name:
Any resource name of the widget. Note that it requires a to
string converter in the code (I added some on the patches), since
all variables values are stored in a 'String' format. Example:
borderWidth
height
font
background
constant-name:
Special values. They aren't normally constants, but a special state
not triggered with resources or variables (They have the highest
precedence, so, to allow these strings as resource names I'll need
to allow some sort of escape sequences). Examples:
mine # event->xany.window == XtWindow(widget)
faked # event->xany.send_event != 0
true # you know
false # " "
args:
Special strings values interpreted by the translation binding.
The operators (currently) understood are:
~ - NOT
& - AND
| - OR
^ - XOR
( - RP
) - LP
The final result value is and'ed with 1.
Sample translation to make a label widget behave like a button: