Yeah I concur go back to the fusebox
1.action="index.cfm?fuseaction=pagerouter&function=input"
2.action="index.cfm?fuseaction=pagerouter&function=output"
This will keep your code simple and modular.
It will be easy to tell what pagerouter does. Also, you will be able to
edit the input and output in the same template. This has proven to be very
valuable months later when something needs to be maintained.
John Anderson
http://www.aloha-webdesign.com
-----Original Message-----
From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2001 1:22 PM
To: Fusebox
Subject: Re: A single fuse or two
Gary that's not an "either-or" question. The answer, instead, is "yes" and
"yes". yes, you go back to the Fusebox, and "yes" you call the same page
again --because the page called *was* the fusebox :)
That's not a smart-ass answer, that really is the core idea--that everything
gets pointed to a fusebox . how did the FORM page load? It called the
fusebox and its fuseaction included code for the FORM. How does the ACTION
page of the FORM get called? It calls the fusebox and its fuseaction
includes code for the ACTION page. in short, your FORM should have
<form action="index.cfm?fuseaction=actionfuse" method="post"> or the
functional equivalent
(the except being any custom tags you might be using)
----- Original Message -----
From: "Gary Morin" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Monday, March 05, 2001 1:26 PM
Subject: RE: A single fuse or two
> Sure, when submitting the form after input do you go back to the Fusebox,
or
> do you just call the same page again with the variable set to 'output'.
>
> I know it can easily be done, I just trying to do it the Fusebox way.
>
> Gary Morin
>
> KeyGIS Limited
> Tel: +44 (0)1604 891152
> Fax: +44 (0)1604 891164
> www.keygis.co.uk
> [EMAIL PROTECTED]
>
> -----Original Message-----
> From: John Anderson [mailto:[EMAIL PROTECTED]]
> Sent: 05 March 2001 17:57
> To: Fusebox
> Subject: RE: A single fuse or two
>
> You could just set up one fuse and one template to do the whole thing.
>
> I have done this before in my apps:
>
> ie : fuseaction="pagerouter"
>
> Your pagerouter template can be set up to expect a variable for its
> particular action.
> either 'input'-(I need to take a property from a client side ActiveX) or
> 'output'-(use it in a Query to populate a
> display page.)
>
> This can all be done in the same template ("act_pagerouter") and
fuseaction
> "pagerouter".
>
> Hope this helps,
> John Anderson
> http://www.aloha-webdesign.com
>
>
>
> -----Original Message-----
> From: Gary Morin [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 05, 2001 1:05 AM
> To: Fusebox
> Subject: A single fuse or two
>
>
> I'm slowly getting to grip with Fusebox, but I still get a bit confuse on
> how much to put in a single fuse.
>
> For instance, take the following example.
>
> When a user selects a hyperlink or on initial entry to page, I need to
take
> a property from a client side ActiveX, and use it in a Query to populate a
> display page.
>
> So my logic would be, to use JavaScript to set a hidden form variable to
> the ActiveX property and to do a .submit() to automatically submit the
form.
> Then with the form results do a query and display the results
>
> So my question is should this be done in one fuse or two? I guess it
should
> be two, the first uses JavaScript to set the hidden form variable and to
> automatically submit the form with its action being the second Fuse, which
> queries and displays the results.
>
> But the two fuses will always go together so it complicates matters having
> two fuses.
>
> Cheers
>
> Gary
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
