Hello list,
I am trying to modularize an existing turbine 2.3.2 app. The app should
be shipped to several customers, each with a distinct layout. But - how?
As far as I can see, the skin mechanism is not enough because I can only
"skin-ize" images, colors etc. Instead, what I want to do is to
implement completely different layout sets having customer specific
appearance beyond just replacing images: e.g. using a table layout for
one customer and using sophisticated <div> elements for the other.
My first idea was: put each customer layout set in different subdirs of
the templates/app/* directories, e.g:
templates
app
layouts
default
customer1
customer2
navigations
default
customer1
customer2
screens
default
customer1
customer2
Now each time I use a reference to a template file, I have to "qualify"
it using the customer directory prefix. E.g.:
customerDir = "customer1"; // this would be in fact a global setting
rundata.setScreenTemplate(customerDir + "," + "Orders.vm");
To be able to qualify template links in my .vm files, I would implement
a pull tool (here named $tpl):
<a href='$link.setPage($tpl.qualify("Orders.vm"))'>Orders</a>
Do you think this is the right, Turbine-friendly way to tackle the
problem? Or am I missing something and there is a better way?
TIA,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
