[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 1615, Wed Jan 21 23:38:39 2004 UTC version 1633, Sun Jan 25 02:32:15 2004 UTC
Line 12 
Line 12 
       - Make it possible to adapt from condition->value, so deriving from conds        - Make it possible to adapt from condition->value, so deriving from conds
         can still work, and implement events.AllOf() as a condition          can still work, and implement events.AllOf() as a condition
   
       - Replace IMainLoop activity monitoring with a plugin-based mechanism?      * peak.ddt
   
     * peak.naming        - Row and Action processors, better heading->property name translation
   
       - 'ILoadingService', 'IObjectLoader' and 'load:kind@URL' scheme  
   
     * peak.config  
   
       - "service zones" or "service groups" to do smarter service groupings  
   
       - plugin keys ordered by definition sequence, rather than randomly  
   
       - ZConfig factory support to allow "smart" interpretation of strings,  
         section names, etc.  
   
     * peak.running.logs  
   
       - Separate formatters from publishers  
   
       - ZConfig schema for logging plugins, allowing multiple handlers/category  
   
     * peak.binding  
   
       - Cleanup/document attribute binding interface  
   
   
   
     * peak.running.timers  
   
       - Factor out state into separate object so timers aren't shared state  
   
       - Look at possible integration of peak.query and cursor formatters, in  
         order to view stats as an in-memory mini-DB w/reporting.  
   
     * peak.running  
   
        - Add "error formatting" and "error reporting" services  
   
     * peak.web (some of this may get bumped to alpha 4)  
   
        - clean up DOMlet parse/build framework (e.g. add line number info)  
   
        - default error templates, w/useful info  
   
        - A set of simple, basic form controls that handle value rendering only  
          (form metadata, validation, etc. will be handled by peak.web.forms in  
          a later release)  
   
        - try/catch DOMlet (and related error rendering interface/framework)  
   
   
    Targeted for 0.5 Alpha 4
   
       * 'ILoadingService', 'IObjectLoader' and 'load:kind@URL' scheme
   
       * peak.config
   
         - "service zones" or "service groups" to do smarter service groupings
   
         - Replace IMainLoop activity monitoring with a plugin-based mechanism?
   
         - plugin keys ordered by definition sequence, rather than randomly
   
         - ZConfig factory support to allow "smart" interpretation of strings,
           section names, etc.
   
         - Writable and subscribable config sources, including editable .ini's
   
       * peak.running.logs
   
         - Separate formatters from publishers
   
         - ZConfig schema for logging plugins, allowing multiple handlers/category
   
       * peak.running.commands
   
          - Add "error formatting" and "error reporting" services
   
          - Add option parsing framework based on optparse (backported to 2.2)
   
       * peak.binding
   
         - Cleanup/document attribute binding interface
   
       * peak.running.timers
   
         - Factor out state into separate object so timers aren't shared state
   
         - Look at possible integration of peak.query and cursor formatters, in
           order to view stats as an in-memory mini-DB w/reporting.
   
  Targeted for 0.5 Alpha 4  
   
     * Transaction/storage refactorings      * Transaction/storage refactorings
   
Line 92 
Line 90 
   
       - DM.find()/DM.get() queries        - DM.find()/DM.get() queries
   
     * peak.running.commands      * peak.web
   
        - Add option parsing framework based on optparse (backported to 2.2)         - clean up DOMlet parse/build framework (e.g. add line number info)
   
     * peak.config         - default error templates, w/useful info
   
        - Writable and subscribable config sources, including editable .ini's         - A set of simple, basic form controls that handle value rendering only
            (form metadata, validation, etc. will be handled by peak.web.forms in
            a later release)
   
     * peak.web         - try/catch DOMlet (and related error rendering interface/framework)
   
        - allow use of // in DOMlets' data paths, to access resource space         - allow use of // in DOMlets' data paths, to access resource space
   
Line 164 
Line 164 
   
  Targeted for version 0.6   Targeted for version 0.6
   
      * Functional/acceptance tests that access "real" databases, LDAP, etc.
   
    * Get XMI writing in place, w/transaction support     * Get XMI writing in place, w/transaction support
   
    * Generate UML 1.5 and CWM 1.0 and 1.1, and add them to the     * Generate UML 1.5 and CWM 1.0 and 1.1, and add them to the
Line 174 
Line 176 
   
    * Lock management interfaces/API for peak.storage     * Lock management interfaces/API for peak.storage
   
      * Support for sending and receiving remote cache invalidation
        messages between DataManagers.
   
    * 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.  (Or replace with ZConfig       produce ambiguous or unintended results.  (Or replace with ZConfig
Line 198 
Line 203 
   
   
   
   
   
   
   
   
  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.)  
   
   Miscellaneous  
   
     * Functional tests that access "real" databases, LDAP, etc.  
   
   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  
       untrapped.  This might be okay under most circumstances, but need to  
       consider edge cases.  
   
     * 'makeClass()' should probably become part of the core API, where  
       it can be used to resolve __metaclass__ conflicts during the first  
       pass of importing a module (prior to running 'setupModule()')  
   
   
   Messaging/ObjectSpaces  
   
     * Support for sending and receiving remote cache invalidation  
       messages between DataManagers.  
   
   
   
   
   
   
   
   
   
   
   
   
   peak.model  
   
     * Implement WarpCORE-oriented structural model, w/Querying support  
   
     * "Indexed" version of in-memory model?  
   
   
     Queries  
   
        * Refactor to use interfaces, if appropriate  
   
        * Incorporate into AbstractModel?  
   
          - Pros:  
   
            * Queries always available  
   
            * Each StructuralModel implementation can easily include its own  
              performance-tuned version of the basic items.  
   
          - Con: default implementation doesn't perform well on large datasets  
   
        * How much of framework needs extensibility?  Should the predicate  
          classes be placed in the StructuralModel's namespace so that predicates  
          have their meaning assigned by the StructuralModel implementation?  
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   peak.metamodels.uml  
   
     * Helper methods in Elements & Services for marshalling, common queries, etc.  
   
     * Generator framework  
   
       - Tagged values in stereotypes vs. main values?  
   
       - Should tagged values be copied directly into templates?  Treated as  
         Python expressions?  
   
       - Should Services be generated using an Element class' "static"  
         (class-scope) methods/attributes?  
   
         - Are association-ends scoped?  
   
         - Would it be better to seperate them?  
   
       - What determines whether an implemented Service actually stores objects  
         or delegates this to its subclass services?  
   
     * Simple demo (browse XMI model via the web)  
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   


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

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help