[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 656, Sun Nov 10 02:46:58 2002 UTC version 752, Wed Nov 27 00:32:49 2002 UTC
Line 2 
Line 2 
   
  Targeted for 0.5 Alpha 1   Targeted for 0.5 Alpha 1
   
     * Review possible cross-locational or "root" things like      * Finish tutorial chapter 2
       'PropertyName' -- should these things move to the API?  
       Or where?  They're not 'util' things, certainly.  Perhaps  
       there should be a 'peak.core' module or package for things  
       that are foundational to all the packages?  
   
     * Updated reference docstrings for 'peak.api', 'peak.binding',      * Updated reference docstrings for 'peak.api', 'peak.binding',
       'peak.config', 'peak.exceptions', and 'peak.naming'.        'peak.config', 'peak.exceptions', and 'peak.naming'.
   
     * Additional content for the tutorial's chapter on binding  
   
  Targeted for 0.5 Final Release (or sooner)   Targeted for 0.5 Final Release (or sooner)
   
     General  
   
         * Update tutorial documentation      General
   
         * Up-to-date and complete Persistence package          * Tutorial complete through chapter 4
   
     peak.storage      peak.storage
   
         - SQL cursor(joinTxn=flag) shortcut for .joinTxn()          - unit tests for more complex object scenarios: references, thunks..?
   
         - SQL cursor error logging, close conn on error, and rewrap errors  
           w/SQL in error object  
   
         - SQL field type conversion  
   
         - LDAP field type conversion  
   
         - Rack -> DM  
   
         - "facade" DM base class(es)          - lock management interfaces/API
   
         - "query" DM base class(es)          - docstrings for reference
   
         - unit tests for more complex object scenarios: references, thunks..?      peak.model
   
         - docstrings for reference          - clean up TW docstrings & interfaces
   
         - URL+driver for postgres      peak.naming
   
     peak.model          - useful example "flat" naming context (e.g. like AppUtils.URLkeys)
   
         - add support for lazy-loaded attributes          - useful example hierarchical naming context (e.g. like JNDI's LDAP
             context or filesystem context)
   
         - clean up TW docstrings & interfaces          - 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
   
Line 58 
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 69 
Line 58 
     peak.config      peak.config
   
         - "Rule"-oriented configuration files (section specifies component          - "Rule"-oriented configuration files (section specifies component
           rather than property name prefix).            rather than property name prefix), so that daemons and other simple
             apps can be fully configured and run via a config file.
   
     peak.util      peak.util
   
Line 80 
Line 70 
   
   
   
   
   
   
   
   
   
   
   
   
   
  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.656  
changed lines
  Added in v.752
cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help