Sincerely, Amit Talwar intellikaps

-----Original Message----- From: Brad Roberts [mailto:broberts@nxs.net] Sent: Friday, May 11, 2001 3:56 AM To: Fusebox Subject: RE: xFATs Anyone? (was RE: XFB question - XFA in MyGlobals?)

> How do you unit test your fuse files?

Expain what you mean.

> What if your IT department says "that worm that's putting 'f**ck USA > Government' all over web sites is a threat; we're setting our > servers to use > start.cfm as the default filename; all index.cfm files must be renamed > immediately"?

No big deal. You could easily define #request.self# in application.cfm and use that instead of hard coding.

> What do you do when you want to change what happens after a user > logs in?

Okay, just change <cflocation url="DoThis.cfm"> to <cflocation url="DoThat.cfm">

> Looks like you have to chase around the fuse files AND the xFATs > to find out > how things work, then makes changes to the existing fuse file and its > associated xFAT.

Not really. Just do the above. When you make a change in XFB you just change the XFA, here you just change the XFAT (XFA Templates).

I actually made a "viewer" to view xFATs. It uses cfdirectory to get all the files and reads the file to give you the fuseaction. You can sort by fuseaction which is neat. You can even click a link to create a static html file for any fuseaction.

> Why even pretend that this approach is Fusebox? It violates the > one tenet that > makes Fusebox what it is: all calls go back to the Fusebox.

Everything still goes through index.cfm. You could just as easily point to index.cfm?fuseaction=login and it works fine.

> I don't think I want to pay that price for search engine friendliness.

Okay, that's cool. I'm not saying "Make this the Rule", just saying, "What do you guys think?"

Thanks for the feedback. I'd like more if you've got any.

> > - Jeff > > On 10 May 2001, at 14:21, Brad Roberts wrote: > > > Check this out: > > > > In place of XFA's, I started creating what I call XFA Templates > (or XFATs). > > I place them in the root directory. Here's a skinny XFAT example: > > > > <!--- SignUp.cfm ---> > > <cfset attributes.fuseaction="members.signup.new"> > > <cfinclude template="index.cfm"> > > <!--- End ---> > > > > Here's how I use it in my code: > > > > {a href="SignUp.cfm">Sign Up!</a> > > or > > <form action="SignUp.cfm"> > > > > Opposed to: {a > href="#request.self#?fuseaction=#attributes.xfa.signup#>Sign > > Up!</a> > > > > This is more "search engine friendly" and easier for people to read. > > ============================================================== > | Jeffrey S. Peters | "Specialization is for insects." | > | jeff@GrokFusebox.com | - Lazarus Long | > | PGP key for Jeffrey S. Peters at ldap://keyserver.pgp.com | > ============================================================== > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists