| Open Issues/To-Do Items |
Open Issues/To-Do Items |
| |
|
| Release Checklist for 0.5 Alpha 1 |
Targeted for 0.5 Alpha 3 |
| |
|
| - Cleanup/document attribute binding mechanism as an 'IAttributeBinding' interface |
* peak.binding |
| |
|
| - Make all API signatures start with context component |
- Cleanup/document attribute binding interface |
| |
|
| - Review binding tutorial and correct any errors relative to current APIs |
- 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. |
| |
|
| - Add 'fcgiapp' module sources to distribution; update README/INSTALL to credit |
* peak.running.logs |
| DC and OpenMarket and reference their licenses. |
|
| |
|
| |
- Separate formatters from publishers |
| |
|
| Targeted for 0.5 Alpha 2 |
- Configurable EventClass |
| |
|
| * ZConfig Integration |
- Loggers know their names and pass that info to event constructor |
| |
|
| - A 'config.ZConfig' module that provides "PEAK-aware" versions of ZConfig |
- Events should use standard IComponentFactory constructor interface |
| services (e.g. it will use 'peak.naming' to resolve URLs) |
|
| |
|
| - App startup tools based on ZConfig files. |
* peak.web (some of this may get bumped to alpha 4) |
| |
|
| - Sample 'AdaptiveTask' classes that perform the same functions as those in |
- fix 'text' DOMlet quoting (i.e., the lack thereof) |
| the MetaDaemon package, with a ZConfig schema to run them in a daemon-like |
|
| application. |
|
| |
|
| * Fix issue w/reading XMI 1.1 files where metamodel has nested packages |
- clean up DOMlet parse/build framework (e.g. add line number info) |
| |
|
| * Generate UML 1.4 and 1.5 and CWM 1.0 and 1.1, and add them to the |
|
| 'setup.py' package lists. |
|
| |
|
| * Get XMI writing in place, w/transaction support |
|
| |
|
| * Generate ZConfig schemas from 'peak.model' or MOF models? |
|
| |
|
| * 'peak.running' refactorings: use standard 'logging' module's log levels, |
|
| add 'logging' distro to 'peak.util' for 2.2 backward compatibility, |
|
| and possibly adjust cluster stuff to work off ZConfig primary and |
|
| generate clustertools file(s). |
|
| |
|
| * 'peak.naming' refactorings: 'peak.model'-based syntax utilities for |
|
| creating address syntaxes. |
|
| |
|
| |
- default error templates, w/useful info |
| |
|
| Targeted for 0.5 Beta 1 |
- 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) |
| |
|
| * Updated reference docstrings for 'peak.api', 'peak.binding', |
- A set of simple, basic form controls that handle value rendering only |
| 'peak.config', 'peak.exceptions', and 'peak.naming'. |
(form metadata, validation, etc. will be handled by peak.web.forms in |
| |
a later release) |
| |
|
| * Finish tutorial chapter 2 (?) |
- try/catch DOMlet (and related error rendering interface/framework) |
| |
|
| * On-the-fly class combination (think "runtime module inheritance", |
|
| without the modules) for DMs. |
|
| |
|
| |
* 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 |
| |
|
| |
|
| |
|
| Targeted for 0.5 Final Release (or sooner) |
Targeted for 0.5 Final Release (or sooner) |
| |
|
| General |
|
| |
|
| * Tutorial complete through chapter 4 |
|
| |
|
| peak.storage |
peak.storage |
| |
|
| - unit tests for more complex object scenarios: references, thunks..? |
- unit tests for more complex object scenarios: references, thunks..? |
| |
|
| - lock management interfaces/API |
|
| |
|
| - docstrings for reference |
|
| |
|
| peak.model |
|
| |
|
| - clean up TW docstrings & interfaces |
|
| |
|
| peak.naming |
peak.naming |
| |
|
| - useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
- useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
| |
|
| - useful example hierarchical naming context (e.g. like JNDI's LDAP |
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
| context or 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? |
|
| |
|
| peak.running |
|
| |
|
| - make 'cluster' parser complain about things that would cause |
|
| the clusterit tools to choke or barf on the file, or which would |
|
| produce ambiguous or unintended results. |
|
| |
|
| - simple daemons comparable to those in MetaDaemon, unit tests |
|
| |
|
| - docstrings for reference |
|
| |
|
| |
|
| peak.config |
|
| |
|
| - "Rule"-oriented configuration files (section specifies component |
|
| rather than property name prefix), so that daemons and other simple |
|
| apps can be fully configured and run via a config file. |
|
| |
|
| peak.util |
|
| |
|
| - docstrings for reference |
|
| |
|
| - more unit tests? |
|
| |
|
| |
|
| |
|
| |
|
| |
Targeted for version 0.6 |
| |
|
| |
* Get XMI writing in place, w/transaction support |
| |
|
| |
* Generate UML 1.5 and CWM 1.0 and 1.1, and add them to the |
| |
'setup.py' package lists. |
| |
|
| |
* On-the-fly class combination (think "runtime module inheritance", |
| |
but possibly without the modules) for DMs. |
| |
|
| |
* Lock management interfaces/API for peak.storage |
| |
|
| |
* Make 'cluster' parser complain about things that would cause |
| |
the clusterit tools to choke or barf on the file, or which would |
| |
produce ambiguous or unintended results. (Or replace with ZConfig |
| |
schema that can generate clusterit files. And/or replace clusterit |
| |
tools with PEAK ones.) |
| |
|
| |
|
| |
|
| - 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