Adam, we've kept the original naming (plus expansions). If you get so many
that you need to quickly identify all the functionality for a specific area,
then you can as easily use circuit apps. In fact it makes more logical sense
to do that. The naming convention of the files only have meaning in the
context of the *non*-programmer functionality--ie coming into a project
late, or porting off all the DSP's to a graphic designer for additional
work, or passing all the QRY's over to a DB guy , etc. In all these cases,
having prefixed the DSP, QRY, ACT, etc. names makes identification much
easier.
Further, using that notation, at least for me, seems to help preserve the
[FUNCTION]_[VERB][NOUN] format which again just helps standardize your
coding practices.
here is one thing to do perhaps what you would like but still keep the
advanatages of the Function_ file naming: try doing :
[function]_[noun][verb] that way all the code touching a particular
functionality is identified directly after the underscore. It will be easy
for a human to see when scanning a DIR, and easy for a program to parse ,
etc.
----- Original Message -----
From: "Reynolds, Adam" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Monday, October 09, 2000 12:28 PM
Subject: Naming conventions
> Anybody else moved the dsp/act/qry prefixes to the end of the filenames?
> This is making our 'identify all the functionality for a specific area'
> excericse far simpler...ie.
>
> stock_list_dsp.cfm
> stock_insert_act.cfm
>
>
> etc....
>
> Adam
> **********************************************************************
> This email and any attachments are confidential and solely
> for the use of the intended recipient. They may contain
> material protected by legal professional or other privilege.
> If you are not the intended recipient or the person responsible
> for delivering to the intended recipient, you are not authorised
> to and must not disclose, copy, distribute or retain this email
> or its attachments. Although this email and its attachments
> are believed to be free of any virus or other defect, it is the
> responsibility of the recipient to ensure that they are virus free
> and no responsibility is accepted by the company for any
> loss or damage arising from receipt or use thereof.
>
> **********************************************************************
> --------------------------------------------------------------------------
----
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
