*** empty log message ***

svn path=/trunk/boinc/; revision=4654

doc/app.php

@@ -3,9 +3,9 @@ require_once("docutil.php");
 page_head("Applications and versions");
 echo "
 <p>
-An <b>application</b> represents a particular distributed computation;
+An <b>application</b> represents a collection of related computation.
-it consists of a program (perhaps with versions for different platforms)
+It consists of a program (perhaps with versions for different platforms)
-and a set of workunits and results.
+and a set of <a href=work.php>workunits</a> and <a href=result.php>results</a>.
 A project can operate many applications. 
 Applications are maintained in the <b>application</b> table in the BOINC DB,
 and can be created using the <a href=tool_xadd.php>xadd</a> utility. 
@@ -16,15 +16,16 @@ An application program may go through a sequence of
 A particular version, compiled for a particular platform, is
 called an <b>application version</b>. 
 An application version can consist of multiple files: for example, a
-controller script, pre- and post-processing programs, and a primary executable.
+controller script, pre- and post-processing programs, and a primary program.
 
 <p>
 Each application version has an integer <b>version number</b>.
-Projects can assign version numbers however they like; for example,
+This number is of the form 100*major + minor;
-version 304 might represent major version 3 and minor version 4. 
+for example, 304 represents major version 3 and minor version 4. 
+An application version will only run on a core client
+having the same major version.
 Version numbers should be used consistently across platforms;
-Windows version 304 should be computationally identical to
+Windows version 304 should be computationally identical to Mac version 304. 
-Mac version 304. 
 
 <p>
 Each application has a <b>minimum version</b>. 
@@ -37,22 +38,22 @@ Application versions are maintained in the <b>app_version</b> table
 in the BOINC DB.
 Each entry includes an XML document describing the
 files that make up the application version: 
-<pre>
+<pre>".htmlspecialchars("
-&lt;file_info&gt; ... 
+<file_info>
-&lt;/file_info&gt;
+   ... 
-[ ... 
+</file_info>
-]
+[ ... ]
-&lt;app_version&gt;
+<app_version>
-    &lt;app_name&gt;foobar&lt;/app_name&gt;
+    <app_name>foobar</app_name>
-    &lt;version_num&gt;4&lt;/version_num&gt;
+    <version_num>4</version_num>
-    &lt;file_ref&gt;
+    <file_ref>
-        &lt;file_name&gt;program_1&lt;/file_name&gt;
+        <file_name>program_1</file_name>
-        &lt;main_program/&gt;
+        <main_program/>
-    &lt;/file_ref&gt;
+    </file_ref>
-    &lt;file_ref&gt;
+    <file_ref>
-        &lt;file_name&gt;library_12&lt;/file_name&gt;
+        <file_name>library_12</file_name>
-    &lt;/file_ref&gt;
+    </file_ref>
-&lt;/app_version&gt;
+</app_version>")."
 </pre>
 Application versions can be created using
 <a href=tool_update_versions.php>update_versions</a>.

doc/work.php

@@ -4,7 +4,7 @@ page_head("Workunits");
 echo "
 <p>
 A <b>workunit</b> describes a computation to be performed.
-The basic workunit attributes include:
+Its attributes include:
 ";
 
 list_start();
@@ -14,10 +14,10 @@ list_item(
 );
 list_item(
     "application",
-    "Which application performs the computation.
+    "Which <a href=app.php>application</a> will perform the computation.
-    A workunit is associated with an application, not with a particular
+    A workunit is associated with an application,
-    version or range of versions.
+	not with a particular version or range of versions.
-    If the format of your input data changes in
+    If the input data format changes in
     a way that is incompatible with older versions,
     you must create a new application.
     This can often be avoided by using XML data format. "