Am 22.11.2006 um 17:37 schrieb Tres Seaver:
The following two commands create the absolute minimum product which
makes filesystem skins availalbe. Run this from your INSTANCE_HOME:
$ mkdir -p Products/myproduct/skins/myproduct
$ cat > Products/myproduct/__init__.py <<EOT
from Products.CMFCore.DirectoryView import registerDirectory
You would then begin putting templates, scripts, etc. into the
'skins/myproduct' directory of the product, e.g.:
$ cat > Products/myproduct/skins/myproduct/some_script.py << EOT
## Script (Python) "some_script"
return 'Kilroy was here!'
Next, register that skin directory in your site's skins tool, by
a "Filesystem Directory View" using the registered path. Finally, add
the 'myproduct' skins dir to the search path for your skin on the
tool's "Properties" tab.
That is the business!
One slight addition to make it idiot-proof (or at least Charlie-
proof!) The Filesystem Directory View should be added in the sites
This all begs the question that if, as Jens suggests, file system is
the way to go, surely this process can be automated when creating a
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests