I'v been playing with BodyContent and app_layou ideas in my PHP-Fusebox stuff.
One of the methods I am liking is to name the different blocks of layout using
the BodyContent class (you can do this with the CF custom tag as well), and
then just having ONE layout template that outputs the variables containing the
different display blocks.
That is, instead of having a header, footer, and body block, I have "topnav",
"bottomnav", "advertisements", and "body" blocks each in a variable, then in
my app_layout.php, I just include the template I want to use, displaying the
blocks where they belong by just placing the variable output in the right
places. It would be VERY easy to change the look-and-feel by using a
different stylesheet and layout template, simply by setting a variable with
the template name, or doing some conditional handling in the app_layout
template.
Hope that makes sense,
David Huyck
[EMAIL PROTECTED]
Michel Gallant wrote:
| My company is looking into developping a set of custom tags to speed up
| development of sites for our clients. We want to make modules for the
| commonly used componants (forums, calendars, etc). The problem I have is
| that different clients want their forums and calendars to have different
| layouts, often requiring us to modify the module itself, then we're stuck
| with many slightly different versions of the same module to upkeep. I was
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
