> Brian wrote:
> That's an interesting approach, but doesn't it seem like overkill?
Not at all. I think it's a logical extension of Hal's original idea.
Look at this new way compared to Hal's old way. Which is easier to
read? Which is easier to maintain? Which is more likely to break?
<!--- new way --->
<a href="#exitPoints.write('createPerson')#">Create Person</a><br>
<cfloop query="people">
<a href="#exitPoints.write('selectPerson', people.id )#">#people.name#</a>
<a href="#exitPoints.write('removePerson', people.id , groupID)#">[remove]</a>
<br>
</cfloop>
<!--- old way --->
<a href="#request.self#fuseaction=#xfa.createPerson#">Create Person</a><br>
<cfloop query="people">
<a href="#request.self#fuseaction=#xfa.selectPerson#&personID=#people.id#
)#">#people.name#</a>
<a
href="#request.self#fuseaction=#xfa.removePerson#&personID=#people.id#&groupID=#groupID)#">[remove]</a>
<br>
</cfloop>
If I start using this idea and like it a lot I might implement
Barney's idea of using replaceable parameters with a post- (or pre-)
processor. And I would probably create an XML schema to define the
exit points. I would probably create plugins for Mach-ii/FB4 so that I
can include the ExitPoint XML tags in the Mach-ii/FB4 configuration
files. That's why I'm surprised something like this doesn't already
exist.
Patrick
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
