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
registerDirectory('skins', globals())
EOT
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"
##parameters=
return 'Kilroy was here!'
EOT
Next, register that skin directory in your site's skins tool, by
adding
a "Filesystem Directory View" using the registered path. Finally, add
the 'myproduct' skins dir to the search path for your skin on the
skins
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
"skins" folders.
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
portal?
Charlie
--
Charlie Clark
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
