Welcome to the Zope source release
This document provides some general information about the Zope
source release and provides links to other documents.
Installation information can be found in doc/INSTALL.txt. Other
documentation is also in the doc directory.
Zope information is available at http://www.zope.org/
Report problems with this release on the Zope mailing list
(zope@zope.org) To subscribe to the list send mail to
zope-request@zope.org with "subscribe" in the subject line.
Introduction
The source release is intended for tinkerers, those who want
to use Zope components separately, Bobo hackers, people who
want to use their own Python, and people who work on obscure
platforms because they love to compile everything from source.
If you just want to use Zope easily and aren't a programmer
the binary release will probably suit you better. All are
available at http://www.zope.org/Download
License
The Zope License is included in LICENSE.txt Send your feedback
about the license to zope-license@zope.org.
Important
This release requires Python 1.5.2.
Installing Zope
Follow the instructions in doc/INSTALL.txt to install Zope.
Using Zope Components Separately
Zope consists of many Python packages which can be profitably
used by themselves. For example you will find all your old friends
from Bobo here:
* ZPublisher - A packagized version of the Bobo ORB you know and
love.
* DocumentTemplate - This package includes cDocumentTemplate which
speeds things up considerably.
* BoboPOS - This is NOT ZODB 3. It a version of BoboPOS2 which
include c code to make things faster.
You can find most of these packages in the lib/python directory. If
you poke around, you might find other goodies too, like StructuredText.
ZPublisher and DocumentTemplate are also available separately.
Notes
* Zope requires Python 1.5.2.
* Lots more documentation is coming.
* Don't forget to check the Zope web site and mailing list.
* Read the source, have fun!
authored
user-visible change for now is that property types are now shown for each property. The actual name/type changing code is pretty minimal, so it has been committed to the trunk but is not yet exposed. We'd like to get some community input on the UI to make sure its what we want (and get the documentation updated) before exposing it.