Well, here's one idea: XFA.onSubmitArticle XFA.onBrowseArchive XFA.onComment You understand that the fuseactions would NOT be called this--the idea of the XFA is that it descibes HOW the user (or system) exits the fuse. Hal Helms Team Allaire [ See www.halhelms.com <http://www.halhelms.com> for info on training classes ] -----Original Message----- From: Toby Tremayne [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 13, 2001 11:30 PM To: Fusebox Subject: RE: XFA's to carry that thought on actually... where I run into problems is when I have a bunch of hrefs in a fuse, which might go off to three different fuseactions. Say for instance I'm on a page that views articles - there would be links to "submit an article", "browse the archive" and "comment on this". how would you name the XFA's for these? Toby Tremayne Code Poet and Zen Master of the Heavy Sleep Show Ads Interactive 359 Plummer St Port Melbourne VIC 3207 P +61 3 9245 1247 F +61 3 9646 9814 ICQ UIN 13107913 -----Original Message----- From: Toby Tremayne [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 14 March 2001 2:49 PM To: Fusebox Subject: RE: XFA's since I know you're looking at your email right now <grin>... when you name your XFA's, what kind of convention do you tend toward? I find that often I'm setting an XFA name which is identical to the fuseaction that gets set as it's value, IE <cfset attributes.XFA.updatePoem = "UpdatePoem"> I'm thinking that wherever possible I'm supposed to be saying <cfset attributes.XFA.onSubmitForm = "UpdatePoem"> or <cfset attributes.XFA.onCancel = "ListPoems"> etc - naming the XFA's as ACTIONS rather than fuseactions themselves... that would make a little more sense to me. Is that what I should be doing? Toby Tremayne Code Poet and Zen Master of the Heavy Sleep Show Ads Interactive 359 Plummer St Port Melbourne VIC 3207 P +61 3 9245 1247 F +61 3 9646 9814 ICQ UIN 13107913 -----Original Message----- From: Hal Helms [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 14 March 2001 2:13 PM To: Fusebox Subject: RE: XFA's Some of them (navigation XFAs for example) are almost constants and I sometimes put those in myGlobals.cfm. But most of them need to be set in the cfcase statement. For example, XFA.onSubmitForm will vary from case to case. Hal Helms Team Allaire [ See www.halhelms.com <http://www.halhelms.com> for info on training classes ] -----Original Message----- From: Toby Tremayne [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 13, 2001 9:41 PM To: Fusebox Subject: XFA's just curious, do most of you tend to code your XFA's in a big block at the top of index.cfm or individually for each fuse, within the cfcase statement? Toby Tremayne Code Poet and Zen Master of the Heavy Sleep Show Ads Interactive 359 Plummer St Port Melbourne VIC 3207 P +61 3 9245 1247 F +61 3 9646 9814 ICQ UIN 13107913 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
