[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 860, Fri Feb 7 23:55:35 2003 UTC version 1055, Wed Apr 30 22:40:30 2003 UTC
Line 1 
Line 1 
 Open Issues/To-Do Items  Open Issues/To-Do Items
   
  Targeted for 0.5 Alpha 1   Release Checklist for 0.5 Alpha 1
   
     * Finish tutorial chapter 2      - Cleanup/document attribute binding mechanism as an 'IAttributeBinding' interface
   
       - Make all API signatures start with context component
   
       - Review binding tutorial and correct any errors relative to current APIs
   
       - Add 'fcgiapp' module sources to distribution; update README/INSTALL to credit
         DC and OpenMarket and reference their licenses.
   
   
   Targeted for 0.5 Alpha 2
   
       * ZConfig Integration
   
         - A 'config.ZConfig' module that provides "PEAK-aware" versions of ZConfig
           services (e.g. it will use 'peak.naming' to resolve URLs)
   
         - App startup tools based on ZConfig files.
   
         - Sample 'AdaptiveTask' classes that perform the same functions as those in
           the MetaDaemon package, with a ZConfig schema to run them in a daemon-like
           application.
   
       * Fix issue w/reading XMI 1.1 files where metamodel has nested packages
   
       * Generate UML 1.4 and 1.5 and CWM 1.0 and 1.1, and add them to the
         'setup.py' package lists.
   
       * Get XMI writing in place, w/transaction support
   
       * Generate ZConfig schemas from 'peak.model' or MOF models?
   
       * 'peak.running' refactorings: use standard 'logging' module's log levels,
          add 'logging' distro to 'peak.util' for 2.2 backward compatibility,
          and possibly adjust cluster stuff to work off ZConfig primary and
          generate clustertools file(s).
   
       * 'peak.naming' refactorings: 'peak.model'-based syntax utilities for
          creating address syntaxes.
   
   
    Targeted for 0.5 Beta 1
   
     * 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'.
   
       * Finish tutorial chapter 2 (?)
   
       * On-the-fly class combination (think "runtime module inheritance",
         without the modules) for DMs.
   
   
   
   
   
   
  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
Line 41 
Line 112 
   
     peak.running      peak.running
   
         - more docs for new 'cluster' tools  
   
         - make 'cluster' parser complain about things that would cause          - make 'cluster' parser complain about things that would cause
           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.
   
         - finish misc tasks on peak.running.logs's TODO list          - simple daemons comparable to those in MetaDaemon, unit tests
   
         - simple daemons comparable to those in MetaDaemon  
   
         - unit tests for daemons  
   
         - docstrings for reference          - docstrings for reference
   
   
     peak.config      peak.config
   
         - "Rule"-oriented configuration files (section specifies component          - "Rule"-oriented configuration files (section specifies component
Line 80 
Line 146 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  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
   relevant as written, they are being kept on this list as placeholders for    relevant as written, they are being kept on this list as placeholders for
   ideas or problem areas that may need to be re-considered in future.)    ideas or problem areas that may need to be re-considered in future.)
   
     Miscellaneous
   
       * Functional tests that access "real" databases, LDAP, etc.
   
   Simulator/Module Inheritance    Simulator/Module Inheritance
   
       * Allow 'declareModule()' to bootstrap non-existent modules; this might
         let us create "virtual packages" made by assembling other packages and
         modules.
   
     * Need a strategy for handling "del" operations; they are currently      * Need a strategy for handling "del" operations; they are currently
       untrapped.  This might be okay under most circumstances, but need to        untrapped.  This might be okay under most circumstances, but need to
       consider edge cases.        consider edge cases.
Line 101 
Line 190 
   Messaging/ObjectSpaces    Messaging/ObjectSpaces
   
     * Support for sending and receiving remote cache invalidation      * Support for sending and receiving remote cache invalidation
       messages between RecordManagers.        messages between DataManagers.
   
   
   
   
   
   
   
   
   
   
Line 123 
Line 205 
   
   peak.model    peak.model
   
     * A way to generate Z3 Interfaces from Feature-based specifications?  
   
     * Implement WarpCORE-oriented structural model, w/Querying support      * Implement WarpCORE-oriented structural model, w/Querying support
   
     * "Indexed" version of in-memory model?      * "Indexed" version of in-memory model?
Line 162 
Line 242 
   
   
   
   peak.metamodels.uml  
   
     * Need to write an MMX or XMI -> Python generator, and hook it back up into  
       the UML package, since we're right now relying on a module generated    peak.metamodels.uml
       by code that depends on stuff which is going away.  
   
     * Helper methods in Elements & Services for marshalling, common queries, etc.      * Helper methods in Elements & Services for marshalling, common queries, etc.
   
Line 191 
Line 269 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   


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

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help