[nautilus-actions] Update NACT user's manual



commit 16de5d4a494ecf547f82bf8b1649e50157cfee92
Author: Pierre Wieser <pwieser trychlos org>
Date:   Mon Aug 2 21:11:54 2010 +0200

    Update NACT user's manual

 doc/nact/.gitignore                         |    1 +
 doc/nact/C/articleinfo.xml                  |    2 +-
 doc/nact/C/figures/add.png                  |  Bin 0 -> 448 bytes
 doc/nact/C/figures/remove.png               |  Bin 0 -> 261 bytes
 doc/nact/C/nact-usage.xml                   | 1215 ++++++++++++++++++++++-----
 doc/nact/C/nautilus-actions-config-tool.xml |   63 ++-
 doc/nact/Makefile.am                        |    2 +
 7 files changed, 1079 insertions(+), 204 deletions(-)
---
diff --git a/doc/nact/.gitignore b/doc/nact/.gitignore
index e8a71e0..45852b4 100644
--- a/doc/nact/.gitignore
+++ b/doc/nact/.gitignore
@@ -1 +1,2 @@
 *.omf
+*.pdf
diff --git a/doc/nact/C/articleinfo.xml b/doc/nact/C/articleinfo.xml
index 80bc04e..03f3c68 100644
--- a/doc/nact/C/articleinfo.xml
+++ b/doc/nact/C/articleinfo.xml
@@ -74,7 +74,7 @@
       <revdescription>
         <para role="author">
           Pierre Wieser
-	    <email>pwieser trychlos org</email>
+          <email>pwieser trychlos org</email>
         </para>
       </revdescription>
     </revision>
diff --git a/doc/nact/C/figures/add.png b/doc/nact/C/figures/add.png
new file mode 100644
index 0000000..9f222fc
Binary files /dev/null and b/doc/nact/C/figures/add.png differ
diff --git a/doc/nact/C/figures/remove.png b/doc/nact/C/figures/remove.png
new file mode 100644
index 0000000..a12ec4a
Binary files /dev/null and b/doc/nact/C/figures/remove.png differ
diff --git a/doc/nact/C/nact-usage.xml b/doc/nact/C/nact-usage.xml
index 73616ed..a402b0f 100644
--- a/doc/nact/C/nact-usage.xml
+++ b/doc/nact/C/nact-usage.xml
@@ -22,12 +22,12 @@
       </para>
       <para>
         A new action is inserted in the items list. The exact place where the
-        action is inserted depends of the current sort order of the items list.
+        action is inserted depends of the current sort order of the items list:
       </para>
       <variablelist>
         <varlistentry>
           <term>
-            Manual order
+            Manual order:
           </term>
           <listitem>
             <para>
@@ -40,12 +40,12 @@
         </varlistentry>
         <varlistentry>
           <term>
-            Ascending (resp. descending) alphabetical order
+            Ascending (resp. descending) alphabetical order:
           </term>
           <listitem>
             <para>
               The new action is inserted at the correct place, regarding the default
-              "New Nautilus action" label.
+              &laquosp;<literal>New Nautilus action</literal>&spraquo; label.
             </para>
             <para>
               This place will be automatically changed, each time you modify the
@@ -59,13 +59,13 @@
       </para>
       <note>
         <para>
-          In items list, the new action is displayed in italic characters. Italics are used
-          as a reminder that the item has not yet been saved.
+          In theitems list, the new action is displayed in italic characters.
+          Italics are used as a reminder that the item has not yet been saved.
         </para>
       </note>
       <note>
         <para>
-          The new action is also displayed in red color in items list.
+          The new action is also displayed in red color in the items list.
           Red color is used as an indicator that the item
           is invalid, that is that the item cannot be candidate to be displayed in a
           &nautilus; context menu because some of its informations are missing or erroneous.
@@ -77,70 +77,1080 @@
       <sect3 id="usage-create-action-where">
         <title>Where should appear the action ?</title>
         <para>
+          &nautilus; file-manager may display your custom action in different places,
+          depending on you will request here, and if some item is currently selected.
         </para>
+
+        <sect4 id="usage-create-action-where-selection">
+          <title>Targeting the selection context menu</title>
+          <para>
+            When <guilabel>Display item in selection context menu</guilabel> checkbox
+            is activated, then your action will be candidate to be displayed in 
+            &nautilus; context menu, as long as at least one item is selected in 
+            the file-manager. Your action will so deal with currently selected
+            item(s).
+          </para>
+          <tip>
+            <para>
+              When an action targets the selection context menu, and is actually 
+              displayed in &nautilus; context menu, then it is also displayed
+              in the <guimenu>Edit</guimenu> menu.
+            </para>
+          </tip>
+          <para>
+            This checkbox is activated by default.
+          </para>
+          <para>
+            When targeting the selection context menu, and in order to be
+            actually displayed, all the conditions defined in
+            your candidate action must be met by each item currently selected
+            in the &nautilus; file-manager. 
+          </para>
+        </sect4>
+
+        <sect4 id="usage-create-action-where-location">
+          <title>Targeting the location context menu</title>
+          <para>
+            When <guilabel>Display item in location context menu</guilabel> checkbox
+            is activated, then your action will be candidate to be displayed in 
+            &nautilus; context menu, when the file-manager selection will be empty.
+            Your action will so deal with currently displayed location.
+          </para>
+          <tip>
+            <para>
+              When an action targets the location context menu, and is actually 
+              displayed in &nautilus; context menu, then it is also displayed
+              in the <guimenu>File</guimenu> menu.
+            </para>
+          </tip>
+          <para>
+            When targeting the location context menu, and in order to be
+            actually displayed, all the conditions defined in
+            your candidate action must be met by the location currently displayed
+            in the &nautilus; file-manager. 
+          </para>
+        </sect4>
+
+        <sect4 id="usage-create-action-where-toolbar">
+          <title>Targeting the toolbar</title>
+          <para>
+            When <guilabel>Display item in the toolbar</guilabel> checkbox
+            is activated, then your action will be candidate to be displayed in 
+            &nautilus; toolbar.
+          </para>
+          <para>
+            Actions displayed in the toolbar only deal with the location which
+            is currently displayed in the file-manager, not with the items which
+            may be currently selected (or not). In order to be displayed, all the
+            conditions defined in your candidate action must so be met by the
+            current location. 
+          </para>
+        </sect4>
+
+        <sect4 id="usage-create-action-where-notes">
+          <title>Notes</title>
+            <para>
+              An action may target both the selection context menu, the location context
+              menu and the toolbar, or one or more among these. If no target is defined,
+              <abbrev>i.e.</abbrev> if the three checkboxes are unchecked, then your action
+              will never be displayed.
+            </para>
+        </sect4>
       </sect3>
 
       <sect3 id="usage-create-action-display">
         <title>How the action will it appear ?</title>
