ARSObjectNames
From ARSWiki
The first thing in programming is generally a "Hello World" program. Well, in ARS that is not exactly where I think you should start.
I tend to think the most basic thing(object) in ARS is really an ARS field. While some people might not describe an ARS field as an "ARS Object" I tend to think that the field is the most important one!
So as it is the most important ARS object, let us talk about how we name and use them.
A field has a few names. However a field's most basic name is actually a number. :) Specifically this name is better know as an ARS fieldID. There are rules for ARS fieldID values too, but for now we can skip those details. At this point the important thing to know about fieldID's is that once a fieldID is set, it really should not be changed. (As of v7, it can not be changed without external tools.) So in my book, an ARS fieldID is the most primary name in ARS. Also a fieldID is unique in the scope of the Form that contains the field. However, as I mentioned a field has a few names so on to it's other names. It's secondary "primary" name is its database name. This is a string name that is also unique to the ARS form object that contains the field. A given fieldID/database name can be (and should be!) reused on other forms. Next there are a set of optional Field Labels, one for every Form View that this field exists on. I know that all might seem confusing right now, but it really is easy. As a developer your focus is on the fieldID and database name for the field. The labels are really for ARS "Users" and rarely are actually part of any ARS design patterns. To use programming speak for a second, an ARS field is as close to a variable as it comes in ARS. (Which is also why I think it is the most basic part of ARS Objects.)
Now it is important, like in any programming language, to reuse variables, and to keep track of what purpose each variable is designed for. This is where field names start to become important, but it is realy just the tip of the Object Oriented(OO) iceberg. If you can be consistent about how you name/group/use each and every field then you can start to build up sets of fields that work together (with ARS workflow) to fullfill a specific function. A collection of similar functions that work together to fulfull a larger purpose and we call that an ARS Form. :)
More on this later.. time for me to go to bed. :)
Like some programming languages ARS variables are typed or specific to a single type of data. ARS even has concepts for "tempory" variables, but ARS referese to them as "display only".
