Getting Started - The Automated Way
You learned from the "first part of this chapter":getting-started how to
manually setup DIYPloneStyle for making it a ready to go skin skeleton
product.
There is a much faster way to get a clean product that can become a new style
for Plone, by making use of the included generator script.
In the DIYPloneStyle product folder on the filesystem, there is a 'bin/'
directory where you will find a python script called 'generator.py'.
This script can be used for applying all the manual modifications that are
listed in the previous part of this chapter.
Download and Expand DIYPloneStyle
* Place the expanded DIYPloneStyle product folder in the 'Products/'
directory of your Zope instance.
* **Uninstall DIYPloneStyle** if you already installed it
(in Plone, as manager, go to *Site Setup > Add/Remove Products*).
Run the script
On Unix/Linux/OSX
From a bash shell (from the Terminal), use a command which should look like
this one::
/path_to_zope_instance_home_folder/Products/DIYPloneStyle/bin/generator.py --productname MyOwnPloneSkin
On Windows
* Choose *run* from the Windows *Start menu* and type 'cmd'. Press *OK*
* Run the script with a command which should look like this one::
python c:\instance_home_folder\Products\DIYPloneStyle\bin\generator.py --productname MyOwnPloneSkin
On Unix like systems, you can call the script from any directory.<br />
On Windows you can't: your current working directory must be outside the
product.
I've heard about permission problems on Windows when using the script from a
subversion checkout of DIYPloneStyle.<br />
If you need to work with the latest *svn trunk* version of the product under
Windows, take the time to remove all its '.svn' folders before running the
script.
Start Building
You now have a fresh Plone skin product in the 'Products/' directory of
your Zope instance.<br />
All you have to do when you want it to be installable in Plone is to restart
the Zope server.
Note --
If you want to learn more about the possible script arguments, you can either
see the script output when called without args (or with the '--help' option)
or read its fairly easy to understand code.
