[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 1502, Fri Nov 28 23:59:01 2003 UTC version 1556, Sun Dec 21 02:24:14 2003 UTC
Line 1 
Line 1 
 Open Issues/To-Do Items  Open Issues/To-Do Items
   
    Short Term Project Support
   
       * Add "performance monitoring" subsystem to 'peak.running'
   
       * Add support for finding/registering plugins to 'peak.config'
   
         - Refactor IConfigKey to support explicit "namespace" concept
   
         - Refactor IPropertyMap -> IConfigMap, add iterability/search
   
           - Add inverted indexes for namespace lookups/search
   
           - Add 'IIterableConfigSource' (?) subclass, use for search funcs.
   
           - Lock namespaces that have been iterated over
   
         - Change existing configuration keys not to use tuples as surrogate keys
   
         - Add 'config.PluginsFor' key that finds plugins
   
           - May need 'suggestParentComponent()' to support dictionaries so plugin
             dictionaries will work correctly
   
           - Should it implement the "smart property" interface?
   
         - Things to look at during refactorings:
   
           - Better consolidation of config/component key and recipe interfaces?
   
           - Rule chaining
   
           - Use objects for section parsing instead of functions?
   
       * peak.storage
   
         - 'storage.dbType()'
   
   
   
  Targeted for 0.5 Alpha 3   Targeted for 0.5 Alpha 3
   
     * peak.binding      * peak.binding
   
        - Cleanup/document attribute binding interface         - Cleanup/document attribute binding interface
   
        - Investigate whether suggestParentComponent() should be suppressed when      * peak.running.logs
          the value is computed by the binding, or if perhaps 'suggestParent'  
          should be set to 'False' by default for some kinds of bindings.        - 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)      * peak.web (some of this may get bumped to alpha 4)
   
          - fix 'text' DOMlet quoting (i.e., the lack thereof)
   
          - 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         - Refactor skin/layer/resource machinery so that layers can be shared
          between skins (because i18n will probably want skins and that's going           between skins (because i18n will probably want skins and that's going
          to greatly multiply memory requirements)           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         - 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 32 
Line 80 
   
   
   
   
   
   
   
   
   
   
  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
   
          - Iterable keys to PropertyMap (rename to configMap?)
   
          - Writable and subscribable config sources, including editable .ini's
   
     * peak.web      * peak.web
   
Line 68 
Line 118 
       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'.
   
   
   
   
   
   
   
   
   
   
  Targeted for 0.5 Beta 1   Targeted for 0.5 Beta 1
   


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

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help