|
|
Targeted for 0.5 Alpha 1 |
Targeted for 0.5 Alpha 1 |
|
|
* CGI/FastCGI Framework - PEAK should be able to run simple "hello world" |
* "Assembly Events" - have a way for root components to notify subcomponents that |
apps under the Zope X3 milestone release, with a basic publication that |
they are connected to a root. This is important for things like periodic tasks, |
includes PEAK transaction support. Traversing will be Bobo/ZPublisher |
GUI components, etc., that need to perform actions as soon as they are part of |
legacy style, to be replaced with something more sophisticated in later |
a valid "whole". |
releases (note that this release will NOT include security support). |
|
|
|
* ZConfig Integration |
* ZConfig Integration |
|
|
- Support for 'urllib2' protocols will be added to 'peak.naming' so that |
- Support for 'urllib2' protocols will be added to 'peak.naming' so that |
it can be used as the basis for the ZConfig services. |
it can be used as the basis for the ZConfig services. |
|
|
* PEAK will use 'zope.interface' and 'persistence', installing its own |
- App startup tools based on ZConfig files. |
copies if Zope X3 isn't on 'sys.path' at install time. |
|
|
|
|
|
|
|
* App startup tools based on ZConfig and PEAK-style .ini files. |
|
|
|
|
|
|
|
|
|
Targeted for 0.5 Alpha 2 |
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 |
* Generate UML 1.4 and 1.5 and CWM 1.0 and 1.1, and add them to the |
'setup.py' package lists. |
'setup.py' package lists. |
|
|
* Fix issue w/reading XMI 1.1 files where metamodel has nested packages |
|
|
|
* Get XMI writing in place, w/transaction support |
* Get XMI writing in place, w/transaction support |
|
|
* On-the-fly class combination (think "runtime module inheritance", |
* Generate ZConfig schemas from 'peak.model' or MOF models? |
without the modules) for DMs. |
|
|
|
* ZConfig support, probably in the form of generating ZConfig schemas |
|
from 'peak.model' or MOF models, but maybe in the form of 'fromZConfig' |
|
constructor methods as well. |
|
|
|
* 'peak.running' refactorings: use standard 'logging' module's log levels, |
* 'peak.running' refactorings: use standard 'logging' module's log levels, |
add 'logging' distro to 'peak.util' for 2.2 backward compatibility, |
add 'logging' distro to 'peak.util' for 2.2 backward compatibility, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Targeted for 0.5 Beta 1 |
Targeted for 0.5 Beta 1 |
|
|
* Document interface expected of "active descriptors" and their complements |
* Document interface expected of "active descriptors" and their complements |
|
|
* Finish tutorial chapter 2 (?) |
* Finish tutorial chapter 2 (?) |
|
|
|
* On-the-fly class combination (think "runtime module inheritance", |
|
without the modules) for DMs. |
|
|
|
|
|
|
|
|