Our framework here uses the custom tag approach, not to imply it is the best way to go, just what has been in use here for years. So a typical page could be something like:
<cf_headertag title="Blah" check="Yes" userlevel="GenUp"> <cf_tableheader title="Something"> <tr><td>Blah</td></tr> <cf_tablefooter> <cf_button label="Back;Menu"> <cf_footer links="Yes"> Now each tag may call other tags, for instance the header one calls a tag that checks to see if logged in, checks to see if you have a user level that is at the level attribute or above and so on. Just glancing at one simple page, looks like 18 total CFM files are called for this page to be displayed, that includes the Application.cfm and OnRequestEnd.cfm files. This same framework uses cfmodule a lot for the database table management section. It essentially is setup so you make one file per table that you need to manage and that file is a huge switch/case and other pages that build your output via cfmodule calls to the switch/case. That section allows for updating/inserting/deleting/viewing/exporting data into whatever database table. I'd almost hate to know how resource wasteful all this comes out to be, but does make it easy for the non-CF people to whip out some applications which is why it is still in use to this day. -- Aaron Rouse http://www.happyhacker.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - RUWebby http://www.ruwebby.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:185813 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
