old-www/HOWTO/XWindow-User-HOWTO/appendix.html

1035 lines
19 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Appendix</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="The X Window User HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Performance Considerations"
HREF="performance.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The X Window User HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="performance.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
>&nbsp;</TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="appendix"
></A
>10. Appendix</H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="terms"
></A
>10.1. Terminology and Usage</H2
><P
>&#13; There are a few basic concepts and terminologies you should be familiar with.
These terms will appear here, in the manual pages, and in other help files and
documentation.
</P
><P
>&#13; <P
></P
><UL
><LI
><P
>&#13; The <SPAN
CLASS="QUOTE"
>"X server"</SPAN
> is the low-level driver software that interacts
with your video card and other system hardware, and manages the
<SPAN
CLASS="QUOTE"
>"display"</SPAN
> and the various components attached to the
<SPAN
CLASS="QUOTE"
>"display"</SPAN
> (keyboard, mouse, etc.). And, of course, handles
requests from clients as well. There are different X servers for different
chipsets.
</P
><P
>&#13; X Servers are referenced in the form of:
</P
><P
>&#13; <EM
>host.domain:display_number.screen_number</EM
>
</P
><P
>&#13; An example would look like: <EM
>my_computer:0.0</EM
>
</P
><P
>&#13; If host (and domain) is omitted, localhost is assumed. <SPAN
CLASS="QUOTE"
>"Host"</SPAN
>
can be a remote host. If <SPAN
CLASS="QUOTE"
>"screen"</SPAN
> is omitted, then
<SPAN
CLASS="QUOTE"
>"0"</SPAN
> (the first screen) is assumed. In it's shortest form, the
X server is often represented as just <SPAN
CLASS="QUOTE"
>":0"</SPAN
>, which would be the
first local <SPAN
CLASS="QUOTE"
>"display"</SPAN
>. <SPAN
CLASS="application"
>X</SPAN
> supports
multiple <SPAN
CLASS="QUOTE"
>"displays"</SPAN
> <EM
>and</EM
> multiple
<SPAN
CLASS="QUOTE"
>"screens"</SPAN
>.
</P
><P
>&#13; <SPAN
CLASS="QUOTE"
>"Screen"</SPAN
> and <SPAN
CLASS="QUOTE"
>"Display"</SPAN
> have special meanings in
relation to X servers, in addition to their more common usage.
</P
></LI
><LI
><P
>&#13; When <SPAN
CLASS="application"
>X</SPAN
> is invoked, the X server will initialize
one or more <SPAN
CLASS="QUOTE"
>"displays"</SPAN
>. Yes, <SPAN
CLASS="application"
>X</SPAN
> can
have more than one <SPAN
CLASS="QUOTE"
>"display"</SPAN
> available (though this is not a
common configuration for the average user). Each <SPAN
CLASS="QUOTE"
>"display"</SPAN
> is
a separate instance of <SPAN
CLASS="QUOTE"
>"X"</SPAN
>. The <SPAN
CLASS="QUOTE"
>"display"</SPAN
>
includes not only the obvious video components, but also the keyboard,
mouse and other input type components. The user can only access one
<SPAN
CLASS="application"
>display</SPAN
> at a time via the same keyboard and
monitor. <SPAN
CLASS="QUOTE"
>"Displays"</SPAN
> may reside locally, or on a networked
host <SPAN
CLASS="QUOTE"
>"somewhere"</SPAN
>, or both. It is possible that if multiple
<SPAN
CLASS="QUOTE"
>"displays"</SPAN
> are available, the user can choose which one he
wants when he logs in. Each <SPAN
CLASS="QUOTE"
>"display"</SPAN
> may have its own
unique configuration (e.g. resolution). But again, the most typical
configuration is just one <SPAN
CLASS="QUOTE"
>"display"</SPAN
> with one <SPAN
CLASS="QUOTE"
>"screen"</SPAN
>,
which is how most of us use <SPAN
CLASS="application"
>X</SPAN
>.
</P
></LI
><LI
><P
>
In reference to X servers, <SPAN
CLASS="QUOTE"
>"screen"</SPAN
> means the primary video
output with which you view <SPAN
CLASS="application"
>X</SPAN
>.
And there can be more than one <SPAN
CLASS="QUOTE"
>"screen"</SPAN
>, just like you can
have more than one <SPAN
CLASS="QUOTE"
>"display"</SPAN
>. Additional
<SPAN
CLASS="QUOTE"
>"screens"</SPAN
> are used in <SPAN
CLASS="QUOTE"
>"multi-headed displays"</SPAN
> for
instance. In fact you can even have more than one computer running off a
single X server. This is beyond the scope of this document, but you should
be aware of this degree of flexibility as it is an important ingredient of
the <SPAN
CLASS="application"
>X</SPAN
> protocol.
</P
></LI
><LI
><P
>&#13; <SPAN
CLASS="QUOTE"
>"Desktop"</SPAN
> can mean different things in different
contexts. Often, <SPAN
CLASS="QUOTE"
>"desktop"</SPAN
> means what is more properly
called the <SPAN
CLASS="QUOTE"
>"Desktop Environment"</SPAN
>. Prime examples of this are
<SPAN
CLASS="application"
>KDE</SPAN
>, <SPAN
CLASS="application"
>GNOME</SPAN
>, and the not
as well-known <SPAN
CLASS="application"
>CDE</SPAN
>, which are high level
applications that control much of how the user interacts with the
<SPAN
CLASS="application"
>X</SPAN
> session. They provide consistent look and
feel, as well as consistent configuration and come bundled with their own
set of utilities for common tasks.
</P
><P
>&#13; <SPAN
CLASS="QUOTE"
>"Desktop"</SPAN
> also sometimes just means the viewable screen area.
This is more of the MS Window's meaning. <SPAN
CLASS="application"
>X</SPAN
>
environments though are capable of having multiple virtual
<SPAN
CLASS="QUOTE"
>"desktops"</SPAN
> that can be switched between as needed. This helps with
organizing different tasks. Each <SPAN
CLASS="QUOTE"
>"desktop"</SPAN
> may its own windows
and clients that are specific to it. Right now I have seven
<SPAN
CLASS="application"
>WindowMaker</SPAN
> desktops
(<SPAN
CLASS="application"
>WindowMaker</SPAN
> calls them
<SPAN
CLASS="QUOTE"
>"WorkSpaces"</SPAN
>), and one of those I have dedicated to writing
this document. This <SPAN
CLASS="QUOTE"
>"desktop"</SPAN
> has thirteen unique windows at
the moment (man pages, browser windows, clock, gvim, xterms, etc).
</P
></LI
><LI
><P
>&#13; <SPAN
CLASS="QUOTE"
>"Clients"</SPAN
> are any program that connect to the X server, and
require an X server for some task (e.g. to display itself). Often, these
are displayed in their own <SPAN
CLASS="QUOTE"
>"window"</SPAN
>, but not always. For
instance, if I use <TT
CLASS="literal"
>CTRL-N</TT
> to open a new
<SPAN
CLASS="application"
>Mozilla</SPAN
> window, this is one
<SPAN
CLASS="application"
>X</SPAN
> client but with two windows. If I run a command
line <SPAN
CLASS="application"
>X</SPAN
> utility like <B
CLASS="command"
>xev</B
> to
view key and mouse events, this runs in the <B
CLASS="command"
>xterm's</B
>
window, so has none of its own, but is still a <SPAN
CLASS="QUOTE"
>"client"</SPAN
>.
Clients can be locally running applications, or applications that are
running on another system over the network, but are displayed locally.
</P
></LI
><LI
><P
>
The <SPAN
CLASS="QUOTE"
>"Window Manager"</SPAN
> is a special type of client application
and a user definable component of the GUI. It is what the user interacts
with to a large extent. The Window Manager provides such functionality as
window borders and decorations, menus, icons, virtual desktops, button
bars, tool bars, and allows the user to customize these. It is technically
possible to run <SPAN
CLASS="application"
>X</SPAN
> without a window manager
(though not very functional), but not the other way around. Window managers
should not be confused with <SPAN
CLASS="QUOTE"
>"Desktop Environments"</SPAN
> like
<SPAN
CLASS="application"
>KDE</SPAN
>. Desktop Environments include their own
preferred Window Manager, but this is a configurable. There is some
overlapping of responsibilities between Window Managers and Desktop
Environments.
</P
></LI
><LI
><P
>
The <SPAN
CLASS="QUOTE"
>"root window"</SPAN
> is the background of your screen. It is
referred to as a window in name alone, it does not behave like any other
window, but rather you run your applications on the root window, or put an
image on it, or perhaps just a solid color. All other windows are children
of this parent window. The root window conceivably can be larger than the viewable
screen area.
</P
></LI
><LI
><P
>
The <SPAN
CLASS="QUOTE"
>"pointer"</SPAN
> is the arrow or indicator of any
given shape which represents the location of your mouse, or other pointing
device. The pointer often changes to give you contextual feedback as to
what will happen when you use the mouse at that point on the screen.
</P
></LI
><LI
><P
>
The <SPAN
CLASS="QUOTE"
>"window"</SPAN
> is a frame in which any given application runs
and which is <SPAN
CLASS="QUOTE"
>"managed"</SPAN
> by the Window Manager. This includes
pretty much anything except the so-called root window. Even windows which
do not appear to have frames, titles, or normal borders of any kind are
being managed by your window manger. The <SPAN
CLASS="QUOTE"
>"active window"</SPAN
> is
the window you are currently using. This window will will respond to the
keyboard when you type, and is traditionally denoted by the fact that your
mouse cursor is pointing at it, though this is not always the case. The
active window is said to have <SPAN
CLASS="QUOTE"
>"focus"</SPAN
>. Most Window Managers
will somehow highlight the <SPAN
CLASS="QUOTE"
>"active"</SPAN
>, or focused, window to
differentiate it from other windows.
</P
></LI
><LI
><P
>
<SPAN
CLASS="QUOTE"
>"Menus"</SPAN
>, <SPAN
CLASS="QUOTE"
>"icons"</SPAN
> and <SPAN
CLASS="QUOTE"
>"task bars"</SPAN
>
behave in <SPAN
CLASS="application"
>X</SPAN
> similar to the way they behave in
other windowing systems, and the same general principles apply.
</P
></LI
><LI
><P
>
Windows that run text only applications are called <SPAN
CLASS="QUOTE"
>"terminal
emulators"</SPAN
>, such as <B
CLASS="command"
>xterm</B
> and various
similar applications. This is the well-known <SPAN
CLASS="QUOTE"
>"command line"</SPAN
> in
an X environment. These basically emulate a console text-only display, and
have some advantages due to their being used in
<SPAN
CLASS="application"
>X</SPAN
>. These are much more complex and sophisticated
applications than a simple <SPAN
CLASS="application"
>DOS</SPAN
> box on Windows.
</P
></LI
><LI
><P
>
<SPAN
CLASS="QUOTE"
>"Widgets"</SPAN
> is the term used to describe such GUI control
components as buttons, sliders, menus, scrollbars, listboxes, checkboxes, etc.
<SPAN
CLASS="QUOTE"
>"Toolkits"</SPAN
> are libraries containing a diverse set of widgets
with the same look and feel. Some common examples are
<SPAN
CLASS="application"
>GTK+</SPAN
> (used by <SPAN
CLASS="application"
>GNOME</SPAN
>,
<SPAN
CLASS="application"
>Mozilla</SPAN
> and others), <SPAN
CLASS="application"
>Xaw</SPAN
>
(X Athena Widget set), <SPAN
CLASS="application"
>Tk</SPAN
>,
<SPAN
CLASS="application"
>Motif</SPAN
> and <SPAN
CLASS="application"
>QT</SPAN
> (used
by <SPAN
CLASS="application"
>KDE</SPAN
>). Applications are built with one toolkit
or another. Sometimes the same application can be built with different
toolkits, depending on compile time options.
</P
></LI
><LI
><P
>&#13; Window <SPAN
CLASS="QUOTE"
>"geometry"</SPAN
> is a shorthand way of expressing a window's
size and screen placement. This might look like
<SPAN
CLASS="QUOTE"
>"60x20+10+50"</SPAN
>, which is <TT
CLASS="literal"
>WIDTH x HEIGHT +VERT_OFFSET
+HORZ_OFFSET</TT
>. While both pairs are often specified, it is
permissible to use just one or the other pair.
</P
></LI
><LI
><P
>&#13; In <SPAN
CLASS="application"
>X</SPAN
> lingo, <SPAN
CLASS="QUOTE"
>"resources"</SPAN
> are
definable application attributes. Commonly available
<SPAN
CLASS="QUOTE"
>"resources"</SPAN
> are fonts, colors, size, window title, etc,
etc.
</P
></LI
></UL
>
</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="links"
></A
>10.2. Links and other References</H2
><P
>&#13; <P
></P
><UL
><LI
><P
>&#13; The definitive source of information on XFree86 is, of course,
<A
HREF="http://xfree86.org"
TARGET="_top"
>http://xfree86.org</A
>. Don't forget
the man pages that you have installed already too (X, Xserver, XF86Config,
XFree86, xdm, xinit, xmodmap, startx, xauth, Xsecurity, etc, etc). These are
really mostly decent, though some are quite technical.
</P
><P
>&#13; Some pages at xfree86.org to check:
</P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; Docs and support info: <A
HREF="http://www.xfree86.org/support.html"
TARGET="_top"
>http://www.xfree86.org/support.html</A
> for
various versions and topics.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; README: <A
HREF="http://www.xfree86.org/current/README.html"
TARGET="_top"
>http://www.xfree86.org/current/README.html</A
>
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; Release Notes: <A
HREF="http://www.xfree86.org/current/RELNOTES.html"
TARGET="_top"
>http://www.xfree86.org/current/RELNOTES.html</A
>
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; DRI: <A
HREF="http://www.xfree86.org/current/DRI.html"
TARGET="_top"
>http://www.xfree86.org/current/DRI.html</A
>
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; Status: <A
HREF="http://www.xfree86.org/current/Status.html"
TARGET="_top"
>http://www.xfree86.org/current/Status.html</A
>
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; Mouse: <A
HREF="http://www.xfree86.org/current/mouse.html"
TARGET="_top"
>http://www.xfree86.org/current/mouse.html</A
>
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; Supported card list:
<A
HREF="http://xfree86.org/cardlist.html"
TARGET="_top"
>http://xfree86.org/cardlist.html</A
>
</TD
></TR
></TBODY
></TABLE
><P
></P
></LI
><LI
><P
>&#13; Other related documents from LDP:
</P
><P
>&#13; <P
></P
><UL
><LI
><P
>&#13; If you are just starting out, you may find the
<A
HREF="http://tldp.org/HOWTO/XWindow-Overview-HOWTO/index.html"
TARGET="_top"
>X Window System Architecture Overview HOWTO</A
>
to be helpful. It covers all the basic concepts quite well.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/Remote-X-Apps.html"
TARGET="_top"
>The Remote X Apps Mini HOWTO
</A
>
does a nice job of discussing running <SPAN
CLASS="application"
>X</SPAN
>
remotely, and related security issues of <SPAN
CLASS="application"
>X</SPAN
> networking.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/XDMCP-HOWTO/index.html"
TARGET="_top"
>The XDMCP HOWTO
</A
>
covers the X Display Manager Control Protocol, for running
<SPAN
CLASS="application"
>X</SPAN
> remotely. Also,
<A
HREF="http://tldp.org/HOWTO/XDM-Xterm/index.html"
TARGET="_top"
>The XDM and X Terminal mini-HOWTO
</A
>.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/XFree86-HOWTO/index.html"
TARGET="_top"
>The XFree86 HOWTO
</A
>
succinctly covers installation, and initial configuration.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html"
TARGET="_top"
>The XFree86 Video Timings HOWTO
</A
>
gets down and dirty with the finer points of monitor tuning. Generally
not required for XFree86 v4.x.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/Xinerama-HOWTO.html"
TARGET="_top"
>The Xinerama HOWTO</A
>
covers multi-headed displays.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/Font-HOWTO.html"
TARGET="_top"
>The Font HOWTO</A
>
covers various font topics.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/FDU/index.html"
TARGET="_top"
>The Font De-Uglification Mini HOWTO
</A
>
covers a range of <SPAN
CLASS="application"
>X</SPAN
> font issues.
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/Intkeyb/index.html"
TARGET="_top"
>The International Keyboard HOWTO
</A
>
</P
></LI
><LI
><P
>&#13;<A
HREF="http://tldp.org/HOWTO/Infrared-HOWTO/index.html"
TARGET="_top"
>The Linux Infrared HOWTO
</A
>
</P
></LI
></UL
>
</P
></LI
><LI
><P
>&#13; Looking for information on a Window Manager, or wanting to try
something new or different:
<A
HREF="http://www.plig.org/xwinman/"
TARGET="_top"
>http://www.plig.org/xwinman/</A
>
</P
></LI
><LI
><P
>&#13; Wheel mice tips and configuration:
<A
HREF="http://koala.ilog.fr/colas/mouse-wheel-scroll/"
TARGET="_top"
>http://koala.ilog.fr/colas/mouse-wheel-scroll/</A
>
</P
></LI
><LI
><P
>&#13; Linux and Laptops:
<A
HREF="http://www.linux-laptop.net/"
TARGET="_top"
>http://www.linux-laptop.net/</A
>
</P
></LI
><LI
><P
>&#13; The O'Reilly series on X Window! Visit <A
HREF="http://www.ora.com/"
TARGET="_top"
>http://www.ora.com/</A
> for the definitive books on <SPAN
CLASS="application"
>X</SPAN
>.
</P
></LI
><LI
><P
>&#13; The X Consortium's web site is <A
HREF="http://www.x.org/"
TARGET="_top"
>http://www.x.org/</A
> ... or perhaps it's moved to
<A
HREF="http://www.opengroup.org/"
TARGET="_top"
>http://www.opengroup.org/</A
>.
</P
></LI
><LI
><P
>&#13; <A
HREF="http://www.x11.org/"
TARGET="_top"
>http://www.x11.org/</A
> is sort of a clearinghouse
for all things X.
</P
></LI
><LI
><P
>&#13; And for everything else under the Sun: <A
HREF="http://google.com/linux/"
TARGET="_top"
>http://google.com/linux/</A
>.
An incredible resource in its own right.
</P
></LI
></UL
>
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="performance.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Performance Considerations</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>