thank you all for your hints, after thinking about the pros and cons and
my requirements a little more, I decided to:
- implement a mainly CSS based layout with "skinned" CSS files
- separate different layout sets (with major difference) via the
velocity template dir (TR.properties)
Thus, I will switch between very different layouts in the course of the
build process, using the build scripts to set the course. Therefore, it
is now part of the build process to set these 2 properties:
services.VelocityService.file.resource.loader.path =
$CUSTOMER_TPL_HOME
tool.ui.skin=$CUSTOMER
Below the several $CUSTOMER_TPL_HOME dir, there is the turbine standard
template directory structure:
- CUST1
+- layouts
+- navigations
+- screens
- CUST2
+- layouts
+- navigations
+- screens
the decision at build time has also the advantage that there are no
files CUST2 specific files are shipped to CUST1 (although deactivated,
it would be a minor issue that CSS files and layouts of other customers
are available on the server of one cust). instead, the build process
leaves me with just the needed files for the customer we have built for.
thx for your help,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
