[Zope3-checkins] CVS: Zope3/doc - CHANGES.txt:1.493

[Jim Fulton]

Update of /cvs-repository/Zope3/doc
In directory cvs.zope.org:/tmp/cvs-serv28160

Modified Files:
	CHANGES.txt 
Log Message:
Added my changes.


=== Zope3/doc/CHANGES.txt 1.492 => 1.493 ===
--- Zope3/doc/CHANGES.txt:1.492	Mon Nov 24 10:00:03 2003
+++ Zope3/doc/CHANGES.txt	Mon Nov 24 10:48:54 2003
@@ -13,6 +13,7 @@
     support.   Zope 3.0 will provide support for Zope 2 content and
     products, probably using conversion utilities of some sort. 
 
+
 preparing for the MS:
 
     Stephan works here:
@@ -23,8 +24,86 @@
 
     Jim works here:
 
+    Backward compatibility notes
+
+    - If you have any add-on prodycts that used the old context-wrapper or
+      "context awareness" APIs, you will need to update these use the
+      new, and much simpler,  location API.  See
+      zope/app/interfaces/location.py. 
+
+    - If you have add-on products that register views or resources
+      using the view or resource directives from the zope ZCML
+      namespace, you will need to change the value of the 'type'
+      attribute to refer to a request type, rather than a presentation
+      type. 
+
+    - If you have an add-on product that defines new layers, you need
+      to use the zope:layer or browser:layer directive to define the
+      layer before you use it in a skin definition or a view or
+      resource definition:
+
+        <browser:layer name="rotterdam" />
+
+
+    - If you had a local (through the web) adapter service, you will
+      need to recreate it and reactivate your adapter registrations.
+
+    - If you had a local (through the web) view service, you will
+      need to create a local presentation service and reactivate your
+      page or view registrations.
+
+    Features
+
+    - Changed the way presentation components are managed.
+
+      o The view, resource, and skin services have been combined into
+        a new presentation service.
+
+      o Views and resources no adapt requests.  They are registered
+        for request types rather than presentation types.
+
+    - Refactored the way interfaces, declarations amd adapters are
+      implemented.  We now use a cleaner architecture that no-longer
+      requires a caching mechanism beyond what's provided by the
+      underlying data structures.  This has led to a significant speed
+      up for Zope 3.
+
+    - Refactored the way location-related events are generated and
+      handled.
+
+      For more details, see:
+      http://dev.zope.org/Zope3/LocationRelatedEvents
+      http://dev.zope.org/Zope3/SimplifyObjectLifecycleAndLocationEvents
+
+    - Refactored the way object location is modeled.  Zope 3 no longer
+      uses context wrappers. Instead, objects have __parent__
+      attributes that reference their containers.  Objects that don't
+      maintain these attributes themselves are warpped in persistent
+      proxy objects that do so.
+
+      For more details, see:
+      http://dev.zope.org/Zope3/ParentGeddon
+
+    - Added catalogs.  Catalogs can be used in two-ways:
+
+      o Site-wide utilities
+
+        A catalog is created in a site-management folder and
+        registered as a named utility.
+
+      o Local content objects.
+
+        A catalog is added to a regular content folder. 
+
+    - Added object fields. Object fields provide a simple composite
+      field mechanism. An object field is defined by a schema and,
+      thus, can contain sub-fields.
 
+    - Added working widgets for list fields. List fields contain a
+      sequence of monogenous values.
 
+    - Improved forms error reporting. Error messages now appear next
+      to fields where errors occured.