I think it depends.
Yours is easier and quicker to write and maintain.
Mine accomplishes the task within the format of the DTD, and would be easier
to understand, in my opinion. If you are a fusecoder, then you should be
able to understand my method without explanation. But, If you are doing
both the documenting and the coding, mine is awfully verbose.
With yours outside of what I would expect from a fusedoc, I would imagine
that you would need to explain how yours works to the fusecoder. But it is
simple enough that it would take no time to pick up, and get used to.
I am however, hesitant to agree with having more than 1 out section.
I could see though something along the lines of what you have, but instead
of several outs, something like below.
I added a FICTIONAL eXitFuseAction container
<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>
<eXitFuseaction name="selectUser">
<String name="fuseaction" Scope="FormOrUrl" Optional="False"
default="#xfa.SelectUser#"/>
<String name="username" Scope="FormOrUrl" Optional="False"
default="#users.username#"/>
</eXitFuseaction>
<eXitFuseaction name="selectGroup">
<String name="fuseaction" Scope="FormOrUrl" Optional="False"
default="#xfa.SelectUser#"/>
<number name="groupID" Scope="FormOrUrl" Optional="False"
default="#val(users.groupid)#"/>
</eXitFuseaction>
<eXitFuseaction name="deleteuser">
<String name="fuseaction" Scope="FormOrUrl" Optional="False"
default="#xfa.SelectUser#"/>
<number name="userid" Scope="FormOrUrl" Optional="False"
default="#val(users.userid)#"/>
</eXitFuseaction>
<eXitFuseaction name="save">
<String name="fuseaction" Scope="FormOrUrl" Optional="False"
default="#xfa.SelectUser#"/>
<number name="userid" Scope="FormOrUrl" Optional="False"
default="#val(users.userid)#"/>
<number name="groupID" Scope="FormOrUrl" Optional="False"
default="#val(users.groupid)#"/>
<String name="username" Scope="FormOrUrl" Optional="False"
default="#users.username#"/>
<String name="email" Scope="FormOrUrl" Optional="False"
default="#users.email#"/>
<String name="name" Scope="FormOrUrl" Optional="False"
default="#users.name#"/>
</eXitFuseaction>
</out>
</IO>
-----Original Message-----
From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 10, 2002 3:00 PM
To: [EMAIL PROTECTED]
Subject: RE: Fusedoc XFAs
> Matthew wrote:
>
> 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.
>
Okay, both methods work. (Well, mine's not legal, at least
at the moment, but nevermind that for now...) Which of the
two do you think is easier to read and maintain?
Patrick
==^================================================================
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
==^================================================================
