| Open Issues/To-Do Items |
Open Issues/To-Do Items |
| |
|
| Targeted for 0.5 Alpha 1 |
Targeted for 0.5 Alpha 2 |
| |
|
| * Object name/path support in 'peak.binding' |
* Finish 'protocols' breakout and prepare for possible PEP |
| |
|
| * Review possible cross-locational or "root" things like |
- Add reference docs |
| 'PropertyName' -- should these things move to the API? |
|
| Or where? They're not 'util' things, certainly. Perhaps |
- Create tutorial |
| there should be a 'peak.core' module or package for things |
|
| that are foundational to all the packages? |
* ZConfig Integration |
| |
|
| |
- Sample 'AdaptiveTask' classes that perform the same functions as those |
| |
in the MetaDaemon package, integrated into the 'peak.running' |
| |
ZConfig schema component. |
| |
|
| |
|
| |
Targeted for 0.5 Beta 1 |
| |
|
| * Updated reference docstrings for 'peak.api', 'peak.binding', |
* Updated reference docstrings for 'peak.api', 'peak.binding', |
| 'peak.config', 'peak.exceptions', and 'peak.naming'. |
'peak.config', 'peak.exceptions', and 'peak.naming'. |
| |
|
| * Additional content for the tutorial's chapter on binding |
* Finish tutorial chapter 2 (?) |
| |
|
| Targeted for 0.5 Final Release |
* Web publishing framework sufficient to deploy page-based or object- |
| |
published apps |
| |
|
| |
* Get XMI writing in place, w/transaction support |
| |
|
| |
* On-the-fly class combination (think "runtime module inheritance", |
| |
without the modules) for DMs. |
| |
|
| General |
|
| |
|
| * Update tutorial documentation |
|
| |
|
| * Up-to-date and complete Persistence package |
|
| |
|
| peak.storage |
|
| |
|
| - URL+driver for postgres |
|
| |
|
| - LDAP schema properties, SQL type mapping utilities |
|
| |
|
| - Rack -> DM |
|
| |
|
| - "facade" DM base class(es) |
|
| |
|
| - "query" DM base class(es) |
|
| |
Targeted for 0.5 Final Release (or sooner) |
| |
|
| |
General |
| |
|
| |
* Tutorial complete through chapter 4 |
| |
|
| |
peak.storage |
| |
|
| - unit tests for more complex object scenarios: references, thunks..? |
- unit tests for more complex object scenarios: references, thunks..? |
| |
|
| |
- lock management interfaces/API |
| |
|
| - docstrings for reference |
- docstrings for reference |
| |
|
| peak.model |
peak.model |
| |
|
| - add support for lazy-loaded attributes |
|
| |
|
| - clean up TW docstrings & interfaces |
- clean up TW docstrings & interfaces |
| |
|
| peak.running |
peak.naming |
| |
|
| |
- useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
| |
|
| - more docs for new 'cluster' tools |
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
| |
context or filesystem context) |
| |
|
| - create a basic LogFile logging provider |
- 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? |
| |
|
| - unit tests for daemons? |
peak.running |
| |
|
| - simple daemons comparable to those in MetaDaemon? |
- 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 |
| |
|
| - docstrings for reference |
- docstrings for reference |
| |
|
| |
|
| |
peak.config |
| |
|
| |
- "Rule"-oriented configuration files (section specifies component |
| |
rather than property name prefix), so that daemons and other simple |
| |
apps can be fully configured and run via a config file. |
| |
|
| peak.util |
peak.util |
| |
|
| - docstrings for reference |
- docstrings for reference |
| - more unit tests? |
- more unit tests? |
| |
|
| |
|
| |
Targeted for version 0.6 |
| |
|
| |
* Generate UML 1.5 and CWM 1.0 and 1.1, and add them to the |
| |
'setup.py' package lists. |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| relevant as written, they are being kept on this list as placeholders for |
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.) |
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. |
| Messaging/ObjectSpaces |
Messaging/ObjectSpaces |
| |
|
| * Support for sending and receiving remote cache invalidation |
* Support for sending and receiving remote cache invalidation |
| messages between RecordManagers. |
messages between DataManagers. |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| peak.model |
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 |
* Implement WarpCORE-oriented structural model, w/Querying support |
| |
|
| * "Indexed" version of in-memory model? |
* "Indexed" version of in-memory model? |
| |
|
| * "Persistent" StructuralModel (indexes w/BTrees? Catalog?) |
|
| |
|
| |
|
| Queries |
Queries |
| |
|
| |
|
| |
|
| |
|
| 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. |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
peak.metamodels.uml |
| |
|
| * Helper methods in Elements & Services for marshalling, common queries, etc. |
* Helper methods in Elements & Services for marshalling, common queries, etc. |
| |
|
| |
|
| |
|
| |
|
| 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