[Zope3-checkins] CVS: Zope3/lib/python/Zope/Schema - README.stx:1.7

[R. David Murray]

Update of /cvs-repository/Zope3/lib/python/Zope/Schema
In directory cvs.zope.org:/tmp/cvs-serv19028/lib/python/Zope/Schema

Modified Files:
	README.stx 
Log Message:
Reformat long paragraphs to fit in default terminal width,
and fix a minor gramatical error.


=== Zope3/lib/python/Zope/Schema/README.stx 1.6 => 1.7 ===
--- Zope3/lib/python/Zope/Schema/README.stx:1.6	Thu Dec  5 08:22:07 2002
+++ Zope3/lib/python/Zope/Schema/README.stx	Mon Dec 16 17:38:29 2002
@@ -6,7 +6,8 @@
 
      Long introduction
 
-     What is a schema, how does it compare to an interface and why should you care?
+     What is a schema, how does it compare to an interface and why
+     should you care?
 
      What does a Schema look like 
      
@@ -17,18 +18,20 @@
 
 Introduction
 
-     Schemas extend the notion of interfaces to descriptions of Attributes rather than 
-     methods.  Every Schema is an interface and specifies the public fields of an 
-     object.  A "Field" roughly corresponds to an attribute of a python object. 
-     But a Field provides space for a title and a description. It can also constrain
-     its value and provide a validation method.  Besides you can optionally specify
-     characteristics such as its value beeing readonly or not required. 
-
-     Zope 3 schemas were born when Jim Fulton and Martijn Faassen thought about 
-     Formulator for Zope3 and PropertySets while at the Zope3 sprint at the 
-     Zope BBQ in Berlin. They realized that if you strip all view logic 
-     from forms than you have something to interfaces. 
-     And thus schemas were born.
+     Schemas extend the notion of interfaces to descriptions of
+     Attributes rather than methods.  Every Schema is an interface
+     and specifies the public fields of an object.  A "Field" roughly
+     corresponds to an attribute of a python object.  But a Field
+     provides space for a title and a description. It can also
+     constrain its value and provide a validation method.  Besides
+     you can optionally specify characteristics such as its value
+     beeing readonly or not required.
+
+     Zope 3 schemas were born when Jim Fulton and Martijn Faassen
+     thought about Formulator for Zope3 and PropertySets while at
+     the Zope3 sprint at the Zope BBQ in Berlin. They realized that
+     if you strip all view logic from forms than you have something
+     to interfaces.  And thus schemas were born.
 
 Dependencies
 
@@ -65,7 +68,7 @@
     (resp. its code and state). 
 
     A Schema starts out like an interface but defines certain
-    Fields to which an object's attributes must conform to. Let's look at 
+    Fields to which an object's attributes must conform. Let's look at 
     a stripped down example from the programmer's tutorial (chapter two)::
 
     from Interface import Interface
@@ -123,9 +126,10 @@
     class book(Interface):
         author = ITextLine()
      
-    To get to the And in view, while the widget or widget's messages are constructed:
-  
-    TranslatorService.getMessage('book.author.title','DE_DE')   
+    To get to the And in view, while the widget or widget's messages
+    are constructed:
+
+    TranslatorService.getMessage('book.author.title','DE_DE')
 
  Integration with Interfaces