cfflush & fusebox

Has anyone else noticed that the cfflush tag is completely useless if you use the fusebox layout method? ... I'm working on an application that was built by some other folks in fb2 ( though the same would apply if it were fb3 ) and they asked me to add an "ALL" button to a page which uses pagination... but because the potential exists that the contents of the page could be inordinately large ...  ( thousands of results in the list query, with a gratuitous amount of cf code for each result ) , it may not be feasible to display the page without flushing the output buffer ... but cfflush can't be used inside of a <cfsavecontent> or <cf_bodycontent> tag, which is where the fusebox layout would necessitate it being, and even if it could, it would either display the content above the top of the layout (where it shouldn't be) or would display nothing at all until the page finished loading anyway, which was the problem necessitating the cfflush solution ... so my options are to leave it alone and risk things blowing up because impatient users continually hit the refresh button before the page finishes loading, or tediously extricate the content from the fusebox architecture and then have to maintain it separately... <sigh> ... this is very frustrating... Hey Hal, any thoughts on a revision to the fb3 suggested specification for layouts? Isaac Dealey New Epoch www.turnkey.to 954-776-0046

Yes, Issac, we're working on that. For the record, it's not just Fusebox; it's any code that uses <cfsavecontent>. But we've got some ideas brewing... Has anyone else noticed that the cfflush tag is completely useless if you use the fusebox layout method? ... I'm working on an application that was built by some other folks in fb2 ( though the same would apply if it were fb3 ) and they asked me to add an "ALL" button to a page which uses pagination... but because the potential exists that the contents of the page could be inordinately large ...  ( thousands of results in the list query, with a gratuitous amount of cf code for each result ) , it may not be feasible to display the page without flushing the output buffer ... but cfflush can't be used inside of a <cfsavecontent> or <cf_bodycontent> tag, which is where the fusebox layout would necessitate it being, and even if it could, it would either display the content above the top of the layout (where it shouldn't be) or would display nothing at all until the page finished loading anyway, which was the problem necessitating the cfflush solution ... so my options are to leave it alone and risk things blowing up because impatient users continually hit the refresh button before the page finishes loading, or tediously extricate the content from the fusebox architecture and then have to maintain it separately... <sigh> ... this is very frustrating... Hey Hal, any thoughts on a revision to the fb3 suggested specification for layouts? Isaac Dealey New Epoch www.turnkey.to 954-776-0046

> Yes, Issac, we're working on that. For the record, it's > not just Fusebox; it's any code that uses <cfsavecontent>. > But we've got some ideas brewing... Hey Hal, Yea, I know it's not _just_ fusebox... Sorry about that, I really didn't mean it to sound antagonistic... I was just really frustrated earlier today. :) My first thinking on the subject was something like this: <cfinclude template="#layoutdir#/#layoutfile#"> <cfinclude template="#circuits[fusebox.thiscircuit]#/fbx_switch.cfm"> <cfinclude template="#layoutdir#/#layoutfile#"> ... admittedly, you still have to check for the length of the layoutfile variable and of course, redo the loops to account for nested layouts, however, the advantage is that this would keep the layouts in a single file ( one of the big advantages to the current method over the more common _header.cfm and _footer.cfm files I see in non-cf apps ) and all the people who are using fb layout files currently can convert to this with a _BARE_MINIMUM_ of effort. :) A layout file like this: <table ...> <tr><td>   #fusebox.layout# </td></tr> </table> Would simply become <cfif fusebox.layoutmode is "start">   <table ...>   <tr><td> <cfelse>   </td></tr>   </table> </cfif> As a matter of fact, some developers who are particularly good with regular expressions may be able to convert layouts for an entire app with a single multi-file REReplace in CF Studio! :) I started looking at converting on of my own apps to use this structure, but just didn't have the time to really disect the existing core files... Isaac www.turnkey.to 954-776-0046