Thank you, that helped a lot. -----Original Message----- From: craig girard [mailto:[EMAIL PROTECTED]] Sent: Monday, October 09, 2000 7:13 PM To: Fusebox Subject: RE: Idea? There is a decent, although not in-depth, description in the upcoming book. There is a good example of it in use also. Basically app_model is ......well, 'modeled' after Javascripts document object model. It is a place to store all your global variables used for the site. When used in conjunction with cf_bodycontent and app_layout it offers a lot of reuse/control over your code. Here is a sample app_model <!--- Site variables ---> <cfparam name="request.site.mainDSN" default="jazzloft"> <!--- Path variables ---> <cfparam name="request.site.cfroot" default="/jazzloft"> <cfparam name="request.site.webRoot" default="/jazzloft"> <cfset request.site.imagePath = "/jazzloft/graphics"> <cfset request.site.imageAbsolutePath = "c:\webshare\wwwroot\jazzloft\graphics"> <!--- Page display variables ---> <cfparam name="request.page.headerfile" default="#request.site.cfRoot#/dsp_header.cfm"> <cfparam name="request.page.footerfile" default="#request.site.cfRoot#/dsp_footer.cfm"> <cfparam name="request.page.title" default="My Title"> <cfparam name="request.page.bgcolor" default="800000"> <cfparam name="request.page.font.color" default="FFFFFF"> <cfparam name="request.page.link.color" default="FFCC66"> <!--- User Variables ---> <cfset client.customerid= "whatever"> then a dsp_header file could work like so... <cfoutput> <HTML> <HEAD> <TITLE>#request.page.title#</TITLE> </HEAD> <body bgcolor="#request.page.bgcolor#" text="#request.page.font.color#" link="#request.page.link.color#" vlink="#request.page.vlink.color#" alink="#request.page.vlink.color#"> <div align="center"> </cfoutput> Hope this makes sense, Craig -----Original Message----- From: Jesse McPherson [mailto:[EMAIL PROTECTED]] Sent: Monday, October 09, 2000 7:04 AM To: Fusebox Subject: RE: Idea? I already went through the presentation and I thought it should of been more detailed with better examples, and I wanted the input of people that have implemented it. -----Original Message----- From: Michael Slatoff [mailto:[EMAIL PROTECTED]] Sent: Monday, October 09, 2000 4:50 PM To: Fusebox Subject: Re: Idea? This was a presentation at the Fusebox Conference http://www.fusebox.org/Files/presentations/ApplicationObjectModel.ppt ----- Original Message ----- From: "Josh" <[EMAIL PROTECTED]> To: "Fusebox" <[EMAIL PROTECTED]> Sent: Monday, October 09, 2000 8:37 AM Subject: Re: Idea? > What does app_model stand for anyway? Model of what? > > Josh Diehl > > craig girard wrote: > > > I use quite a few request scope variable, but I also use Gabe Roffman's > > app_model (best idea of 2000?). It works wonderful, but you do have to > > remember which variables are global, but thats not hard. It does NOT > > however convert url and form vars to request scope, just attribute scope. > > > > Craig > > > > -----Original Message----- > > From: Nat Papovich [mailto:[EMAIL PROTECTED]] > > Sent: Monday, October 09, 2000 1:39 AM > > To: Fusebox > > Subject: RE: Idea? > > > > ...and since Hal includes entire Fuseboxes within other Fuseboxes (as we all > > should be doing ;) ), that eliminates module independance. > > > > Nat Papovich > > ICQ 32676414 > > "If it was hard to write," > > says the Real Programmer, > > "it should be hard to understand." > > > > -----Original Message----- > > From: Hal Helms [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, October 08, 2000 10:20 PM > > To: Fusebox > > Subject: RE: Idea? > > > > Not just in custom tags, but in any included pages as well. > > > > -----Original Message----- > > From: paul smith [mailto:[EMAIL PROTECTED]] > > Sent: Monday, October 09, 2000 12:59 AM > > To: Fusebox > > Subject: RE: Idea? > > > > I'm trying to understand how a request scoped variable that > > > > 1. Is unique to a user, and > > 2. Dies with a new page request > > > > can have an unexpected value in other nooks and crannies in an > > application. > > > > Is the *real* problem only with custom tags? > > > > best, paul > > > > -------------------------------------------------------------------------- -- > > -- > > To Unsubscribe visit > > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or > > send a message to [EMAIL PROTECTED] with 'unsubscribe' in > > the body. > > > > -------------------------------------------------------------------------- ---- > > To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. > > -------------------------------------------------------------------------- ---- > To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. > ---------------------------------------------------------------------------- -- To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. ---------------------------------------------------------------------------- -- To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. ---------------------------------------------------------------------------- -- To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
