> > from the core files.
>
> It's still all driven through index.cfm isn't it? With other templates
> using <cfinclude> to wrap/mask the index.cfm?
No, not necessarily. I've got a couple apps that are controlled via other
templates (i.e. index.cfm is non-fusebox, and templateXYZ.cfm is a fusebox
root), and a couple that run via custom tags (i.e. the entire application is
in a custom tag directory, and the root file is the custom tag itself). For
"normal" apps, 'index.cfm' is specified via the default document setting in
your web server, not the framework. If you do want to consider it a forced
template, then it applies to both FBs and Mach-II as well.
> > The XML files have fixed names (which can be .xml or
> > .xml.cfm, you only list
> > the latter, btw), but there are no code files that have
> > fixed names.
>
> Doesn't every framework require some template(s) with fixed names? One
> at least...
The core files have fixed names. Plugins have to be in a certain directory
in relation to the core files ("./plugins"). fusebox.xml has to be in the
same directory as the core files. Other than that, you can literally
sprinkle whatever you want, wherever you want, as long as it can be reached
from a relative path from the directory the core files reside in.
Cheers,
barneyb
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
