Yeah, but your way when you update one layout you'll have to make changes to others and provides for a bad maintenance design. It doesn't make sense to me to make a new layout that is almost exactly the same as another one. >From a reusability standpoint I would think it would be more beneficial to be able to remove. That way I can use one layout and can guarantee that any changes to the one layout gets applied across the application.
Shawn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig McClanahan Sent: Tuesday, November 22, 2005 4:45 PM To: Struts Users Mailing List Subject: Re: [tiles] On 11/22/05, Garner, Shawn <[EMAIL PROTECTED]> wrote: > > There are ways to put content into a tile but there isn't a way to remove > a > tile. > > Say we have a layout that has a menu by default then you extend that > layout > and you don't want a menu. Instead of thinking about removing tiles from a layout, I would suggest thinking about your hierarchy the other way around. Build a layout that does not have the menu, and another layout (extending the previous one) that does have a menu. Now, for any particular tile, choose the correct layout to extend based on whether you want the menu or not. Craig **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
