Repository :
http://git.fedorahosted.org/cgit/cura-tools.git
On branch : master
---------------------------------------------------------------
commit dd808f0b22cae7fac20e3e828bec500186a5d4f3
Author: Michal Minar <miminar(a)redhat.com>
Date: Mon Oct 6 16:45:35 2014 +0200
doc: wrap text in one table
Several rows in a dictionary table contain quite a long text. Without
being treated as a block, the text won't get wrapped causing the table
to be equipped with scrollbars.
---------------------------------------------------------------
doc/src/scripts/development.txt | 67 +++++++++++++++++++--------------------
1 files changed, 33 insertions(+), 34 deletions(-)
diff --git a/doc/src/scripts/development.txt b/doc/src/scripts/development.txt
index 032f29d..c4cb836 100644
--- a/doc/src/scripts/development.txt
+++ b/doc/src/scripts/development.txt
@@ -14,40 +14,39 @@ metacommand* and a package (rpm/python egg) containing it. In this
documentation you'll encounter another words seemingly meaning the same.
Following dictionary tries to clear out any confusion:
-
+-----------------------+----------------------------------------------------------------+
- | Term | Description
|
-
+=======================+================================================================+
- | *command* | Either a subcommand of *LMI metacommand* or a software
|
- | | package containing a *script*. It may have several
|
- | | *subcommands*.
|
-
+-----------------------+----------------------------------------------------------------+
- | *script* | Python library utilizing :ref:`lmi_shell` for instrumenting
|
- | | CIM providers through a CIMOM broker comming with one
|
- | | or more *commands* for *LMI metacommand*.
|
-
+-----------------------+----------------------------------------------------------------+
- | *subcommand* | Same as *command* used in relation to either
|
- | | *metacommand* or another *command*.
|
-
+-----------------------+----------------------------------------------------------------+
- | *command wrapper* | Implementation of a *command* in a *script* as a subclass of
|
- | | :py:class:`~lmi.scripts.common.command.base.LmiBaseCommand`.
|
-
+-----------------------+----------------------------------------------------------------+
- | *top-level command* | Direct *subcommand* of *LMI metacommand*. It appers in its
|
- | | help message.
|
-
+-----------------------+----------------------------------------------------------------+
- | *end-point command* | *command* without any *subcommand*. It handles command-line
|
- | | arguments and renders output.
|
-
+-----------------------+----------------------------------------------------------------+
- | *command multiplexer* | *command* with one or more *subcommands*. They do not handle
|
- | | command line arguments.
|
-
+-----------------------+----------------------------------------------------------------+
- | *command name* | Is a single word denoting *command* on a command line.
|
-
+-----------------------+----------------------------------------------------------------+
- | *command's full name* | All *command names* leading up to the *command*
optionally |
- | | including the ``lmi``. For example in statement
|
- | | ``lmi -h
myhost.example.org storage fs create ext4
/dev/vda5`` |
- | | the full name of *command* ``create`` is
|
- | | ``lmi storage fs create``.
|
-
+-----------------------+----------------------------------------------------------------+
+
+-----------------------+------------------------------------------------------------------+
+ | Term | Description
|
+
+=======================+==================================================================+
+ | *command* | | Either a subcommand of *LMI metacommand* or a software
package |
+ | | containing a *script*. It may have several *subcommands*.
|
+
+-----------------------+------------------------------------------------------------------+
+ | *script* | | Python library utilizing :ref:`lmi_shell` for instrumenting
|
+ | | CIM providers through a CIMOM broker comming with one
|
+ | | or more *commands* for *LMI metacommand*.
|
+
+-----------------------+------------------------------------------------------------------+
+ | *subcommand* | | Same as *command* used in relation to either
|
+ | | *metacommand* or another *command*.
|
+
+-----------------------+------------------------------------------------------------------+
+ | *command wrapper* | | Implementation of a *command* in a *script* as a subclass
of |
+ | |
:py:class:`~lmi.scripts.common.command.base.LmiBaseCommand`. |
+
+-----------------------+------------------------------------------------------------------+
+ | *top-level command* | | Direct *subcommand* of *LMI metacommand*. It appers in its
|
+ | | help message.
|
+
+-----------------------+------------------------------------------------------------------+
+ | *end-point command* | | *command* without any *subcommand*. It handles command-line
|
+ | | arguments and renders output.
|
+
+-----------------------+------------------------------------------------------------------+
+ | *command multiplexer* | | *command* with one or more *subcommands*. They do not
handle |
+ | | command line arguments.
|
+
+-----------------------+------------------------------------------------------------------+
+ | *command name* | | Is a single word denoting *command* on a command line.
|
+
+-----------------------+------------------------------------------------------------------+
+ | *command's full name* | | All *command names* leading up to the *command*
optionally |
+ | | including the ``lmi``. For example in statement
|
+ | | ``lmi -h
myhost.example.org storage fs create ext4
/dev/vda5`` |
+ | | the full name of *command* ``create`` is
|
+ | | ``lmi storage fs create``.
|
+
+-----------------------+------------------------------------------------------------------+
.. only:: html