| 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 |
|
| |
|
| - make indirection convenient (e.g. bind to looking up something from |
* Add "performance monitoring" subsystem to 'peak.running' |
| another binding) |
|
| |
|
| - eliminate remaining introspection/'isinstance()' checks |
* Add support for finding/registering plugins to 'peak.config' |
| |
|
| |
- Add "Import On Demand" section type for .ini files |
| |
|
| * peak.binding |
- Refactor IConfigKey to support explicit "namespace" concept |
| |
|
| - Cleanup/document attribute binding interface |
- Refactor IPropertyMap -> IConfigMap, add iterability/search |
| |
|
| - Attribute -> AttribDef |
- Add inverted indexes for namespace lookups/search |
| |
|
| - binding.AttribDef has an adequate docstring |
- Add 'IIterableConfigSource' (?) subclass, use for search funcs. |
| |
|
| - Review all current usage of NameNotFound in binding and naming |
- Lock namespaces that have been iterated over |
| 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 |
- Change existing configuration keys not to use tuples as surrogate keys |
| |
|
| - Update tutorial for current kwargs |
- Add 'config.PluginsFor' key that finds plugins |
| |
|
| - Investigate whether suggestParentComponent() should be suppressed when |
- May need 'suggestParentComponent()' to support dictionaries so plugin |
| the value is computed by the binding, or if perhaps 'suggestParent' |
dictionaries will work correctly |
| should be set to 'False' by default for some kinds of bindings. |
|
| |
|
| |
- 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()' |
| |
|
| * peak.web (some of this may get bumped to alpha 4) |
Targeted for 0.5 Alpha 3 |
| |
|
| - 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) |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
* 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) |
| |
|
| |
- 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 |
| |
|
| |
- 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 |
| |
(form metadata, validation, etc. will be handled by peak.web.forms in |
| |
a later release) |
| |
|
| |
- try/catch DOMlet (and related error rendering interface/framework) |
| |
|
| |
|
| |
|
| |
|
| - 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 |
| |
|
| |
|
| - 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'. |
| |
|
| Targeted for 0.5 Beta 1 |
Targeted for 0.5 Beta 1 |
| |
|
| - 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) |
| |
|
| |
|
| |
|
Diff of /PEAK/TODO.txt
Parent Directory
| 
Revision Log