[Checkins] SVN: z3c.form/trunk/src/z3c/form/ whitespace

[Stephan Richter]

Log message for revision 98354:
  whitespace

Changed:
  U   z3c.form/trunk/src/z3c/form/browser/object.txt
  U   z3c.form/trunk/src/z3c/form/widget.txt

-=-
Modified: z3c.form/trunk/src/z3c/form/browser/object.txt
===================================================================
--- z3c.form/trunk/src/z3c/form/browser/object.txt	2009-03-25 05:16:44 UTC (rev 98353)
+++ z3c.form/trunk/src/z3c/form/browser/object.txt	2009-03-25 05:33:19 UTC (rev 98354)
@@ -2,13 +2,13 @@
 ObjectWidget
 ============
 
-The ObjectWidget is about rendering a schema's fields as a single widget.
+The `ObjectWidget` widget is about rendering a schema's fields as a single
+widget.
 
+There are way too many preconditions to exercise the `ObjectWidget` as it
+relies heavily on the from and widget framework. It renders the sub-widgets in
+a sub-form.
 
-There are way too many preconditions to exercise the ObjectWidget as it
-relies heavily on the from and widget framework.
-It renders the sub-widgets in a sub-form.
-
 In order to not overwhelm you with our set of well-chosen defaults,
 all the default component registrations have been made prior to doing those
 examples:
@@ -34,9 +34,7 @@
   >>> from z3c.form.error import MultipleErrorViewSnippet
   >>> zope.component.provideAdapter(MultipleErrorViewSnippet)
 
-
-
-As for all widgets, the objectwidget must provide the new ``IWidget``
+As for all widgets, the objectwidget must provide the new `IWidget`
 interface:
 
   >>> from zope.interface.verify import verifyClass
@@ -66,7 +64,8 @@
   >>> widget.update()
   Traceback (most recent call last):
   ...
-  ValueError: <ObjectWidget 'widget.name'> .field is None, that's a blocking point
+  ValueError: <ObjectWidget 'widget.name'> .field is None,
+              that's a blocking point
 
 This schema is specified by the field:
 

Modified: z3c.form/trunk/src/z3c/form/widget.txt
===================================================================
--- z3c.form/trunk/src/z3c/form/widget.txt	2009-03-25 05:16:44 UTC (rev 98353)
+++ z3c.form/trunk/src/z3c/form/widget.txt	2009-03-25 05:33:19 UTC (rev 98354)
@@ -515,14 +515,14 @@
 ------------
 
 A common use case in user interfaces is to ask the user to define one or more
-items. The ``widget`` module provides a basic widget implementation to support 
+items. The ``widget`` module provides a basic widget implementation to support
 this use case.
 
-The MultiWidget allows to store none, one or more values for a sequence field.
-Don't get cinfused by the term sequence. Ther sequence used in SequenceWidget
-means that the widget can choose from a sequence of values which is a really
-a collection. The MultiWidget can collect values for build and store a 
-sequence of values like used in ITuple or IList field.
+The `MultiWidget` allows to store none, one or more values for a sequence
+field.  Don't get cinfused by the term sequence. Ther sequence used in
+`SequenceWidget` means that the widget can choose from a sequence of values
+which is a really a collection. The `MultiWidget` can collect values for build
+and store a sequence of values like used in `ITuple` or `IList` field.
 
   >>> request = TestRequest()
   >>> multiWidget = widget.MultiWidget(request)
@@ -538,7 +538,7 @@
   ...     value_type=zope.schema.Int(default=42))
   >>> multiWidget.field = multiField
 
-The value of a multi widget is always list. When extracting values from the 
+The value of a multi widget is always list. When extracting values from the
 request, the values must be a list of valid values based on the value_type
 field used from the used sequence field. The widget also uses a counter which
 is required for processing the input from a request. The counter is a marker
@@ -573,14 +573,14 @@
   >>> multiWidget.extract()
   [u'bad']
 
-Storing a widget value forces to update the (sub) widgets. this forces also to 
-validate the (sub) widget values. For showing this we nee dot register a 
+Storing a widget value forces to update the (sub) widgets. this forces also to
+validate the (sub) widget values. For showing this we nee dot register a
 validator:
 
   >>> from z3c.form.validator import SimpleFieldValidator
   >>> zope.component.provideAdapter(SimpleFieldValidator)
 
-Since the value of the widget is a list of (widget) value items, when 
+Since the value of the widget is a list of (widget) value items, when
 displaying the values, they can be used as they are:
 
   >>> multiWidget.request = TestRequest(form={'multi.name.count':'2',
@@ -590,9 +590,9 @@
   >>> multiWidget.value
   [u'42', u'43']
 
-Each widget normaly gets first process by it's update method call after 
+Each widget normaly gets first process by it's update method call after
 intialization. This update call forces to call extract, which first will get
-the right amount of (sub) widgets by the given counter value. Based on that 
+the right amount of (sub) widgets by the given counter value. Based on that
 counter value the right amount of widgets will get created. Each widget will
 return it's own value and this collected values get returned by the extract
 method. The multi widget update method will then store this values if any give
@@ -602,7 +602,7 @@
 widget widgets based on the given values and apply the right value for them.
 After that the mutli widget is ready for rendering. The good thing about that
 pattern is that it is possible to set a value before or after the update method
-is called. At any time if we change the mutli widget value the (sub) widgets 
+is called. At any time if we change the mutli widget value the (sub) widgets
 get updated within the new relevant value.
 
   >>> multiRequest = TestRequest(form={'multi.name.count':'2',