[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 365, Wed Mar 27 23:34:39 2002 UTC version 615, Wed Nov 6 20:38:22 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
   
     API.Modules      General
   
       * Add tests for 'adviseModule()' API          * Update tutorial documentation
   
       * Add checks and warnings for ambiguous re-assignments and operations          * Up-to-date and complete Persistence package
         on mutables  (i.e. setting items or attrs), plus "safe" setattr  
   
     Database      peak.storage
   
       * Create test suite to check proper transactional functioning, cache          - URLs and drivers for gadfly, Sybase, and postgres
         consistency, queueing behavior, and typemap management.  
           - LDAP schema properties, SQL type mapping utilities
   
           - Rack -> DM
   
           - "facade" DM base class(es)
   
           - "query" DM base class(es)
   
           - unit tests for more complex object scenarios: references, thunks..?
   
           - docstrings for reference
   
       peak.binding
   
           - object names/paths
   
           - docstrings for reference
   
       peak.model
   
           - add support for lazy-loaded attributes
   
           - clean up TW docstrings & interfaces
   
       peak.config
   
           - docstrings for reference
   
       peak.naming
   
           - clarify requirements re: initial context, and add SPI functions
             to initctx, so that that can be the right way to get such APIs
             (e.g. getURLContext()).
   
           - review context interfaces and URL hooks/hacks
   
           - docstrings for reference
   
       peak.running
   
           - create a basic LogFile logging provider
   
           - unit tests for daemons?
   
           - simple daemons comparable to those in MetaDaemon?
   
           - docstrings for reference
   
       peak.util
   
           - docstrings for reference
   
           - more unit tests?
   
       * Update Interfaces to reflect current API, and document internals  
   
     General  
   
       * Update tutorial documentation  
   
   
  Ideas for 0.3 Release  
   
     Dispatching  
   
       * Virtual features to implement retrieving the other end of a  
         relationship from another Specialist.  
   
     SEF  
   
       * 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?  
   
   
     General  
   
       * Profiling and performance tuning of module inheritance and other  
         core features of API and SEF.  
   
   
   
  Future Releases   Future Releases
   
     (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
     ideas or problem areas that may need to be re-considered in future.)
   
   
   Simulator/Module Inheritance    Simulator/Module Inheritance
   
     * Need a strategy for handling "del" operations; they are currently      * Need a strategy for handling "del" operations; they are currently
Line 62 
Line 102 
       pass of importing a module (prior to running 'setupModule()')        pass of importing a module (prior to running 'setupModule()')
   
   
   Documentation/Tests/General    Messaging/ObjectSpaces
   
       * Support for sending and receiving remote cache invalidation
         messages between RecordManagers.
   
   
   
     * Create tutorials/examples based on actual uses  
   
     * Include dependencies in packaging?  Need to ask copyright owners first.  
   
   
   
Line 80 
Line 123 
   
   
   
   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 134 
   
     * 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      * A way to generate Z3 Interfaces from Feature-based specifications?
   
     InMemory  
   
       * "Indexed" version  
   
       * "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?)
   
   
     Queries      Queries
   
        * Refactor to use interfaces, if appropriate         * Refactor to use interfaces, if appropriate
Line 121 
Line 163 
          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 193 
   
     * 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 206 
   
   
   
   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.365  
changed lines
  Added in v.615

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help