yeah! this is the microsoft hate hate list! ;-)
-----Original Message-----
From: Nat Papovich [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 31, 2001 3:45 PM
To: Fusebox
Subject: RE: new xml fusedoc questions
Kyle -
Please use the topica.com mailing list as your first preference for talking
about all things Fusebox.
> 1)
> <properties>
> <property>
> Is this (and the name/value attributes) just for generic
> properties/attributes that we may want to pass? IOW is this just a
> generic container for anything extra we may want to pass?
> </property>
> </properties>
Yes, generic. It might be applicable to use <note> in this spot as well, if
you have more of a text-based piece of information to pass. The <property>
tag allows you to pass custom properties.
> 2) For the 10 defined variable types:
> ---------------------------------------------
> a) Can someone describe when and how you would use the onCondition=""
> attribute?
You have a fuse file that queries a database, then redirects to one of two
places. It goes to:
index.cfm?fuseaction=#xfa.success#&id=14
OR
index.cfm?fuseaction=#xfa.fail#
Notice that the variable "ID" only goes "out" if I'm using the xfa.success,
not if using xfa.fail. My FD for the ID variable would be like this:
<out>
<number scope="attributes" name="ID" onCondition="xfa.success">
</out>
> b) Can someone describe when and how you would use the mask="" attribute?
Most useful for DATETIME variable - you can declare what format you want the
variable passed out as:
<datetime name="myDate" mask="mm/dd/yyyy">
Also might be useful for embedded lists:
<list name="myEmbeddedList" comments="compoun, embedded list with userID and
objectID" mask="userID|objectID,userID|objectID,userID|objectID">
> c) Can someone describe when and how you would use the default=""
> attribute?
Useful for when you only have a certain variable that can only contain one
of a few values:
<string name="myVar" default="max|john|mike">
OR if you are using it to declare a variable aquiring the value of another
variable:
<in>
<string name="username" scope="formOrURL">
</in>
<out>
<string name="username" scope="client" default="#form.username#">
</out>
> 3)
> <assertions>
> <assert that="??" else="??" on="Server_OR_Client"
> comments="Comments_Here" onCondition="??"/>
> </assertions>
> a) Can someone describe when and how you would use the that="" attribute?
> b) Can someone describe when and how you would use the else="" attribute?
<assert that="len(form.username) gt 4"
else="#xfa.fail#&error=#attributes.errorMessage#">
> c) Can someone describe when and how you would use the on="" attribute?
The On="" attrib is used to tell the coder that this validation should be
performed on the CFML-side or in JavaScript. If the Fusedoc'er makes an
assertion for an outgoing variable, the on="client" should be used.
> If someone can help out with this, I am trying to make the XML doc as
> self-explanatory as possible so that as a new user browses it the
> barrier to
> utilization is very low.
As someone who spent a lot of time working on the XML Fusedocs, I'm glad to
know you're helping out with the polishing! Many thanks to you!
> I have attached the rough draft of the xml doc (fusedoc.xml) for
> comments if
> you have any.
Reattach it and send to [EMAIL PROTECTED] There is a sign-up from
topica.com for this list, if you are not already subscribed.
NAT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
