| Open Issues/To-Do Items |
Targeted for 0.5 Alpha 4 |
| |
|
| Short Term Project Support |
|
| |
|
| * Add "performance monitoring" subsystem to 'peak.running' |
|
| |
|
| * Add support for finding/registering plugins to 'peak.config' |
|
| |
|
| - Refactor IConfigKey to support explicit "namespace" concept |
|
| |
|
| - Refactor IPropertyMap -> IConfigMap, add iterability/search |
|
| |
|
| - Add inverted indexes for namespace lookups/search |
|
| |
|
| - Add 'IIterableConfigSource' (?) subclass, use for search funcs. |
|
| |
|
| - Lock namespaces that have been iterated over |
|
| |
|
| - Change existing configuration keys not to use tuples as surrogate keys |
|
| |
|
| - Add 'config.PluginsFor' key that finds plugins |
|
| |
|
| - May need 'suggestParentComponent()' to support dictionaries so plugin |
|
| dictionaries will work correctly |
|
| |
|
| - Should it implement the "smart property" interface? |
|
| |
|
| - Things to look at during refactorings: |
|
| |
|
| - Better consolidation of config/component key and recipe interfaces? |
|
| |
|
| - Rule chaining |
|
| |
|
| - Use objects for section parsing instead of functions? |
|
| |
|
| * peak.storage |
|
| |
|
| - 'storage.dbType()' |
* peak.config |
| |
|
| |
- "service zones" or "service groups" to do smarter service groupings |
| |
|
| |
- Replace IMainLoop activity monitoring with a plugin-based mechanism? |
| |
|
| Targeted for 0.5 Alpha 3 |
- plugin keys ordered by definition sequence, rather than randomly |
| |
|
| * peak.binding |
- ZConfig factory support to allow "smart" interpretation of strings, |
| |
section names, etc. |
| |
|
| - Cleanup/document attribute binding interface |
- Writable and subscribable config sources, including editable .ini's |
| |
|
| * peak.running.logs |
* peak.running.logs |
| |
|
| - Add 'DefaultLoggingService', service-based system |
|
| |
|
| - Separate formatters from publishers |
- Separate formatters from publishers |
| |
|
| - Loggers should know their names and pass that info to event constructor |
- ZConfig schema for logging plugins, allowing multiple handlers/category |
| |
|
| * peak.config |
|
| |
|
| - 'ZConfigSchemaService' and 'zconfig:schema@streamURL' scheme |
|
| |
|
| * peak.web (some of this may get bumped to alpha 4) |
|
| |
|
| - clean up DOMlet parse/build framework (e.g. add line number info) |
|
| |
|
| - 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) |
|
| |
|
| |
|
| |
* peak.running.commands |
| |
|
| |
- 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. |
| |
|
| |
|
| |
|
| Targeted for 0.5 Alpha 4 |
|
| |
|
| * Transaction/storage refactorings |
* Transaction/storage refactorings |
| |
|
| |
|
| - DM.find()/DM.get() queries |
- DM.find()/DM.get() queries |
| |
|
| * peak.running.commands |
* peak.web |
| |
|
| - Add option parsing framework based on optparse (backported to 2.2) |
|
| |
|
| * peak.config |
- clean up DOMlet parse/build framework (e.g. add line number info, make |
| |
'define' clauses allow multiple names) |
| |
|
| - Iterable keys to PropertyMap (rename to configMap?) |
- default error templates, w/useful info |
| |
|
| - Writable and subscribable config sources, including editable .ini's |
- 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.web |
- try/catch DOMlet (and related error rendering interface/framework) |
| |
|
| - allow use of // in DOMlets' data paths, to access resource space |
- allow use of // in DOMlets' data paths, to access resource space |
| |
|
| * Drop 'persistence' package, since ZODB 4 has been derailed. Change to |
* Drop 'persistence' package, since ZODB 4 has been derailed. Change to |
| "state-delegation" model, which will integrate better with 'peak.query'. |
"state-delegation" model, which will integrate better with 'peak.query'. |
| |
|
| |
|
| Targeted for 0.5 Beta 1 |
Targeted for 0.5 Beta 1 |
| |
|
| * Up-to-date reference docstrings for all packages |
* Up-to-date reference docstrings for all packages |
| |
|
| Targeted for version 0.6 |
Targeted for version 0.6 |
| |
|
| |
* Functional/acceptance tests that access "real" databases, LDAP, etc. |
| |
|
| * Get XMI writing in place, w/transaction support |
* Get XMI writing in place, w/transaction support |
| |
|
| * Generate UML 1.5 and CWM 1.0 and 1.1, and add them to the |
* Generate UML 1.5 and CWM 1.0 and 1.1, and add them to the |
| |
|
| * Lock management interfaces/API for peak.storage |
* 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 |
* Make 'cluster' parser complain about things that would cause |
| the clusterit tools to choke or barf on the file, or which would |
the clusterit tools to choke or barf on the file, or which would |
| produce ambiguous or unintended results. (Or replace with ZConfig |
produce ambiguous or unintended results. (Or replace with ZConfig |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| 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 |
|
| |
|
| * Allow 'declareModule()' to bootstrap non-existent modules; this might |
|
| let us create "virtual packages" made by assembling other packages and |
|
| modules. |
|
| |
|
| * 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 DataManagers. |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| 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 demo (browse XMI model via the web) |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
Diff of /PEAK/TODO.txt
Parent Directory
| 
Revision Log