tony 2004/05/26 14:41:37
Modified: src/blocks/tour/samples/flow/docs index.xml multi-page.xml
number-guess.xml
Log:
more typographical fixes; normalizing case of 'Flowscript'
Revision Changes Path
1.2 +3 -3 cocoon-2.1/src/blocks/tour/samples/flow/docs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/blocks/tour/samples/flow/docs/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 11 May 2004 06:52:30 -0000 1.1
+++ index.xml 26 May 2004 21:41:37 -0000 1.2
@@ -25,7 +25,7 @@
</p>
<p>
A <em>continuation</em> saves the state of execution of the
currently
- running flowscript, and allows this state to be "resurrected"
later on,
+ running Flowscript, and allows this state to be "resurrected"
later on,
typically when the user submits an HTML form that was sent with
the
<em>cocoon.sendPageAndWait</em> instruction.
</p>
@@ -36,10 +36,10 @@
show how little code is used to manage typical interactions.
</p>
<p>
- Having to use javascript to write the Flow scripts might seem
strange
+ Having to use JavaScript to write the Flow scripts might seem
strange
at first, but in practice only a few lines of Flow code will be
required
for a typical application, so this doesn't matter much. The
reason is that
- javascript (through a modified version of the mozilla Rhino
interpreter)
+ JavaScript (through a modified version of the mozilla Rhino
interpreter)
is currently the only continuations-enabled language that can be
distributed with Cocoon.
</p>
1.2 +2 -2
cocoon-2.1/src/blocks/tour/samples/flow/docs/multi-page.xml
Index: multi-page.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/tour/samples/flow/docs/multi-page.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- multi-page.xml 11 May 2004 06:52:30 -0000 1.1
+++ multi-page.xml 26 May 2004 21:41:37 -0000 1.2
@@ -35,7 +35,7 @@
working on a tiny mobile device for a minute.
</p>
<p>
- We won't use Cocoon Forms here, but simply bind a javascript
object
+ We won't use Cocoon Forms here, but simply bind a JavaScript
object
to our form manually.
</p>
<p>
@@ -51,7 +51,7 @@
</p>
<p>
The only specific thing is the importing of the multi-page.js
- flowscript, but this was already present for the previous
+ Flowscript, but this was already present for the previous
example:
<cinclude:include element="xml-code"
src="cocoon:/xml-element/flow/sitemap.xmap/flow"/>
</p>
1.2 +6 -6
cocoon-2.1/src/blocks/tour/samples/flow/docs/number-guess.xml
Index: number-guess.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/tour/samples/flow/docs/number-guess.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- number-guess.xml 11 May 2004 06:52:30 -0000 1.1
+++ number-guess.xml 26 May 2004 21:41:37 -0000 1.2
@@ -35,7 +35,7 @@
<p>
At the sitemap level, Flowscript applications need four things:
<ul>
- <li>The flowscript code must be made available to the
sitemap</li>
+ <li>The Flowscript code must be made available to the
sitemap</li>
<li>
A <em>map:call function</em> instruction must start
the Flowscript function when the "application start"
@@ -46,14 +46,14 @@
continuations when their IDs are received in requests
</li>
<li>
- A "view" pipeline must use the (flowscript-aware)
JXTemplate generator
+ A "view" pipeline must use the (Flowscript-aware)
JXTemplate generator
to insert data provided by Flowscript into pages.
</li>
</ul>
The corresponding excerpts of our sitemap are shown below.
</p>
<h3>Flowscript declaration</h3>
- <p>Note that this already contains the declaration of the next
example's flowscript.</p>
+ <p>Note that this already contains the declaration of the next
example's Flowscript.</p>
<cinclude:include element="xml-code"
src="cocoon:/xml-element/flow/sitemap.xmap/flow"/>
<h3>map:call function</h3>
@@ -77,7 +77,7 @@
<h3>View pipeline using JXTemplageGenerator</h3>
<p>
To be able to include data provided by Flowscript in our forms
and views, we
- use the flowscript-aware JXTemplateGenerator
+ use the Flowscript-aware JXTemplateGenerator
</p>
<p>Here's the pipeline</p>
<cinclude:include element="xml-code"
src="cocoon:/xml-element/flow/sitemap.xmap/views"/>
@@ -105,13 +105,13 @@
<p>
Here's the page definition for our number-guessing form.
JXTemplate codes like <em>${continuation.id}</em>, will by
replaced
- by values provided in the FlowScript <em>sendPageAndWait</em>
function call.
+ by values provided in the Flowscript <em>sendPageAndWait</em>
function call.
</p>
<cinclude:include element="xml-code"
src="cocoon:/xml-element/flow/number-guess/guess.xml/page"/>
<h2>That's it!</h2>
<p>
- We have now seen the complete code of our flowscript application:
+ We have now seen the complete code of our Flowscript application:
<ul>
<li>A few sitemap declarations, which will be very similar
for other Flowscript-based applications</li>
<li>A JXTemplate-based view, a "normal" page with some
substitution codes</li>
