I have seen fse_ for special "fuse" files that combine act, qry and dsp, I
have also seen ctl_ files for circuit controller files (files that help
control a circuit adapt to its parent site when first created stand alone).
I have frm_, err_ and scr_ (script) files as well. As Mr. Helms has pointed
out repeatedly, call 'em what you want. In the long run, all fusebox'ers
have a common base from which they work. If I tell you I am in an action
file doing some "thing" you will know what I mean...and it won't matter if I
use "act" or "act_" or "action_" for the naming convention.
Be warned, however, that if you change those "default" names or add others,
you will not be able to expect help based on your new terminology
alone...you will often need to supply additional explanation. Sometimes
added file naming conventions can really help organize your thoughts and
logic a lot better.
Another good example are action files that perform updates, inserts and
deletes. If you are going to use an "act" or "actions" directory, isn't it
redundant to name those files with the same prefix? Why not use names that
standardize on the root functionality of the file...like upd_, ins_,
del_...or when multiple query actions happen use something like ctl_ or cmb_
for control or combination queries. The same could be said for the other
directories as well.
Neither way is wrong and either way can be right. Just remember, you can
keep calling it an apple as long as no one sees its an orange. Was that a
really crappy made up addage?
Mike Craig
-----Original Message-----
From: Ken Beard [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 7:45 PM
To: Fusebox
Subject: file naming convention (don't shoot!)
I REALLY REALLY don't want to start a war here, I'd just like to HEAR what
other people PREFER TO DO THEMSELVES....
I realize that the standard is act,qry and dsp files.. but I'm thinking in
the particular case of the company I work for, we might want to create some
additional prefixes such as:
1. err_ (form validation)
2. lgc_ (business logic.. to get this out of the act_ files)
those i'm pretty sure we're going to use, but i wonder if there are others
that might be useful..
anybody out there like to have a different prefix for files that reference
stored procedures as opposed to having a normal cfquery in them?
thanks for the nfo & suggestions as always.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
