What i am trying to achieve in terms of layout code would be something like the
following:
cfset newLayout = createObject('component', 'model.layout_twoColumn') cfset menuBar = createObject('component', 'model.layout_mnuBar') cfset list = createObject('component', 'model.HTMLObject_ul' cfset list.configure( content, "class=homepage" ) cfset paragraph = createObject('component', 'model.HTMLObject_p cfset paragraph.configure( content, "class=homepage" )
newLayout.leftColumn.add( menuBar ) newLayout.rightColumn.add( list ) newLayout.rightColumn.add( paragraph ) newLayout.render()
No offense but "Yuk!" - that's exactly the sort of complex code that Java programmers have to deal with when using Swing and AWT and it's *horrible* to work with, believe me!
Mach II provides most of the benefits of the layout manager concept you're seeking (I believe) without half the programming complexity.
Cascading changes through our sites would therefore a lot easier, then if the
formating code was contained on cfm pages even if they were themselves templates.
If you follow the CompositeView design pattern and break pages down into generic cascading views, you can easily make your changes by touching only a very small number of files.
Am i trying too hard to stick everything in the OO box?
Yes, and making a rod for your own back I fear...
Regards, Sean
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
