[Zope3-checkins] CVS: Zope3/doc - TODO.txt:1.6

[Jim Fulton]

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

Modified Files:
	TODO.txt 
Log Message:
Removed some done items.


=== Zope3/doc/TODO.txt 1.5 => 1.6 ===
--- Zope3/doc/TODO.txt:1.5	Wed May 21 11:08:34 2003
+++ Zope3/doc/TODO.txt	Thu Jun 26 11:31:35 2003
@@ -3,31 +3,13 @@
 
 The order that items are listed here is not significant.
 
-- Fill out TALES path api defined in
-  zope.app.interfaces.talesapi.IZopeTalesAPI and implemented in 
-  zope.app.pagetemplate.talesapi.ZopeTalesAPI.
-
-  Codeworks is currently signed up for this.
-
-- Provide a simple Python api accessable from the module
-  zope.app.zapi.  The interface for this module should be defined in
-  zope.app.interfaces.zapi.IZAPI.
-
-  This is meant to support usage like:
-
-  import zapi
-
-  ....
-
-
-  p = zapi.path(someob)
-
-  Codeworks is currently signed up for this.
-
 - Finish cache framework:
 
   http://dev.zope.org/Zope3/Zope.App.Caching
 
+- Write documentation on how to develop principal sources for the
+  pluggable auth service.
+
 - Fill out an authentication service based on the architecture
   that Itamar came up with in Rotterdam. See
   src/zope/app/services/auth.txt. 
@@ -135,6 +117,8 @@
     defined for the system.  You can select a type and see all of the
     configuration for that type.
 
+- Fix a number of bugs and rough edges in page folders
+
 - Finish WebDAV
 
 - Finish XML-RPC
@@ -143,8 +127,6 @@
   review this. For one thing, object methods are implicitly published,
   which is bad.
 
-- Convert to use ZConfig
-
 - Finish "process control", specifically shutting down and restarting
   via the web.  The main issue here is plumbing.  How to get the
   signal from the UI to the server logic. The way to do this is via
@@ -169,14 +151,13 @@
   See http://collector.zope.org/Zope3-dev/109
   This requires a hook in the ZODB that Zope can override.
 
-- Supply a generic property mechanism?
-
 - Python scipts
 
   What form should these take? Should they be like Zope 2 Python
   scipts? or should they by like Python modules.
 
-- Properties
+
+- Supply a generic property mechanism?
 
   In Zope 2, folders and many other objects could have arbitrary
   properties.  This was very useful to storing little bits of
@@ -207,3 +188,4 @@
   sent) and reliable (does not lose mail on crashes, keeps a queue that can
   survive server restarts).
 
+  Codeworks is working on this.