[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 1369, Fri Aug 29 21:11:53 2003 UTC version 1575, Sun Dec 28 14:29:58 2003 UTC
Line 1 
Line 1 
 Open Issues/To-Do Items  Open Issues/To-Do Items
   
  Targeted for 0.5 Alpha 3   Short Term Project Support
   
     * Refactor binding and naming frameworks to      * peak.running.timers
   
       - make indirection convenient (e.g. bind to looking up something from        - Factor out state into separate object so timers aren't shared state
         another binding)  
   
       - eliminate remaining introspection/'isinstance()' checks        - Look at possible integration of peak.query and cursor formatters, in
           order to view stats as an in-memory mini-DB w/reporting.
   
   
     * peak.binding  
   
        - Cleanup/document attribute binding interface  
   
        - Attribute -> AttribDef  
   
        - binding.AttribDef has an adequate docstring  
   
        - Review all current usage of NameNotFound in binding and naming  
          packages.  If possible, push default values closer to the point of  
          retrieval.  (The idea is to minimize the possibility that an unrelated  
          NameNotFound error gets hidden by a routine catching NameNotFound  
          in order to return a default value.)  
   
        - Ensure default __repr__'s for all bindings are acceptable  
   
        - Update tutorial for current kwargs  
   
        - 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.  
   
   
   
Line 39 
Line 25 
   
   
   
     * peak.web (some of this may get bumped to alpha 4)  
   
        - 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)  
   
        - clean up DOMlet parse/build framework (e.g. add line number 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)  
   
   
   
Line 63 
Line 39 
   
   
   
    Targeted for 0.5 Alpha 3
   
       * peak.binding
   
         - Cleanup/document attribute binding interface
   
       * 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)
   
   
   
Line 92 
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 105 
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 'bindTo' bindings to get its        create a subclass component with specified 'Obtain' or 'Make' bindings to
       configuration).        get its configuration).
   
     * Implement "contextual protocols" (c.f. "object teams") and "parameterized  
       protocols" (E.g. 'ListOf(IFoo)', 'MappingOf(keys=IBar,values=IBaz)')  
   
   
   
   
   
       * Drop 'persistence' package, since ZODB 4 has been derailed.  Change to
         "state-delegation" model, which will integrate better with 'peak.query'.
   
   
   
Line 306 
Line 306 
       - What determines whether an implemented Service actually stores objects        - What determines whether an implemented Service actually stores objects
         or delegates this to its subclass services?          or delegates this to its subclass services?
   
     * Simple Zope product demo (upload XMI, then browse the model via the web)      * Simple demo (browse XMI model via the web)
   
   
   


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

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help