>I'm leaning towards default bShowIfEmpty=false -- isn't the >usual templating approach to apply a pre and post HTML >selectors for things like TABLEs, ULs and so on? > >I like the option of having it included or not but the >pre/post options were to enable wrappers for repetitive teaser >elements, no?
I've actually extended many of the core rules to include a closing property so that I can handle TABLEs and ULs. I wanted to be able to use one container to hold two rules, one outputting a LIs and the other teaser text in P blocks. I'm not sure this is the best approach, but it seems to be working. The reason I originally asked this question had to do with using the pre HTML on a landing page's child links container. If page has child links I want to put a heading with the current pages title above the links like so: <con:container label="landing_childlinks" preHTML="<h4>#stObj.title#</h4>"> If there were no child elements I didn't want to display the heading. I know I could search the tree and see if the page had children, but this seemed logical to use the container tag to handle this. With all of that said, my initial thought was that bShowIfEmpty should be false, but I could see it defaulting to true to maintain a consistency with the current container tag's behavior. --Nathan --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
