[Checkins] SVN: bluebream/website/docs/v1.0/manual/ rest fixes

Baiju M baiju.m.mail at gmail.com
Thu Jul 22 14:09:44 EDT 2010


Log message for revision 114936:
  rest fixes
  

Changed:
  U   bluebream/website/docs/v1.0/manual/form.rst
  U   bluebream/website/docs/v1.0/manual/schema.rst

-=-
Modified: bluebream/website/docs/v1.0/manual/form.rst
===================================================================
--- bluebream/website/docs/v1.0/manual/form.rst	2010-07-22 17:59:06 UTC (rev 114935)
+++ bluebream/website/docs/v1.0/manual/form.rst	2010-07-22 18:09:43 UTC (rev 114936)
@@ -23,15 +23,17 @@
 user submitted form data into Python objects.
 
 The formlib provides some base classes for creating view classes.
-The most used base classes are DisplayForm, AddForm and EditForm.
-The DisplayForm is not really a web form to submit, but a convenience
-for displaying values based on particular context/interface.
+The most used base classes are *DisplayForm*, *AddForm* and
+*EditForm*.  The *DisplayForm* is not really a web form to submit,
+but a convenience for displaying values based on particular
+context/interface.
 
 .. note::
 
-  There is another community supported library called `z3c.form
-  <http://docs.zope.org/z3c.form>`_.  Many projects are using this
-  library, and it is very well documented.
+  There is a popular community supported library called `z3c.form
+  <http://docs.zope.org/z3c.form>`_ with more functionality &
+  features compared to *zope.formlib*.  Many projects are using
+  *z3c.form* library, and it is very well documented.
 
 Concepts
 --------
@@ -41,7 +43,7 @@
 Widget
 ~~~~~~
 
-Formlib defines a widget like this: "views on bound schema fields"
+Formlib defines a widget like this: *views on bound schema fields*
 
 Field
 ~~~~~
@@ -51,12 +53,12 @@
 Form
 ~~~~
 
-A form class can define ordered collections of "form fields" using
-the `Fields` constructor.  Form fields are distinct from and build on
+A form class can define ordered collections of *form fields* using
+the *Fields* constructor.  Form fields are distinct from and build on
 schema fields.  A schema field specifies attribute values.  Form
 fields specify how a schema field should be used in a form.  The
 simplest way to define a collection of form fields is by passing a
-schema to the `Fields` constructor.
+schema to the *Fields* constructor.
 
 Action
 ~~~~~~
@@ -99,10 +101,10 @@
 Creating an EditForm
 --------------------
 
-The usage of ``EditForm`` is very similar to ``AddForm``.
+The usage of *EditForm* is very similar to *AddForm*.
 
 Conclusion
 ----------
 
-This chapter introduced zope.formlib library to generate HTML forms
+This chapter introduced *zope.formlib* library to generate HTML forms
 and widgets.

Modified: bluebream/website/docs/v1.0/manual/schema.rst
===================================================================
--- bluebream/website/docs/v1.0/manual/schema.rst	2010-07-22 17:59:06 UTC (rev 114935)
+++ bluebream/website/docs/v1.0/manual/schema.rst	2010-07-22 18:09:43 UTC (rev 114936)
@@ -346,7 +346,7 @@
   that the Publisher already takes care of the encoding issues).
 
 - ``BytesWidget``, ``BytesAreaWidget``: Direct descendents from
-  ``TextWidget`` and ``TextAreaWidget, the only difference is that
+  ``TextWidget`` and ``TextAreaWidget``, the only difference is that
   these widgets expect bytes as input and not a unicode string, which
   means they must be valid ASCII encodable.
 



More information about the checkins mailing list