[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 1518, Wed Dec 3 04:08:12 2003 UTC version 1608, Mon Jan 19 04:03:22 2004 UTC
Line 2 
Line 2 
   
  Targeted for 0.5 Alpha 3   Targeted for 0.5 Alpha 3
   
     * peak.binding      * peak.events migration
   
        - Cleanup/document attribute binding interface        - 'running.IProcessProxy' should use conditions/values instead of
           listeners
   
         - Implement basic 'events.ISelector' and 'IEventLoop'
   
         - 'UntwistedReactor' should use an 'events.ISelector' to implement
           I/O functions, and 'IEventLoop' to implement 'run()'
   
         - Add 'events.twisted_support', with 'TwistedScheduler',
          'TwistedSelector', and 'DeferredAsTaskSwitch'
   
       * peak.naming
   
        - Investigate whether suggestParentComponent() should be suppressed when        - 'ILoadingService', 'IObjectLoader' and 'load:kind@URL' scheme
          the value is computed by the binding, or if perhaps 'suggestParent'  
          should be set to 'False' by default for some kinds of bindings.      * 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      * peak.running.logs
   
       - Separate formatters from publishers        - Separate formatters from publishers
   
       - Configurable EventClass        - ZConfig schema for logging plugins, allowing multiple handlers/category
   
       - Loggers know their names and pass that info to event constructor      * peak.binding
   
       - Events should use standard IComponentFactory constructor interface        - Cleanup/document attribute binding interface
   
     * peak.web (some of this may get bumped to alpha 4)  
   
        - fix 'text' DOMlet quoting (i.e., the lack thereof)      * 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)         - clean up DOMlet parse/build framework (e.g. add line number info)
   
        - default error templates, w/useful info         - default error templates, w/useful info
   
        - Refactor skin/layer/resource machinery so that layers can be shared  
          between skins (because i18n will probably want skins and that's going  
          to greatly multiply memory requirements)  
   
        - 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 63 
        - try/catch DOMlet (and related error rendering interface/framework)         - try/catch DOMlet (and related error rendering interface/framework)
   
   
     * Misc.  
   
       - API consolidation? (some users only want core API's in peak.api)  
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  Targeted for 0.5 Alpha 4   Targeted for 0.5 Alpha 4
Line 56 
Line 96 
   
       - 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 73 
Line 120 
       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.1518  
changed lines
  Added in v.1608

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help