[Zope3-checkins] CVS: Zope3/src/zope/app/schema - fields.zcml:1.7

[Gary Poster]

Update of /cvs-repository/Zope3/src/zope/app/schema
In directory cvs.zope.org:/tmp/cvs-serv9758/src/zope/app/schema

Modified Files:
	fields.zcml 
Log Message:
Convert the field collection behavior as described in 
http://mail.zope.org/pipermail/zope3-dev/2004-May/010797.html

The Sequence field is removed.  As I spoke with Stephan, it may be acceptable to add the Sequence field back in if it actually means something.  Sequence did mean it was iterable but container access API was not described.  It should be described.  IPythonSequence might describe this API.  A Sequence widget should require specification of the factory.

Set now specifies a sets.Set.

IChoiceSequence was removed.




=== Zope3/src/zope/app/schema/fields.zcml 1.6 => 1.7 ===
--- Zope3/src/zope/app/schema/fields.zcml:1.6	Sat Apr 24 19:19:56 2004
+++ Zope3/src/zope/app/schema/fields.zcml	Thu May  6 12:13:49 2004
@@ -85,17 +85,6 @@
 
   </content>
 
-  <content class="zope.schema.Sequence">
-
-    <factory
-	id="zope.schema.Sequence"
-	title="Sequence Field"
-	description="Sequence Field" />
-
-    <require like_class="zope.schema.Field" />
-
-  </content>
-
   <content class="zope.schema.Bytes">
 
     <factory
@@ -203,6 +192,17 @@
 
   </content>
 
+  <content class="zope.schema.Set">
+
+    <factory
+	id="zope.schema.Set"
+	title="Set Field"
+	description="Set Field" />
+
+    <require like_class="zope.schema.Field" />
+
+  </content>
+
   <content class="zope.schema.Password">
 
     <factory
@@ -299,4 +299,13 @@
 
   </content>
 
-</configure>
\ No newline at end of file
+  <content class="zope.schema.vocabulary.SimpleTerm">
+    <allow interface="zope.schema.interfaces.ITitledTokenizedTerm" />
+  </content>
+
+  <content class="zope.schema.vocabulary.SimpleVocabulary">
+    <allow interface="zope.schema.interfaces.IVocabulary" />
+    <allow interface="zope.schema.interfaces.IVocabularyTokenized" />
+  </content>
+
+</configure>