Naming Conventions: Filenames & Code Needed ASAP

[xcelguy]

I am starting a new project, and I want to be correct in naming conventions.
Anyone know what PROGRESS recommends for file names and coding .

file names:
found these

[FONT=&quot]If a filename begins with...[/FONT]​

[FONT=&quot]Then the file is a...[/FONT]​

[FONT=&quot]b[/FONT]​

[FONT=&quot]SmartDataBrowser[/FONT]​

[FONT=&quot]d[/FONT]​

[FONT=&quot]SmartDataObject[/FONT]​

[FONT=&quot]f[/FONT]​

[FONT=&quot]SmartFrame[/FONT]​

[FONT=&quot]g[/FONT]​

[FONT=&quot]SmartDialog[/FONT]​

[FONT=&quot]p[/FONT]​

[FONT=&quot]SmartPanel[/FONT]​

[FONT=&quot]sbo[/FONT]​

[FONT=&quot]SmartBusinessObject[/FONT]​

[FONT=&quot]smr[/FONT]​

[FONT=&quot]Smart[Message]Receiver[/FONT]​

[FONT=&quot]sms[/FONT]​

[FONT=&quot]Smart[Message]Sender[/FONT]​

[FONT=&quot]ob[/FONT]​

[FONT=&quot]SmartObject[/FONT]​

[FONT=&quot]sbb[/FONT]​

[FONT=&quot]SmartB2BObject[/FONT]​

[FONT=&quot]sdf[/FONT]​

[FONT=&quot]SmartDataField[/FONT]​

[FONT=&quot]v[/FONT]​

[FONT=&quot]SmartDataViewer[/FONT]​

[FONT=&quot]w[/FONT]​

[FONT=&quot]SmartWindow[/FONT][FONT=&quot][/FONT]​

[FONT=&quot]ws[/FONT]​

[FONT=&quot]StandardWindow[/FONT]​

[FONT=&quot]gs[/FONT]​

[FONT=&quot]StandardDialog[/FONT]​

But i am looking for these also

what about coding:
variables start with v- ?
browse widget - b ?
temp table -
query -
combo box
selection list
button
etc etc.

What about tables/fields?

some one please help.

Thank you

 

[joey.jeremiah]

besides the very basic, word separators, that -

progress reserved words use hyphens ( - )

databases tables and fields use underscores ( _ )
hyphens are out of the question here
because they're not compatible with sql, java and others

and code ( variables, procedures, functions etc. )
use capital letters ( MixedCase )

the idea ofcourse is to distinguish between them
e.g. that a field name won't conflict with a reserved word in the future


i personally work on dynamics so i use the dynamic conventions
it also saved me the decision

it's a very complete and well thought out convention
of course it has it's ups and downs like everything else

in general the names tend to be very long
but they are also very clear and understandable
even if you didn't write them, the opposite of technical


you can find some of them in
the progress dynamics basic development \ database design principles \ entity naming conventions

and some are dispersed thru the doc


there was a recent thread on the topic of standards
i would also add to Chris Schreiber interesting article

Scott Auge wiki @amduus.com

 

[mpowell_esq]

OLD Method / confuse comipler

Greetings,

The example you have just given for variable names, using eg i_num/i-num is rather an old methodology. Using underscores , and or hyphens (dashes) is a rather outdated method. This method caused / causes problems with compilers, reading them as mathamatical symbols / functions. The new convention is to mix case. You will notice that with Progress OpenEdge 10, the trend is to mix the case of names, to make the syntax more readable. For example, iCustNum / iProductCode ...
Progress with Progress OpenEdge.

 

[Lee Curzon]

Greetings,

The example you have just given for variable names, using eg i_num/i-num is rather an old methodology. Using underscores , and or hyphens (dashes) is a rather outdated method. This method caused / causes problems with compilers, reading them as mathamatical symbols / functions. The new convention is to mix case. You will notice that with Progress OpenEdge 10, the trend is to mix the case of names, to make the syntax more readable. For example, iCustNum / iProductCode ...
Progress with Progress OpenEdge.

We generally use camelCase here, and it is the norm in my experience for 'normal' variables. I wouldn't say I feel particularly strongly that it should be a standard - it's an individual (company) choice. It's certainly not a new development.

If there is a problem with characters in tables as regards SQL, then they shouldn't be used; but the big advantage of using (say) hyphens is that they make searching code for table/field name elements easier.

I've never had any problem with the Progress compiler being tripped up by characters as you suggest, as mathematical operators need to be seperated by spaces.

I would suggest using conventions that are industry standard for the OS you use - eg. there are pointers to MS preferred standards on the web. After that, I would look at how SQL programmers converge for table naming. I would leave Progress standards to code that can be considered 'Progress only' - but this is just a personal opinion.