| Open Issues/To-Do Items |
Open Issues/To-Do Items |
| |
|
| Release Checklist for 0.5 Alpha 1 |
Targeted for 0.5 Alpha 3 |
| |
|
| - Unit tests for event-driven operations: IMainLoop, IPeriodicTask, and ITaskQueue |
* peak.events migration |
| |
|
| - Cleanup/document attribute binding mechanism as an 'IAttributeBinding' interface |
- Add tests for Twisted support |
| |
|
| - Make all API signatures start with context component |
* peak.ddt |
| |
|
| - Finalize name for 'config.Application' - probably 'config.DefaultContext' |
- A bit more doc and demos |
| |
|
| - Review binding tutorial and correct any errors relative to current APIs |
|
| |
|
| - Add 'fcgiapp' module sources to distribution; update README/INSTALL to credit |
|
| DC and OpenMarket and reference their licenses. |
|
| |
|
| |
|
| |
|
| Targeted for 0.5 Alpha 2 |
|
| |
|
| * ZConfig Integration |
|
| |
|
| - A 'config.ZConfig' module that provides "PEAK-aware" versions of ZConfig |
|
| services (e.g. it will use 'peak.naming' to resolve URLs) |
|
| |
|
| - App startup tools based on ZConfig files. |
|
| |
|
| - Sample 'AdaptiveTask' classes that perform the same functions as those in |
|
| 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 |
|
| |
|
| * 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. |
|
| |
|
| |
|
| Targeted for 0.5 Beta 1 |
|
| |
|
| * Updated reference docstrings for 'peak.api', 'peak.binding', |
|
| 'peak.config', 'peak.exceptions', and 'peak.naming'. |
|
| |
|
| * Finish tutorial chapter 2 (?) |
|
| |
|
| * On-the-fly class combination (think "runtime module inheritance", |
|
| without the modules) for DMs. |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
Targeted for 0.5 Alpha 4 |
| |
|
| |
* 'ILoadingService', 'IObjectLoader' and 'load:kind@URL' scheme |
| |
|
| |
* peak.config |
| |
|
| |
- "service zones" or "service groups" to do smarter service groupings |
| |
|
| |
- Replace IMainLoop activity monitoring with a plugin-based mechanism? |
| |
|
| |
- plugin keys ordered by definition sequence, rather than randomly |
| |
|
| |
- ZConfig factory support to allow "smart" interpretation of strings, |
| |
section names, etc. |
| |
|
| |
- Writable and subscribable config sources, including editable .ini's |
| |
|
| |
* peak.running.logs |
| |
|
| |
- Separate formatters from publishers |
| |
|
| |
- ZConfig schema for logging plugins, allowing multiple handlers/category |
| |
|
| |
* peak.running.commands |
| |
|
| |
- Add "error formatting" and "error reporting" services |
| |
|
| Targeted for 0.5 Final Release (or sooner) |
- Add option parsing framework based on optparse (backported to 2.2) |
| |
|
| General |
* peak.binding |
| |
|
| * Tutorial complete through chapter 4 |
- Cleanup/document attribute binding interface |
| |
|
| peak.storage |
* peak.running.timers |
| |
|
| - unit tests for more complex object scenarios: references, thunks..? |
- Factor out state into separate object so timers aren't shared state |
| |
|
| - lock management interfaces/API |
- Look at possible integration of peak.query and cursor formatters, in |
| |
order to view stats as an in-memory mini-DB w/reporting. |
| |
|
| - docstrings for reference |
|
| |
|
| peak.model |
* Transaction/storage refactorings |
| |
|
| - clean up TW docstrings & interfaces |
- transaction scopes for commands and tasks |
| |
|
| peak.naming |
- integrate locks with transactions |
| |
|
| - useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
- transactable persistent queues |
| |
|
| - useful example hierarchical naming context (e.g. like JNDI's LDAP |
- DM.find()/DM.get() queries |
| context or filesystem context) |
|
| |
|
| - rework smtp: to return a factory object that supports open(). |
|
| Also think about whether smtp should move elsewhere. Maybe |
|
| there should be peak.network or peak.internet for things like |
|
| smtp, ftp, etc contexts? |
|
| |
|
| peak.running |
* peak.web |
| |
|
| - 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 |
- clean up DOMlet parse/build framework (e.g. add line number info) |
| |
|
| - docstrings for reference |
- default error templates, w/useful 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) |
| |
|
| peak.config |
- try/catch DOMlet (and related error rendering interface/framework) |
| |
|
| - "Rule"-oriented configuration files (section specifies component |
- allow use of // in DOMlets' data paths, to access resource space |
| rather than property name prefix), so that daemons and other simple |
|
| apps can be fully configured and run via a config file. |
|
| |
|
| peak.util |
- DOMlets for layout/region, as defined in "A layout framework":http://www.eby-sarna.com/pipermail/transwarp/2003-August/000684.html |
| |
|
| - docstrings for reference |
- conditional GET support (last modified/ETag) for static resources |
| |
|
| - more unit tests? |
|
| |
|
| |
- 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). |
| |
|
| |
* 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 |
| |
|
| |
* 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) |
| |
|
| |
peak.storage |
| |
|
| |
- unit tests for more complex object scenarios: references, thunks..? |
| |
|
| |
peak.naming |
| |
|
| |
- useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
| |
|
| |
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
| |
context or a filesystem context) |
| |
|
| |
- rework smtp: to return a factory object that supports open(). |
| |
Also think about whether smtp should move to peak.net? |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| Future Releases |
|
| |
|
| (Note: some of the below is held-over from TransWarp and may no longer be |
|
| relevant as written, they are being kept on this list as placeholders for |
|
| ideas or problem areas that may need to be re-considered in future.) |
|
| |
|
| Miscellaneous |
|
| |
|
| * Functional tests that access "real" databases, LDAP, etc. |
|
| |
|
| Simulator/Module Inheritance |
Targeted for version 0.6 |
| |
|
| * Allow 'declareModule()' to bootstrap non-existent modules; this might |
* Functional/acceptance tests that access "real" databases, LDAP, etc. |
| let us create "virtual packages" made by assembling other packages and |
|
| modules. |
|
| |
|
| * Need a strategy for handling "del" operations; they are currently |
* Get XMI writing in place, w/transaction support |
| untrapped. This might be okay under most circumstances, but need to |
|
| consider edge cases. |
|
| |
|
| * 'makeClass()' should probably become part of the core API, where |
* Generate UML 1.5 and CWM 1.0 and 1.1, and add them to the |
| it can be used to resolve __metaclass__ conflicts during the first |
'setup.py' package lists. |
| pass of importing a module (prior to running 'setupModule()') |
|
| |
|
| |
* On-the-fly class combination (think "runtime module inheritance", |
| |
but possibly without the modules) for DMs. |
| |
|
| Messaging/ObjectSpaces |
* Lock management interfaces/API for peak.storage |
| |
|
| * Support for sending and receiving remote cache invalidation |
* Support for sending and receiving remote cache invalidation |
| messages between DataManagers. |
messages between DataManagers. |
| |
|
| |
* 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.) |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| peak.model |
|
| |
|
| * Implement WarpCORE-oriented structural model, w/Querying support |
|
| |
|
| * "Indexed" version of in-memory model? |
|
| |
|
| |
|
| Queries |
|
| |
|
| * Refactor to use interfaces, if appropriate |
|
| |
|
| * Incorporate into AbstractModel? |
|
| |
|
| - Pros: |
|
| |
|
| * Queries always available |
|
| |
|
| * Each StructuralModel implementation can easily include its own |
|
| performance-tuned version of the basic items. |
|
| |
|
| - Con: default implementation doesn't perform well on large datasets |
|
| |
|
| * How much of framework needs extensibility? Should the predicate |
|
| classes be placed in the StructuralModel's namespace so that predicates |
|
| have their meaning assigned by the StructuralModel implementation? |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| peak.metamodels.uml |
|
| |
|
| * Helper methods in Elements & Services for marshalling, common queries, etc. |
|
| |
|
| * Generator framework |
|
| |
|
| - Tagged values in stereotypes vs. main values? |
|
| |
|
| - Should tagged values be copied directly into templates? Treated as |
|
| Python expressions? |
|
| |
|
| - Should Services be generated using an Element class' "static" |
|
| (class-scope) methods/attributes? |
|
| |
|
| - Are association-ends scoped? |
|
| |
|
| - Would it be better to seperate them? |
|
| |
|
| - What determines whether an implemented Service actually stores objects |
|
| or delegates this to its subclass services? |
|
| |
|
| * Simple Zope product demo (upload XMI, then browse the model via the web) |
|
| |
|
| |
|
| |
|
Diff of /PEAK/TODO.txt
Parent Directory
| 
Revision Log