Thats what I use the comments attribute for, you should notice that the
comments already in there tell you which one I pass on which situation.

curveball, I would handle the same way. Here is my amended code, to include
your curvballs, etc.

I placed the comments on a separate line to aid in readability, but they are
part of the key to your curvballs

<IO>
  <in>
    <structure name="xfa" Scope="variables" Optional="False" >
      <String name="selectUser" Optional="False"  
              comments="Use this eXitFuseAction for when a user is
selected"/>

      <String name="selectGroup" Optional="False"  
              comments="Use this eXitFuseAction for when a group is
selected"/>

      <String name="deleteuser" Optional="False"  
              comments="Use this eXitFuseAction for when a user is selected
for deletion"/>

      <String name="save" Optional="False"  
              comments="Use this eXitFuseAction for when a users information
is saved"/>        
    </structure>
    
    <recordset name="users">
      <number name="userid"/>
      <number name="groupid"/>
      <string name="username"/>
      <string name="email"/>
      <string name="name"/>
    </recordset>

  </in>
  
  <out>
    <String name="fuseaction" Scope="FormOrUrl" Optional="False"  
            comments="Use the appropriate eXit FuseAction"/>  
  
    <number name="userid" Scope="FormOrUrl" Optional="True"
default="#val(users.userid)#"           
            comments="Pass when a user is to be deleted, or a users
information is saved."/>

    <number name="groupID" Scope="FormOrUrl" Optional="True"
default="#val(users.groupid)#"
            comments="Pass when a group is selected, or a users information
is saved."/>   
 
    <String name="username" Scope="FormOrUrl" Optional="True"
default="#users.username#"
            comments="Pass when a user is selected, or a users information
is saved."/>

    <String name="email" Scope="FormOrUrl" Optional="True"
default="#users.email#" 
            comments="Pass when a users information is saved."/>

    <String name="name" Scope="FormOrUrl" Optional="True"
default="#users.name#" 
            comments="Pass when a users information is saved."/>
  </out>
</IO>




-----Original Message-----
From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 10, 2002 2:06 PM
To: [EMAIL PROTECTED]
Subject: RE: Fusedoc XFAs


Ah, but how do you know that selecting a user means that
the username should be passed out? What if I threw you 
this curveball?

<in>
  <recordset name="users">
    <number name="userid"/>
    <string name="username"/>
    <string name="email"/>
    <string name="name"/>
  </recordset>
</in>

Now, when a user is selected, do you pass the userid, 
username, or email, or a combination thereof? And of course
it gets more complicated with more exits and variables. For
example, what if there's a form used to edit user information
and a button to delete that user, do you pass all the user's
info with the delete button? If not, what do you pass?

Patrick

> -----Original Message-----
> From: Matthew W Jones [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 10, 2002 2:48 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Fusedoc XFAs
> 
> 
> For this situation, I do this
> 
> <IO>
>   <in>
>     <structure name="xfa" Scope="variables" Optional="False" 
> format="CFML">
>       <String name="selectUser" Optional="False" 
> format="CFML" comments="Use
> this eXitFuseAction for when a user is selected"/>
>       <String name="selectGroup" Optional="False" format="CFML"
> comments="Use this eXitFuseAction for when a group is selected"/>
>     </structure>
>   </in>
>   
>   <out>
>     <String name="fuseaction" Scope="FormOrUrl" Optional="False"
> format="CFML" comments="Use the appropriate eXit FuseAction"/>
>     <String name="username" Scope="FormOrUrl" Optional="True" 
> format="CFML"
> comments="Pass when a user is selected."/>
>     <String name="groupID" Scope="FormOrUrl" Optional="True" 
> format="CFML"
> comments="Pass when a group is selected."/>    
>   </out>
> </IO>
> 
> 
> -----Original Message-----
> From: The Elegant [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 10, 2002 1:20 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Fusedoc XFAs
> 
> 
> This doesn't conform to the DTD, but here's what I do:
> 
> <out xfa="selectUser">
>   <string name="username">
> </out>
> <out xfa="selectGroup">
>   <string name="groupID">
> </out>
> 
> That way I know that "selectUser" exit should pass out
> a username and the "selectGroup" exit should pass out a
> groupID, etc. 
> 
> Patrick
> 
> > -----Original Message-----
> > From: Michael Slatoff [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, May 10, 2002 1:29 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Fusedoc XFAs
> > 
> > 
> > Maybe I shoulda asked it this way... How are people 
> > fusedocing their XFAs?
> > 
> > : Yes, all the time....you can't not document XFAs.
> > 
> > 
> 
> 

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to