Okay, now I guess I'm just being dense...
If copying everything to VARIABLE scope is the answer, the what was the
question???
What is the problem that using VARIABLE scope instead of ATTRIBUTES fixes?
I know there's a good reply to this one ;-)
Lee.
-----Original Message-----
From: Hal Helms
Fair enough. I think my suggested solution of rewriting the
FormURL2Attributes to allow for scoping as variables.vars will take care
of
everyone, no?
....
-----Original Message-----
From: BORKMAN Lee [mailto:[EMAIL PROTECTED]]
....
I think the main questions to be addressed are (not very well phrased):
1) What shortcomings of FB does XFB alleviate?
2) What shortcomings does XFB introduce?
3) What advantages does XFB bring?
4) What existing FB advantages does XFB ruin?
The same questions (roughly) could be be asked of FORMURL2ATTRIBUTES.
The trouble is that XFB as it stands can be encompassed as an
interesting,
attractive variation on FB. But if XFB removes the FORMURL2ATTRIBUTES
(without replacing it with some equivalent), then we are looking at a
substantial schism, in which you have to choose one or the other, and
never
the twain shall meet.
IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used by
the named addressee. It is confidential and may contain legally privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. If you receive this e-mail in error, please
immediately delete it from your system and notify the sender. You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient. The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
