Thank you, the problem turned out to be the debug at
the begining of the frameset and in my
application.cfm. Apparently IE5.5 won't render the
html correctly if you have anything that is not a
regular <!--comment--> before it. I fixed the fuses to
all point back to index also.
Andrew
--- David Huyck <[EMAIL PROTECTED]> wrote:
> Your url would read index.cfm?fuseaction=frameset,
> and your "frameset" case
> statement would have a dsp_frameset.cfm file in it.
> Then in the
> dsp_frameset.cfm file you'd have your <frame
> src="index.cfm?fuseaction=menu"> and <frame
> src="index.cfm?fuseaction=addUpdate">. Next, in
> your "menu" case statement,
> you'd have a dsp_menu.cfm file (plus any act_files
> to set up the menu
> correctly, if needed), and in your "addUpdate" case
> statement, you'd have
> the act_files and qry_files you lined up before to
> get all the necessary
> info into your form.
>
> Are we getting there? The idea in fusebox is that
> everything goes through
> the index.cfm file. You never call the "fuses"
> directly, fuses being the
> dsp_files, act_files, and qry_files (etc.). So in
> fusebox with frames, the
> same idea holds true, but you just have to think
> about each frame as a
> separate document, and therefore a separate call to
> the fusebox (index.cfm).
>
> For more info (if you haven't seen it) go check out
> Nat's Fusebox 'n' Frames
> PowerPoint slideshow...
>
http://www.fusebox.org/Files/presentations/FuseboxandFrames.ppt
>
> David Huyck
> [EMAIL PROTECTED]
>
>
> ----- Original Message -----
> From: "Andrew Middleton" <[EMAIL PROTECTED]>
> To: "Fusebox" <[EMAIL PROTECTED]>
> Sent: Tuesday, April 24, 2001 12:48 PM
> Subject: Re: Frames not showing with Fusebox
>
>
> | Yes that makes sense, but...
> |
> | How would you call all three fuses at the same
> time
> | (ie, one hyperlink sends them to a new frame
> layout)?
> | Or did I miss the point? I tested just creating
> the
> | frameset and still all I get is source code for
> the
> | page, but no display of the html, not even the
> frame
> | borders....
> |
> | Andrew
> | --- David Huyck <[EMAIL PROTECTED]> wrote:
> | > Well, the problem is that you are calling three
> | > different pages, but you are
> | > treating it as one call-- your frameset is
> getting
> | > all the query
> | > information, but the sources of each of the
> frames
> | > is just the EntryMenu.cfm
> | > file and the dsp_AddUpdateBCI.cfm file-- they
> aren't
> | > being called through
> | > the fusebox.
> | >
> | > That's the trick-- even though to the user it
> looks
> | > like one page, it is
> | > really three (1- frameset, 2- menu, 3- form),
> which
> | > means to us Fuseboxers,
> | > that there should be three calls to the fusebox
> | > (index.cfm). What you need
> | > to do is set up a fuseaction for the frameset
> and
> | > one for each frame:
> | > index.cfm?fuseaction=frameset builds the
> frameset;
> | > index.cfm?fuseaction=menu
> | > would populate the left frame with your menu;
> and
> | > index.cfm?fuseaction=addUpdate would populate
> the
> | > middle frame. Then the
> | > <cfcase value="addUpdate"> would contain all the
> | > queries you laid out, plus
> | > the dsp_AddUpdateBCI.cfm file, so it would have
> | > access to those queries
> | > (since they now come from the same request).
> | >
> | > Make sense?
> | > David Huyck
> | > [EMAIL PROTECTED]
> | >
> | >
> | > | Anyone that can explain this would help out
> | > | tremendously.
> | > |
> | > | I have a fusebox app that is pretty simple.
> It is
> | > | basically a bunch of add/update forms. The
> issue
> | > is
> | > | the home fuse is a simple menu at the top of
> the
> | > page,
> | > | once a user clicks on Add or Update, etc. they
> are
> | > | then sent to a frameset with left navigation
> and
> | > the
> | > | form on the right with record navigation
> above. I
> | > am
> | > | using the following code for my index fuse:
> | > |
> | > | <CFCASE value="dsp_AddUpdate">
> | > | <!--- This checks to see if the user is
> running an
> | > | update or insert query and sets the switch
> | > variable
> | > | --->
> | > | <CFIF attributes.CaseID is 0>
> | > | <CFSET NewCase = "Yes">
> | > | <CFELSE>
> | > | <CFSET NewCase = "No">
> | > | </CFIF>
> | > | <!--- Need to pass in caseID and then check
> which
> | > | query to run --->
> | > | <CFIF NewCase IS "No">
> | > | <CFINCLUDE template="qry_PullUpdateBCI.cfm">
> | > | <CFELSE>
> | > | <CFINCLUDE template="qry_PopulateBCI.cfm">
> | > | </CFIF>
> | > | <!--- Includes the frameset which displays
> form
> | > (add
> | > | or update) --->
> | > | <CFINCLUDE template="act_frameset.cfm">
> | > | </CFCASE>
> | > |
> | > | The problem is my frameset runs (I put in a
> debug
> | > line
> | > | at the top which shows), but none of my
> display
> | > pages
> | > | appear. The code for the frameset is below:
> | > |
> | > | the frameset is running
> | > | <frameset cols="185,913*" frameborder="YES"
> | > border="2"
> | > | framespacing="2" rows="*"
> bordercolor="#666666">
> | > | <frame name="leftFrame" scrolling="NO"
> noresize
> | > | src="EntryMenu.cfm">
> | > | <frame name="midFrame"
> | > src="dsp_AddUpdateBCI.cfm">
> | > | </frameset>
> | > | <noframes>
> | > | <body bgcolor="#FFFFFF">
> | > | </body>
> | > | </noframes>
> | > | </html>
> | >
> | >
> | >
> | >
> | >
> |
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
