[Zope-CVS] CVS: Packages/JobBoardEx - Tutorial.html:1.15

[Guido van Rossum]

Update of /cvs-repository/Packages/JobBoardEx
In directory cvs.zope.org:/tmp/cvs-serv30210

Modified Files:
	Tutorial.html 
Log Message:
Be consistent about the config code -- these are configuration
directives.  Add a "TO DO" section about config files.


=== Packages/JobBoardEx/Tutorial.html 1.14 => 1.15 ===
 
 <p>The view is attached to the Job class by means of a single
-statement in the configuration file:
+directive in the configuration file:
 
 <pre>
 &lt;browser:view name="index.html"
@@ -160,8 +160,8 @@
 requires the permission Zope.Public, a fancy way to say that anyone
 can view the job; more about permissions later.
 
-<p>Another statement in the configuration file tells Zope that this is
-the default view for such objects:
+<p>Another configuration directive tells Zope that this is the default
+view for such objects:
 
 <pre>
 &lt;browser:defaultView for=".IJob."
@@ -220,7 +220,7 @@
 job id.
 
 <p>The view is attached to the JobList class and made the default view
-by the following statements in the configuration file:
+by the following configuration directives:
 
 <pre>
 &lt;browser:view name="index.html"
@@ -321,7 +321,7 @@
 <h4>Configuration Directives</h4>
 
 <p>The JobCreateView class and its views are tied together with the
-following configuration code:
+following configuration directives:
 
 <pre>
 &lt;browser:view for=".IJobList."
@@ -377,7 +377,7 @@
 
 <p>The last step in the workflow is the approval form.  This form is
 only accessible for site managers.  Let's start with the configuration
-code for a change:
+directives for a change:
 
 <pre>
 &lt;browser:view for=".IJobList."
@@ -423,27 +423,37 @@
 selected value for each group of radio buttons is sent to to the
 action() method of the AppriveJobsView class.  (The browser sends it
 to the "approve" view, which is mapped to the "action" button by the
-configuration code above.)  The action() method iterates over the keys
-of the form (which are of course the field names), ignoring keys that
-aren't the job id for an existing job.  Then for each valid job id,
-the value from the form is inspected, and the appropriate action is
-taken: to approve a job, its approve() method is called; to discard a
-job, it is deleted from the job list.  If the action code isn't either
-'approve' or 'discard', nothing is done to the job, and it remains in
-the PendingApproval state.
+configuration directives above.)  The action() method iterates over
+the keys of the form (which are of course the field names), ignoring
+keys that aren't the job id for an existing job.  Then for each valid
+job id, the value from the form is inspected, and the appropriate
+action is taken: to approve a job, its approve() method is called; to
+discard a job, it is deleted from the job list.  If the action code
+isn't either 'approve' or 'discard', nothing is done to the job, and
+it remains in the PendingApproval state.
 
 <p>Finally, the action() method directs the browser back to the view
 named approveForm.html.  As an aside, note that this means we can't
-just change the name of that form in the configuration file; we'd have
-to change it in the code of the action() method too.
+just change the name of that form in the configuration directives and
+the page templates; we'd have to change it in the Python code for the
+action() method too.
 
 
 <h2>Page Templates</h2>
 
-<p>In the previous section there was a bit of introduction to page
-templates.  Here we'll go into detail and explain how page templates
-are associated with objects, and how they extract information from
-their objects.
+<p>In the previous sections there was some mention of page templates.
+Here we'll go into detail and explain how page templates are
+associated with objects, and how they extract information from their
+objects.
+
+<p>...
+
+
+<h2>Zope Configuration Files</h2>
+
+<p>We've already seen several configuration directives.  This section
+gives a general introduction to Zope configuration files and spells
+out some details.
 
 <p>...