[sapwood] properly format the new readme
- From: Sven Herzberg <herzi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [sapwood] properly format the new readme
- Date: Wed, 4 Aug 2010 11:10:52 +0000 (UTC)
commit 9dc2fd325f6217fd2f3c36e424478cf565031ebb
Author: Sven Herzberg <herzi gnome-de org>
Date: Sun Aug 1 21:57:14 2010 +0200
properly format the new readme
* readme.xml: properly format the document into a docbook book
readme.xml | 472 +++++++++++++++++++++++++++++++++--------------------------
1 files changed, 264 insertions(+), 208 deletions(-)
---
diff --git a/readme.xml b/readme.xml
index c2c23b3..128dcc9 100644
--- a/readme.xml
+++ b/readme.xml
@@ -4,64 +4,70 @@
<book id="sapwood-readme" lang="en">
<title>README for Sapwood</title>
- <chapter>
+ <preface>
<title>Sapwood</title>
- <para>
-Derived from the pixbuf engine in gtk-engines 2.2.0
-
-Uses X pixmaps (pixbuf engine uses pixbufs)
-Not supported:
- * scaling of images
- * 8bit alpha
- * gradients
- * recoloring
-
-Instead
- * uses a separate daemon process
- * images are tiled (see 'Images and borders' below)
- * 1bit alpha
- * shaped windows (see 'shaped' below)
- * leading wildcard in detail handling
- * special cases for some widgets (see 'Special cases')
-
-
-Note that 1bit alpha still allows you to do things like drop shadows in some
-cases. You just need to be careful about the background and fake the effect
-with opaque bitmaps.
+
+ <para>
+ Derived from the pixbuf engine in gtk-engines 2.2.0
</para>
- </chapter>
+
+ <para>
+ Uses X pixmaps (pixbuf engine uses pixbufs). Not supported:
+ <itemizedlist>
+ <listitem>scaling of images</listitem>
+ <listitem>8bit alpha</listitem>
+ <listitem>gradients</listitem>
+ <listitem>recoloring</listitem>
+ </itemizedlist>
+ </para>
+
+ <para>
+ Instead
+ <itemizedlist>
+ <listitem>uses a separate daemon process</listitem>
+ <listitem>images are tiled (see <xref linkend="images-and-borders"/>)</listitem>
+ <listitem>1bit alpha</listitem>
+ <listitem>shaped windows (see <xref linkend="shaped"/>)</listitem>
+ <listitem>leading wildcard in detail handling</listitem>
+ <listitem>special cases for some widgets (see <xref linkend="special-cases"/>)</listitem>
+ </itemizedlist>
+ </para>
+
+ <para>
+ Note that 1bit alpha still allows you to do things like drop shadows in some
+ cases. You just need to be careful about the background and fake the effect
+ with opaque bitmaps.
+ </para>
+ </preface>
<chapter>
<title>Installation</title>
- <para>
- ./configure
+ <informalexample><programlisting>./configure
make
[ become root ]
- make install
- </para>
+ make install</programlisting></informalexample>
</chapter>
<chapter>
<title>Running</title>
<para>
-In order to run applications using the sapwood theme engine, the
-sapwood-server needs to be started beforehand. You can do this by running the
-following command:
-
- /usr/lib/sapwood/sapwood-server &
-
-It is important to use the same TMPDIR and DISPLAY environment variables for
-both the sapwood-server as well as the applications so that the theme engine
-knows how to connect to the server. If the theme engine fails to connect to
-the server for any reason you should see an error message similar to following
-in the console:
-
- `/usr/lib/sapwood/sapwood-server' MUST be started before applications
+ In order to run applications using the sapwood theme engine, the
+ sapwood-server needs to be started beforehand. You can do this by running the
+ following command:
+ <informalexample><programlisting>/usr/lib/sapwood/sapwood-server &</programlisting></informalexample>
+ </para>
-When that happens, check the TMPDIR and DISPLAY environment variables and
-check the sapwood-server process is running.
+ <para>
+ It is important to use the same TMPDIR and DISPLAY environment variables for
+ both the sapwood-server as well as the applications so that the theme engine
+ knows how to connect to the server. If the theme engine fails to connect to
+ the server for any reason you should see an error message similar to following
+ in the console:
+ <informalexample><programlisting>`/usr/lib/sapwood/sapwood-server' MUST be started before applications</programlisting></informalexample>
+ When that happens, check the TMPDIR and DISPLAY environment variables and
+ check the sapwood-server process is running.
</para>
</chapter>
@@ -69,8 +75,7 @@ check the sapwood-server process is running.
<title>Bugs</title>
<para>
-Please report bugs to maemo.org bugzilla:
-https://bugs.gnome.org/bugzilla/enter_bug.cgi?product=sapwood
+ Please report bugs to <ulink href="https://bugs.gnome.org/bugzilla/enter_bug.cgi?product=sapwood";>GNOME's bugzilla</ulink>.
</para>
</chapter>
@@ -78,44 +83,46 @@ https://bugs.gnome.org/bugzilla/enter_bug.cgi?product=sapwood
<title>gtkrc</title>
<para>
-Mostly compatible with the pixbuf engine
- * engine "sapwood" instead of "pixmap"
- * 'recolorable' declaration is not supported
-
-This document covers only the theme engine specific details. For more generic
-overview see the following links:
- * http://developer.gnome.org/doc/API/2.0/gtk/gtk-Resource-Files.html
- * http://live.gnome.org/GnomeArt/Tutorials/GtkThemes
+ Mostly compatible with the pixbuf engine
+ <itemizedlist>
+ <listitem>engine "sapwood" instead of "pixmap"</listitem>
+ <listitem>'recolorable' declaration is not supported</listitem>
+ </itemizedlist>
+ </para>
+
+ <para>
+ This document covers only the theme engine specific details. For more generic
+ overview see the following links:
+ <itemizedlist>
+ <listitem><ulink href="http://developer.gnome.org/doc/API/2.0/gtk/gtk-Resource-Files.html";>GtkRC API reference</ulink></listitem>
+ <listitem><ulink href="http://live.gnome.org/GnomeArt/Tutorials/GtkThemes";>GTK+ Theming Tutorial</ulink></listitem>
+ </itemizedlist>
</para>
<section>
<title>Overview</title>
- <para>
-
-engine "sapwood" {
+ <informalexample><programlisting>engine "sapwood" {
image { ... }
image { ... }
image { ... }
...
-}
+}</programlisting></informalexample>
-image {
+ <informalexample><programlisting>image {
[match options]
[image data]
-}
-
-'image data' is optional. You can disable painting by omitting all file
-references. This can be useful for FOCUS rules in case you want to use the
-background images to indicate the focus and not paint the focus indicator
-separately on top.
+}</programlisting></informalexample>
-Example:
-
-image {
+ <para>
+ 'image data' is optional. You can disable painting by omitting all file
+ references. This can be useful for FOCUS rules in case you want to use the
+ background images to indicate the focus and not paint the focus indicator
+ separately on top. Example:
+ <informalexample><programlisting>image {
function = FOCUS
-}
+}</programlisting></informalexample>
</para>
</section>
@@ -123,10 +130,9 @@ image {
<title>Precedence</title>
<para>
-The order of image blocks matters. The first image to satisfy the match options
-is used. Put the specific rules first and generic rules last, like this:
-
-engine "sapwood" {
+ The order of image blocks matters. The first image to satisfy the match options
+ is used. Put the specific rules first and generic rules last, like this:
+ <informalexample><programlisting>engine "sapwood" {
image {
function = BOX
state = INSENSITIVE
@@ -136,10 +142,12 @@ engine "sapwood" {
function = BOX
[generic image]
}
-}
+}</programlisting></informalexample>
+ </para>
-If the two image blocks are reordered, the 'generic image' is always used,
-even for INSENSITIVE widgets.
+ <para>
+ If the two image blocks are reordered, the 'generic image' is always used,
+ even for INSENSITIVE widgets.
</para>
</section>
@@ -147,20 +155,27 @@ even for INSENSITIVE widgets.
<title>match options</title>
<para>
-The widget, widget_class and class declarations supported by gtk+ let you to
-attach style declarations to widgets. The image declarations let you attach
-images to the painting commands used by the widgets.
-
-Match options are used to select the right image
+ The widget, widget_class and class declarations supported by gtk+ let you to
+ attach style declarations to widgets. The image declarations let you attach
+ images to the painting commands used by the widgets.
+ </para>
-The values map directly to the functions and parameters used by the
-implementation.
+ <para>
+ Match options are used to select the right image.
+ </para>
-http://live.gnome.org/GnomeArt/Tutorials/GtkThemes describes how some widgets
-are drawn, but in most cases you need to read the code to find the details.
+ <para>
+ The values map directly to the functions and parameters used by the
+ implementation.
+ </para>
+ <para>
+ The <ulink href="http://live.gnome.org/GnomeArt/Tutorials/GtkThemes";>GTK+
+ Theming tutorial</ulink> describes how some widgets
+ are drawn, but in most cases you need to read the code to find the details.
+ </para>
-C gtkrc
+ <informalexample><programlisting>C gtkrc
--------------------------------------------------------------------
style "button" {
engine "sapwood" {
@@ -176,28 +191,33 @@ gtk_paint_box( function = BOX
}
}
class "GtkButton" style "button"
---------------------------------------------------------------------
+--------------------------------------------------------------------</programlisting></informalexample>
-The following options are always available. 'function' is mandatory and
-determines what other options are available.
- function = (mandatory, see the table below for recognized values)
+ <para>
+ The 'function' is mandatory and determines what other options are available:
+ <informalexample><programlisting>function = (mandatory, see the table below for recognized values)</programlisting></informalexample>
+ </para>
-You can add specifity to the rule with the following options, regardless of
-function:
- detail = (string, such as "buttondefault")
- state = NORMAL | ACTIVE | PRELIGHT | SELECTED | INSENSITIVE
+ <para>
+ The following options are always available.
+ You can add specifity to the rule with the following options, regardless of
+ function:
+ <informalexample><programlisting>detail = (string, such as "buttondefault")
+state = NORMAL | ACTIVE | PRELIGHT | SELECTED | INSENSITIVE</programlisting></informalexample>
+ </para>
-You can add further specifity to the rules with the following options,
-depending on function (see the table below for which options are valid for each
-function)
- arrow_direction = UP | DOWN | LEFT | RIGHT
+ <para>
+ You can add further specifity to the rules with the following options,
+ depending on function (see the table below for which options are valid for each
+ function):
+ <informalexample><programlisting> arrow_direction = UP | DOWN | LEFT | RIGHT
gap_side = TOP | BOTTOM | LEFT | RIGHT
orientation = HORIZONTAL | VERTICAL
position = (comma separated list of) UP | DOWN | LEFT | RIGHT
- shadow = NONE | IN | OUT | ETCHED_IN | ETCHED_OUT
-
+ shadow = NONE | IN | OUT | ETCHED_IN | ETCHED_OUT</programlisting></informalexample>
+ </para>
-function options gtk function call
+ <informalexample><programlisting>function options gtk function call
----------------------------------------------------------------------------------------------
ARROW | arrow_direction shadow | gtk_paint_arrow, gtk_paint_expander
BOX_GAP | gap_side orientation shadow | gtk_paint_box_gap
@@ -216,8 +236,7 @@ SLIDER | orientation shadow | gtk_paint_slider
STEPPER | arrow_direction shadow |
TAB | shadow | gtk_paint_tab
VLINE | orientation | gtk_paint_vline
-----------------------------------------------------------------------------------------------
- </para>
+----------------------------------------------------------------------------------------------</programlisting></informalexample>
<section>
<title>function = ARROW</title>
@@ -231,9 +250,9 @@ VLINE | orientation | gtk_paint_vline
<title>function = FOCUS</title>
<para>
-Focus indicator is always painted on top of all other graphics and the widget
-content. It should be a (hollow) rectangle with transparency. Otherwise it will
-hide the content.
+ Focus indicator is always painted on top of all other graphics and the widget
+ content. It should be a (hollow) rectangle with transparency. Otherwise it will
+ hide the content.
</para>
</section>
@@ -245,19 +264,23 @@ hide the content.
</para>
</section>
- <section>
+ <section id="position">
<title>position</title>
<para>
-You can select different graphics based on the position of the widget inside
-the container. The value for position is a combination of LEFT, RIGHT, TOP, and
-BOTTOM when the widget is leftmost, rightmost, topmost, or bottommost
-respectively.
+ You can select different graphics based on the position of the widget inside
+ the container. The value for position is a combination of LEFT, RIGHT, TOP, and
+ BOTTOM when the widget is leftmost, rightmost, topmost, or bottommost
+ respectively.
+ </para>
-You'll need to set the "maemo-position-theming" property of the widgets' parent to
-TRUE for this data to be set in sapwood.
+ <para>
+ You'll need to set the "maemo-position-theming" property of the widgets' parent to
+ TRUE for this data to be set in sapwood.
+ </para>
-See demos/buttonbox.gtkrc
+ <para>
+ See demos/buttonbox.gtkrc
</para>
</section>
</section>
@@ -265,16 +288,14 @@ See demos/buttonbox.gtkrc
<section>
<title>image data</title>
-
- <para>
-file = (filename, see the example below)
+ <informalexample><programlisting>file = (filename, see the example below)
border = { left, right, top, bottom } (default: { 0, 0, 0, 0 })
stretch = TRUE | FALSE (default: TRUE)
-shaped = TRUE | FALSE (default: FALSE)
+shaped = TRUE | FALSE (default: FALSE)</programlisting></informalexample>
-Note the defaults.
-
-image {
+ <para>
+ Note the defaults:
+ <informalexample><programlisting>image {
function = BOX
file = "image.png"
@@ -288,26 +309,28 @@ image {
function = BOX
file = "image.png"
-}
+}</programlisting></informalexample>
</para>
<section>
<title>file</title>
<para>
-Path to an image file whose format is supported by GdkPixbuf. The path should
-be relative (relative to the directory where the gtkrc file is located, or
-relative to the paths set with 'pixmap_path')
-
-Note that 'pixmap_path' declaration can save you some typing with the
-filenames. Assuming the following directory structure:
-
-/usr/share/themes/mytheme/gtk-2.0/gtkrc
- /images/button.png
+ Path to an image file whose format is supported by GdkPixbuf. The path should
+ be relative (relative to the directory where the gtkrc file is located, or
+ relative to the paths set with 'pixmap_path').
+ </para>
-The following gtkrc snippets are equivalent.
+ <para>
+ Note that 'pixmap_path' declaration can save you some typing with the
+ filenames. Assuming the following directory structure:
+ <informalexample><programlisting>/usr/share/themes/mytheme/gtk-2.0/gtkrc
+ /images/button.png</programlisting></informalexample>
+ </para>
-----
+ <para>
+ The following gtkrc snippets are equivalent.
+ <informalexample><programlisting>----
style "button" {
engine "sapwood" {
image {
@@ -317,8 +340,8 @@ style "button" {
}
}
}
-----
-pixmap_path "../images"
+----</programlisting></informalexample>
+ <informalexample><programlisting>pixmap_path "../images"
style "button" {
engine "sapwood" {
@@ -329,7 +352,7 @@ style "button" {
}
}
}
-----
+----</programlisting></informalexample>
</para>
</section>
@@ -337,29 +360,36 @@ style "button" {
<title>border</title>
<para>
-Used together with 'stretch = TRUE' See 'Images and borders' below for more
-details.
-
-NOTE: the same file (including overlays and gaps) can not be referenced
-multiple times with different border values. This is a limitation in the
-implementation. It is unlikely to cause any significant problems as the same
-image is rarely meant to be tiled in different ways. It is more commonly an
-indication of a typo in the gtkrc file.
+ Used together with 'stretch = TRUE' See <xref linkend="images-and-borders"/> for more
+ details.
+ </para>
+
+ <para>
+ NOTE: the same file (including overlays and gaps) can not be referenced
+ multiple times with different border values. This is a limitation in the
+ implementation. It is unlikely to cause any significant problems as the same
+ image is rarely meant to be tiled in different ways. It is more commonly an
+ indication of a typo in the gtkrc file.
</para>
</section>
- <section>
+ <section id="shaped">
<title>shaped</title>
<para>
-When set to TRUE the transparent pixels (more than 50% transparency) in the
-bitmap are applied to the underlying window. This allows menus, for example,
-to have rounded corners.
+ When set to TRUE the transparent pixels (more than 50% transparency) in the
+ bitmap are applied to the underlying window. This allows menus, for example,
+ to have rounded corners.
+ </para>
-NOTE: If the bitmap does not have an alpha channel, shaped must NOT be set or
-strange drawing artefacts will appear.
+ <para>
+ NOTE: If the bitmap does not have an alpha channel, shaped must NOT be set or
+ strange drawing artefacts will appear.
+ <!-- FIXME: this is a bug. we should write a test case and then fix the bug -->
+ </para>
-Used only for GtkWindow and GtkMenu widgets (and derivatives)
+ <para>
+ Used only for GtkWindow and GtkMenu widgets (and derivatives).
</para>
</section>
@@ -367,12 +397,16 @@ Used only for GtkWindow and GtkMenu widgets (and derivatives)
<title>stretch</title>
<para>
-When set to TRUE the image is stretched to fill the whole area that is
-requested. See 'Images and borders' below for how the stretching is done.
+ When set to TRUE the image is stretched to fill the whole area that is
+ requested. See 'Images and borders' below for how the stretching is done.
+ </para>
-When set to FALSE the image is centered instead.
+ <para>
+ When set to FALSE the image is centered instead.
+ </para>
-Note: stretch = FALSE and border != 0 makes no sense
+ <para>
+ Note: stretch = FALSE and border != 0 makes no sense
</para>
</section>
@@ -380,16 +414,22 @@ Note: stretch = FALSE and border != 0 makes no sense
<title>overlay</title>
<para>
-overlay_file, overlay_border, overlay_stretch
+ overlay_file, overlay_border, overlay_stretch
+ </para>
-Overlay image is painted after the background image (as referenced by 'file')
-This allows you to add small details to parts of the widgets, such as the
-scrollbar slider or the GtkPaned drag handle.
+ <para>
+ Overlay image is painted after the background image (as referenced by 'file')
+ This allows you to add small details to parts of the widgets, such as the
+ scrollbar slider or the GtkPaned drag handle.
+ </para>
-NOTE: 'overlay_stretch = TRUE' rarely makes sense as it'll paint over the area
-already covered by the background image.
+ <para>
+ NOTE: 'overlay_stretch = TRUE' rarely makes sense as it'll paint over the area
+ already covered by the background image.
+ </para>
-Not used if function is BOX_GAP, FOCUS, HLINE, SHADOW, SHADOW_GAP, or VLINE.
+ <para>
+ Not used if function is BOX_GAP, FOCUS, HLINE, SHADOW, SHADOW_GAP, or VLINE.
</para>
</section>
@@ -397,37 +437,49 @@ Not used if function is BOX_GAP, FOCUS, HLINE, SHADOW, SHADOW_GAP, or VLINE.
<title>gap_start, gap, gap_end</title>
<para>
-When function is BOX_GAP or SHADOW_GAP more images are needed to paint the gap
-differently from its surroundings. Use the following declarations:
- * gap_start_file, gap_start_border, gap_start_stretch
- * gap_file, gap_border, gap_stretch
- * gap_end_file, gap_end_border, gap_end_stretch
+ When function is BOX_GAP or SHADOW_GAP more images are needed to paint the gap
+ differently from its surroundings. Use the following declarations:
+ <itemizedlist>
+ <listitem>gap_start_file, gap_start_border, gap_start_stretch</listitem>
+ <listitem>gap_file, gap_border, gap_stretch</listitem>
+ <listitem>gap_end_file, gap_end_border, gap_end_stretch</listitem>
+ </itemizedlist>
+ </para>
-They're similar to file, border and stretch.
+ <para>
+ They're similar to file, border and stretch.
</para>
</section>
</section>
</chapter>
- <chapter>
+ <chapter id="images-and-borders">
<title>Images and borders</title>
<para>
-border = { left, right, top, bottom }
-the number of pixels from left, right, top and bottom edge respectively
+ border = { left, right, top, bottom }
+ </para>
-This chapter tries to explain how the image stretching is done. The border
-values define how the original image is to be stretched to fill up larger
-areas. They are used to divide the image into a 3x3 grid of smaller images.
-These smaller images are tiled, or not depending on their position in the
-grid, while painting.
+ <para>
+ the number of pixels from left, right, top and bottom edge respectively
+ </para>
-Take a 5x5 pixels image for example, with borders of 2px on each side. The
-grid will look something like below. The corner pieces (1,3,7,9) are 2x2
-pixels, the center (5) is 1x1 pixels and the horizontal (4,6) and vertical
-(2,8) slices are 2x1 and 1x2 pixels respectively.
+ <para>
+ This chapter tries to explain how the image stretching is done. The border
+ values define how the original image is to be stretched to fill up larger
+ areas. They are used to divide the image into a 3x3 grid of smaller images.
+ These smaller images are tiled, or not depending on their position in the
+ grid, while painting.
+ </para>
-+--+-+--+
+ <para>
+ Take a 5x5 pixels image for example, with borders of 2px on each side. The
+ grid will look something like below. The corner pieces (1,3,7,9) are 2x2
+ pixels, the center (5) is 1x1 pixels and the horizontal (4,6) and vertical
+ (2,8) slices are 2x1 and 1x2 pixels respectively.
+ </para>
+
+ <informalexample><programlisting>+--+-+--+
|11|2|33| top
|11|2|33|
+--+-+--+
@@ -437,16 +489,17 @@ pixels, the center (5) is 1x1 pixels and the horizontal (4,6) and vertical
|77|8|99|
+--+-+--+
^ right
- left
-
+ left</programlisting></informalexample>
-When the image is stretched to fill up say a 11x8 pixels area the stretched
-image will look something like below. The corner pieces (1,3,7,9) are still
-2x2 pixels, the horizontal slices (4,6) are tiled only vertically, the
-vertical slices (2,8) are tiled only horizontally, and the center (5) is tiled
-both horizontally and vertically.
+ <para>
+ When the image is stretched to fill up say a 11x8 pixels area the stretched
+ image will look something like below. The corner pieces (1,3,7,9) are still
+ 2x2 pixels, the horizontal slices (4,6) are tiled only vertically, the
+ vertical slices (2,8) are tiled only horizontally, and the center (5) is tiled
+ both horizontally and vertically.
+ </para>
-+--+-------+--+
+ <informalexample><programlisting>+--+-------+--+
|11|2222222|33| top
|11|2222222|33|
+--+-------+--+
@@ -459,32 +512,35 @@ both horizontally and vertically.
|77|8888888|99|
+--+-------+--+
^ right
- left
+ left</programlisting></informalexample>
-1,3,7,9 are fixed
- 2,8 are tiled horizontally
- 4,6 are tiled vertically
- 5 is tiled both horizontally and vertically
+ <para>
+ 1,3,7,9 are fixed;
+ 2,8 are tiled horizontally;
+ 4,6 are tiled vertically;
+ 5 is tiled both horizontally and vertically.
</para>
</chapter>
- <chapter>
+ <chapter id="special-cases">
<title>Special cases</title>
<para>
-The theme engine includes special cases for some widgets which are needed to
-get the Maemo look and feel. They should not interfere when not used.
+ The theme engine includes special cases for some widgets which are needed to
+ get the Maemo look and feel. They should not interfere when not used.
</para>
<section>
<title>GtkButton</title>
<para>
-You can use the button position in the button box (solitary, leftmost, middle,
-rightmost) to select different bitmaps for buttons in button boxes. This allows
-painting dialog buttons nicely rounded.
+ You can use the button position in the button box (solitary, leftmost, middle,
+ rightmost) to select different bitmaps for buttons in button boxes. This allows
+ painting dialog buttons nicely rounded.
+ </para>
-See 'position' above and demos/buttonbox.gtkrc
+ <para>
+ See <xref linkend="position"/> and demos/buttonbox.gtkrc.
</para>
</section>
@@ -492,28 +548,28 @@ See 'position' above and demos/buttonbox.gtkrc
<title>GtkCheckButton and GtkRadioButton</title>
<para>
-You can use artificial ACTIVE state to select different bitmaps for check and
-radio button indicators when the widget is focused. This allows painting focus
-indicator style different from the standard dashed rectangle.
+ You can use artificial ACTIVE state to select different bitmaps for check and
+ radio button indicators when the widget is focused. This allows painting focus
+ indicator style different from the standard dashed rectangle.
+ </para>
-GtkCheckButton:
+ <informalexample><programlisting>GtkCheckButton:
function = CHECK
state = ACTIVE
GtkRadioButton:
function = OPTION
- state = ACTIVE
- </para>
+ state = ACTIVE</programlisting></informalexample>
</section>
<section>
<title>GtkMenuItem</title>
- <para>
+ <informalexample><programlisting>
Selected item background:
function = BOX
state = PRELIGHT for active, SELECTED for passive focus
- </para>
+ </programlisting></informalexample>
</section>
<section>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
