[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 1407, Fri Oct 3 23:06:06 2003 UTC version 1615, Wed Jan 21 23:38:39 2004 UTC
Line 2 
Line 2 
   
  Targeted for 0.5 Alpha 3   Targeted for 0.5 Alpha 3
   
     * peak.binding      * peak.events migration
   
         - 'running.IProcessProxy' should use conditions/values instead of
           listeners, and related command/supervisor tools should also be ported
   
         - Add tests for Twisted support
   
         - Make it possible to adapt from condition->value, so deriving from conds
           can still work, and implement events.AllOf() as a condition
   
         - Replace IMainLoop activity monitoring with a plugin-based mechanism?
   
       * peak.naming
   
         - '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.
   
        - make indirection convenient (e.g. bind to looking up something from      * peak.running.logs
          another binding)  
         - Separate formatters from publishers
   
         - ZConfig schema for logging plugins, allowing multiple handlers/category
   
       * peak.binding
   
        - Cleanup/document attribute binding interface         - Cleanup/document attribute binding interface
   
        - Ensure default __repr__'s for all bindings are acceptable  
   
        - Investigate whether suggestParentComponent() should be suppressed when  
          the value is computed by the binding, or if perhaps 'suggestParent'  
          should be set to 'False' by default for some kinds of bindings.  
   
       * peak.running.timers
   
     * peak.web (some of this may get bumped to alpha 4)        - Factor out state into separate object so timers aren't shared state
   
        - default error templates, w/useful info        - 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
   
        - Refactor skin/layer/resource machinery so that layers can be shared         - Add "error formatting" and "error reporting" services
          between skins (because i18n will probably want skins and that's going  
          to greatly multiply memory requirements)      * peak.web (some of this may get bumped to alpha 4)
   
        - clean up DOMlet parse/build framework (e.g. add line number info)         - 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         - A set of simple, basic form controls that handle value rendering only
          (form metadata, validation, etc. will be handled by peak.web.forms in           (form metadata, validation, etc. will be handled by peak.web.forms in
          a later release)           a later release)
Line 39 
Line 69 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  Targeted for 0.5 Alpha 4   Targeted for 0.5 Alpha 4
   
     * Transaction/storage refactorings      * Transaction/storage refactorings
Line 51 
Line 92 
   
       - DM.find()/DM.get() queries        - DM.find()/DM.get() queries
   
       * peak.running.commands
   
          - Add option parsing framework based on optparse (backported to 2.2)
   
       * peak.config
   
          - Writable and subscribable config sources, including editable .ini's
   
     * peak.web      * peak.web
   
Line 64 
Line 112 
   
        - the return of the Specialist         - the return of the Specialist
   
     * "Pre-forking event driven services":http://www.eby-sarna.com/pipermail/transwarp/2003-August/000697.html  
   
     * Have a way to easily in-line custom component usage (e.g. automatically      * Have a way to easily in-line custom component usage (e.g. automatically
       create a subclass component with specified 'Obtain' or 'Make' bindings to        create a subclass component with specified 'Obtain' or 'Make' bindings to
       get its configuration).        get its configuration).
   
     * Implement "contextual protocols" (c.f. "object teams") and "parameterized      * Drop 'persistence' package, since ZODB 4 has been derailed.  Change to
       protocols" (E.g. 'ListOf(IFoo)', 'MappingOf(keys=IBar,values=IBaz)')        "state-delegation" model, which will integrate better with 'peak.query'.
   
   
   
   
   
   
   
   


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

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help