-        <para>
-        </para>
+
+        <sect4 id="usage-create-action-display-menu">
+          <title>If your action targets a menu</title>
+          <para>
+            Whether your action targets the selection context menu or the location
+            context menu, and both in &nautilus; context menus that in 
+            <guimenu>File</guimenu> or <guimenu>Edit</guimenu> menus, your
+            action will be displayed as
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                the <guilabel>Context label</guilabel> as a label,
+              </para>
+              <para>
+                The label is a mandatory property of your action. If it happens
+                to be empty, then your action will be considered as invalid by
+                &prodname;, and will never be candidate to be displayed in the
+                file-manager context menus.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                the <guilabel>Icon</guilabel>,
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                associated with the <guilabel>Tooltip</guilabel>.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <note>
+            <para>
+              Depending of the exact configuration of your desktop environment,
+              the icon may or may not be displayed in front of the label in
+              the menu.
+            </para>
+          </note>
+          <tip>
+              <para>
+                You may embed some parameters in the label, the icon name of the tooltip.
+                These parameters will be dynamically substituted at runtime with values
+                which will depend of currently selected item(s). 
+              </para>
+          </tip>
+        </sect4>
+
+        <sect4 id="usage-create-action-display-toolbar">
+          <title>If your action targets the toolbar</title>
+          <para>
+            In the toolbar, your action will be displayed as
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                the <guilabel>Toolbar label</guilabel> as a label,
+              </para>
+              <tip>
+                <para>
+                  The toolbar label defaults to the same label than
+                  those used in menus. By unchecking the
+                  <guilabel>Use same label for icon in the toolbar</guilabel>
+                  checkbox, then you can define a label specific to the
+                  toolbar, usually shorter those defined for the menus.
+                </para>
+              </tip>
+            </listitem>
+            <listitem>
+              <para>
+                the <guilabel>Icon</guilabel>,
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                associated with the <guilabel>Tooltip</guilabel>.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <note>
+            <para>
+              Depending of the exact configuration of your desktop environment,
+              the toolbar label may or may not be displayed in front of the icon
+              in the toolbar.
+            </para>
+          </note>
+          <tip>
+              <para>
+                You may embed some parameters in the toolbar label, the icon name of the tooltip.
+                These parameters will be dynamically substituted at runtime with values
+                which will depend of currently selected item(s). 
+              </para>
+          </tip>
+        </sect4>
+
+        <sect4 id="usage-create-action-display-icon">
+          <title>Choosing an icon</title>
+          <para>
+            You have two ways of choosing the icon associated to your action.
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                Click on the dropdown list to select an icon among standard
+                themed icons of your desktop environment.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                Click on the <guibutton>Browse</guibutton> button to search 
+                for an image in the filesystem.
+              </para>
+            </listitem>
+          </itemizedlist>
+        </sect4>
       </sect3>
 
       <sect3 id="usage-create-action-when">
         <title>When the action will it be displayed ?</title>
         <para>
+          Whether your action is actually displayed in &nautilus; file-manager
+          context menus and toolbar depends of the conditions you will define
+          for it.
+        </para>
+        <para>
+          All defined conditions must be satisfied by the current file-manager
+          selection (resp. location) in order your action be displayed. 
         </para>
 
         <sect4 id="usage-create-action-when-basenames">
           <title>Basenames</title>
+          <figure id="nact-FIG-tab-basenames">
+            <title>Basename-based conditions</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-basenames-tab.png" format="PNG" />
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the tab which lets you define basename-based conditions.</phrase>
+                </textobject>
+                <caption>
+                  <para>The basename-based conditions tab</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
           <para>
+            You may define that your action will only appear depending on the basenames
+            of the items currently selected in the file-manager. You may define that each
+            item of the selection must meet some sort of condition; and you may simultaneously
+            decide that none of the selected item(s) can have some other sort of basename.
+          </para>
+          <para>
+            Defining a new basename-based condition involves only two simple steps.
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                Press <keycap>Insert</keycap> or click on 
+                <guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
+                button to insert a new condition filter
+              </para>
+              <tip>
+                <para>
+                  A condition may use &laquosp;<literal>*</literal>&spraquo; or
+                  &laquosp;<literal>?</literal>&spraquo; wildcard characters.
+                </para>
+              </tip>
+            </listitem>
+            <listitem>
+              <para>
+                Click on the <guilabel>Must match one of</guilabel> or
+                <guilabel>Must not match any of</guilabel> radio button in the same
+                row to set a &laquosp;must have&spraquo; or
+                &laquosp;must not have&spraquo; condition.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <para>
+            Depending of your target operating system, make sure that the
+            <guilabel>Match case</guilabel> checkbox is activated (or not). 
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                When activated, all filters are considered as case sensitive,
+                which means that <filename>/my/file</filename> filename is
+                considered distinct from <filename>My/File</filename> one.
+              </para>
+              <para>
+                This is the default behavior on Unix-like systems.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                When disactivated, filters are considered as case insensitive,
+                which means that <filename>/my/file</filename> and
+                <filename>My/File</filename> filenames are considered the same
+                name.
+              </para>
+              <para>
+                This is most probably what you want if you target some sort of
+                &windows; system.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <para>
+            When the action is examined to see if it should be displayed, the basename
+            of each currently selected item is compared to the list of these basename-based
+            conditions for this action.
+          </para>
+          <para>
+            By default, the basename-based condition is just one
+            &laquosp;<literal>must match *</literal>&spraquo; condition.
+            This means that basenames are not considered as a relevant condition
+            for the action.
           </para>
         </sect4>
 
         <sect4 id="usage-create-action-when-mimetypes">
           <title>Mimetypes</title>
