Title: Message
i'd be more inclined to re-use the two fuses, qry_Passwordinfo.cfm and act_validatePassword in the SendPassword fuseaction, with some conditional logic perhaps? maybe something like:
 
<cfcase value="SendPassword">           

     <cfset XFA.Login = "home.login">

             <cfinclude template = "qry_Passwordinfo.cfm">

             <cfinclude template = "act_validatePassword.cfm">    

                            

             <cfif validatePassword is Success>       

                  <cfinclude template = "qry_sendPassword.cfm">

                  <cfinclude template = "act_sendPassword.cfm"> 

                  <cfinclude template = "dsp_sendPassword.cfm">                        

             </cfif>

 </cfcase>

 

just a thought....and as for passing form variables, the core file will create a structure called attributes and populate that with the values from the form, so whether your posting or getting the form you can refer to a variable in the receiving page as attributes.somevariable or attributes.someothervariable.

 

as for layouts, each circuit can use it's own layout so you can 'nest' layouts within an application - i'll let a layout guru expand on that though :)

 

jb.

-----Original Message-----
From: Schweitzer,Dan [mailto:[EMAIL PROTECTED]]
Sent: 10 April 2002 15:53
To: [EMAIL PROTECTED]
Subject: RE: Another newbie question

Also,

 

Can you have multiple layouts in a circuit?

How do you pass variables from one fuseaction to the next and circuit?

 

i.e.

            <cfcase value="validatePassword">

                        <cfset XFA.success = "home.sendPassword">

                        <cfset XFA.Efailure = "home.EFailure">  

                        <cfinclude template = "qry_Passwordinfo.cfm">

                        <cfinclude template = "act_validatePassword.cfm">                                 

            </cfcase>

 

queries user information and I would like to pass that along to SendPassword if the validation is a success.

 

            <cfcase value="SendPassword">           

                        <cfset XFA.Login = "home.login">

                        <cfinclude template = "qry_sendPassword.cfm">

                        <cfinclude template = "act_sendPassword.cfm"> 

                        <cfinclude template = "dsp_sendPassword.cfm">                        

            </cfcase>

 

without having to do a second query in SendPassword ?

 

Dan Schweitzer

Web Content Developer

Enterprise Systems Administration

[EMAIL PROTECTED]

512.438.4365

 

-----Original Message-----
From: Schweitzer,Dan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 9:38 AM
To: [EMAIL PROTECTED]
Subject: RE: Another newbie question

 

Last try I think I got it now.

 

fbxswitch.cfm

Is a circuit?

 

<cfcase value="validateUser">

            <cfset XFA.success = "home.admin">

            <cfset XFA.Pfailure = "home.Pfailure">   

            <cfset XFA.Ufailure = "home.Ufailure">   

 

<cfinclude template = "qry_userinfo.cfm">

Is a fuse?

<cfinclude template = "act_validateUser.cfm">  

Is a fuse?

           

</cfcase>

Is a fuseaction?

 

So fbx.switch is a circuit, cfinclude is a fuse, and cfcase is a fuseaction?

And I only need index.cfm in my home circuit or all circuits?

 

Dan Schweitzer

Web Content Developer

Enterprise Systems Administration

[EMAIL PROTECTED]

512.438.4365

 

-----Original Message-----
From: Lee Borkman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 9:23 AM
To: [EMAIL PROTECTED]
Subject: Re: Another newbie question

 

For those interested, I have made a very rough attempt at a UML class diagram to describe the relationships between Circuits, Fuseactions, etc:
http://bjork.net/index.cfm/fuseaction/content.display/page/architecture.htm

 

 

----- Original Message -----

 

 

No.  Look out, Dan.  John mistyped.  It's the English weather - freezes up the joints.

 

It should be "a Circuit is an application like userManager and a fuseaction would be
addUser, which has one or many fuses."

 

Just remember...

 

App -> Circuit -> Fuseaction -> Fuse

 

LeeBB

----- Original Message -----

 

 

Okay so a Circuit is an application "usermanager" and a fuse would be
"addUser", which has one or many fuseactions.  ...

==^================================================================
This email was sent to: [EMAIL PROTECTED]
 
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bWa8zN
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
==^================================================================
==^================================================================
This email was sent to: [EMAIL PROTECTED]
 
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bWa8zN
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
==^================================================================

_____________________________________________________________________
This message has been checked for all known viruses by UUNET delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.uk.uu.net/products/security/virus/
==^================================================================
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