> I have developed a method to bridge the gap between creating > page-containers and site-containers and the rules that are defined > within them.
Kewl idea (even if just for the inherit concept) but how would it be used ? I am trying to think of a scenario where I would want the parents container stuff in a child. I suppose you could use it to save you building different templates or "inheriting" a sidebar maybe. > The basis of this mod is to create a container within a template using > the following naming convention. #stobj.objectID#_test!!inherit. The key > part is using "!!inherit" to allow for the special processing in > container.cfm. If we are going to submit this as a candidate for modification to the core, why not modify the container.cfm to have an additional attribute instead of playing with the container name ? > I know that we should not tamper with core, but I hope that this idea > proves useful and finds it way into core for all to use. Well - "tamper with" and "propose enhancements in a supplied set of files" are two different things. Where you would be in trouble is if Daemon refused to add the changes and your site absolutely relied on them being there. Then you would be in the dark when upgrading. I have coded up quite a few modifications so far (generally after running it by the Daemon guys) and then just subimitted the changed file with the mods clearly identified. And !voila! it appears in the next build (and quite often you get your name in the file and a mention in the release notes) - it's very kewl. Regards, Gary --- 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
