|
|
* Refactor binding and naming frameworks to |
* Refactor binding and naming frameworks to |
|
|
- get rid of cruft (such as JNDI 'attrs' hangover) and duplication |
- make indirection convenient (e.g. bind to looking up something from |
|
another binding) |
|
|
- make adaptation available for bindings (e.g. 'adaptTo=' keyword), |
- eliminate remaining introspection/'isinstance()' checks |
including when bindings are set via kwargs in component constructor |
|
|
|
- streamline descriptor mechanisms used by binding and model to make them |
|
uniform and cleanly functional (in both senses of the word functional) |
|
|
|
- clean up attribute metadata framework and get rid of all the special |
* peak.binding |
cases (e.g. isinstance() checks, special attribute names, etc.) |
|
|
|
- add class framework for bindings so that new features like 'adaptTo' |
- Cleanup/document attribute binding interface |
don't have to be added to a jillion individual binding constructors |
|
|
|
- make indirection convenient (e.g. bind to looking up something from |
- Attribute -> AttribDef |
another binding) |
|
|
- 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. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* 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) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Targeted for 0.5 Alpha 4 |
|
|
|
* Transaction/storage refactorings |
|
|
|
- transaction scopes for commands and tasks |
|
|
|
- integrate locks with transactions |
|
|
|
- transactable persistent queues |
|
|
|
- DM.find()/DM.get() queries |
|
|
|
|
|
* peak.web |
|
|
|
- allow use of // in DOMlets' data paths, to access resource space |
|
|
|
- DOMlets for layout/region, as defined in "A layout framework":http://www.eby-sarna.com/pipermail/transwarp/2003-August/000684.html |
|
|
|
- conditional GET support (last modified/ETag) for static resources |
|
|
|
- image resources |
|
|
|
- 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 |
|
create a subclass component with specified 'bindTo' bindings to get its |
|
configuration). |
|
|
* Implement "contextual protocols" (c.f. "object teams") and "parameterized |
* Implement "contextual protocols" (c.f. "object teams") and "parameterized |
protocols" (E.g. 'ListOf(IFoo)', 'MappingOf(keys=IBar,values=IBaz)') |
protocols" (E.g. 'ListOf(IFoo)', 'MappingOf(keys=IBar,values=IBaz)') |
|
|
* Rough-out web publishing framework |
|
|
|
- Publication interfaces |
|
|
|
- Viewer/Controller adaptation mechanisms |
|
|
|
|
|
|
|
|
|
Targeted for 0.5 Beta 1 |
Targeted for 0.5 Beta 1 |
|
|
* Web publishing framework sufficient to deploy page-based or object- |
* Web publishing framework sufficient to deploy page-based or object- |
published apps |
published apps |
|
|
|
|
|
|
Targeted for 0.5 Final Release (or sooner) |
Targeted for 0.5 Final Release (or sooner) |
|
|
peak.storage |
peak.storage |
context or a filesystem context) |
context or a filesystem context) |
|
|
- rework smtp: to return a factory object that supports open(). |
- rework smtp: to return a factory object that supports open(). |
Also think about whether smtp should move elsewhere. Maybe |
Also think about whether smtp should move to peak.net? |
there should be peak.network or peak.internet for things like |
|
smtp, ftp, etc contexts? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- add in Ty's cool "n2" (Namespace Navigator) shell for working with |
|
naming providers. |
|
|
|
|
|
Targeted for version 0.6 |
Targeted for version 0.6 |
tools with PEAK ones.) |
tools with PEAK ones.) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Future Releases |
Future Releases |
|
|
(Note: some of the below is held-over from TransWarp and may no longer be |
(Note: some of the below is held-over from TransWarp and may no longer be |