+          <figure id="nact-FIG-tab-mimetypes">
+            <title>Mimetype-based conditions</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-mimetypes-tab.png" format="PNG"/>
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the tab which lets you define mimetype-based conditions.</phrase>
+                </textobject>
+                <caption>
+                  <para>The mimetype-based conditions tab</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
           <para>
+            You may define that your action will only appear depending on the mimetypes
+            of the items currently selected in the file-manager. You may define that each
+            item of the selection must meet some sort of condition; and you may simultaneously
+            decide that none of the selected item(s) can have some other sort of mimetype.
           </para>
+          <para>
+            Defining a new mimetype-based condition involves only two simple steps.
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                Press <keycap>Insert</keycap> or click on 
+                <guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
+                button to insert a new condition filter
+              </para>
+              <para>
+                A mimetype must be defined as a <literal>group/subgroup</literal>
+                group.
+              </para>
+              <para>
+                Some sort of wildcards are accepted.
+              </para>
+              <itemizedlist>
+                <listitem>
+                  <para>
+                    The &laquosp;<literal>*/*</literal>&spraquo; literal
+                    matches all mimetypes. As a convenient shortcut, the
+                    &laquosp;<literal>*</literal>&spraquo; literal is
+                    also accepted for the same purpose.
+                  </para>
+                </listitem>
+                <listitem>
+                  <para>
+                    A &laquosp;<literal>group/*</literal>&spraquo; string
+                    matches all subgroups of <literal>group</literal> mimetype.
+                  </para>
+                </listitem>
+              </itemizedlist>
+              <note>
+                <para>
+                  The &laquosp;<literal>*/subgroup</literal>&spraquo; string
+                  is not accepted as a valid wildcard.
+                </para>
+              </note>
+            </listitem>
+            <listitem>
+              <para>
+                Click on the <guilabel>Must match one of</guilabel> or
+                <guilabel>Must not match any of</guilabel> radio button in the same
+                row to set a &laquosp;must have&spraquo; or
+                &laquosp;must not have&spraquo; condition.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <para>
+            When the action is examined to see if it should be displayed, the mimetype
+            of each currently selected item is compared to the list of these mimetype-based
+            conditions for this action.
+          </para>
+          <para>
+            By default, the mimetype-based condition is just one
+            &laquosp;<literal>must match */*</literal>&spraquo; condition.
+            This means that mimetypes are not considered as a relevant condition
+            for the action.
+          </para>
+          <example>
+            <title>Example of usual mimetypes</title>
+            <variablelist>
+              <varlistentry>
+                <term>
+                  all/all
+                </term>
+                <listitem>
+                  <para>
+                    Matches all items.
+                  </para>
+                </listitem>
+              </varlistentry>
+              <varlistentry>
+                <term>
+                  all/allfiles
+                </term>
+                <listitem>
+                  <para>
+                    Matches all regular files.
+                  </para>
+                </listitem>
+              </varlistentry>
+              <varlistentry>
+                <term>
+                  inode/directory
+                </term>
+                <listitem>
+                  <para>
+                    Matches only directories.
+                  </para>
+                </listitem>
+              </varlistentry>
+            </variablelist>
+          </example>
         </sect4>
 
         <sect4 id="usage-create-action-when-folders">
           <title>Folders</title>
+          <figure id="nact-FIG-tab-folders">
+            <title>Folder-based conditions</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-folders-tab.png" format="PNG"/>
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the tab which lets you define folder-based conditions.</phrase>
+                </textobject>
+                <caption>
+                  <para>The folder-based conditions tab</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
+          <para>
+            You may define that your action will only appear depending on the directory
+            the items currently selected in the file-manager are located in.
+            You may define that each item of the selection must be located in one
+            hierarchy or in another; and you may simultaneously
+            decide that none of the selected item(s) can be located in some other
+            hierarchy.
+          </para>
           <para>
+            Defining a new folder-based condition involves only two simple steps.
           </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                Press <keycap>Insert</keycap> or click on 
+                <guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
+                button to insert a new condition filter, or click on
+                <guibutton>Browse</guibutton> to select a folder on the filesystem.
+              </para>
+              <para>
+                A folder-based condition must be understood as the specification
+                of the hierarchy in which the currently examined item should (or
+                should not) stay.
+              </para>
+              <note>
+                <para>
+                  The &laquosp;<literal>*</literal>&spraquo; and
+                  &laquosp;<literal>?</literal>&spraquo; characters
+                  are accepted as wildcards at any level of the defined
+                  folder filter.
+                </para>
+              </note>
+            </listitem>
+            <listitem>
+              <para>
+                Click on the <guilabel>Must match one of</guilabel> or
+                <guilabel>Must not match any of</guilabel> radio button in the same
+                row to set a &laquosp;must have&spraquo; or
+                &laquosp;must not have&spraquo; condition.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <para>
+            When the action is examined to see if it should be displayed, the location
+            of each currently selected item is compared to the list of these folder-based
+            conditions for this action.
+          </para>
+          <para>
+            By default, the folder-based condition is just one
+            &laquosp;<literal>must match /</literal>&spraquo; condition.
+            As <literal>/</literal> is always the top of an Unix-like filesystem,
+            then all selected files always match this condition.
+          </para>
+          <note>
+            <para>
+              If you target a &windows; system, then this default value may
+              not be what you actually want.
+            </para>
+          </note>
         </sect4>
 
         <sect4 id="usage-create-action-when-schemes">
           <title>Schemes</title>
+          <figure id="nact-FIG-tab-schemes">
+            <title>Scheme-based conditions</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-schemes-tab.png" format="PNG"/>
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the tab which lets you define scheme-based conditions.</phrase>
+                </textobject>
+                <caption>
+                  <para>The scheme-based conditions tab</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
+          <para>
+            You may define that your action will only appear depending on the schemes
+            of the URIs of the items currently selected in the file-manager.
+            You may define that each item of the selection must have some scheme;
+            and you may simultaneously
+            decide that none of the selected item(s) may have some other scheme.
+          </para>
           <para>
+            Defining a new scheme-based condition involves only two simple steps.
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                Press <keycap>Insert</keycap> or click on 
+                <guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
+                button to insert a new condition filter, or click on
+                <guibutton>Common</guibutton> to select a scheme among these
+                defined as default schemes in 
+                <menuchoice>
+                  <guimenu>Edit</guimenu>
+                  <guimenuitem>Preferences</guimenuitem>
+                </menuchoice>.
+              </para>
+              <para>
+                Scheme-based conditions only accept
+                &laquosp;<literal>*</literal>&spraquo; wildcard,
+                which stands for &laquosp;any scheme&spraquo;.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                Click on the <guilabel>Must match one of</guilabel> or
+                <guilabel>Must not match any of</guilabel> radio button in the same
+                row to set a &laquosp;must have&spraquo; or
+                &laquosp;must not have&spraquo; condition.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <para>
+            When the action is examined to see if it should be displayed, the
+            scheme of the URI
+            of each currently selected item is compared to the list of these
+            scheme-based conditions for this action.
+          </para>
+          <para>
+            By default, the folder-based condition is just one
+            &laquosp;<literal>must match *</literal>&spraquo; condition,
+            which means that schemes are not relevant for this action.
           </para>
         </sect4>
 
         <sect4 id="usage-create-action-when-capabilities">
           <title>Capabilities</title>
           <para>
+            Capabilities are some properties that a file may exhibit to the user.
+          </para>
+          <figure id="nact-FIG-add-capability">
+            <title>Managed capabilities</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-new-capability.png" format="PNG"/>
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the list of managed capabilities.</phrase>
+                </textobject>
+                <caption>
+                  <para>The list of managed capabilities</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
+          <para>
+            But the <literal>Local</literal> capability, all others are dependant
+            of the user who executes the command.
+          </para>
+          <figure id="nact-FIG-tab-capabilities">
+            <title>Capability-based conditions</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-capabilities-tab.png" format="PNG"/>
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the tab which lets you define capability-based conditions.</phrase>
+                </textobject>
+                <caption>
+                  <para>The capability-based conditions tab</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
+          <para>
+            You may so decide that your action will appear, or not, depending
+            on the capabilities of the selected item(s) <abbrev>vs.</abbrev>
+            the current user.
           </para>
+          <para>
+            Defining a new capability-based condition involves only two simple steps.
+          </para>
+          <itemizedlist>
+            <listitem>
+              <para>
+                Press <keycap>Insert</keycap> or click on 
+                <guibutton><inlinegraphic fileref="figures/add.png"/></guibutton>
+                button to insert a new condition filter.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                Click on the <guilabel>Must match one of</guilabel> or
+                <guilabel>Must not match any of</guilabel> radio button in the same
+                row to set a &laquosp;must have&spraquo; or
+                &laquosp;must not have&spraquo; condition.
+              </para>
+            </listitem>
+          </itemizedlist>
+          <para>
+            When the action is examined to see if it should be displayed, this list
+            of capabilities that selected item(s) must match (or not) is compared
+            to those exhibited to the user.
+          </para>
+          <para>
+            By default, the capability-based condition list is empty. This means
+            that capabilities are not relevant for this action.
+          </para>
+          <note>
+            <para>
+              If you target a &windows; system, then this default value may
+              not be what you actually want.
+            </para>
+          </note>
         </sect4>
 
         <sect4 id="usage-create-action-when-environment">
           <title>Environment</title>
-          <para>
-          </para>
+          <figure id="nact-FIG-tab-environment">
+            <title>Environment-based conditions</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-environment-tab.png" format="PNG"/>
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the tab which lets you define environment-based conditions.</phrase>
+                </textobject>
+                <caption>
+                  <para>The environment-based conditions tab</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
+
+          <sect5 id="usage-create-action-when-environment-count">
+            <title>Selection count</title>
+            <para>
+              You may define that your action will only appear if the current
+              selection in the file-manager has some precise count.
+            </para>
+            <example>
+              <title>A selection count use case</title>
+              <para>
+                If your action consists in displaying the difference between
+                two files, you may define here
+                <guilabel>Count = (equal to) 2</guilabel>.
+              </para>
+            </example>
+            <para>
+              To define a selection count condition
+            </para>
+            <itemizedlist>
+              <listitem>
+                <para>
+                  Select in the dropdown list the operator you want apply
+                  to the selection count
+                </para>
+                <simplelist type="vert">
+                  <member><literal>&lt; (strictly less than)</literal></member>
+                  <member><literal>= (equal to)</literal></member>
+                  <member><literal>&gt; (strictly greather than)</literal></member>
+                </simplelist>
+              </listitem>
+              <listitem>
+                <para>
+                  Enter the reference count you wish.
+                </para>
+              </listitem>
+            </itemizedlist>
+            <para>
+              The selection count defaults to
+              <guilabel>Count > (strictly greater than) 0</guilabel>
+              which means that the action will be candidate to be displayed
+              as soon as at least one item is selected in the file-manager.
+            </para>
+          </sect5>
+
+          <sect5 id="usage-create-action-when-environment-desktop">
+            <title>Desktop environment</title>
+            <para>
+              You may define that your action will only appear in some given
+              desktop environments, or, contrarily, will not appear in some
+              given desktop environments.
+            </para>
+            <para>
+              To define the desktop environment condition
+            </para>
+            <orderedlist>
+              <listitem>
+                <para>
+                  First select the type of filter
+                </para>
+                <simplelist type="vert">
+                  <member>does your action should always appear, regarding of
+                   the desktop environment ?</member>
+                  <member>does your action should also appear in some desktop
+                   environment(s) ?</member>
+                  <member>does your action should never appeat in some
+                   desktop environment(s) ?</member>
+                </simplelist>
+              </listitem>
+              <listitem>
+                <para>
+                  If your action does not should always appear, then
+                  select the relevant desktop environment(s) in the listbox
+                  in the right side.
+                </para>
+              </listitem>
+            </orderedlist>
+            <para>
+              The target desktop environment condition defaults to
+              <guilabel>Always appear</guilabel>
+              which means that the action will be candidate to be displayed
+              regarding of the current desktop environment.
+            </para>
+          </sect5>
+
+          <sect5 id="usage-create-action-when-environment-executable">
+            <title>Presence of an executable</title>
+            <para>
+              You may define that your action will only appear in some given
+              file is present on the filesystem and is executable.
+            </para>
+            <para>
+              To define the relevant file, enter its full filename in the
+              <guilabel>Appears if the file is executable</guilabel> entry
+              box, or click on <guibutton>Browse</guibutton> to select a file
+              on the filesystem.
+            </para>
+            <para>
+              Leave the field empty if this condition is not relevant for
+              your action.
+            </para>
+            <tip>
+              <para>
+                You may embed some parameters in the searched filename or its options.
+                These parameters will be dynamically substituted at runtime with values
+                which will depend of currently selected item(s). 
+              </para>
+            </tip>
+          </sect5>
+
+          <sect5 id="usage-create-action-when-environment-dbus">
+            <title>D-Bus-registered name</title>
+            <para>
+              You may define that your action will only appear in some given
+              name is registered on D-Bus system at runtime.
+            </para>
+            <para>
+              To define the relevant name, enter it in the
+              <guilabel>Appears if the name is registered on D-Bus</guilabel>
+              entry box.
+            </para>
+            <para>
+              Leave the field empty if this condition is not relevant for
+              your action.
+            </para>
+            <tip>
+              <para>
+                You may embed some parameters in the searched name.
+                These parameters will be dynamically substituted at runtime with values
+                which will depend of currently selected item(s). 
+              </para>
+            </tip>
+          </sect5>
+
+          <sect5 id="usage-create-action-when-environment-true">
+            <title>Customized condition</title>
+            <para>
+              You may define that your action will only appear in some given
+              command outputs a <literal>true</literal> string.
+            </para>
+            <para>
+              This lets you define your own customized condition filter,
+              by writing a small script which outputs, or not, the
+              <literal>true</literal> string when it is ran.
+            </para>
+            <para>
+              To define the command, enter it in the
+              <guilabel>Appears if the command outputs "true"</guilabel>
+              entry box.
+            </para>
+            <para>
+              Leave the field empty if this condition is not relevant for
+              your action.
+            </para>
+            <tip>
+              <para>
+                You may embed some parameters in the executed filename or its options.
+                These parameters will be dynamically substituted at runtime with values
+                which will depend of currently selected item(s). 
+              </para>
+            </tip>
+          </sect5>
+
+          <sect5 id="usage-create-action-when-environment-run">
+            <title>Running process</title>
+            <para>
+              You may define that your action will only appear in some given
+              binary is currently running.
+            </para>
+            <para>
+              To define the binary, enter its name in the
+              <guilabel>Appears if the binary is running</guilabel>
+              entry box, or click on <guibutton>Browse</guibutton> to select
+              a file on the filesystem.
+            </para>
+            <note>
+              <para>
+                Even if you enter here the full filename of a binary, only
+                its basename will be searched for in the processes list
+                at runtime.
+              </para>
+            </note>
+            <para>
+              Leave the field empty if this condition is not relevant for
+              your action.
+            </para>
+            <tip>
+              <para>
+                You may embed some parameters in the searched name.
+                These parameters will be dynamically substituted at runtime with values
+                which will depend of currently selected item(s). 
+              </para>
+            </tip>
+          </sect5>
         </sect4>
 
       </sect3>
+      <!-- end of sect3 - conditions section -->
 
       <sect3 id="usage-create-action-what">
         <title>What the action should it execute ?</title>
         <para>
+          You most probably want your action eventually ends up with
+          executing something. As a matter of fact, having something
+          to execute is one of the few conditions which are required
+          in order an action be considered as valid.
+        </para>
+        <para>
+          Enter the command you wish to execute in the <guilabel>Path</guilabel>
+          entry box. Or click on <guibutton>Browse</guibutton> to
+          select a file on the filesystem.
+        </para>
+        <para>
+          Enter the parameters of your command in the
+          <guilabel>Parameters</guilabel> entry box.
+        </para>
+        <para>
+          The <guibutton>Legend</guibutton> button has a toggling action:
+          click once to display the <guilabel>Parameter Legend</guilabel>
+          dialog box; click a second time to hide it.
         </para>
+          <figure id="nact-FIG-legend">
+            <title>List of available parameters</title>
+            <screenshot>
+              <mediaobject>
+                <imageobject>
+                  <imagedata fileref="figures/nact-legend.png" format="PNG"/>
+                </imageobject>
+                <textobject>
+                  <phrase>Shows the list of available parameters.</phrase>
+                </textobject>
+                <caption>
+                  <para>The available parameters</para>
+                </caption>
+              </mediaobject>
+            </screenshot>
+          </figure>
+        <note>
+          <para>
+            That the <guilabel>Path</guilabel> and <guilabel>Parameters</guilabel>
+            fields be separated is only a matter of making easier to set up the
+            data.
+          </para>
+          <para>
+            If you do not use, by example, the <guibutton>Browse</guibutton> button,
+            you may perfectly enter the path of the command along with its parameters
+            in any of the <guilabel>Path</guilabel> or <guilabel>Parameters</guilabel>
+            entry boxes (but not in both), as long as you take care of separating them
+            by at least one space.
+          </para>
+        </note>
       </sect3>
 
-      <sect3 id="usage-create-action-how">
-        <title>How the action should it be executed ?</title>
+      <sect3 id="usage-create-action-work">
+        <title>Where the action should it be executed ?</title>
+        <para>
+          Your action may be executed in a particular working directory.
+          You may specify it in the <guilabel>Command</guilabel> tab, in the
+          <guilabel>Working directory</guilabel> entry box, or by clicking
+          on <guibutton>Browse</guibutton> to select a folder on the 
+          filesystem.
+        </para>
         <para>
+          The working directory defaults to <literal>%d</literal>, which runs
+          the command in the base directory of the first selected item.
         </para>
       </sect3>
 
+      <sect3 id="usage-create-action-how">
+        <title>How the action should it be executed ?</title>
+        <figure id="nact-FIG-execution">
+          <title>Configuration of the execution mode</title>
+          <screenshot>
+            <mediaobject>
+              <imageobject>
+                <imagedata fileref="figures/nact-execution-tab.png" format="PNG"/>
+              </imageobject>
+              <textobject>
+                <phrase>Shows how to configure the execution mode of a command.</phrase>
+              </textobject>
+              <caption>
+                <para>Configuration of the execution mode</para>
+              </caption>
+            </mediaobject>
+          </screenshot>
+        </figure>
+
+        <sect4 id="usage-create-action-how-mode">
+          <title>Specifying the execution mode</title>
+          <para>
+            The execution mode of your command may be choosen between following 
+            values:
+          </para>
+          <variablelist>
+            <varlistentry>
+              <term>
+                Normal
+              </term>
+              <listitem>
+                <para>
+                  Starts the command as a standard graphical user interface.
+                </para>
+              </listitem>
+            </varlistentry>
+            <varlistentry>
+              <term>
+                Terminal
+              </term>
+              <listitem>
+                <para>
+                  Starts the preferred terminal of the desktop environment,
+                  and runs the command in it.
+                </para>
+              </listitem>
+            </varlistentry>
+            <varlistentry>
+              <term>
+                Embedded
+              </term>
+              <listitem>
+                <para>
+                  Makes use of a special feature of the file manager which may allow
+                  a terminal to be ran in it.
+                </para>
+                <para>
+                  As &nautilus; does not have this feature, this option is strictly
+                  equivalent to <literal>Terminal</literal> option.
+                </para>
+              </listitem>
+            </varlistentry>
+            <varlistentry>
+              <term>
+                Display output
+              </term>
+              <listitem>
+                <para>
+                  Starts the preferred terminal of the desktop environment, and
+                  runs the command in it. At end, standard streams (stdout, stderr) 
+                  are collected and displayed.
+                </para>
+              </listitem>
+            </varlistentry>
+          </variablelist>
+          <para>
+            The execution mode of a command defaults to <literal>Normal</literal>.
+            That is, the command is executed without any particular pre- or
+            post-work.
+          </para>
+        </sect4>
+
+        <sect4 id="usage-create-action-how-notify">
+          <title>Specifying the startup notification</title>
+          <para>
+            If the execution mode of the command is actually <literal>Normal</literal>,
+            and if you know that the application will send a <literal>remove</literal>
+            message with the <envar>DESKTOP_STARTUP_ID</envar> environment variable set,
+            then check the <guilabel>Startup notify</guilabel> checkbox.
+          </para>
+          <para>
+            See the
+            <ulink url="http://www.freedesktop.org/Standards/startup-notification-spec"; type="http">
+            <citetitle>Startup Notification Protocol Specification</citetitle></ulink>
+            for more details.
+          </para>
+        </sect4>
+
+        <sect4 id="usage-create-action-how-class">
+          <title>Specifying the window class</title>
+          <para>
+            If the execution mode of the command is actually <literal>Normal</literal>,
+            and if you know that the application will map at least one window with a
+            given class name,
+            then enter that name into the <guilabel>Startup Window Manager class</guilabel>
+            entry box.
+          </para>
+          <para>
+            See the
+            <ulink url="http://www.freedesktop.org/Standards/startup-notification-spec"; type="http">
+            <citetitle>Startup Notification Protocol Specification</citetitle></ulink>
+            for more details.
+          </para>
+        </sect4>
+
+        <sect4 id="usage-create-action-how-user">
+          <title>Specifying the owner of the execution</title>
+          <para>
+            Enter in the <guilabel>Execute as user</guilabel> entry box the username
+            or the <acronym>UID</acronym> of the user your command must be ran as.
+          </para>
+          <para>
+            If you do not enter anything in this field, then the command will be
+            executed as the current user.
+          </para>
+        </sect4>
+
+        <sect4 id="usage-create-action-how-singular">
+          <title>Singular <abbrev>vs.</abbrev> plural forms</title>
+          <para>
+          </para>
+        </sect4>
+      </sect3>
+
     </sect2>
     <!-- end of creating an action -->
 
@@ -168,188 +1178,17 @@
       </para>
     </sect2>
 
-    <sect2 id="usage-import">
-      <title>Importing</title>
-      <para>
-      </para>
-    </sect2>
-
     <sect2 id="usage-export">
       <title>Exporting</title>
       <para>
       </para>
     </sect2>
-    
-      <!--
-        The <application>Select Movies or Playlists</application> dialog is displayed.
-      </para>
-      <para>You can drag a file from another application such as a file manager to the
-        <application>
-&appname;        </application> window. If you drag the file to the display area, the file will replace the current
-        playlist and will start playing immediately. If you drag the file to the playlist in the sidebar, the file will be
-        appended to the current playlist. The <application>
-&appname;        </application> application
-        will open the file and play the movie or song. <application>
-&appname;        </application>
-        displays the title of the movie or song in the titlebar of
-        the window and in the playlist in the sidebar.
-      </para>
-      <para>If you try to open a file format that <application>
-&appname;        </application> does
- not recognize, the application displays an error message. This error is most often encountered
- if you do not have the correct codecs installed. Information on getting codecs working can be found on
- the <ulink url="http://projects.gnome.org/totem/#codecs"; type="http"><application>
-&appname;          </application> website</ulink>.
+
+    <sect2 id="usage-import">
+      <title>Importing</title>
+      <para>
       </para>
     </sect2>
-      
-  Select the file or files you want to open, then click
- <guibutton>OK</guibutton>.
-
-      <para>To pause a movie or song that is playing, click on the
-        <inlinemediaobject>
-          <imageobject>
-            <imagedata fileref="figures/totem_pause_button.png" format="PNG"/>
-          </imageobject>
-          <textobject>
-            <phrase>Shows pause button.</phrase>
-          </textobject>
-        </inlinemediaobject> button, or choose
-        <menuchoice>
-          <shortcut>
-            <keycombo>
-              <keycap>Ctrl</keycap>
-              <keycap>Space</keycap>
-            </keycombo>
-          </shortcut>
-          <guimenu>Movie</guimenu>
-          <guimenuitem>Play / Pause</guimenuitem>
-        </menuchoice>. You may also use the <keycap>P</keycap> key to pause or play a movie.
-      </para>
-    
-    <sect2 id="totem-usage-change-zoom">
-      <title>To Change the Zoom Factor</title>
-      <sect3 id="totem-usage-change-size">
-        <title>To Change the Video Size</title>
-        <para>To change the zoom factor of the display area, you can use the
-        following methods:
-      </para>
-        <itemizedlist>
-          <listitem>
-            <para>To zoom to fullscreen mode, choose
-   <menuchoice>
-                <shortcut>
-                  <keycap>F11</keycap>
-                </shortcut>
-                <guimenu>View</guimenu>
-                <guimenuitem>Fullscreen</guimenuitem>
-              </menuchoice>. You can also
-   use the <keycap>F</keycap> key to toggle fullscreen mode.
-   To exit fullscreen mode, click on the
-   <guibutton>Leave Fullscreen</guibutton> button or press
-   <keycap>Esc</keycap>, <keycap>F11</keycap> or <keycap>F</keycap>.
-          </para>
-          </listitem>
-          <listitem>
-            <para>To change the size of the original movie or visualization,
-            choose
-            <menuchoice>
-                <shortcut>
-                  <keycombo>
-                    <keycap>Ctrl</keycap>
-                    <keycap>0</keycap>
-                  </keycombo>
-                </shortcut>
-                <guimenu>View</guimenu>
-                <guimenuitem>Fit Window to Movie</guimenuitem>
-              </menuchoice> and choose a scale ratio.
-      </para>
-          </listitem>
-        </itemizedlist>
-      </sect3>
-
-        <para>By default, <application>
-&appname;          </application> will choose the same language for the
-   subtitles as the one you normally use on your computer.</para>
-      </note>
-      <para><application>
-&appname;        </application> will automatically load and display subtitles for a video if it finds a subtitle file with the
-   same name as the video being played, and the extension <filename class="extension">asc</filename>, <filename class="extension">txt</filename>,
-   <filename class="extension">sub</filename>, <filename class="extension">srt</filename>, <filename class="extension">smi</filename>,
-   <filename class="extension">ssa</filename> or <filename class="extension">ass</filename>.
-   </para>
-   
-      <para>With the <guilabel>Coherence DLNA/UPnP Client</guilabel> plugin enabled, choose
-
-    <sect2 id="totem-plugins-gromit">
-      <title>Gromit Annotations</title>
-      <para>The <guilabel>Gromit Annotations</guilabel> plugin allows you to draw on top of movies as they are played using
-        <ulink url="http://www.home.unix-ag.org/simon/gromit/"; type="http">
-          <application>Gromit</application>
-        </ulink>. You must have
-
-      <title>Jamendo</title>
-      <para>The <guilabel>Jamendo</guilabel> plugin allows you to listen to the collection of Creative Commons-licensed music on the
-        <ulink url="http://www.jamendo.com/en/"; type="http">Jamendo</ulink> service.</para>
-      <sect3 id="totem-plugins-jamendo-configuration">
-        <title>To Configure the Plugin</title>
-        <para>The <guilabel>Jamendo</guilabel> plugin can be configured. Click on the <guibutton>Configure</guibutton> button when enabling the plugin,
-          and the <application>Jamendo Plugin Configuration</application> dialog will be displayed. Here, you can choose whether to download songs in Ogg or
-          MP3 format (Ogg is preferred due to its open-source nature); and the number of albums to retrieve when doing a search (choose more albums if
-          you have a faster Internet connection).</para>
-        <para>Once you&apos;re done, click <guibutton>OK</guibutton>.</para>
-      </sect3>
-      <sect3 id="totem-plugins-jamendo-setup">
-        <title>To Display the Jamendo Sidebar</title>
-        <para>With the <guilabel>Jamendo</guilabel> plugin enabled, choose
-          <menuchoice>
-            <shortcut>
-              <keycap>F9</keycap>
-            </shortcut>
-            <guimenu>View</guimenu>
-            <guimenuitem>Sidebar</guimenuitem>
-          </menuchoice> or click on the
-          <guibutton>Sidebar</guibutton> button to show the sidebar. Select <guilabel>Jamendo</guilabel> from the drop-down list at the top of the sidebar
-          to display the <guilabel>Jamendo</guilabel> sidebar.</para>
-      </sect3>
-      <sect3 id="totem-plugins-jamendo-search">
-        <title>To Search for Music</title>
-        <para>Enter your search terms in the search entry at the top of the <guilabel>Jamendo</guilabel> sidebar. You can search by either artist or
-          by tags. Click on the search button to start your search.</para>
-        <para>Search results will be displayed in the tree view in the <guilabel>Search Results</guilabel> page of the sidebar, and can be browsed
-          through using the arrow buttons at the bottom of the sidebar. Albums are listed, and if you click on an album, its tracks will be listed
-          below it. Click again to hide the album&apos;s tracks.</para>
-        <para>With an artist selected, you can click on the <guibutton>Jamendo Album Page</guibutton> button to open that album&apos;s page on the
-          Jamendo website. Double-clicking an album, or choosing <menuchoice>
-            <guimenuitem>Add to Playlist</guimenuitem>
-          </menuchoice> from the album&apos;s
-          context menu, will replace your playlist with all the tracks on that album and begin streaming the first track from Jamendo&apos;s website.
-          Double-clicking an individual track will replace your playlist with just that track.</para>
-      </sect3>
-      <sect3 id="totem-plugins-jamendo-popular">
-
-    <sect2 id="totem-plugins-publish">
-      <title>Publish Playlist</title>
-      <para>The <guilabel>Publish Playlist</guilabel> plugin allows you to publish playlists on your local network to allow other computers to access
-        and play them.</para>
-      <sect3 id="totem-plugins-publish-configuration">
-        <title>To Configure the Plugin</title>
-        <para>The <guilabel>Publish Playlist</guilabel> plugin can be configured. Click on the <guibutton>Configure</guibutton> button when enabling the
-          plugin, and the configuration dialog will be displayed. Here, you can change the name which will appear for your playlist share. The following
-          strings will be replaced when playlists are published:
-          <variablelist>
-            <varlistentry>
-              <term>
-                <literal>%a</literal>
-              </term>
-              <listitem>
-                <para>Replaced with the program&apos;s name: <application>
-&appname;                  </application>.</para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
- </para>
-      -->
 
   </sect1>
   <!-- end of sect1 - using nautils-actions-config-tool -->
diff --git a/doc/nact/C/nautilus-actions-config-tool.xml b/doc/nact/C/nautilus-actions-config-tool.xml
index 2596163..2256c22 100644
--- a/doc/nact/C/nautilus-actions-config-tool.xml
+++ b/doc/nact/C/nautilus-actions-config-tool.xml
@@ -11,14 +11,21 @@
   <!ENTITY manrevision "3.0">
   <!ENTITY mandate "August 2010">
 
+  <!-- product name used -->
   <!ENTITY nautilus "<productname>Nautilus</productname>">
-  
+  <!ENTITY windows  "<productname>Windows</productname>">
+
+  <!-- the synopsys of the document -->
   <!ENTITY articleinfo SYSTEM "articleinfo.xml">
+  <!ENTITY legalnotice SYSTEM "legalnotice.xml">
   <!ENTITY usage       SYSTEM "nact-usage.xml">
   <!ENTITY preferences SYSTEM "nact-prefs.xml">
   <!ENTITY misc-infos  SYSTEM "nact-misc.xml">
-  <!ENTITY legalnotice SYSTEM "legalnotice.xml">
   <!ENTITY gnu-fdl     SYSTEM "appendix-gnu-fdl-1.3.xml">
+
+  <!-- some user-defined internal entities -->
+  <!ENTITY laquosp "&laquo;&nbsp;">
+  <!ENTITY spraquo "&nbsp;&raquo;">
 ]>
 
 <!-- ========================= Document Header ======================== -->
@@ -67,7 +74,7 @@
         <para>Import and export actions and menus from and to outside world.</para>
       </listitem>
     </itemizedlist>
-    <tip>
+    <note>
       <para>
         &prodname; also comes with additional features such as:
       </para>
@@ -84,7 +91,8 @@
           </para>
           <para>
             Associated with the D-Bus interface, this program lets the user
-            run any action from a keyboard shortcut.
+            run any action from a keyboard shortcut, applying this action
+            to the item(s) currently selected in the file manager.
           </para>
         </listitem>
         <listitem>
@@ -94,10 +102,10 @@
         </listitem>
       </itemizedlist>
       <para>
-        All these features are more throughly described in the global
+        All these features are more thoroughly described in the global
         &prodname; documentation.
       </para>
-    </tip>
+    </note>
   </sect1>
 
 <!-- ========================= Getting Started ======================== -->
@@ -111,7 +119,7 @@
 
   <sect1 id="getting-started">
     <title>Getting Started</title>
-    
+
     <sect2 id="getting-started-starting">
       <title>Starting &appname;</title>
       <para>
@@ -126,8 +134,7 @@
               <menuchoice>
                 <guisubmenu>Preferences</guisubmenu>
                 <guimenuitem>Look and Feel</guimenuitem>
-              </menuchoice>
-              .
+              </menuchoice>.
             </para>
           </listitem>
         </varlistentry>
@@ -139,12 +146,20 @@
               then press <keycap>Return</keycap>:
             </para>
             <para>
-              <command>nautilus-actions-config-tool</command>
+              <command><filename>nautilus-actions-config-tool</filename></command>
             </para>
             <tip>
               <para>
                 To view other command line options that are available,
-                type <command>nautilus-actions-config-tool --help-all</command>,
+                type
+              </para>
+              <para>
+                <command>
+                  <filename>nautilus-actions-config-tool</filename>
+                  <option>--help-all</option>
+                </command>
+              </para>
+              <para>
                 then press <keycap>Return</keycap>.
               </para>
             </tip>
@@ -152,7 +167,7 @@
         </varlistentry>
       </variablelist>
     </sect2>
-    
+
     <sect2 id="getting-started-first-run">
       <title>The first run</title>
       <para>
@@ -166,7 +181,12 @@
               <imagedata fileref="figures/nact-main-empty.png" format="PNG"/>
             </imageobject>
             <textobject>
-              <phrase> Shows &appname; main window. Contains menubar, display area, an empty items list in the left, several disabled properties tab, and statusbar. </phrase>
+              <phrase>
+                Shows &appname; main window.
+                Contains menubar, toolbar, display area,
+                an empty items list in the left, several disabled properties tabs,
+                and statusbar.
+              </phrase>
             </textobject>
             <caption>
               <para>The empty &appname; main window</para>
@@ -282,7 +302,7 @@
                 </term>
                 <listitem>
                   <para>
-                    Insert the content of the clipboard as subitems of the current item.
+                    Insert the content of the clipboard as subitem(s) of the current item.
                   </para>
                 </listitem>
               </varlistentry>
@@ -327,6 +347,19 @@
           </listitem>
         </varlistentry>
         <varlistentry>
+          <term>Toolbar.</term>
+          <listitem>
+            <para>
+              Several toolbars may be displayed below the menubar, depending of
+              your choices in the
+              <menuchoice>
+                <guimenu>View</guimenu>
+                <guimenuitem>Toolbars</guimenuitem>
+              </menuchoice> submenu.
+            </para>
+          </listitem>
+        </varlistentry>
+        <varlistentry>
           <term>Items list.</term>
           <listitem>
             <para>
@@ -458,7 +491,7 @@
                 </term>
                 <listitem>
                   <para>
-                    Display items properties.
+                    Display item properties.
                   </para>
                 </listitem>
               </varlistentry>
diff --git a/doc/nact/Makefile.am b/doc/nact/Makefile.am
index 5ee24c3..e38242a 100644
--- a/doc/nact/Makefile.am
+++ b/doc/nact/Makefile.am
@@ -48,6 +48,8 @@ DOC_INCLUDES = \
 	$(NULL)
 
 DOC_FIGURES = \
+	figures/add.png								\
+	figures/remove.png							\
 	figures/nact-basenames-tab.png				\
 	figures/nact-capabilities-tab.png			\
 	figures/nact-command-tab.png				\



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]