|
|
Targeted for 0.5 Alpha 1 |
Targeted for 0.5 Alpha 1 |
|
|
* "Rule"-oriented configuration files (section specifies component rather |
* Finish tutorial chapter 2 |
than property name prefix), w/support for chaining loader objects across |
|
includes, and the ability to specify "Load on Demand" sections. |
|
|
|
* Review possible cross-locational or "root" things like |
|
'PropertyName' -- should these things move to the API? |
|
Or where? They're not 'util' things, certainly. Perhaps |
|
there should be a 'peak.core' module or package for things |
|
that are foundational to all the packages? |
|
|
|
* 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 |
|
|
|
Targeted for 0.5 Final Release (or sooner) |
Targeted for 0.5 Final Release (or sooner) |
|
|
General |
|
|
|
* Update tutorial documentation |
General |
|
|
* Up-to-date and complete Persistence package |
* Tutorial complete through chapter 4 |
|
|
peak.storage |
peak.storage |
|
|
- SQL cursor(joinTxn=flag) shortcut for .joinTxn() |
- unit tests for more complex object scenarios: references, thunks..? |
|
|
- SQL cursor error logging, close conn on error, and rewrap errors |
|
w/SQL in error object |
|
|
|
- SQL field type conversion |
|
|
|
- LDAP field type conversion |
|
|
|
- Rack -> DM |
|
|
|
- "facade" DM base class(es) |
- lock management interfaces/API |
|
|
- "query" DM base class(es) |
- docstrings for reference |
|
|
- unit tests for more complex object scenarios: references, thunks..? |
peak.model |
|
|
- docstrings for reference |
- clean up TW docstrings & interfaces |
|
|
- URL+driver for postgres |
peak.naming |
|
|
peak.model |
- useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
|
|
- add support for lazy-loaded attributes |
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
|
context or filesystem context) |
|
|
- clean up TW docstrings & interfaces |
- 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? |
|
|
peak.running |
peak.running |
|
|
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 |
- finish misc tasks on peak.running.logs's TODO list |
|
|
- simple daemons comparable to those in MetaDaemon |
- simple daemons comparable to those in MetaDaemon |
|
|
|
|
- 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|
|
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) |
|
|
|
|
|