I think I misunderstood the question. I have always thought of Tapestry as component centric. So, it didn't seem to be much of a question. I have thought that due to my framework. Since I only have one page, I only create components. The other option is to create many pages and only embed standard components there, without creating new components.
<rambling thoughts> So, then the question is which is better, new custom components or custom pages? Creating custom components has not been a problem, it also enables re-use. We have two pages, one that is my "frame" and the other that holds all of my components. The page that holds my components has 78 components in it. Pages seem to be "destinations". The XPer in me says, in general, not to create components because you may want to re-use them some day. There is a certain amount of manual overhead in creating lots of components. In general, you can create lots of pages with very little components or you can create lots of pages with a component for each one or something in the middle. Being at one end of the extreme, many components hasn't caused me any grief, so far ;-). </rambling thoughts> HTH, Mark -----Original Message----- From: Robert Walker [mailto:[EMAIL PROTECTED] Sent: Tue 8/9/2005 8:13 AM To: Tapestry users Subject: RE: Component Abuse I have a bunch of custom components in my project and the vast majority of them are project-specific. I'd agree that it's not a good idea to make a component just because you can, but I think as long as it's saving SOMEBODY time and code (even if it's just yourself), the component's existence is justified. Robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
