Well, I've been using frameworks since Fusebox 2 came out, so I still
tend to follow generic CF framework conventions, if you can call them that.
* display a message, a menu, or data: dsp.user.cfm, and depending on
the framework, all displays probably go in a /views subfolder;
there may be a /views folder for each module if it's a complex
application; even if it's a long template, it's all in one file, I
would find it highly inefficient to have to hunt around across
multiple files for all the output that makes up a single page,
excluding headers, footers, nav, and other site-wide or
module-wide wrappers, which are generally site-level includes or
wrapper templates
* display a form for data entry or editing: frm.user.cfm, again
usually in the proper /views subfolder
* for years now I've used event-driven MVC style frameworks, so I
use index.cfm as the front side controller: there is generally a
site-level one and then another in each module, and the index.cfm
files take care of handling the request and marshalling the
necessary CFCs and views
* CFCs are then used to handle all sorts of things: utility methods
I tend to put in a root /components/Util.cfc or something like
that and utilities as well as any singleton (yes, I know other
languages don't mean the same thing, but I'm talking about the
quasi-accepted CF 'singleton' here) CFCs are generally loaded into
the application scope, whether by Application.cfc or by individual
controllers; these generally go into /com subfolders
* CFCs that are more like objects, such as file formatters or true
classes (properties + methods, instances are not singletons and
may be passed around within the application), I generally put into
a /model subfolder, mostly just to distinguish them from the
application-scope components
This type of arrangement allows me, for example, to have a root-level
index.cfm simply include the index.cfm of another module and voila, the
whole module is available to the application. It's well organized in
terms of having to show other developers around the application, and it
makes the separation of concerns nice and clear, in my opinion. YMMV
On 11/15/2010 5:13 PM, Paul Alkema wrote:
> Thanks for your feedback. You make some good points.
>
> Does anyone out there have any written coding standards or coding
> documentation that they would be willing to share? I would be interested in
> seeing what other development teams use as far as coding standards.
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:339248
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
