| Open Issues/To-Do Items |
Open Issues/To-Do Items |
| |
|
| Targeted for 0.2 Final Release |
Short Term Project Support |
| |
|
| |
* 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 3 |
| |
|
| |
* peak.binding |
| |
|
| |
- Cleanup/document attribute binding interface |
| |
|
| |
* peak.running.logs |
| |
|
| |
- Add 'DefaultLoggingService', service-based system |
| |
|
| |
- Separate formatters from publishers |
| |
|
| |
- Loggers should know their names and pass that info to event constructor |
| |
|
| |
* 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) |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
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.running.commands |
| |
|
| |
- Add option parsing framework based on optparse (backported to 2.2) |
| |
|
| |
* peak.config |
| |
|
| |
- Writable and subscribable config sources, including editable .ini's |
| |
|
| |
* 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). |
| |
|
| |
* 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? |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
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.) |
| |
|
| API.Modules |
|
| |
|
| * Add tests for 'adviseModule()' API |
|
| |
|
| * Add checks and warnings for ambiguous re-assignments of global |
|
| variables and class attributes. |
|
| |
|
| Database |
|
| |
|
| * Create test suite to check proper transactional functioning, cache |
|
| consistency, queueing behavior, and typemap management. |
|
| |
|
| * Update Interfaces to reflect current API, and document internals |
|
| |
|
| General |
|
| |
|
| * Update tutorial documentation |
|
| |
|
| Ideas for 0.3 Release |
|
| |
|
| Dispatching |
|
| |
|
| * Virtual features to implement retrieving the other end of a |
|
| relationship from another Specialist, and to handle rebinding to |
|
| records after record invalidation. |
|
| |
|
| SEF |
|
| |
|
| * Move binding tools to a seperate module (e.g. 'TW.CIS' for "Component |
|
| Integration Services"). |
|
| |
|
| * Persistent SEF module, with Base.__getstate__ supporting omission |
|
| of Once attributes, and DynamicBinding setting _p_changed on |
|
| instantiation. |
|
| |
|
| * A way to generate Z3 Interfaces from Feature-based specifications? |
|
| |
|
| Database |
|
| |
|
| * Rack-like object to do persistent storage of Elements? |
|
| |
|
| * Support for field transformations and default values at RecordType |
|
| level, e.g marshalling and type conversion. This would be |
|
| especially useful for LDAP. |
|
| |
|
| * Support for sending and receiving remote cache invalidation |
|
| messages between RecordManagers. |
|
| |
|
| General |
|
| |
|
| * Profiling and performance tuning of module inheritance and other |
|
| core features of API and SEF. |
|
| |
|
| |
|
| |
|
| Future Releases |
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 |
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 |
* Need a strategy for handling "del" operations; they are currently |
| untrapped. This might be okay under most circumstances, but need to |
untrapped. This might be okay under most circumstances, but need to |
| consider edge cases. |
consider edge cases. |
| pass of importing a module (prior to running 'setupModule()') |
pass of importing a module (prior to running 'setupModule()') |
| |
|
| |
|
| Documentation/Tests/General |
Messaging/ObjectSpaces |
| |
|
| * Create tutorials/examples based on actual uses |
* Support for sending and receiving remote cache invalidation |
| |
messages between DataManagers. |
| |
|
| * Include dependencies in packaging? Need to ask copyright owners first. |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| SEF |
|
| |
|
| * 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 |
|
| |
|
| * Implement WarpCORE-oriented structural model, w/Querying support |
|
| |
|
| InMemory |
|
| |
|
| * "Indexed" version |
peak.model |
| |
|
| * "WeakRefs" version (no acquisition, use w/Python 2.1 weakrefs) |
* Implement WarpCORE-oriented structural model, w/Querying support |
| |
|
| * "Circular" version (suitable for use w/2.1 GC or Jython) |
* "Indexed" version of in-memory model? |
| |
|
| * "Persistent" StructuralModel (indexes w/BTrees? Catalog?) |
|
| |
|
| Queries |
Queries |
| |
|
| have their meaning assigned by the StructuralModel implementation? |
have their meaning assigned by the StructuralModel implementation? |
| |
|
| |
|
| 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. |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
peak.metamodels.uml |
| |
|
| * Helper methods in Elements & Services for marshalling, common queries, etc. |
* Helper methods in Elements & Services for marshalling, common queries, etc. |
| |
|
| - 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) |
| |
|
| * Reporting mixins? Graphviz visualization? |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| 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) |
|
| |
|
| |
|
Diff of /PEAK/TODO.txt
Parent Directory
| 
Revision Log