[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 378, Sun Mar 31 22:20:56 2002 UTC version 578, Wed Oct 30 21:28:50 2002 UTC
Line 1 
Line 1 
 Open Issues/To-Do Items  Open Issues/To-Do Items
   
  Targeted for 0.2 Final Release   Targeted for 0.5 Final Release
   
     General      General
   
Line 13 
Line 13 
   
       * Update Interfaces to reflect current API, and document internals        * Update Interfaces to reflect current API, and document internals
   
  Ideas for 0.3 Release  
   
     Dispatching  
   
       * Virtual features to implement retrieving the other end of a  
         relationship from another Specialist, and to handle rebinding to  
         records after record invalidation.  
   
     SEF  
   
       * Move binding tools to a seperate module (e.g. 'TW.CIS' for "Component  
         Integration Services").  
   
       * Persistent SEF module, with Base.__getstate__ supporting omission  
         of Once attributes, and DynamicBinding setting _p_changed on  
         instantiation.  
   
       * A way to generate Z3 Interfaces from Feature-based specifications?  
   
     Database  
   
       * Rack-like object to do persistent storage of Elements?  
   
       * Support for field transformations and default values at RecordType  
         level, e.g marshalling and type conversion.  This would be  
         especially useful for LDAP.  
   
       * Support for sending and receiving remote cache invalidation  
         messages between RecordManagers.  
   
     General  
   
       * Profiling and performance tuning of module inheritance and other  
         core features of API and SEF.  
   
   
   
  Future Releases   Future Releases
Line 67 
Line 32 
   
     * Create tutorials/examples based on actual uses      * Create tutorials/examples based on actual uses
   
     * Include dependencies in packaging?  Need to ask copyright owners first.  
   
   
   
   
   
   
   
   
   
     Messaging/ObjectSpaces
   
       * Support for sending and receiving remote cache invalidation
         messages between RecordManagers.
   
   
   SEF    peak.model
   
     * Review other-end-notification protocols in the light of managed storage      * Review other-end-notification protocols in the light of managed storage
       models (e.g. database Records using virtual sequence objects as fields)        models (e.g. database Records using virtual sequence objects as fields)
Line 89 
Line 48 
   
     * More S-E-F metadata: features, subclasses, svc.<->class, nested services      * More S-E-F metadata: features, subclasses, svc.<->class, nested services
   
     * Implement WarpCORE-oriented structural model, w/Querying support      * Persistent SEF module, with Base.__getstate__ supporting omission
         of Once attributes, and DynamicBinding setting _p_changed on
     InMemory        instantiation.
   
       * "Indexed" version      * A way to generate Z3 Interfaces from Feature-based specifications?
   
       * "WeakRefs" version (no acquisition, use w/Python 2.1 weakrefs)      * Implement WarpCORE-oriented structural model, w/Querying support
   
       * "Circular" version (suitable for use w/2.1 GC or Jython)      * "Indexed" version of in-memory model?
   
       * "Persistent" StructuralModel (indexes w/BTrees?  Catalog?)        * "Persistent" StructuralModel (indexes w/BTrees?  Catalog?)
   
Line 121 
Line 80 
          have their meaning assigned by the StructuralModel implementation?           have their meaning assigned by the StructuralModel implementation?
   
   
   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
       the UML package, since we're right now relying on a module generated        the UML package, since we're right now relying on a module generated
Line 148 
Line 107 
   
     * Simple Zope product demo (upload XMI, then browse the model via the web)      * Simple Zope product demo (upload XMI, then browse the model via the web)
   
     * Reporting mixins?  Graphviz visualization?  
   
   
   
Line 162 
Line 120 
   
   
   
   XMI  
     peak.metamodels.xmi
   
     * 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      * Refactoring to pure S-E-F model using Persistence
   
     * Document version of standard used      * Document version of standard used
   


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

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help