Anonymous avatar Anonymous committed 8cba76f

chapter08 final

Comments (0)

Files changed (162)

chapter08/archgenxml.buildout/README.txt

+=======================
+Using a custom buildout
+=======================
+
+Note: If you are using Windows, if you do not have PIL installed, or you are
+not using Python 2.4 as your main system Python, please see the relevant
+sections below.
+
+You probably got here by running something like:
+
+ $ paster create -t plone3_buildout
+
+Now, you need to run:
+
+ $ python bootstrap.py
+
+This will install zc.buildout for you.
+
+To create an instance immediately, run:
+
+ $ bin/buildout
+
+This will download Plone's eggs and products for you, as well as other
+dependencies, create a new Zope 2 installation (unless you specified
+an existing one when you ran "paster create"), and create a new Zope instance
+configured with these products.
+
+You can start your Zope instance by running:
+
+ $ bin/instance start
+
+or, to run in foreground mode:
+
+ $ bin/instance fg
+
+To run unit tests, you can use:
+
+ $ bin/instance test -s my.package
+
+Installing PIL
+--------------
+
+To use Plone, you need PIL, the Python Imaging Library. If you don't already
+have this, download and install it from http://www.pythonware.com/products/pil.
+
+Using a different Python installation
+--------------------------------------
+
+Buildout will use your system Python installation by default. However, Zope
+2.10 (and by extension, Plone) will only work with Python 2.4. You can verify
+which version of Python you have, by running:
+
+ $ python -V
+
+If that is not a 2.4 version, you need to install Python 2.4 from
+http://python.org. If you wish to keep another version as your main system
+Python, edit buildout.cfg and add an 'executable' option to the "[buildout]"
+section, pointing to a python interpreter binary:
+
+ [buildout]
+ ...
+ executable = /path/to/python
+
+Working with buildout.cfg
+-------------------------
+
+You can change any option in buildout.cfg and re-run bin/buildout to reflect
+the changes. This may delete things inside the 'parts' directory, but should
+keep your Data.fs and source files intact.
+
+To save time, you can run buildout in "offline" (-o) and non-updating (-N)
+mode, which will prevent it from downloading things and checking for new
+versions online:
+
+ $ bin/buildout -Nov
+
+Creating new eggs
+-----------------
+
+New packages you are working on (but which are not yet released as eggs and
+uploaded to the Python Package Index, aka PYPI) should be placed in src. You can do:
+
+ $ cd src/
+ $ paster create -t plone my.package
+
+Use "paster create --list-templates" to see all available templates. Answer
+the questions and you will get a new egg. Then tell buildout about your egg
+by editing buildout.cfg and adding your source directory to 'develop':
+
+ [buildout]
+ ...
+ develop =
+    src/my.package
+
+You can list multiple packages here, separated by whitespace or indented
+newlines.
+
+You probably also want the Zope instance to know about the package. Add its
+package name to the list of eggs in the "[instance]" section, or under the
+main "[buildout]" section:
+
+ [instance]
+ ...
+ eggs =
+    ${buildout:eggs}
+    ${plone:eggs}
+    my.package
+
+Leave the ${buildout:eggs} part in place - it tells the instance to use the
+eggs that buildout will have downloaded from the Python Package Index
+previously.
+
+If you also require a ZCML slug for your package, buildout can create one
+automatically. Just add the package to the 'zcml' option:
+
+ [instance]
+ ...
+ zcml =
+    my.package
+
+When you are finished, re-run buildout. Offline, non-updating mode should
+suffice:
+
+ $ bin/buildout -Nov
+
+Developing old-style products
+-----------------------------
+
+If you are developing old-style Zope 2 products (not eggs) then you can do so
+by placing the product code in the top-level 'products' directory. This is
+analogous to the 'Products/' directory inside a normal Zope 2 instance and is
+scanned on start-up for new products.
+
+Depending on a new egg
+----------------------
+
+If you want to use a new egg that is in the Python Package Index, all you need
+to do is to add it to the "eggs" option under the main "[buildout]" section:
+
+ [buildout]
+ ...
+ eggs =
+    my.package
+
+If it's listed somewhere else than the Python Package Index, you can add a link
+telling buildout where to find it in the 'find-links' option:
+
+ [buildout]
+ ...
+ find-links =
+    http://dist.plone.org
+    http://download.zope.org/distribution/
+    http://effbot.org/downloads
+    http://some.host.com/packages
+
+Using existing old-style products
+---------------------------------
+
+If you are using an old-style (non-egg) product, you can either add it as an
+automatically downloaded archive or put it in the top-level "products" folder.
+The former is probably better, because it means you can redistribute your
+buildout.cfg more easily:
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+    http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+
+If someproduct-1.3.tar.gz extracts into several products inside a top-level
+directory, e.g. SomeProduct-1.3/PartOne and SomeProduct-1.3/PartTwo, then
+add it as a "nested package":
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+    http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+ nested-packages =
+    someproduct-1.3.tar.gz
+
+Alternatively, if it extracts to a directory which contains the version
+number, add it as a "version suffix package":
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+    http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+ version-suffix-packages =
+    someproduct-1.3.tar.gz
+
+You can also track products by adding a new bundle checkout part. It
+doesn't strictly have to be an svn bundle at all, any svn location will do,
+and cvs is also supported:
+
+ [buildout]
+ ...
+ parts =
+    plone
+    zope2
+    productdistros
+    myproduct
+    instance
+    zopepy
+
+Note that "myproduct" comes before the "instance" part. You then
+need to add a new section to buildout.cfg:
+
+ [myproduct]
+ recipe = plone.recipe.bundlecheckout
+ url = http://svn.plone.org/svn/collective/myproduct/trunk
+
+Finally, you need to tell Zope to find this new checkout and add it to its
+list of directories that are scanned for products:
+
+ [instance]
+ ...
+ products =
+    ${buildout:directory}/products
+    ${productdistros:location}
+    ${plonebundle:location}
+    ${myproduct:location}
+
+Without this last step, the "myproduct" part is simply managing an svn
+checkout and could potentially be used for something else instead.
+
+=============
+Using Windows
+=============
+
+To use buildout on Windows, you will need to install a few dependencies which
+other platforms manage on their own.
+
+Here are the steps you need to follow (thanks to Hanno Schlichting for these):
+
+Python (http://python.org)
+--------------------------
+
+  - Download and install Python 2.4.4 using the Windows installer from
+    http://www.python.org/ftp/python/2.4.4/python-2.4.4.msi
+    Select 'Install for all users' and it will put Python into the
+    "C:\Python24" folder by default.
+
+  - You also want the pywin32 extensions available from
+    http://downloads.sourceforge.net/pywin32/pywin32-210.win32-py2.4.exe?modtime=1159009237&big_mirror=0
+
+  - And as a last step you want to download the Python imaging library available
+    from http://effbot.org/downloads/PIL-1.1.6.win32-py2.4.exe
+
+  - If you develop Zope based applications you will usually only need Python 2.4
+    at the moment, so it's easiest to put the Python binary on the systems PATH,
+    so you don't need to specify its location manually each time you call it.
+
+    Thus, put "C:\Python24" and "C:\Python24\Scripts" onto the PATH. You can
+    find the PATH definition in the control panel under system preferences on
+    the advanced tab at the bottom. The button is called environment variables.
+    You want to add it at the end of the already existing PATH in the system
+    section. Paths are separated by a semicolons.
+
+  - You can test if this was successful by opening a new shell (cmd) and type
+    in 'python -V'. It should report version 2.4.4 (or whichever version you
+    installed).
+
+    Opening a new shell can be done quickly by using the key combination
+    'Windows-r' or if you are using Parallels on a Mac 'Apple-r'. Type in 'cmd'
+    into the popup box that opens up and hit enter.
+
+
+Subversion (http://subversion.tigris.org)
+-----------------------------------------
+
+  - Download the nice installer from
+    http://subversion.tigris.org/files/documents/15/35379/svn-1.4.2-setup.exe
+
+  - Run the installer. It defaults to installing into
+    "C:\Program Files\Subversion".
+
+  - Now put the install locations bin subfolder (for example
+    "C:\Program Files\Subversion\bin") on your system PATH in the same way you
+    put Python on it.
+
+  - Open a new shell again and type in: 'svn --version' it should report
+    version 1.4.2 or newer.
+
+
+MinGW (http://www.mingw.org/)
+-----------------------------
+
+  This is a native port of the gcc compiler and its dependencies for Windows.
+  There are other approaches enabling you to compile Python C extensions on
+  Windows including Cygwin and using the official Microsoft C compiler, but this
+  is a lightweight approach that uses only freely available tools. As
+  it's used by a lot of people chances are high it will work for you and there's
+  plenty of documentation out there to help you in troubleshooting problems.
+
+  - Download the MinGW installer from
+    http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe?modtime=1168794334&big_mirror=1
+
+  - The installer will ask you which options you would like to install. Choose
+    base and make here. It will install into "C:\MinGW" by default. The install
+    might take some time as it's getting files from sourceforge.net and you
+    might need to hit 'retry' a couple of times.
+
+  - Now put the install location's bin subfolder (for example "C:\MinGW\bin") on
+    your system PATH in the same way you put Python on it.
+
+  - Test this again by typing in: 'gcc --version' on a newly opened shell and
+    it should report version 3.4.2 or newer.
+
+
+Configure Distutils to use MinGW
+--------------------------------
+
+  Some general information are available from
+  http://www.mingw.org/MinGWiki/index.php/Python%20extensions for example but
+  you don't need to read them all.
+
+  - Create a file called 'distutils.cfg' in "C:\Python24\Lib\distutils". Open it
+    with a text editor ('notepad distutils.cfg') and fill in the following lines:
+
+    [build]
+    compiler=mingw32
+
+    This will tell distutils to use MinGW as the default compiler, so you don't
+    need to specify it manually using "--compiler=mingw32" while calling a
+    package's setup.py with a command that involves building C extensions. This
+    is extremely useful if the build command is written down in a buildout
+    recipe where you cannot change the options without hacking the recipe
+    itself. The z2c.recipe.zope2install used in ploneout is one such example.

chapter08/archgenxml.buildout/bootstrap.py

+##############################################################################
+#
+# Copyright (c) 2006 Zope Corporation and Contributors.
+# All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL).  A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE.
+#
+##############################################################################
+"""Bootstrap a buildout-based project
+
+Simply run this script in a directory containing a buildout.cfg.
+The script accepts buildout command-line options, so you can
+use the -c option to specify an alternate configuration file.
+
+$Id: bootstrap.py 85041 2008-03-31 15:57:30Z andreasjung $
+"""
+
+import os, shutil, sys, tempfile, urllib2
+
+tmpeggs = tempfile.mkdtemp()
+
+try:
+    import pkg_resources
+except ImportError:
+    ez = {}
+    exec urllib2.urlopen('http://peak.telecommunity.com/dist/ez_setup.py'
+                         ).read() in ez
+    ez['use_setuptools'](to_dir=tmpeggs, download_delay=0)
+
+    import pkg_resources
+
+if sys.platform == 'win32':
+    def quote(c):
+        if ' ' in c:
+            return '"%s"' % c # work around spawn lamosity on windows
+        else:
+            return c
+else:
+    def quote (c):
+        return c
+
+cmd = 'from setuptools.command.easy_install import main; main()'
+ws  = pkg_resources.working_set
+assert os.spawnle(
+    os.P_WAIT, sys.executable, quote (sys.executable),
+    '-c', quote (cmd), '-mqNxd', quote (tmpeggs), 'zc.buildout',
+    dict(os.environ,
+         PYTHONPATH=
+         ws.find(pkg_resources.Requirement.parse('setuptools')).location
+         ),
+    ) == 0
+
+ws.add_entry(tmpeggs)
+ws.require('zc.buildout')
+import zc.buildout.buildout
+zc.buildout.buildout.main(sys.argv[1:] + ['bootstrap'])
+shutil.rmtree(tmpeggs)

chapter08/archgenxml.buildout/buildout.cfg

+[buildout]
+parts =
+    archgenxml
+	agx-profile
+
+[archgenxml]
+recipe = zc.recipe.egg:scripts
+eggs = 
+    archgenxml
+    i18ndude
+
+[agx-profile]
+recipe = collective.recipe.cmd
+on_install=true
+on_update=false
+cmds = 
+	${buildout:directory}/bin/agx_argouml_profile
+	mkdir ${buildout:directory}/profiles
+	mv ${buildout:directory}/archgenxml_profile.xmi ${buildout:directory}/profiles
+

chapter08/archgenxml.buildout/products/README.txt

+Old-style Zope products you are developing can be added here

chapter08/archgenxml.buildout/src/README.txt

+Packages in eggs that you develop should go in this directory

chapter08/pox.buildout/README.txt

+=======================
+Using a custom buildout
+=======================
+
+Note: If you are using Windows, if you do not have PIL installed, or you are
+not using Python 2.4 as your main system Python, please see the relevant
+sections below.
+
+You probably got here by running something like:
+
+ $ paster create -t plone3_buildout
+
+Now, you need to run:
+
+ $ python bootstrap.py
+
+This will install zc.buildout for you.
+
+To create an instance immediately, run:
+
+ $ bin/buildout
+
+This will download Plone's eggs and products for you, as well as other
+dependencies, create a new Zope 2 installation (unless you specified
+an existing one when you ran "paster create"), and create a new Zope instance
+configured with these products.
+
+You can start your Zope instance by running:
+
+ $ bin/instance start
+
+or, to run in foreground mode:
+
+ $ bin/instance fg
+
+To run unit tests, you can use:
+
+ $ bin/instance test -s my.package
+
+Installing PIL
+--------------
+
+To use Plone, you need PIL, the Python Imaging Library. If you don't already
+have this, download and install it from http://www.pythonware.com/products/pil.
+
+Using a different Python installation
+--------------------------------------
+
+Buildout will use your system Python installation by default. However, Zope
+2.10 (and by extension, Plone) will only work with Python 2.4. You can verify
+which version of Python you have, by running:
+
+ $ python -V
+
+If that is not a 2.4 version, you need to install Python 2.4 from
+http://python.org. If you wish to keep another version as your main system
+Python, edit buildout.cfg and add an 'executable' option to the "[buildout]"
+section, pointing to a python interpreter binary:
+
+ [buildout]
+ ...
+ executable = /path/to/python
+
+Working with buildout.cfg
+-------------------------
+
+You can change any option in buildout.cfg and re-run bin/buildout to reflect
+the changes. This may delete things inside the 'parts' directory, but should
+keep your Data.fs and source files intact.
+
+To save time, you can run buildout in "offline" (-o) and non-updating (-N)
+mode, which will prevent it from downloading things and checking for new
+versions online:
+
+ $ bin/buildout -Nov
+
+Creating new eggs
+-----------------
+
+New packages you are working on (but which are not yet released as eggs and
+uploaded to the Python Package Index, aka PYPI) should be placed in src. You can do:
+
+ $ cd src/
+ $ paster create -t plone my.package
+
+Use "paster create --list-templates" to see all available templates. Answer
+the questions and you will get a new egg. Then tell buildout about your egg
+by editing buildout.cfg and adding your source directory to 'develop':
+
+ [buildout]
+ ...
+ develop =
+    src/my.package
+
+You can list multiple packages here, separated by whitespace or indented
+newlines.
+
+You probably also want the Zope instance to know about the package. Add its
+package name to the list of eggs in the "[instance]" section, or under the
+main "[buildout]" section:
+
+ [instance]
+ ...
+ eggs =
+    ${buildout:eggs}
+    ${plone:eggs}
+    my.package
+
+Leave the ${buildout:eggs} part in place - it tells the instance to use the
+eggs that buildout will have downloaded from the Python Package Index
+previously.
+
+If you also require a ZCML slug for your package, buildout can create one
+automatically. Just add the package to the 'zcml' option:
+
+ [instance]
+ ...
+ zcml =
+    my.package
+
+When you are finished, re-run buildout. Offline, non-updating mode should
+suffice:
+
+ $ bin/buildout -Nov
+
+Developing old-style products
+-----------------------------
+
+If you are developing old-style Zope 2 products (not eggs) then you can do so
+by placing the product code in the top-level 'products' directory. This is
+analogous to the 'Products/' directory inside a normal Zope 2 instance and is
+scanned on start-up for new products.
+
+Depending on a new egg
+----------------------
+
+If you want to use a new egg that is in the Python Package Index, all you need
+to do is to add it to the "eggs" option under the main "[buildout]" section:
+
+ [buildout]
+ ...
+ eggs =
+    my.package
+
+If it's listed somewhere else than the Python Package Index, you can add a link
+telling buildout where to find it in the 'find-links' option:
+
+ [buildout]
+ ...
+ find-links =
+    http://dist.plone.org
+    http://download.zope.org/distribution/
+    http://effbot.org/downloads
+    http://some.host.com/packages
+
+Using existing old-style products
+---------------------------------
+
+If you are using an old-style (non-egg) product, you can either add it as an
+automatically downloaded archive or put it in the top-level "products" folder.
+The former is probably better, because it means you can redistribute your
+buildout.cfg more easily:
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+    http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+
+If someproduct-1.3.tar.gz extracts into several products inside a top-level
+directory, e.g. SomeProduct-1.3/PartOne and SomeProduct-1.3/PartTwo, then
+add it as a "nested package":
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+    http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+ nested-packages =
+    someproduct-1.3.tar.gz
+
+Alternatively, if it extracts to a directory which contains the version
+number, add it as a "version suffix package":
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+    http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+ version-suffix-packages =
+    someproduct-1.3.tar.gz
+
+You can also track products by adding a new bundle checkout part. It
+doesn't strictly have to be an svn bundle at all, any svn location will do,
+and cvs is also supported:
+
+ [buildout]
+ ...
+ parts =
+    plone
+    zope2
+    productdistros
+    myproduct
+    instance
+    zopepy
+
+Note that "myproduct" comes before the "instance" part. You then
+need to add a new section to buildout.cfg:
+
+ [myproduct]
+ recipe = plone.recipe.bundlecheckout
+ url = http://svn.plone.org/svn/collective/myproduct/trunk
+
+Finally, you need to tell Zope to find this new checkout and add it to its
+list of directories that are scanned for products:
+
+ [instance]
+ ...
+ products =
+    ${buildout:directory}/products
+    ${productdistros:location}
+    ${plonebundle:location}
+    ${myproduct:location}
+
+Without this last step, the "myproduct" part is simply managing an svn
+checkout and could potentially be used for something else instead.
+
+=============
+Using Windows
+=============
+
+To use buildout on Windows, you will need to install a few dependencies which
+other platforms manage on their own.
+
+Here are the steps you need to follow (thanks to Hanno Schlichting for these):
+
+Python (http://python.org)
+--------------------------
+
+  - Download and install Python 2.4.4 using the Windows installer from
+    http://www.python.org/ftp/python/2.4.4/python-2.4.4.msi
+    Select 'Install for all users' and it will put Python into the
+    "C:\Python24" folder by default.
+
+  - You also want the pywin32 extensions available from
+    http://downloads.sourceforge.net/pywin32/pywin32-210.win32-py2.4.exe?modtime=1159009237&big_mirror=0
+
+  - And as a last step you want to download the Python imaging library available
+    from http://effbot.org/downloads/PIL-1.1.6.win32-py2.4.exe
+
+  - If you develop Zope based applications you will usually only need Python 2.4
+    at the moment, so it's easiest to put the Python binary on the systems PATH,
+    so you don't need to specify its location manually each time you call it.
+
+    Thus, put "C:\Python24" and "C:\Python24\Scripts" onto the PATH. You can
+    find the PATH definition in the control panel under system preferences on
+    the advanced tab at the bottom. The button is called environment variables.
+    You want to add it at the end of the already existing PATH in the system
+    section. Paths are separated by a semicolons.
+
+  - You can test if this was successful by opening a new shell (cmd) and type
+    in 'python -V'. It should report version 2.4.4 (or whichever version you
+    installed).
+
+    Opening a new shell can be done quickly by using the key combination
+    'Windows-r' or if you are using Parallels on a Mac 'Apple-r'. Type in 'cmd'
+    into the popup box that opens up and hit enter.
+
+
+Subversion (http://subversion.tigris.org)
+-----------------------------------------
+
+  - Download the nice installer from
+    http://subversion.tigris.org/files/documents/15/35379/svn-1.4.2-setup.exe
+
+  - Run the installer. It defaults to installing into
+    "C:\Program Files\Subversion".
+
+  - Now put the install locations bin subfolder (for example
+    "C:\Program Files\Subversion\bin") on your system PATH in the same way you
+    put Python on it.
+
+  - Open a new shell again and type in: 'svn --version' it should report
+    version 1.4.2 or newer.
+
+
+MinGW (http://www.mingw.org/)
+-----------------------------
+
+  This is a native port of the gcc compiler and its dependencies for Windows.
+  There are other approaches enabling you to compile Python C extensions on
+  Windows including Cygwin and using the official Microsoft C compiler, but this
+  is a lightweight approach that uses only freely available tools. As
+  it's used by a lot of people chances are high it will work for you and there's
+  plenty of documentation out there to help you in troubleshooting problems.
+
+  - Download the MinGW installer from
+    http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe?modtime=1168794334&big_mirror=1
+
+  - The installer will ask you which options you would like to install. Choose
+    base and make here. It will install into "C:\MinGW" by default. The install
+    might take some time as it's getting files from sourceforge.net and you
+    might need to hit 'retry' a couple of times.
+
+  - Now put the install location's bin subfolder (for example "C:\MinGW\bin") on
+    your system PATH in the same way you put Python on it.
+
+  - Test this again by typing in: 'gcc --version' on a newly opened shell and
+    it should report version 3.4.2 or newer.
+
+
+Configure Distutils to use MinGW
+--------------------------------
+
+  Some general information are available from
+  http://www.mingw.org/MinGWiki/index.php/Python%20extensions for example but
+  you don't need to read them all.
+
+  - Create a file called 'distutils.cfg' in "C:\Python24\Lib\distutils". Open it
+    with a text editor ('notepad distutils.cfg') and fill in the following lines:
+
+    [build]
+    compiler=mingw32
+
+    This will tell distutils to use MinGW as the default compiler, so you don't
+    need to specify it manually using "--compiler=mingw32" while calling a
+    package's setup.py with a command that involves building C extensions. This
+    is extremely useful if the build command is written down in a buildout
+    recipe where you cannot change the options without hacking the recipe
+    itself. The z2c.recipe.zope2install used in ploneout is one such example.

chapter08/pox.buildout/bootstrap.py

+##############################################################################
+#
+# Copyright (c) 2006 Zope Corporation and Contributors.
+# All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL).  A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE.
+#
+##############################################################################
+"""Bootstrap a buildout-based project
+
+Simply run this script in a directory containing a buildout.cfg.
+The script accepts buildout command-line options, so you can
+use the -c option to specify an alternate configuration file.
+
+$Id: bootstrap.py 85041 2008-03-31 15:57:30Z andreasjung $
+"""
+
+import os, shutil, sys, tempfile, urllib2
+
+tmpeggs = tempfile.mkdtemp()
+
+try:
+    import pkg_resources
+except ImportError:
+    ez = {}
+    exec urllib2.urlopen('http://peak.telecommunity.com/dist/ez_setup.py'
+                         ).read() in ez
+    ez['use_setuptools'](to_dir=tmpeggs, download_delay=0)
+
+    import pkg_resources
+
+if sys.platform == 'win32':
+    def quote(c):
+        if ' ' in c:
+            return '"%s"' % c # work around spawn lamosity on windows
+        else:
+            return c
+else:
+    def quote (c):
+        return c
+
+cmd = 'from setuptools.command.easy_install import main; main()'
+ws  = pkg_resources.working_set
+assert os.spawnle(
+    os.P_WAIT, sys.executable, quote (sys.executable),
+    '-c', quote (cmd), '-mqNxd', quote (tmpeggs), 'zc.buildout',
+    dict(os.environ,
+         PYTHONPATH=
+         ws.find(pkg_resources.Requirement.parse('setuptools')).location
+         ),
+    ) == 0
+
+ws.add_entry(tmpeggs)
+ws.require('zc.buildout')
+import zc.buildout.buildout
+zc.buildout.buildout.main(sys.argv[1:] + ['bootstrap'])
+shutil.rmtree(tmpeggs)

chapter08/pox.buildout/buildout.cfg

+[buildout]
+parts =
+    zope2
+    productdistros
+    instance
+    zopepy
+    ipzope
+    seleniumenv
+    omelette
+
+unzip = true
+# Change the number here to change the version of Plone being used
+extends = 
+    http://dist.plone.org/release/3.3.5/versions.cfg
+    http://good-py.appspot.com/release/dexterity/1.0a2
+    versions.cfg
+versions = versions
+
+# Add additional egg download sources here. dist.plone.org contains archives
+# of Plone packages.
+index = http://plone.intranet.rcom.com.ar/pypi/
+find-links =
+    http://dist.plone.org/release/3.3.5
+    http://download.zope.org/ppix/
+    http://download.zope.org/distribution/
+    http://effbot.org/downloads
+
+# Add additional eggs here
+eggs =
+    PILwoTk
+    Products.DocFinderTab
+    Products.Clouseau
+    Products.PDBDebugMode
+    plone.reload
+    zope.testrecorder
+    pox.banner
+    pox.video
+    pox.policy
+
+# Reference any eggs you are developing here, one per line
+# e.g.: develop = src/my.package
+develop =
+    src/pox.banner
+    src/pox.video
+    src/pox.policy
+
+[zope2]
+# For more information on this step and configuration options see:
+# http://pypi.python.org/pypi/plone.recipe.zope2install
+recipe = plone.recipe.zope2install
+fake-zope-eggs = true
+skip-fake-eggs =
+    zope.i18n
+    docutils
+additional-fake-eggs = 
+    ZODB3
+    Testing
+url = ${versions:zope2-url}
+
+# Use this section to download additional old-style products.
+# List any number of URLs for product tarballs under URLs (separate
+# with whitespace, or break over several lines, with subsequent lines
+# indented). If any archives contain several products inside a top-level
+# directory, list the archive file name (i.e. the last part of the URL,
+# normally with a .tar.gz suffix or similar) under 'nested-packages'.
+# If any archives extract to a product directory with a version suffix, list
+# the archive name under 'version-suffix-packages'.
+[productdistros]
+# For more information on this step and configuration options see:
+# http://pypi.python.org/pypi/plone.recipe.distros
+recipe = plone.recipe.distros
+urls =
+nested-packages =
+version-suffix-packages =
+
+[instance]
+# For more information on this step and configuration options see:
+# http://pypi.python.org/pypi/plone.recipe.zope2instance
+recipe = plone.recipe.zope2instance
+zope2-location = ${zope2:location}
+user = admin:admin
+http-address = 8080
+debug-mode = on
+verbose-security = on
+
+# If you want Zope to know about any additional eggs, list them here.
+# This should include any development eggs you listed in develop-eggs above,
+# e.g. eggs = Plone my.package
+eggs =
+    Plone
+    ${buildout:eggs}
+
+# If you want to register ZCML slugs for any packages, list them here.
+# e.g. zcml = my.package my.other.package
+zcml =
+    five.grok
+    zope.testrecorder
+    pox.video
+
+products =
+    ${buildout:directory}/products
+    ${productdistros:location}
+environment-vars =
+    PTS_LANGUAGES es en
+
+[zopepy]
+# For more information on this step and configuration options see:
+# http://pypi.python.org/pypi/zc.recipe.egg
+recipe = zc.recipe.egg
+eggs = ${instance:eggs}
+interpreter = zopepy
+extra-paths = ${zope2:location}/lib/python
+scripts = zopepy
+
+[plonesite]
+recipe = collective.recipe.plonesite
+site-id = plone
+instance = instance
+products =
+    Clouseau
+
+[ipzope]
+# a IPython Shell for interactive use with zope running. you also need to put
+# https://svn.plone.org/svn/collective/dotipython/trunk/ipy_profile_zope.py
+# to your $HOME/.ipython directory for the following to work.
+recipe = zc.recipe.egg:scripts
+eggs =
+    ipython
+    ${instance:eggs}
+initialization =
+    import sys, os
+    os.environ["SOFTWARE_HOME"] = "${zope2:location}/lib/python"
+    os.environ["INSTANCE_HOME"] = "${instance:location}"
+    sys.argv[1:1] = "-p zope".split()
+entry-points = ipython=IPython.ipapi:launch_new_instance
+extra-paths = ${zope2:location}/lib/python
+scripts = ipython=ipzope
+
+[seleniumenv]
+recipe = rcom.recipe.seleniumenv
+seleniumversion = 1.0.1
+eggs = ${instance:eggs}
+
+[omelette]
+recipe = collective.recipe.omelette
+eggs = 
+    ${instance:eggs}
+products =
+    ${instance:products}
+packages = 
+    ${zope2:location}/lib/python ./    

chapter08/pox.buildout/coreloadtests.cfg

+[buildout]
+extends = 
+    funkload.cfg
+parts +=
+    coreloadtests_site
+eggs +=
+    collective.coreloadtests
+
+auto-checkout +=
+    collective.coreloadtests
+
+[sources]
+collective.coreloadtests = svn https://svn.plone.org/svn/collective/collective.coreloadtests/trunk
+
+[collective.funkload]
+eggs += collective.coreloadtests
+
+[fl-run-bench]
+eggs += collective.coreloadtests
+
+[coreloadtests_site]
+recipe = collective.recipe.plonesite >= 0.6
+site-id = coreloadtests
+site-replace = True

chapter08/pox.buildout/etc/monitor.conf

+# default configuration file for the monitor server
+# note that %(FLOAD_HOME)s is accessible
+#
+# $Id: credential.conf 22780 2005-06-06 09:43:52Z bdelbosc $
+
+# ------------------------------------------------------------
+[server]
+# configuration used by monitord
+host = localhost
+port = 8008
+
+# sleeptime between monitoring in second
+# note that load average is updated by the system only every 5s
+interval = .5
+
+# network interface to monitor lo, eth0
+interface = lo
+
+# ------------------------------------------------------------
+[client]
+# configuration used by monitorctl
+host = localhost
+port = 8008

chapter08/pox.buildout/funkload.cfg

+[buildout]
+extends = 
+    buildout.cfg
+parts +=
+    tcpwatch-source
+    tcpwatch-install
+    funkload
+#    collective.funkload
+#   fl-run-bench
+    fl-tests
+    site-pox.banner.tests
+        
+auto-checkout +=
+    collective.funkload
+    collective.recipe.funkload
+
+[sources]
+collective.funkload = svn https://svn.plone.org/svn/collective/collective.funkload/trunk
+collective.recipe.funkload = svn http://svn.plone.org/svn/collective/buildout/collective.recipe.funkload/trunk/
+
+[tcpwatch-source]
+recipe = hexagonit.recipe.download
+url = http://hathawaymix.org/Software/TCPWatch/tcpwatch-1.3.tar.gz
+
+[tcpwatch-install]
+recipe = z3c.recipe.egg:setup
+setup = ${tcpwatch-source:location}/tcpwatch
+args = install_scripts --install-dir=${tcpwatch-source:location}/bin
+
+[funkload]
+recipe = zc.recipe.egg:scripts
+eggs = 
+    docutils
+    funkload
+    ${instance:eggs}
+extra-paths=${zope2:location}/lib/python
+#scripts = 
+#    fl-monitor-ctl
+#    fl-recorder
+initialization =
+    import os
+    os.environ['PATH'] = (
+        '${tcpwatch-source:location}/bin:'+os.environ['PATH'])
+
+[fl-tests]
+recipe = collective.recipe.funkload
+eggs = 
+    ${instance:eggs}
+zope2-location = ${zope2:location}
+url = http://localhost:8080
+
+[instance]
+eggs +=
+    collective.funkload
+    Products.CacheSetup
+    
+[site-pox.banner.tests]
+recipe = collective.recipe.plonesite
+site-id = pox.banner.tests
+instance = instance
+site-replace = True
+products =
+    pox.banner
+    pox.video
+
+[site-pox.banner.tests.withcache]
+recipe = collective.recipe.plonesite
+site-id = pox.banner.tests
+instance = instance
+site-replace = True
+products =
+    CacheSetup
+    pox.banner
+    pox.video
+
Add a comment to this file

chapter08/pox.buildout/models/poxContentTypes.zargo

Binary file added.

chapter08/pox.buildout/products/README.txt

+Old-style Zope products you are developing can be added here

chapter08/pox.buildout/src/Products.poxContentTypes/Products/__init__.py

+# See http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages
+try:
+    __import__('pkg_resources').declare_namespace(__name__)
+except ImportError:
+    from pkgutil import extend_path
+    __path__ = extend_path(__path__, __name__)

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/INTEGRATION.txt

+>>> self.loginAsPortalOwner()
+>>> portal.invokeFactory('XNewsItem', 'dummy')
+'dummy'
+>>> portal.dummy
+<XNewsItem at /plone/dummy>
+
+>>> portal.dummy.countryVocabulary()
+(('AQ', 'Antartiqa'), ('AR', 'Argentina'), ('BS', 'Bahamas'), ('BR', 'Brazil'), ('CM', 'Cameroon'), ('CL', 'Chile'))    

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/README.txt

+>>> from Products.poxContentTypes import config
+>>> from Products.poxContentTypes.content.XNewsItem import XNewsItem
+
+>>> xni = XNewsItem('dummy')
+>>> xni
+<XNewsItem at dummy>
+
+>>> xni.countryVocabulary()
+(('AQ', 'Antartiqa'), ('AR', 'Argentina'), ('BS', 'Bahamas'), ('BR', 'Brazil'), ('CM', 'Cameroon'), ('CL', 'Chile'))

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/__init__.py

+# -*- coding: utf-8 -*-
+#
+# File: poxContentTypes.py
+#
+# Copyright (c) 2009 by []
+# Generator: ArchGenXML Version 2.4.1
+#            http://plone.org/products/archgenxml
+#
+# GNU General Public License (GPL)
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
+# 02110-1301, USA.
+#
+
+__author__ = """JPG & MFR <unknown>"""
+__docformat__ = 'plaintext'
+
+
+# There are three ways to inject custom code here:
+#
+#   - To set global configuration variables, create a file AppConfig.py.
+#       This will be imported in config.py, which in turn is imported in
+#       each generated class and in this file.
+#   - To perform custom initialisation after types have been registered,
+#       use the protected code section at the bottom of initialize().
+
+import logging
+logger = logging.getLogger('poxContentTypes')
+logger.debug('Installing Product')
+
+import os
+import os.path
+from Globals import package_home
+import Products.CMFPlone.interfaces
+from Products.Archetypes import listTypes
+from Products.Archetypes.atapi import *
+from Products.Archetypes.utils import capitalize
+from Products.CMFCore import DirectoryView
+from Products.CMFCore import permissions as cmfpermissions
+from Products.CMFCore import utils as cmfutils
+from Products.CMFPlone.utils import ToolInit
+from config import *
+
+DirectoryView.registerDirectory('skins', product_globals)
+
+
+##code-section custom-init-head #fill in your manual code here
+##/code-section custom-init-head
+
+
+def initialize(context):
+    """initialize product (called by zope)"""
+    ##code-section custom-init-top #fill in your manual code here
+    ##/code-section custom-init-top
+
+    # imports packages and types for registration
+    import content
+    import tests
+
+
+    # Initialize portal content
+    all_content_types, all_constructors, all_ftis = process_types(
+        listTypes(PROJECTNAME),
+        PROJECTNAME)
+
+    cmfutils.ContentInit(
+        PROJECTNAME + ' Content',
+        content_types      = all_content_types,
+        permission         = DEFAULT_ADD_CONTENT_PERMISSION,
+        extra_constructors = all_constructors,
+        fti                = all_ftis,
+        ).initialize(context)
+
+    # Give it some extra permissions to control them on a per class limit
+    for i in range(0,len(all_content_types)):
+        klassname=all_content_types[i].__name__
+        if not klassname in ADD_CONTENT_PERMISSIONS:
+            continue
+
+        context.registerClass(meta_type   = all_ftis[i]['meta_type'],
+                              constructors= (all_constructors[i],),
+                              permission  = ADD_CONTENT_PERMISSIONS[klassname])
+
+    ##code-section custom-init-bottom #fill in your manual code here
+    ##/code-section custom-init-bottom
+

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/browser.txt

+Create the browser object we'll be using.
+
+    >>> from Products.Five.testbrowser import Browser
+    >>> from Products.PloneTestCase.setup import portal_owner, default_password
+    >>> browser = Browser()
+    >>> portal_url = self.portal.absolute_url()
+    >>> browser.open(portal_url)
+    >>> browser.getLink('Log in').click()
+    >>> browser.getControl('Login Name').value = portal_owner
+    >>> browser.getControl('Password').value = default_password
+    >>> browser.getControl('Log in').click()
+    >>> browser.open(portal_url + '/createObject?type_name=XNewsItem')
+    >>> browser.getControl('Title').value = 'This is an XNewsItem title'
+    >>> browser.getControl('Lead').value = 'Lead field is required'
+    >>> browser.getControl('Country').value = ('AR',)
+    >>> browser.getControl('Save').click()
+    >>> 'Changes saved.' in browser.contents
+    True

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/config.py

+# -*- coding: utf-8 -*-
+#
+# File: poxContentTypes.py
+#
+# Copyright (c) 2009 by []
+# Generator: ArchGenXML Version 2.4.1
+#            http://plone.org/products/archgenxml
+#
+# GNU General Public License (GPL)
+#
+
+__author__ = """JPG & MFR <unknown>"""
+__docformat__ = 'plaintext'
+
+
+# Product configuration.
+#
+# The contents of this module will be imported into __init__.py, the
+# workflow configuration and every content type module.
+#
+# If you wish to perform custom configuration, you may put a file
+# AppConfig.py in your product's root directory. The items in there
+# will be included (by importing) in this file if found.
+
+from Products.CMFCore.permissions import setDefaultRoles
+##code-section config-head #fill in your manual code here
+##/code-section config-head
+
+
+PROJECTNAME = "poxContentTypes"
+
+# Permissions
+DEFAULT_ADD_CONTENT_PERMISSION = "Add portal content"
+setDefaultRoles(DEFAULT_ADD_CONTENT_PERMISSION, ('Manager', 'Owner', 'Contributor'))
+ADD_CONTENT_PERMISSIONS = {
+    'XNewsItem': 'poxContentTypes: Add XNewsItem',
+}
+
+setDefaultRoles('poxContentTypes: Add XNewsItem', ('Manager','Owner'))
+
+product_globals = globals()
+
+# Dependencies of Products to be installed by quick-installer
+# override in custom configuration
+DEPENDENCIES = []
+
+# Dependend products - not quick-installed - used in testcase
+# override in custom configuration
+PRODUCT_DEPENDENCIES = []
+
+##code-section config-bottom #fill in your manual code here
+##/code-section config-bottom
+
+
+# Load custom configuration not managed by archgenxml
+try:
+    from Products.poxContentTypes.AppConfig import *
+except ImportError:
+    pass

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/configure.zcml

+<configure xmlns="http://namespaces.zope.org/zope" 
+           xmlns:browser="http://namespaces.zope.org/browser" 
+           xmlns:five="http://namespaces.zope.org/five"
+           xmlns:i18n="http://namespaces.zope.org/i18n"
+           i18n_domain="poxContentTypes">
+  
+  <i18n:registerTranslations directory="locales" />
+
+  <include file="profiles.zcml" />
+
+
+
+  <!-- ##code-section configure.zcml -->
+  <!-- ##/code-section configure.zcml -->
+
+</configure>

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/content/XNewsItem.py

+# -*- coding: utf-8 -*-
+#
+# File: XNewsItem.py
+#
+# Copyright (c) 2009 by []
+# Generator: ArchGenXML Version 2.4.1
+#            http://plone.org/products/archgenxml
+#
+# GNU General Public License (GPL)
+#
+
+__author__ = """JPG & MFR <unknown>"""
+__docformat__ = 'plaintext'
+
+from AccessControl import ClassSecurityInfo
+from Products.Archetypes.atapi import *
+from zope.interface import implements
+import interfaces
+
+from Products.CMFDynamicViewFTI.browserdefault import BrowserDefaultMixin
+
+from Products.ATReferenceBrowserWidget.ATReferenceBrowserWidget import \
+    ReferenceBrowserWidget
+from Products.ATContentTypes.content.newsitem import ATNewsItem
+from Products.ATContentTypes.content.newsitem import ATNewsItemSchema
+from Products.poxContentTypes.config import *
+
+##code-section module-header #fill in your manual code here
+##/code-section module-header
+
+copied_fields = {}
+copied_fields['relatedItems'] = ATNewsItemSchema['relatedItems'].copy()
+copied_fields['relatedItems'].schemata = "default"
+schema = Schema((
+
+    StringField(
+        name='lead',
+        widget=StringField._properties['widget'](
+            label='Lead',
+            label_msgid='poxContentTypes_label_lead',
+            i18n_domain='poxContentTypes',
+        ),
+        required=True,
+        label="Lead",
+    ),
+    StringField(
+        name='country',
+        widget=SelectionWidget(
+            label="Country",
+            description="Country where this piece of news has taken place",
+            label_msgid='poxContentTypes_label_country',
+            description_msgid='poxContentTypes_help_country',
+            i18n_domain='poxContentTypes',
+        ),
+        enforceVocabulary=True,
+        vocabulary="countryVocabulary",
+        languageIndependent=True,
+    ),
+    copied_fields['relatedItems'],
+
+),
+)
+
+##code-section after-local-schema #fill in your manual code here
+##/code-section after-local-schema
+
+XNewsItem_schema = ATNewsItemSchema.copy() + \
+    schema.copy()
+
+##code-section after-schema #fill in your manual code here
+XNewsItem_schema.moveField('lead', after='title')
+XNewsItem_schema.moveField('country', before='text')
+XNewsItem_schema.moveField('relatedItems', pos='bottom')
+##/code-section after-schema
+
+class XNewsItem(ATNewsItem):
+    """
+    """
+    security = ClassSecurityInfo()
+
+    implements(interfaces.IXNewsItem)
+
+    meta_type = 'XNewsItem'
+    _at_rename_after_creation = True
+
+    schema = XNewsItem_schema
+
+    ##code-section class-header #fill in your manual code here
+    ##/code-section class-header
+
+    # Methods
+
+    security.declarePublic('countryVocabulary')
+    def countryVocabulary(self):
+        """
+        Returns a list of country codes and their names for the "country" field
+        """
+
+        return (\
+                ('AQ', 'Antartiqa'),\
+                ('AR', 'Argentina'),\
+                ('BS', 'Bahamas'),\
+                ('BR', 'Brazil'),\
+                ('CM', 'Cameroon'),\
+                ('CL', 'Chile')\
+                )
+
+registerType(XNewsItem, PROJECTNAME)
+# end of class XNewsItem
+
+##code-section module-footer #fill in your manual code here
+##/code-section module-footer
+
+
+

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/content/__init__.py

+# -*- coding: utf-8 -*-
+#
+# File: content.py
+#
+# Copyright (c) 2009 by []
+# Generator: ArchGenXML Version 2.4.1
+#            http://plone.org/products/archgenxml
+#
+# GNU General Public License (GPL)
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
+# 02110-1301, USA.
+#
+
+__author__ = """JPG & MFR <unknown>"""
+__docformat__ = 'plaintext'
+
+
+##code-section init-module-header #fill in your manual code here
+##/code-section init-module-header
+
+
+# Subpackages
+# Additional
+
+# Classes
+import XNewsItem
+
+##code-section init-module-footer #fill in your manual code here
+##/code-section init-module-footer
+

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/content/interfaces.py

+# -*- coding: utf-8 -*-
+
+from zope.interface import Interface
+
+##code-section HEAD
+##/code-section HEAD
+
+class IXNewsItem(Interface):
+    """Marker interface for .XNewsItem.XNewsItem
+    """
+
+##code-section FOOT
+##/code-section FOOT

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/doc/__init__.py

+#

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/doc/testXNewsItem.txt

+This is a sample for a doctest file
+Here you can simply write python expressions
+and compare the output results like this:
+
+>>> i=1
+>>> print i
+1
+
+Lets import the necessary modules
+>>> from Products.poxContentTypes import config
+
+
+every line that starts with '>>>' will be interpreted
+as python statement.
+By writing the expected output after the python
+prompt lines you can compare that with the result
+from the above python statements. If the outputs
+differ you the test fails.
+
+
+
+Now you can continue with the further tests of your classes here

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/i18n/generated.pot

+# archgenxml generated POT File
+# JPG & MFR <unknown>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: poxContentTypes\n"
+"POT-Creation-Date: Sun Oct 04 13:00:53 2009\n"
+"PO-Revision-Date: Sun Oct 04 13:00:53 2009\n"
+"Last-Translator: JPG & MFR <unknown>\n"
+"Language-Team: JPG & MFR <unknown>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0\n"
+"Language-Code: en\n"
+"Language-Name: English\n"
+"Preferred-Encodings: latin1 utf-8\n"
+"Domain: poxContentTypes\n"
+
+#. Default: "Country where this piece of news has taken place"
+#: content\XNewsItem.py
+msgid "poxContentTypes_help_country"
+msgstr ""
+
+#. Default: "Country"
+#: content\XNewsItem.py
+msgid "poxContentTypes_label_country"
+msgstr ""
+
+#. Default: "Lead"
+#: content\XNewsItem.py
+msgid "poxContentTypes_label_lead"
+msgstr ""
+
+#. Default: "Testxnewsitems"
+#: content\xnewsitem_testxnewsitem.py
+msgid "poxContentTypes_label_testxnewsitems"
+msgstr ""
+

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/i18n/poxContentTypes-es.po

+msgid ""
+msgstr ""
+"Project-Id-Version: poxContentTypes 1.0\n"
+"POT-Creation-Date: Thu Oct 01 23:21:25 2009\n"
+"PO-Revision-Date: 2009-10-04 14:37-0300\n"
+"Last-Translator: Marcos F. Romero <marcosfromero@gmail.com>\n"
+"Language-Team: Spanish <spanish@yourdomain.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0\n"
+"Language-Code: es\n"
+"Language-Name: SpanishPreferred-Encodings: utf-8 latin1\n"
+"Domain: poxContentTypes\n"
+"X-Poedit-Basepath: C:\\progfiles\\Plone\\src\\Products.poxContentTypes\\Products\\poxContentTypes\n"
+
+#. Default: "Country where this piece of news has taken place"
+#: content\XNewsItem.py
+msgid "poxContentTypes_help_country"
+msgstr "País en donde ocurrieron estos hechos"
+
+#. Default: "Country"
+#: content\XNewsItem.py
+msgid "poxContentTypes_label_country"
+msgstr "País"
+
+#. Default: "Lead"
+#: content\XNewsItem.py
+msgid "poxContentTypes_label_lead"
+msgstr "Volanta"
+
+#. Default: "Testxnewsitems"
+#: content\xnewsitem_testxnewsitem.py
+msgid "poxContentTypes_label_testxnewsitems"
+msgstr ""
+
+#. Default: "Country where this piece of news has taken place"
+#: content\XNewsItem.py
+msgid "xnewsitem_desc"
+msgstr "Noticia eXtendida"
+

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/i18n/poxContentTypes.pot

+# archgenxml generated POT File
+# JPG & MFR <unknown>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: poxContentTypes\n"
+"POT-Creation-Date: Thu Oct 01 23:21:25 2009\n"
+"PO-Revision-Date: Thu Oct 01 23:21:25 2009\n"
+"Last-Translator: JPG & MFR <unknown>\n"
+"Language-Team: JPG & MFR <unknown>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0\n"
+"Language-Code: en\n"
+"Language-Name: English\n"
+"Preferred-Encodings: latin1 utf-8\n"
+"Domain: poxContentTypes\n"
+
+#. Default: "Country where this piece of news has taken place"
+#: content\XNewsItem.py
+msgid "poxContentTypes_help_country"
+msgstr ""
+
+#. Default: "Country"
+#: content\XNewsItem.py
+msgid "poxContentTypes_label_country"
+msgstr ""
+
+#. Default: "Lead"
+#: content\XNewsItem.py
+msgid "poxContentTypes_label_lead"
+msgstr ""
+
+#. Default: "Testxnewsitems"
+#: content\xnewsitem_testxnewsitem.py
+msgid "poxContentTypes_label_testxnewsitems"
+msgstr ""
+
+#. Default: "Country where this piece of news has taken place"
+#: content\XNewsItem.py
+msgid "xnewsitem_desc"
+msgstr ""
+

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/profiles.zcml

+<configure
+    xmlns="http://namespaces.zope.org/zope"
+    xmlns:genericsetup="http://namespaces.zope.org/genericsetup"
+    i18n_domain="poxContentTypes">
+
+  <include package="Products.GenericSetup" file="meta.zcml" />
+
+  <!-- ##code-section profiles.zcml-top #fill in your manual code here -->
+  <!-- ##/code-section profiles.zcml-top -->
+
+  <genericsetup:registerProfile
+      name="default"
+      title="poxContentTypes"
+      directory="profiles/default"
+      description="Extension profile for poxContentTypes."
+      provides="Products.GenericSetup.interfaces.EXTENSION"
+      />
+  
+  <!-- ##code-section profiles.zcml-bottom #fill in your manual code here -->
+  <!-- ##/code-section profiles.zcml-bottom -->
+
+</configure>

chapter08/pox.buildout/src/Products.poxContentTypes/Products/poxContentTypes/profiles/default/cssregistry.xml

+<?xml version="1.0"?>