| |
|
| Targeted for 0.5 Alpha 3 |
Targeted for 0.5 Alpha 3 |
| |
|
| * Refactor binding and naming frameworks to |
* peak.binding |
| |
|
| - streamline descriptor mechanisms used by binding and model to make them |
- Cleanup/document attribute binding interface |
| uniform and cleanly functional (in both senses of the word functional) |
|
| |
|
| - make indirection convenient (e.g. bind to looking up something from |
- Investigate whether suggestParentComponent() should be suppressed when |
| another binding) |
the value is computed by the binding, or if perhaps 'suggestParent' |
| |
should be set to 'False' by default for some kinds of bindings. |
| |
|
| - eliminate remaining introspection/'isinstance()' checks |
* peak.running.logs |
| |
|
| * Implement "contextual protocols" (c.f. "object teams") and "parameterized |
- Separate formatters from publishers |
| protocols" (E.g. 'ListOf(IFoo)', 'MappingOf(keys=IBar,values=IBaz)') |
|
| |
|
| * Rough-out web publishing framework |
- Configurable EventClass |
| |
|
| - Publication interfaces |
- Loggers know their names and pass that info to event constructor |
| |
|
| - Viewer/Controller adaptation mechanisms |
- Events should use standard IComponentFactory constructor interface |
| |
|
| |
* peak.web (some of this may get bumped to alpha 4) |
| |
|
| Targeted for 0.5 Beta 1 |
- fix 'text' DOMlet quoting (i.e., the lack thereof) |
| |
|
| * Up-to-date reference docstrings for all packages |
- clean up DOMlet parse/build framework (e.g. add line number info) |
| |
|
| * Finish tutorial chapter 2 (?) |
- default error templates, w/useful info |
| |
|
| * Web publishing framework sufficient to deploy page-based or object- |
- Refactor skin/layer/resource machinery so that layers can be shared |
| published apps |
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) |
| |
|
| |
|
| |
* Misc. |
| |
|
| |
- Namespace re-orgs? (e.g. peak.running.tools -> peak.tools?) |
| |
|
| |
- API consolidation? (some users only want core API's in peak.api) |
| |
|
| |
|
| |
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 |
| |
|
| |
* Have a way to easily in-line custom component usage (e.g. automatically |
| |
create a subclass component with specified 'Obtain' or 'Make' bindings to |
| |
get its configuration). |
| |
|
| |
* Implement "contextual protocols" (c.f. "object teams") and "parameterized |
| |
protocols" (E.g. 'ListOf(IFoo)', 'MappingOf(keys=IBar,values=IBaz)') |
| |
|
| |
|
| |
|
| |
Targeted for 0.5 Beta 1 |
| |
|
| |
* Up-to-date reference docstrings for all packages |
| |
|
| |
* Finish tutorial chapter 2 (?) |
| |
|
| |
* Web publishing framework sufficient to deploy page-based or object- |
| |
published apps |
| |
|
| |
|
| |
|
| 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 |
| - 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