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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Nov 2006, at 13:44, Charlie Clark wrote:
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?
Why? Not everyone who creates a portal wants to
Am 24.11.2006 um 16:00 schrieb Jens Vagelpohl:
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?
Why? Not everyone who creates a portal wants to develop filesystem
products.
I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Nov 2006, at 16:22, Charlie Clark wrote:
I was extrpolating from your previous post about the correct way to
do customisation:
Or, and this is the more complicated but right way to do it,
you create a filesystem product with a filesystem
Am 24.11.2006 um 16:26 schrieb Jens Vagelpohl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Nov 2006, at 16:22, Charlie Clark wrote:
I was extrpolating from your previous post about the correct way
to do customisation:
Or, and this is the more complicated but right way to do it,
Am 21.11.2006 um 17:14 schrieb Jens Vagelpohl:
No, you either go into the portal_skins tool, find the
main_template and use the Customize functionality to create a
copy in the custom skin folder, which you can edit. Or, and this
is the more complicated but right way to do it, you create a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22 Nov 2006, at 17:12, Charlie Clark wrote:
Am 21.11.2006 um 17:14 schrieb Jens Vagelpohl:
No, you either go into the portal_skins tool, find the
main_template and use the Customize functionality to create a
copy in the custom skin
