On Jun 10, 2005, at 12:26 AM, Ashish Raniwala wrote:
Hi Erik,
This is a public list - no need to address anyone in particular here.
I have a design issue and our team need some guidelines on what
functionality should be written as component and what should be page?
General guideline is, follow DRY and make everything which is re
usable as component. But we have some complex cases where it is
getting difficult.
I want to validate that we are not voilating basic rules of tapestry.
There are no rules. Do what feels right. If you are copy/pasting
code, then back up and componentize or centralize. If you're not,
then keep cruising.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
