>
> 1) Form fields: Do they count as outgoing paramters?
> If not, how do you specify their existence?
yes, noted as
<-- myfieldname
you could optionally use
<-- FORM.myfieldname
but that is just extra info anyway since FORMURL2attributes will change it
all at the next fuseaction. Since you're never really gonna refer to
FORM.myfieldname in the next template, then the fusedoc specifying the FORM
scope is *too* specific, IMHO
> 2) A parameter that is both incoming and outgoing, and
> may be changed (so it's not just a pass through <=>)?
is notated as
<-> myfieldname
>
> 3) A parameter that is optionally incoming and
> always outgoing (e.g., one that would be set by
> a <cfparam> tag)?
two entries:
--> [myfieldname]
<-- myfieldname
happens all the time, particularly with a search form or the results thereof
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
