[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 596, Mon Nov 4 00:05:25 2002 UTC version 961, Thu Apr 3 22:39:50 2003 UTC
Line 1 
Line 1 
 Open Issues/To-Do Items  Open Issues/To-Do Items
   
  Targeted for 0.5 Final Release   Targeted for 0.5 Alpha 1
   
     General      * Fix issue w/reading XMI 1.1 files where metamodel has nested packages
   
         * Update tutorial documentation      * Document interface expected of "active descriptors" and their complements
         (e.g. __class_provides__), refactoring for cleanliness as needed.
   
         * Up-to-date and complete Persistence package      * Refactor "Pythonic" UML 1.3 extensions so they're usable for most
         MOF-aligned metamodels (e.g. all UML and CWM versions)
   
     peak.storage      * Remove deprecated items from peak.model: Feature, Reference, Package,
         Model, Namespace, DataType, etc.
   
         - URLs and drivers for gadfly, Sybase, and postgres      * Get XMI writing in place, w/transaction support
   
         - policy/providers for global/local txn scopes      * Updated reference docstrings for 'peak.api', 'peak.binding',
         'peak.config', 'peak.exceptions', and 'peak.naming'.
   
         - "alternate key" rack base class(es)      * Finish tutorial chapter 2 (?)
   
         - "query" rack base class(es)   Targeted for 0.5 Alpha 2
   
         - unit tests for more complex object scenarios: references, thunks..?      * On-the-fly class combination (think "runtime module inheritance",
         without the modules) for DMs.
   
         - docstrings for reference      * ZConfig support, probably in the form of generating ZConfig schemas
         from 'peak.model' or MOF models, but maybe in the form of 'fromZConfig'
         constructor methods as well.
   
     peak.model      * 'peak.running' refactorings: use standard 'logging' module's log levels,
          add 'logging' distro to 'peak.util' for 2.2 backward compatibility,
          make daemons based on 'peak.model' (or at least define ZConfig schemas),
          and possibly adjust cluster stuff to work off ZConfig primary and
          generate clustertools file(s).  App startup tools based on ZConfig and
          PEAK-style .ini files.
   
         - add support for lazy-loaded attributes      * 'peak.naming' refactorings: 'peak.model'-based syntax utilities for
          creating address syntaxes.
   
         - review XMI/Querying extensions for forward compatibility planning   Targeted for 0.5 Final Release (or sooner)
   
         - clean up TW docstrings & interfaces      General
   
     peak.running          * Tutorial complete through chapter 4
   
         - create a basic LogFile logging provider      peak.storage
   
         - unit tests for daemons?          - unit tests for more complex object scenarios: references, thunks..?
   
         - simple daemons comparable to those in MetaDaemon?          - lock management interfaces/API
   
         - docstrings for reference          - docstrings for reference
   
     peak.binding      peak.model
   
         - docstrings for reference          - clean up TW docstrings & interfaces
   
     peak.config      peak.naming
   
         - docstrings for reference          - useful example "flat" naming context (e.g. like AppUtils.URLkeys)
   
     peak.naming          - useful example hierarchical naming context (e.g. like JNDI's LDAP
             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
   
           - make 'cluster' parser complain about things that would cause
             the clusterit tools to choke or barf on the file, or which would
             produce ambiguous or unintended results.
   
           - simple daemons comparable to those in MetaDaemon, unit tests
   
         - docstrings for reference          - docstrings for reference
   
   
       peak.config
   
           - "Rule"-oriented configuration files (section specifies component
             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
   
         - docstrings for reference          - docstrings for reference
Line 80 
Line 114 
   
   
   
   
   
   
   
   
   
   
  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 164 
   
   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.  
   
     * More S-E-F metadata: features, subclasses, svc.<->class, nested services  
   
     * 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?
   
     * "Persistent" StructuralModel (indexes w/BTrees?  Catalog?)  
   
   
     Queries      Queries
   
Line 162 
Line 192 
   
   
   
   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  
       by code that depends on stuff which is going away.  
   
   
   
   
   
   
   
     peak.metamodels.uml
   
     * Helper methods in Elements & Services for marshalling, common queries, etc.      * Helper methods in Elements & Services for marshalling, common queries, etc.
   
Line 191 
Line 228 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   peak.metamodels.xmi  
   
     * 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  
   
     * Metamodel identity/version checking  
   
     * XMI.Writing  
   
     * Strict parsing and/or diagnostics on files that don't match the metamodel?  
   
     * UUID/GUID support  
   
     * Support for advanced references, external references?  
   
     * XML Namespaces (do any current XMI tools need this?  Which spec version  
       requires this?)  
   
     * DOM StructuralModel (so files can be edited without affecting vendor XMI  
       extensions)  
   
   

Generate output suitable for use with a patch program
Legend:
Removed from v.596  
changed lines
  Added in v.961
cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help