1352
Comment:
|
1347
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
Line 6: | Line 5: |
Line 10: | Line 8: |
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. |
General Forumla: ['''form''']_['''type''']_['''purpose'''] |
Line 15: | Line 10: |
=== Forms === Forms: Examples: main, contacts, charts |
Casing: Camel case (modified) |
Line 19: | Line 12: |
=== Types === Types (GUI Elements): 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 === The "purpose" should provide a what or how this object will be used. Examples: sql_main_GetStudentID, main_DD_CurrTerm, main_LB_Donors === Other Types === Some variables are outside of the Form. With these, we prefix them with the External Type first. sql (SQL) res (Results) 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 |
* No spaces are allowed in variable names. * An underscore is used to separate words when naming. |
Line 52: | Line 17: |
=== Forms === Forms: Examples: main, contacts, charts === Types === Types (GUI Elements): 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 === The "purpose" should provide a what or how this object will be used. Examples: sql_main_GetStudentID, main_DD_CurrTerm, main_LB_Donors === Other Types === Some variables are outside of the Form. With these, we prefix them with the External Type first. sql (SQL) res (Results) 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
Contents
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
Forms: Examples: main, contacts, charts
Types
Types (GUI Elements): 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
The "purpose" should provide a what or how this object will be used. Examples: sql_main_GetStudentID, main_DD_CurrTerm, main_LB_Donors
Other Types
Some variables are outside of the Form. With these, we prefix them with the External Type first. sql (SQL) res (Results)
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