T

In Mobile Application, there is general guidelines for UI design regarding collecting information from users. This applies to collecting both attributes from a Feature and other user inputs in a more general sense. Information is normally organized by Groups, with each Group presenting certain information. Technically, each Group contains a collection of items. For example, when user edits attributes for a newly collected Feature, each column is presented on the Page as a Group. And each Group may have a header Item (i.e., column name), and a value Item (i.e, the value of the field). When the Group is tapped, the application would navigate user to a new page/dialog for providing a new value. If the column is of text type, the new page/dialog may contain a TextBox with SIP enabled. If the column is numeric, the new page/dialog may show a TextBox with customized a numeric keypad.

In fact, the application framework has provided a set of Groups that you can use with minimum programming efforts. Depending on different data type, you can choose to use one of the folowing groups: StringAttributeGroup, DateAttributeGroup, EnumAttributeGroup, NumericAttributeGroup, RadioGroup, SelectionGroup, etc.

If you want to show user a read-only group, use ReadOnlyAttributeGroup.

Group should be used with GroupView.

System.Object
   ESRI.ArcGIS.Mobile.Client.Controls.Groups.Group
      ESRI.ArcGIS.Mobile.Client.Controls.Groups.Group

Reference