crossley 2004/05/07 09:33:37
Modified: src/blocks/supersonic/samples/bean-editor/docs forms.xml
src/blocks/supersonic/samples/flow/docs multi-page.xml
number-guess.xml
src/blocks/supersonic/samples/intro/docs bizlayer.xml
facts.xml resources.xml use-cases.xml
Log:
Minor text tweaks.
Revision Changes Path
1.2 +2 -2
cocoon-2.1/src/blocks/supersonic/samples/bean-editor/docs/forms.xml
Index: forms.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/supersonic/samples/bean-editor/docs/forms.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- forms.xml 4 May 2004 17:25:10 -0000 1.1
+++ forms.xml 7 May 2004 16:33:37 -0000 1.2
@@ -49,7 +49,7 @@
</ul>
This seems a lot of work when described in this way, but notice
once again how modular things are: each "concern" of our bean
editor
- is cleary defined in its own place.
+ is clearly defined in its own place.
</p>
<p>
Note also that, while our example uses static XML files for these
@@ -150,7 +150,7 @@
</p>
<p>
For the <em>taskId</em> form field, the <em>readonly</em> flag
- makes the binding unidirectional,
+ makes the binding unidirectional.
The value of the form field will not be copied to the bean
when <em>form.save</em> is called.
</p>
1.3 +3 -3
cocoon-2.1/src/blocks/supersonic/samples/flow/docs/multi-page.xml
Index: multi-page.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/supersonic/samples/flow/docs/multi-page.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- multi-page.xml 4 May 2004 19:56:31 -0000 1.2
+++ multi-page.xml 7 May 2004 16:33:37 -0000 1.3
@@ -62,7 +62,7 @@
<cinclude:include element="flowscript-code"
src="cocoon:/text-file/flow/multi-page/multi-page.js"/>
</p>
<p>
- It's not more complicated than the previous example, but slightly
+ It is not more complicated than the previous example, but
slightly
longer due to the (boring) copying of request parameters into
the message object. This boring part is where Cocoon Forms will
come into play, by making it easier to <em>bind</em> data to
@@ -86,8 +86,8 @@
</p>
<cinclude:include element="xml-code"
src="cocoon:/xml-element/flow/multi-page/page1.xml/page"/>
<p>
- This is page 1, page 2 is similar but shows the <em>text</em>
field instead of
- the fields present on page 1.
+ This is page 1. The page 2 is similar but shows the <em>text</em>
+ field instead of the fields present on page 1.
</p>
</content>
</page>
1.3 +1 -1
cocoon-2.1/src/blocks/supersonic/samples/flow/docs/number-guess.xml
Index: number-guess.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/supersonic/samples/flow/docs/number-guess.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- number-guess.xml 4 May 2004 19:28:32 -0000 1.2
+++ number-guess.xml 7 May 2004 16:33:37 -0000 1.3
@@ -63,7 +63,7 @@
</p>
<p>
The maxValue parameter is used by our Flowscript
<em>public_startGuessNumber</em> function,
- but doesn't hurt if it's passed to other functions (like in the
next example).
+ but doesn't hurt if it is passed to other functions (like in the
next example).
</p>
<cinclude:include element="xml-code"
src="cocoon:/xml-element/flow/sitemap.xmap/start"/>
1.2 +5 -4
cocoon-2.1/src/blocks/supersonic/samples/intro/docs/bizlayer.xml
Index: bizlayer.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/supersonic/samples/intro/docs/bizlayer.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bizlayer.xml 4 May 2004 17:25:10 -0000 1.1
+++ bizlayer.xml 7 May 2004 16:33:37 -0000 1.2
@@ -23,7 +23,7 @@
is <em>how to implement my business layer</em>.
</p>
<p>
- The short answer: <em>it's up to you</em> ;-)
+ The short answer: <em>it is up to you</em> ;-)
</p>
<p>
More precisely, you could say that Cocoon leaves a lot
@@ -52,11 +52,11 @@
objects from Flowscript code.
Such objects do not necessarily need to know about Cocoon or
Avalon classes, which means that legacy code could be easily
integrated,
- provided their are no class libraries conflicts.
+ provided there are no class libraries conflicts.
</p>
<p>
Working in this way however, prevents you from using any Avalon
features
- like configuration, logging and monitoring facilities.
+ like configuration, logging, and monitoring facilities.
</p>
<p>
As such, this is a suboptimal solution, but might be interesting
for
@@ -81,7 +81,8 @@
The benefits are largely worth it for serious applications.
</p>
<p>
- Structuring your code in <em>blocks</em> as is done inside
Cocoon will make integration
+ Structuring your code in <em>blocks</em>, as is done inside
Cocoon,
+ will make integration
easier and should help future migrations to newer versions of
Cocoon.
</p>
1.2 +6 -3
cocoon-2.1/src/blocks/supersonic/samples/intro/docs/facts.xml
Index: facts.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/supersonic/samples/intro/docs/facts.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- facts.xml 4 May 2004 17:25:11 -0000 1.1
+++ facts.xml 7 May 2004 16:33:37 -0000 1.2
@@ -43,8 +43,9 @@
<h2>Licensing</h2>
<p>
- Cocoon is distributed under the fairly liberal <em>Apache
Software Foundation License</em>,
- which allows it to be used in most any way provided due credit
is given to the Foundation.
+ Cocoon is distributed under the liberal
+ <em><a href="http://www.apache.org/licenses/";>Apache
License</a></em>
+ which maximises its use while still providing protection.
</p>
<h2>Community</h2>
@@ -56,7 +57,9 @@
</p>
<p>
The current team comprises more than 40 active committers, of
which about 20
- are regularly active and contribute new components, bug fixes,
tests and documentation.
+ are regularly active. Those committers and the wider Cocoon
+ community contribute new components, bug fixes, tests and
+ documentation, and provide user support to each other.
</p>
</content>
1.2 +2 -2
cocoon-2.1/src/blocks/supersonic/samples/intro/docs/resources.xml
Index: resources.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/supersonic/samples/intro/docs/resources.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- resources.xml 4 May 2004 17:25:11 -0000 1.1
+++ resources.xml 7 May 2004 16:33:37 -0000 1.2
@@ -29,8 +29,8 @@
</p>
<p>
- The samples provided with Cocoon
- will help explore the functionality of the various blocks. The
main
+ The <a href="../../../..">samples</a> provided with Cocoon
+ will help to explore the functionality of the various blocks.
The main
website contains some <em>documentation tracks</em> which will
help
you analyze and understand the samples.
</p>
1.2 +1 -1
cocoon-2.1/src/blocks/supersonic/samples/intro/docs/use-cases.xml
Index: use-cases.xml
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/supersonic/samples/intro/docs/use-cases.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- use-cases.xml 4 May 2004 17:25:11 -0000 1.1
+++ use-cases.xml 7 May 2004 16:33:37 -0000 1.2
@@ -46,7 +46,7 @@
<p>
See also the list
of Cocoon features at
- <a
href="http://cocoon.apache.org/2.1/features.html";>http://cocoon.apache.org/2.1/features.html</a>.
+ <a
href="http://cocoon.apache.org/2.1/features.html";>http://cocoon.apache.org/2.1/features.html</a>
</p>
</content>
</page>
