[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 670, Tue Nov 12 21:25:29 2002 UTC version 752, Wed Nov 27 00:32:49 2002 UTC
Line 1 
Line 1 
 Open Issues/To-Do Items  Open Issues/To-Do Items
   
   
  Targeted for 0.5 Alpha 1   Targeted for 0.5 Alpha 1
   
     * Finish tutorial chapter 2      * Finish tutorial chapter 2
Line 9 
Line 8 
       'peak.config', 'peak.exceptions', and 'peak.naming'.        'peak.config', 'peak.exceptions', and 'peak.naming'.
   
   
   
  Targeted for 0.5 Final Release (or sooner)   Targeted for 0.5 Final Release (or sooner)
   
   
Line 17 
Line 15 
   
         * Tutorial complete through chapter 4          * Tutorial complete through chapter 4
   
         * Up-to-date and complete Persistence package  
   
   
     peak.storage      peak.storage
   
         - LDAP field type conversion  
   
         - Rack -> DM  
   
         - "facade" DM base class(es)  
   
         - "query" DM base class(es)  
   
         - unit tests for more complex object scenarios: references, thunks..?          - unit tests for more complex object scenarios: references, thunks..?
   
         - SQL field type conversion for txnTime?  
   
         - lock management interfaces/API          - lock management interfaces/API
   
         - docstrings for reference          - docstrings for reference
   
   
     peak.model      peak.model
   
         - add support for lazy-loaded attributes  
   
         - clean up TW docstrings & interfaces          - clean up TW docstrings & interfaces
   
     peak.naming      peak.naming
Line 52 
Line 34 
         - useful example hierarchical naming context (e.g. like JNDI's LDAP          - useful example hierarchical naming context (e.g. like JNDI's LDAP
           context or filesystem context)            context or filesystem context)
   
           - rework smtp: to return a factory object that supports open().
             Also think about whether smtp should move elsewhere. Maybe
             there should be peak.network or peak.internet for things like
             smtp, ftp, etc contexts?
   
     peak.running      peak.running
   
         - more docs for new 'cluster' tools          - more docs for new 'cluster' tools
Line 60 
Line 47 
           the clusterit tools to choke or barf on the file, or which would            the clusterit tools to choke or barf on the file, or which would
           produce ambiguous or unintended results.            produce ambiguous or unintended results.
   
         - create a basic LogFile logging provider w/URL comparable to AppUtils          - finish misc tasks on peak.running.logs's TODO list
   
         - simple daemons comparable to those in MetaDaemon          - simple daemons comparable to those in MetaDaemon
   
Line 80 
Line 67 
   
         - more unit tests?          - more unit tests?
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  Future Releases   Future Releases
   
   (Note: some of the below is held-over from TransWarp and may no longer be    (Note: some of the below is held-over from TransWarp and may no longer be
Line 123 
Line 123 
   
   peak.model    peak.model
   
     * Review other-end-notification protocols in the light of managed storage  
       models (e.g. database Records using virtual sequence objects as fields)  
   
     * Marshalling interface in Services; implementations for Enumeration, etc.      * Marshalling interface in Services; implementations for Enumeration, etc.
   
     * More S-E-F metadata: features, subclasses, svc.<->class, nested services      * More S-E-F metadata: features, subclasses, svc.<->class, nested services
Line 136 
Line 133 
   
     * "Indexed" version of in-memory model?      * "Indexed" version of in-memory model?
   
     * "Persistent" StructuralModel (indexes w/BTrees?  Catalog?)  
   
   
     Queries      Queries
   
Line 162 
Line 157 
   
   
   
   
   
   
   
   
   peak.metamodels.uml    peak.metamodels.uml
   
     * Need to write an MMX or XMI -> Python generator, and hook it back up into      * Need to write an MMX or XMI -> Python generator, and hook it back up into
Line 207 
Line 207 
   
     * Re-org to self-contain all XMI stuff inside an _XMI sub-component/service      * Re-org to self-contain all XMI stuff inside an _XMI sub-component/service
   
     * Refactoring to pure S-E-F model using Persistence  
   
     * Document version of standard used      * Document version of standard used
   
     * Metamodel identity/version checking      * Metamodel identity/version checking


Generate output suitable for use with a patch program
Legend:
Removed from v.670  
changed lines
  Added in v.752

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help