RE: [ACFUG Discuss] Best Practice for Assembling Pages
Thanks to all for your ideas -- Much appreciated! Precia, what did you mean about using custom tag instead of cfinclude? How would you use attributes? Clarke -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Precia Sent: Tuesday, November 07, 2006 11:04 AM To: discussion@acfug.org Subject: Re: [ACFUG Discuss] Best Practice for Assembling Pages What if you used method 2 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. but used a custom tag for the header and footer instead of cfInclude so you may make better use of attributes. Precia. On 11/7/06, Clarke Bishop [EMAIL PROTECTED] wrote: Did my questions not make sense to anyone or was everyone just feeling sorry for me sending messages out on Saturday night? If this is confusing, please let me know. Clarke From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Saturday, November 04, 2006 8:01 PM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages I am building a simple information-oriented site. Each page will have the same header, footer, right-hand column and a content area. Ideally, I'd like my customer to be able to edit the content area, but nothing else. I'd like to ask all of you about the best practice for assembling the page. Here are the ways I'm thinking about: 1. Use a Dreamweaver template and/or Dreamweaver library. I've done this before, so I know it works. 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. 3. Use onRequestStart in Application.cfc to cfinclude the header, footer, etc. 4. Some other more CF-oriented approach, but hopefully not FuseBox I like method #1 or #2, because then I can use Contribute and allow my customer to edit certain content. Right now, the site will only use the most minimal CF for a Contact Form, etc. Still, I want to get this right from the start. Thanks for any ideas! Clarke - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -
Re: [ACFUG Discuss] Best Practice for Assembling Pages
cfif attributes.Category=Hardware should be cfif attributes.Category is Hardware On 11/9/06, Precia [EMAIL PROTECTED] wrote: Clarke, If you produced a custom tag from the cfm file PageHeaderFooter.cfm, cf_PageHeaderFooter ---page content--- /cf_PageHeaderFooter would be the beginning and ending tags. This is a great wrapper for your page. For the custom tag code... !---PageHeaderFooter.cfm--- cfif thisTag.ExecutionMode is 'start' !--- Start tag processing --- Header information cfelse !--- End tag processing --- Footer information /cfif As for the attributes…. cf_PageHeaderFooter Category=Hardware cfif thisTag.ExecutionMode is 'start' !--- Start tag processing --- cfif attributes.Category=Hardware Header information for hardware (such as differ color, different title for the category, different navigation) cfifelse attributes.Category is Software Header information for software (such as differ color, different title for the category, different navigation) cfelse Header information for anything else /cfif cfelse !--- End tag processing --- Footer information /cfif - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -
RE: [ACFUG Discuss] Best Practice for Assembling Pages
BTW also if you are just using cf for includes and a mail form, you might consider something less expensive like php includes and the php mail function. Your client could still do edits through Contribute. This way you could run the simple site off of a very simple hosting. Linux/php hosting plans are really cheap compared to cf plans. I am starting to get away from cf for sites that dont have any real application features. Of course for any real web application, I still prefer cf for its developer friendliness. Dusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Tuesday, November 07, 2006 10:29 AM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages Did my questions not make sense to anyone or was everyone just feeling sorry for me sending messages out on Saturday night? If this is confusing, please let me know. Clarke From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Saturday, November 04, 2006 8:01 PM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages I am building a simple information-oriented site. Each page will have the same header, footer, right-hand column and a content area. Ideally, I'd like my customer to be able to edit the content area, but nothing else. I'd like to ask all of you about the best practice for assembling the page. Here are the ways I'm thinking about: 1. Use a Dreamweaver template and/or Dreamweaver library. I've done this before, so I know it works. 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. 3. Use onRequestStart in Application.cfc to cfinclude the header, footer, etc. 4. Some other more CF-oriented approach, but hopefully not FuseBox I like method #1 or #2, because then I can use Contribute and allow my customer to edit certain content. Right now, the site will only use the most minimal CF for a Contact Form, etc. Still, I want to get this right from the start. Thanks for any ideas! Clarke - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink -
RE: [ACFUG Discuss] Best Practice for Assembling Pages
I've been told I did it wrong, but I'm from the school that says if it works and works well, then it's not wrong. What we did and have been doing since CF5 is using the Application.cfm to setup the variables as well as the frame of the page using CFINCLUDES for the header and after that we open up a table and include a directory-dependent subnav in the left TD and open the right TD for the content of the actual page being called. We use OnRequestEnd.cfm for the footer which ends the table and includes the header links file. This allows the page layout to remain constant across our entire site while affording the flexibility of including the directory-dependent subnav.cfm. We do some access control in the included headers and subnavs too. The Application.cfm establishes the css, but you could easily stash that in thesubnav.HTH mf mark fennell athens regional medical center athens, ga -- This email is intended only for the named recipient(s). It may containinformation that is proprietary, confidential or otherwise prohibited fromdisclosure. If you are not the named addressee,you are not authorized to read, print, retain, copy or disseminatethis message or anypart of it. Ifyou have received this message inerror, pleasereply immediately by email or telephoneme at 706-475-4357 and delete all copiesof the message. -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Clarke BishopSent: Tuesday, November 07, 2006 10:29 AMTo: discussion@acfug.orgSubject: [ACFUG Discuss] Best Practice for Assembling Pages Did my questions not make sense to anyone or was everyone just feeling sorry for me sending messages out on Saturday night? If this is confusing, please let me know. Clarke From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke BishopSent: Saturday, November 04, 2006 8:01 PMTo: discussion@acfug.orgSubject: [ACFUG Discuss] Best Practice for Assembling Pages I am building a simple information-oriented site. Each page will have the same header, footer, right-hand column and a content area. Ideally, I'd like my customer to be able to edit the content area, but nothing else. I'd like to ask all of you about the best practice for assembling the page. Here are the ways I'm thinking about: 1. Use a Dreamweaver template and/or Dreamweaver library. I've done this before, so I know it works. 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. 3. Use onRequestStart in Application.cfc to cfinclude the header, footer, etc. 4. Some other more CF-oriented approach, but hopefully not FuseBox I like method #1 or #2, because then I can use Contribute and allow my customer to edit certain content. Right now, the site will only use the most minimal CF for a Contact Form, etc. Still, I want to get this right from the start. Thanks for any ideas! Clarke- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink -
RE: [ACFUG Discuss] Best Practice for Assembling Pages
Return Receipt Your RE: [ACFUG Discuss] Best Practice for Assembling Pages document: wasShawn Gorrell/ATL/FRS received by: at:11/07/2006 11:18:36 AM - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -
Re: [ACFUG Discuss] Best Practice for Assembling Pages
What if you used method 2 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. but used a custom tag for the header and footer instead of cfInclude so you may make better use of attributes. Precia. On 11/7/06, Clarke Bishop [EMAIL PROTECTED] wrote: Did my questions not make sense to anyone or was everyone just feeling sorry for me sending messages out on Saturday night? If this is confusing, please let me know. Clarke From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Saturday, November 04, 2006 8:01 PM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages I am building a simple information-oriented site. Each page will have the same header, footer, right-hand column and a content area. Ideally, I'd like my customer to be able to edit the content area, but nothing else. I'd like to ask all of you about the best practice for assembling the page. Here are the ways I'm thinking about: 1. Use a Dreamweaver template and/or Dreamweaver library. I've done this before, so I know it works. 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. 3. Use onRequestStart in Application.cfc to cfinclude the header, footer, etc. 4. Some other more CF-oriented approach, but hopefully not FuseBox I like method #1 or #2, because then I can use Contribute and allow my customer to edit certain content. Right now, the site will only use the most minimal CF for a Contact Form, etc. Still, I want to get this right from the start. Thanks for any ideas! Clarke - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -
RE: [ACFUG Discuss] Best Practice for Assembling Pages
Also your number 2 approach will work good with Contribute and prevent the client from being able to edit the include areas in Contribute (unless they go to the include file in contribute to make the edit). Again cant think of a reason to use the DW template if you use includes. Dusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dusty Hale Sent: Tuesday, November 07, 2006 10:59 AM To: discussion@acfug.org Subject: RE: [ACFUG Discuss] Best Practice for Assembling Pages Clarke: I have successfully used your #2 approach and by using the includes, it will prevent your client from being able to edit the include areas which I think is what you want. I personally think this is much better than going the DW template route. BTW I dont see why you would been the DW template if you use the includes but that is just me. Hope this info helps in your decesion making. Dusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Tuesday, November 07, 2006 10:29 AM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages Did my questions not make sense to anyone or was everyone just feeling sorry for me sending messages out on Saturday night? If this is confusing, please let me know. Clarke From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Saturday, November 04, 2006 8:01 PM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages I am building a simple information-oriented site. Each page will have the same header, footer, right-hand column and a content area. Ideally, I'd like my customer to be able to edit the content area, but nothing else. I'd like to ask all of you about the best practice for assembling the page. Here are the ways I'm thinking about: 1. Use a Dreamweaver template and/or Dreamweaver library. I've done this before, so I know it works. 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. 3. Use onRequestStart in Application.cfc to cfinclude the header, footer, etc. 4. Some other more CF-oriented approach, but hopefully not FuseBox I like method #1 or #2, because then I can use Contribute and allow my customer to edit certain content. Right now, the site will only use the most minimal CF for a Contact Form, etc. Still, I want to get this right from the start. Thanks for any ideas! Clarke - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink -
Re: RE: [ACFUG Discuss] Best Practice for Assembling Pages
Im not sure how the latest version of contribute is but, in dealing with templates that are calling includes it can be a pain because Contribute wants the user to enter the page title. It can cause a double title to appear if you are say setting the title in a variable and then contribute sticks it in as well. Just something to keep in mind when you build DW templates and use them in Contribute. I think the templates are ok but can be overrated. On 11/7/06, Dusty Hale [EMAIL PROTECTED] wrote: Also your number 2 approach will work good with Contribute and prevent the client from being able to edit the include areas in Contribute (unless they go to the include file in contribute to make the edit). Again can't think of a reason to use the DW template if you use includes. Dusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dusty Hale Sent: Tuesday, November 07, 2006 10:59 AM To: discussion@acfug.org Subject: RE: [ACFUG Discuss] Best Practice for Assembling Pages Clarke: I have successfully used your #2 approach and by using the includes, it will prevent your client from being able to edit the include areas which I think is what you want. I personally think this is much better than going the DW template route. BTW I don't see why you would been the DW template if you use the includes but that is just me. Hope this info helps in your decesion making. Dusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Tuesday, November 07, 2006 10:29 AM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages Did my questions not make sense to anyone or was everyone just feeling sorry for me sending messages out on Saturday night? If this is confusing, please let me know. Clarke From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clarke Bishop Sent: Saturday, November 04, 2006 8:01 PM To: discussion@acfug.org Subject: [ACFUG Discuss] Best Practice for Assembling Pages I am building a simple information-oriented site. Each page will have the same header, footer, right-hand column and a content area. Ideally, I'd like my customer to be able to edit the content area, but nothing else. I'd like to ask all of you about the best practice for assembling the page. Here are the ways I'm thinking about: 1. Use a Dreamweaver template and/or Dreamweaver library. I've done this before, so I know it works. 2. Use Dreamweaver templates as in #1, but cfinclude the header, footer, etc. 3. Use onRequestStart in Application.cfc to cfinclude the header, footer, etc. 4. Some other more CF-oriented approach, but hopefully not FuseBox I like method #1 or #2, because then I can use Contribute and allow my customer to edit certain content. Right now, the site will only use the most minimal CF for a Contact Form, etc. Still, I want to get this right from the start. Thanks for any ideas! Clarke - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by FusionLink - -- Steven Ross web application interface developer http://www.zerium.com [mobile] 404-488-4364 [fax] 928-484-4364 - To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -
