Hi all,
I am using Tapestry in a product that will be used by multiple customers.
There will slight alterations in the pages depending on the customer's
preference like a few more edit fields, additional buttons etc. My question
is how to handle these variations of one page the most elegantly.
These are my ideas:
(1) If/Else approch: <t:if test=${customerA}> ... display some fields ...
<p:else> ... display other fields ... </p:else> </t:if>
(2) CSS Approch: <div class="customerA"> ... some fields ...</div>
<div class="customerB"> ... other fields ...</div> and set one of the
styles as 'display:none'.
(3) Page inheritance approch: Put the common stuff in a BasePage and build
two customer dependent variants inheriting from it. Don't know exactly if
this supported by Tapestry.
(4) Component approch: Put the common stuff in a component and have to
specialized pages use this component.
Any suggestions, possibliy new ideas?
Thanks,
Lothar
--
View this message in context:
http://old.nabble.com/-T5--Best-practices-for-customer-specific-code-in-pages-tp29083515p29083515.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
