| Open Issues/To-Do Items |
Targeted for 0.5 Alpha 4 |
| |
|
| Targeted for 0.5 Final Release |
* peak.config |
| |
|
| General |
- "service zones" or "service groups" to do smarter service groupings |
| |
|
| * Update tutorial documentation |
- Replace IMainLoop activity monitoring with a plugin-based mechanism? |
| |
|
| * Up-to-date and complete Persistence package |
- plugin keys ordered by definition sequence, rather than randomly |
| |
|
| peak.binding |
- ZConfig factory support to allow "smart" interpretation of strings, |
| |
section names, etc. |
| |
|
| - docstrings for reference |
- Writable and subscribable config sources, including editable .ini's |
| |
|
| peak.config |
* peak.running.logs |
| |
|
| - docstrings for reference |
- Separate formatters from publishers |
| |
|
| peak.model |
- ZConfig schema for logging plugins, allowing multiple handlers/category |
| |
|
| - make Element Persistent; add support for lazy-loaded attributes |
* peak.running.commands |
| |
|
| - review XMI/Querying extensions for forward compatibility planning |
- Add "error formatting" and "error reporting" services |
| |
|
| - clean up TW docstrings & interfaces |
- Add option parsing framework based on optparse (backported to 2.2) |
| |
|
| peak.naming |
* peak.binding |
| |
|
| - docstrings for reference |
|
| |
|
| peak.running |
|
| |
|
| - create a basic LogFile logging provider |
|
| |
|
| - unit tests for daemons? |
|
| |
|
| - simple daemons comparable to those in MetaDaemon? |
|
| |
|
| - docstrings for reference |
|
| |
|
| |
- Cleanup/document attribute binding interface |
| |
|
| peak.storage |
* peak.running.timers |
| |
|
| - URLs and drivers for gadfly, Sybase, and postgres |
|
| |
|
| - "alternate key" rack base class(es) |
|
| |
|
| - "query" rack base class(es) |
|
| |
|
| - add logging to transaction error handlers |
|
| |
|
| - unit tests for more complex object scenarios: references, thunks..? |
|
| |
|
| - docstrings for reference |
- Factor out state into separate object so timers aren't shared state |
| |
|
| peak.util |
- 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 |
|
| |
|
| - more unit tests? |
|
| |
|
| |
|
| |
* Transaction/storage refactorings |
| |
|
| |
- transaction scopes for commands and tasks |
| |
|
| |
- integrate locks with transactions |
| |
|
| |
- transactable persistent queues |
| |
|
| |
- DM.find()/DM.get() queries |
| |
|
| |
* peak.web |
| |
|
| |
- clean up DOMlet parse/build framework (e.g. add line number info, make |
| |
'define' clauses allow multiple names) |
| |
|
| |
- 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) |
| |
|
| |
- try/catch DOMlet (and related error rendering interface/framework) |
| |
|
| |
- 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). |
| |
|
| |
* 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 |
| |
|
| Future Releases |
* Finish tutorial chapter 2 (?) |
| |
|
| (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.) |
|
| |
|
| |
|
| Simulator/Module Inheritance |
|
| |
|
| * Need a strategy for handling "del" operations; they are currently |
|
| untrapped. This might be okay under most circumstances, but need to |
|
| consider edge cases. |
|
| |
|
| * 'makeClass()' should probably become part of the core API, where |
|
| it can be used to resolve __metaclass__ conflicts during the first |
|
| pass of importing a module (prior to running 'setupModule()') |
|
| |
|
| |
|
| Messaging/ObjectSpaces |
|
| |
|
| * Support for sending and receiving remote cache invalidation |
|
| messages between RecordManagers. |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
* 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? |
| |
|
| |
|
| |
|
| |
|
| |
|
| peak.model |
|
| |
|
| * Review other-end-notification protocols in the light of managed storage |
|
| models (e.g. database Records using virtual sequence objects as fields) |
|
| |
|
| * Marshalling interface in Services; implementations for Enumeration, etc. |
|
| |
|
| * More S-E-F metadata: features, subclasses, svc.<->class, nested services |
|
| |
|
| * A way to generate Z3 Interfaces from Feature-based specifications? |
|
| |
|
| * Implement WarpCORE-oriented structural model, w/Querying support |
|
| |
|
| * "Indexed" version of in-memory model? |
|
| |
|
| * "Persistent" StructuralModel (indexes w/BTrees? Catalog?) |
|
| |
|
| |
|
| 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 |
|
| |
|
| * Need to write an MMX or XMI -> Python generator, and hook it back up into |
|
| the UML package, since we're right now relying on a module generated |
|
| by code that depends on stuff which is going away. |
|
| |
|
| * 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) |
|
| |
|
| |
Targeted for version 0.6 |
| |
|
| |
* Functional/acceptance tests that access "real" databases, LDAP, etc. |
| |
|
| |
* 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 |
| |
|
| |
* Support for sending and receiving remote cache invalidation |
| |
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.metamodels.xmi |
|
| |
|
| * Re-org to self-contain all XMI stuff inside an _XMI sub-component/service |
|
| |
|
| * Refactoring to pure S-E-F model using Persistence |
|
| |
|
| * Document version of standard used |
|
| |
|
| * Metamodel identity/version checking |
|
| |
|
| * XMI.Writing |
|
| |
|
| * Strict parsing and/or diagnostics on files that don't match the metamodel? |
|
| |
|
| * UUID/GUID support |
|
| |
|
| * Support for advanced references, external references? |
|
| |
|
| * XML Namespaces (do any current XMI tools need this? Which spec version |
|
| requires this?) |
|
| |
|
| * DOM StructuralModel (so files can be edited without affecting vendor XMI |
|
| extensions) |
|
| |
|
| |
|
Diff of /PEAK/TODO.txt
Parent Directory
| 
Revision Log