[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 689, Sun Nov 17 01:27:14 2002 UTC version 707, Tue Nov 19 02:43:42 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)
   
   
     General      General
   
         * Tutorial complete through chapter 4          * Tutorial complete through chapter 4
   
   
     peak.storage      peak.storage
   
         - LDAP field type conversion  
   
         - Rack -> DM  
   
         - "facade" DM base class(es)          - "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? Should already happen          - SQL field type conversion for txnTime? Should already happen
Line 38 
Line 28 
   
         - 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 79 
Line 66 
           rather than property name prefix), so that daemons and other simple            rather than property name prefix), so that daemons and other simple
           apps can be fully configured and run via a config file.            apps can be fully configured and run via a config file.
   
   
     peak.util      peak.util
   
         - docstrings for reference          - docstrings for reference
Line 94 
Line 80 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  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 164 
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 177 
Line 133 
   
     * "Indexed" version of in-memory model?      * "Indexed" version of in-memory model?
   
     * "Persistent" StructuralModel (indexes w/BTrees?  Catalog?)  
   
   
     Queries      Queries
   
Line 203 
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 248 
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.689  
changed lines
  Added in v.707
cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help