|
|
Targeted for 0.5 Alpha 1 |
Targeted for 0.5 Alpha 1 |
|
|
|
* "Assembly Events" - have a way for root components to notify subcomponents that |
|
they are connected to a root. This is important for things like periodic tasks, |
|
GUI components, etc., that need to perform actions as soon as they are part of |
|
a valid "whole". |
|
|
|
* ZConfig Integration |
|
|
|
- A 'config.ZConfigurable' mixin class that gives you a 'fromZConfig()' |
|
constructor for your object classes, suitable for designating as a |
|
section datatype in schemas |
|
|
|
- A 'config.ZConfig' module that provides "PEAK-aware" versions of ZConfig |
|
services (e.g. it will use 'peak.naming' to resolve URLs) |
|
|
|
- ZConfig 1.0 will be distributed with the release, and installed if |
|
Zope X3 isn't on 'sys.path' at install time. |
|
|
|
- Support for 'urllib2' protocols will be added to 'peak.naming' so that |
|
it can be used as the basis for the ZConfig services. |
|
|
|
- App startup tools based on ZConfig files. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Targeted for 0.5 Alpha 2 |
|
|
|
* Fix issue w/reading XMI 1.1 files where metamodel has nested packages |
|
|
|
* Generate UML 1.4 and 1.5 and CWM 1.0 and 1.1, and add them to the |
|
'setup.py' package lists. |
|
|
|
* Get XMI writing in place, w/transaction support |
|
|
|
* Generate ZConfig schemas from 'peak.model' or MOF models? |
|
|
|
* 'peak.running' refactorings: use standard 'logging' module's log levels, |
|
add 'logging' distro to 'peak.util' for 2.2 backward compatibility, |
|
make daemons based on 'peak.model' (or at least define ZConfig schemas), |
|
and possibly adjust cluster stuff to work off ZConfig primary and |
|
generate clustertools file(s). |
|
|
|
* 'peak.naming' refactorings: 'peak.model'-based syntax utilities for |
|
creating address syntaxes. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Targeted for 0.5 Beta 1 |
|
|
|
* Document interface expected of "active descriptors" and their complements |
|
(e.g. __class_provides__), refactoring for cleanliness as needed. |
|
|
* 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 (?) |
|
|
|
* On-the-fly class combination (think "runtime module inheritance", |
|
without the modules) for DMs. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Targeted for 0.5 Final Release (or sooner) |
|
|
|
General |
|
|
|
* Update tutorial documentation |
|
|
|
* Up-to-date and complete Persistence package |
|
|
|
peak.storage |
|
|
|
- SQL cursor(joinTxn=flag) shortcut for .joinTxn() |
|
|
|
- SQL cursor error logging, close conn on error, and rewrap errors |
|
w/SQL in error object |
|
|
|
- SQL field type conversion (should txnTime standard change?) |
|
|
|
- LDAP field type conversion |
|
|
|
- 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..? |
|
|
|
|
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) |
|
|
|
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
|
context or filesystem context) |
|
|
|
- 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? |
|
|
- more docs for new 'cluster' tools |
peak.running |
|
|
- 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. |
produce ambiguous or unintended results. |
|
|
- create a basic LogFile logging provider w/URL comparable to AppUtils |
- simple daemons comparable to those in MetaDaemon, unit tests |
|
|
- simple daemons comparable to those in MetaDaemon |
|
|
|
- unit tests for daemons |
|
|
|
- docstrings for reference |
- docstrings for reference |
|
|
|
|
peak.config |
peak.config |
|
|
- "Rule"-oriented configuration files (section specifies component |
- "Rule"-oriented configuration files (section specifies component |
rather than property name prefix). |
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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Future Releases |
Future Releases |
|
|
(Note: some of the below is held-over from TransWarp and may no longer be |
(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 |
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. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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) |
|
|
|
|
|