Installing a new Third-party plug-in Zope package

After the ZOPE3 installation is complete, you can use it to do a lot of things. Of course, there are some interesting Third-party plug-in (add-on) packages, such as http://www.aliyun.com/zixun/aggregation/22.html "> relational database adapters and wiki implementations. Wikis are made up of a large number of pages and can be edited by any group or person who accesses them. These pages are connected to each other through wiki links, which are pointed to by the names of the other wiki pages. This chapter explains how to install these packages, especially those that are maintained by the Zope warehouse.

Installing a Third-party package in Zope3 is more convenient than Zope 2 and is similar to installing a Third-party package in Python. All you need to do is place the Zope 3 plug-in in any location, as long as it's on the Python path and not much different from installing other Python packages. In other words, you can use the Distutils package to publish your own plug-ins.

Of course, after you install a package, the Zope 3 framework does not yet know about the package, and there is no such thing as a wonderful package detection technique to find the available packages. The Zope 3 framework is configured with the Zope Configuration Markup Language (Zope revisit Markup language,zcml). The Zope proprietary Python package also uses ZCML to register its components in Zope 3. So we have to register a package root ZCML file during the startup process.

This chapter demonstrates how to install the Zope3 Wiki application. If you are currently using the warehouse version of Zope 3, the wiki is already installed, but the steps given in this chapter apply to other packages as well.

First step: Determine the installation path

Because packages can be anywhere in the path hierarchy, it may be difficult to decide where to install the package. For example, Jim Fulton's buddy demo package is a top-level Python package, with this wiki application placed in Zope.app and Jobboard example in Zope.app.Demo.

Generally you want to put a third-party package in the ZOPE3 common directory structure, because it is easier to find it later. When you decide to Zope3 the root of a software package, it's all in place. For a warehouse distribution, the root directory of the package is Zope3/src,zope3, which is the directory you check out from the warehouse. (For example: Svn://svn.zope.org/repos/main/zope3/trunk). For distribution, the root directory of the package is Zope3/lib/python, where the Zope3 default is '/usr/local/zopex3-version ' or the prefix (--prefix) specified when configuring (configure). An alternative is to use the Zope instance as the root of the package-for example, Zope3-instance/lib/python, where zope3-instance is the instance path that you provide to Zope 3 when you invoke Mkzopeinstance. This book will assume that it is your working directory.

To install the wiki application, you must enter the Zope3-instance/lib/python directory, which should be available in every Zope instance.

Step two: Get the wiki application from SNV

The next step is to get the package. Usually you just need to download a tar or zip file and unzip it in its directory. However, there is no such compressed file for wiki applications, so we have to fetch these packages from SVN.

Assuming you have an SVN client installed on your computer, you can use the following command to anonymously check out the wiki's packages from the Zope X3 3.0 branch:

1 SVN co \
2 Svn://svn.zope.org/repos/main/zope3/branches/zopex3-3.0/src/zwiki
3 Zwiki

When SVN allows you to name the directory you created, it is necessary to name it a wiki because the name is assumed to be used when importing the package. When the command line returns, the package should be located under Zope3-instance/lib/python/zwiki.