Kay Smoljak wrote: > Can you give me an example of where this approach is an advantage? > Sounds interesting...
Well, the example I'm most familiar with is my community app... it's been designed to support a level of "skinning" that allows more than the typical layout modifications. It can support completely different interface structures... the user can choose to view the forum as a UBB-style, linear board, in a Compuserve-style, multi-framed and fully threaded format, and so on. Whatever the developer can dream up. Each skin exists as its own little pseudo-circuit, and relies on a central set of dsp_ files to feed it data. The generic dsp_s process queries, check permissions, and so on... but leave the actual display of data to the individual skin's tmp_ files. All of which has two primary advantages: (1) Those dsp_s get re-used over and over across multiple skins. (2) I can restrict the CFML in tmp_ files to CFOUTPUT and CFLOOP... not so much as a CFSET anywhere in sight. That leaves the templates much easier for non-programming types to modify. -- Roger ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
