Differences between revisions 13 and 15 (spanning 2 versions)
Revision 13 as of 2016-03-23 13:06:06
Size: 1357
Editor: cox
Comment:
Revision 15 as of 2016-03-23 13:07:45
Size: 1303
Editor: cox
Comment:
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:

Line 36: Line 34:
The "purpose" should provide a what or how this object will be used.
Line 38: Line 35:
=== Other Types === The "purpose" should provide a what or how this object will be used.

=== Other Types (SQL / Results) ===
Examples: sql_main_ChrtEnrl (an SQL variable to drive an enrollment chart on form Main … etc)

Examples: res_main_MC_AllEnrolled, res_contacts_OLAP_DonatePctTarget
Line 41: Line 44:
SQL variables: Examples: sql_main_ChrtEnrl (an SQL variable to drive an enrollment chart on form Main … etc)

Results (from an on-screen multi-column or OLAP): Examples: res_main_MC_AllEnrolled, res_contacts_OLAP_DonatePctTarget

Argos Naming Conventions

General Rules

General Forumla: [form]_[type]_[purpose]

Casing: Camel case (modified)

  • No spaces are allowed in variable names.
  • An underscore is used to separate words when naming.

Forms

Examples: main, contacts, charts

Types

Examples: main_LB_Degrees, main_DD_CurrTerm

  • BT (Button)
  • CB (Check Box)
  • CH (Chart)
  • DD (Drop Down List Box)
  • DT (Date Entry)
  • EB (Edit Box)
  • LB (List Box)
  • MB (Memo Box)
  • MC (Multi-Column List Box)
  • RB (Radio Button)

Purpose

Examples: sql_main_GetStudentID, main_DD_CurrTerm, main_LB_Donors

The "purpose" should provide a what or how this object will be used.

Other Types (SQL / Results)

Examples: sql_main_ChrtEnrl (an SQL variable to drive an enrollment chart on form Main … etc)

Examples: res_main_MC_AllEnrolled, res_contacts_OLAP_DonatePctTarget

Some variables are outside of the Form. With these, we prefix them with the External Type first. sql (SQL) res (Results)