Hmm... I kinda like that! This seems like something you could translate
pretty easily to a PHP-fusebox class, too:
$Fusebox= new Fusebox;
$Fusebox->open();
switch($fuseaction) {
case "list":
include("qry_getList.php");
include("dsp_viewList.php");
break;
[etc...]
}
$Fusebox->close();
Issues I forsee are thinkgs like portability-- making sure the location of
the app_globals, etc. is one of the attributes of the tag/class, so if you
have to move an app to a deeper location in the larger app, you can still
tell the fusebox where it is in relation to the app_globals, app_layout,
etc.
I'll see what I can come up with in PHP, and you keep us posted on your CF
version...
David Huyck
[EMAIL PROTECTED]
> I'm considering adopting a new tag to encapsulate
> all the code that goes into EVERY fusebox app.
>
> <cf_fusebox defaultFuseaction="list" header="dsp_header.cfm"
> footer="dsp_footer.cfm">
> <cfcase value="list">
> <cfinclude template="qry_getList">
> <cfinclude template="dsp_viewList">
> </cfcase>
> <cfcase value="view">
> <cfinclude template="qry_getItem">
> <cfinclude template="dsp_viewItem">
> </cfcase>
> </cf_fusebox>
>
> The cf_fusebox tag would include references to
> the app_ files, the formURL2Attributes code,
> the <cf_bodycontent> code, and the <cfswitch>
> tags (including <cfdefaultcase>), and
> whatever else normally goes into a fusebox
> file.
>
> Suggestions? Comments?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
