[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 1573, Sun Dec 28 00:14:24 2003 UTC version 1608, Mon Jan 19 04:03:22 2004 UTC
Line 1 
Line 1 
 Open Issues/To-Do Items  Open Issues/To-Do Items
   
  Short Term Project Support   Targeted for 0.5 Alpha 3
   
     * Add support for finding/registering plugins to 'peak.config'  
   
       - Add 'config.PluginsFor' key that finds plugins      * peak.events migration
   
         - May need 'suggestParentComponent()' to support dictionaries so plugin        - 'running.IProcessProxy' should use conditions/values instead of
           dictionaries will work correctly          listeners
   
         - Should it implement the "smart property" interface?        - Implement basic 'events.ISelector' and 'IEventLoop'
   
       - Lock namespaces that have been iterated over (do we need this?)        - 'UntwistedReactor' should use an 'events.ISelector' to implement
           I/O functions, and 'IEventLoop' to implement 'run()'
   
       - Things to look at during refactorings:        - Add 'events.twisted_support', with 'TwistedScheduler',
          'TwistedSelector', and 'DeferredAsTaskSwitch'
   
         - Better consolidation of config/component key and recipe interfaces?      * peak.naming
   
         - Rule chaining        - 'ILoadingService', 'IObjectLoader' and 'load:kind@URL' scheme
   
         - Use objects for section parsing instead of functions?      * peak.config
   
     * peak.storage        - "service zones" or "service groups" to do smarter service groupings
   
       - 'storage.dbType()'        - 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)
   
  Targeted for 0.5 Alpha 3         - default error templates, w/useful info
   
     * peak.binding         - 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)
   
       - Cleanup/document attribute binding interface         - try/catch DOMlet (and related error rendering interface/framework)
   
     * peak.running.logs  
   
       - Add 'DefaultLoggingService', service-based system  
   
       - Separate formatters from publishers  
   
       - Loggers should know their names and pass that info to event constructor  
   
     * peak.config  
   
       - 'ZConfigSchemaService' and 'zconfig:schema@streamURL' scheme  
   
     * 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)  
   
   
   


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

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help