Changeset 259 for trunk

Timestamp:

Jul 15, 2011, 11:32:36 AM (13 years ago)

Author:

djay

Message:

Small fix for zcfg syntaxe hightlighting, small fixes some typos in JS doc.

Location:

trunk/docs

Files:

• api/examples.txt (modified) (2 diffs)
• services/zcfg-reference.txt (modified) (3 diffs)

trunk/docs/api/examples.txt

@@ -21 +21 @@
   }
 
-In this really short example you can see how to create ZOO.Process class instance and 
+In this really short example you can see how to create ``ZOO.Process`` class instance and 
 call the Execute method on such an instance. Then you'll just need to return a JavaScript 
 object containing the attributes result and outputs, which I'm sure you already know 
-what is about. The first is about the status of the process (can be ZOO.SERVICE_SUCEEDED,
-ZOO.SERVICE_FAILED and so on), the last is obviously the resulting maps (take a 
-look at the maps internal data structure used by ZOO Kernel in service.h).
+what is about. The first is about the status of the process (can be ``ZOO.SERVICE_SUCEEDED``,
+``ZOO.SERVICE_FAILED`` and so on), the last is obviously the resulting maps (take a 
+look at the maps internal data structure used by ZOO Kernel in ``service.h``).
 
 ZOO.UpdateStatus
@@ -48 +48 @@
   }
 
-You can see in this sample code how to use the ZOOUpdateStatus function to update the 
+You can see in this sample code how to use the ``ZOOUpdateStatus`` function to update the 
 current status of your running process. This information will be really helpfull when the 
-ZOO Kernel will run your JavaScript Service in background mode (if the user set to true 
-the storeExecuteResponse parameter in his request).
+ZOO Kernel will run your JavaScript Service in background mode (if the user set to ``true`` 
+the ``storeExecuteResponse`` parameter in his request).
 

trunk/docs/services/zcfg-reference.txt

@@ -31 +31 @@
 You can see below a description of the main metadata information:
 
-.. code-block:: guess
+.. code-block:: none
    :linenos:
 
@@ -59 +59 @@
 A typical list of inputs (``<DataInputs>``) look like the following:
 
-.. code-block:: guess
+.. code-block:: none
    :linenos:
    
@@ -86 +86 @@
 A typical ``<DataOutputs>`` node looks like the following:
 
-.. code-block:: guess
+.. code-block:: none
    :linenos: