Open Issues/To-Do Items |
Open Issues/To-Do Items |
|
|
Targeted for 0.2 Final Release |
Targeted for 0.5 Alpha 3 |
|
|
API.Modules |
* peak.events migration |
|
|
* Add tests for 'adviseModule()' API |
- 'running.IProcessProxy' should use conditions/values instead of |
|
listeners, and related command/supervisor tools should also be ported |
|
|
Database |
- Add tests for Twisted support |
|
|
* Create test suite to check proper transactional functioning, cache |
* peak.ddt |
consistency, queueing behavior, and typemap management. |
|
|
|
* Update Interfaces to reflect current API, and document internals |
- Test Action processor |
|
|
General |
- Add Row processor, maybe cursor processor |
|
|
* Update tutorial documentation |
- A bit more doc and demos |
|
|
|
|
|
|
|
|
|
|
|
|
Future Releases |
Targeted for 0.5 Alpha 4 |
|
|
Simulator/Module Inheritance |
* 'ILoadingService', 'IObjectLoader' and 'load:kind@URL' scheme |
|
|
* Need a strategy for handling "del" operations; they are currently |
* peak.config |
untrapped. This might be okay under most circumstances, but need to |
|
consider edge cases. |
|
|
|
* 'makeClass()' should probably become part of the core API, where |
- "service zones" or "service groups" to do smarter service groupings |
it can be used to resolve __metaclass__ conflicts during the first |
|
pass of importing a module (prior to running 'setupModule()') |
|
|
|
* Test "advice" functionality, add more docs. |
- Replace IMainLoop activity monitoring with a plugin-based mechanism? |
|
|
|
- plugin keys ordered by definition sequence, rather than randomly |
|
|
Database |
- ZConfig factory support to allow "smart" interpretation of strings, |
|
section names, etc. |
|
|
* Create configurable caching mixins/plugins for time/size-limited |
- Writable and subscribable config sources, including editable .ini's |
caching within Specialists |
|
|
|
* Create virtual sequence classes to implement association collections |
* peak.running.logs |
|
|
|
- Separate formatters from publishers |
|
|
Documentation/Tests/General |
- ZConfig schema for logging plugins, allowing multiple handlers/category |
|
|
* Create tutorials/examples based on actual uses |
* peak.running.commands |
|
|
* Include dependencies in packaging? Need to ask copyright owners first. |
- Add "error formatting" and "error reporting" services |
|
|
|
- Add option parsing framework based on optparse (backported to 2.2) |
|
|
|
* peak.binding |
|
|
|
- Cleanup/document attribute binding interface |
|
|
|
* peak.running.timers |
|
|
|
- Factor out state into separate object so timers aren't shared state |
|
|
|
- Look at possible integration of peak.query and cursor formatters, in |
|
order to view stats as an in-memory mini-DB w/reporting. |
|
|
|
|
|
* Transaction/storage refactorings |
|
|
|
- transaction scopes for commands and tasks |
|
|
|
- integrate locks with transactions |
|
|
|
- transactable persistent queues |
|
|
|
- DM.find()/DM.get() queries |
|
|
SEF |
* peak.web |
|
|
* Review other-end-notification protocols in the light of managed storage |
- clean up DOMlet parse/build framework (e.g. add line number info) |
models (e.g. database Records using virtual sequence objects as fields) |
|
|
|
* Marshalling interface in Services; implementations for Enumeration, etc. |
- default error templates, w/useful info |
|
|
* More S-E-F metadata: features, subclasses, svc.<->class, nested services |
- 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) |
|
|
* Implement WarpCORE-oriented structural model, w/Querying support |
- try/catch DOMlet (and related error rendering interface/framework) |
|
|
InMemory |
- allow use of // in DOMlets' data paths, to access resource space |
|
|
* "Indexed" version |
- DOMlets for layout/region, as defined in "A layout framework":http://www.eby-sarna.com/pipermail/transwarp/2003-August/000684.html |
|
|
* "WeakRefs" version (no acquisition, use w/Python 2.1 weakrefs) |
- conditional GET support (last modified/ETag) for static resources |
|
|
* "Circular" version (suitable for use w/2.1 GC or Jython) |
- image resources |
|
|
* "Persistent" StructuralModel (indexes w/BTrees? Catalog?) |
- the return of the Specialist |
|
|
Queries |
* 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). |
|
|
* Refactor to use interfaces, if appropriate |
* Drop 'persistence' package, since ZODB 4 has been derailed. Change to |
|
"state-delegation" model, which will integrate better with 'peak.query'. |
|
|
* Incorporate into AbstractModel? |
|
|
|
- Pros: |
|
|
|
* Queries always available |
Targeted for 0.5 Beta 1 |
|
|
* Each StructuralModel implementation can easily include its own |
* Up-to-date reference docstrings for all packages |
performance-tuned version of the basic items. |
|
|
|
- Con: default implementation doesn't perform well on large datasets |
* Finish tutorial chapter 2 (?) |
|
|
* How much of framework needs extensibility? Should the predicate |
* Web publishing framework sufficient to deploy page-based or object- |
classes be placed in the StructuralModel's namespace so that predicates |
published apps |
have their meaning assigned by the StructuralModel implementation? |
|
|
|
|
|
UML |
|
|
|
* Need to write an MMX or XMI -> Python generator, and hook it back up into |
Targeted for 0.5 Final Release (or sooner) |
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. |
peak.storage |
|
|
* Generator framework |
- unit tests for more complex object scenarios: references, thunks..? |
|
|
- Tagged values in stereotypes vs. main values? |
peak.naming |
|
|
- Should tagged values be copied directly into templates? Treated as |
- useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
Python expressions? |
|
|
|
- Should Services be generated using an Element class' "static" |
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
(class-scope) methods/attributes? |
context or a filesystem context) |
|
|
- Are association-ends scoped? |
- rework smtp: to return a factory object that supports open(). |
|
Also think about whether smtp should move to peak.net? |
|
|
- 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) |
|
|
|
* Reporting mixins? Graphviz visualization? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
XMI |
|
|
|
* Re-org to self-contain all XMI stuff inside an _XMI sub-component/service |
|
|
|
* Refactoring to pure S-E-F model |
|
|
|
* 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) |
|
|
|
|
|