This project seeks to improve the Zope develpment experience through
the use of delegation by way of components as an alternative to
complex multiple inheritence.
The component architecture builds on the design patterns developed
in the ContentManagementFramework. It is based on the notion of
Components and is InterfaceDriven.
See the VisionStatement for a discription of the goals and scope of
Most of this work will actually land on Zope3X (later Zope3). See the
Zope3(X) FAQ for info. There is also a
mailing list for the
effort, with summaries at Zope3DiscussionSummaries. There's also a start on
a CheatSheet, just aching to be fleshed out...
ComponentArchitectureApproach provides some basic ideas and examples
ComponentArchitectureOverview provides an overview of the
component architecture, with definitions of the standard types
Glossary has a list of terms as links to definitions.
A tutorial for Python programmers shows how the component
architecture is used at a low level. The tutorial is in CVS and
you can browse it through the web at:
Note that it is a work in progress and is changing as the software
Zope3Proposals (this is where the current action is)
SoftwarePrototypes (in particular Zope3x -- a moving target)
DocumentationPrototypes (in particular Jim's important tutorial!)
Project leader: firstname.lastname@example.org
This is a ZWiki site, see the RecentChanges, HelpPage and ZWikiLinks for more information.
served by app1
Zope Corporation All rights reserved.