Defines a layout area to group other layout elements together.
GROUP item basics
A GROUP form item type groups other form items together,
typically in a groupbox widget.
Defining an GROUP
The
GROUP form item typically gets a
TEXT attribute, to
define the title of the group. Consider using
localized strings for this
attribute:
GROUP ...
TEXT=%"customer.info";
Note: Some front-ends render group containers as a groupbox widget, displaying a title
on the top of the child elements, while other front-ends may not show a group title.
Consider identifying group elements with a name, in order to manipulate the group
during program execution. For example use the
ui.Form.setElementHidden() method to hide or show groups in a
form:
GROUP g1: g_cust_info, ... ; -- grid-based layout
GROUP g_cust_info, ... ; -- stack-based layout
Some front-ends support different presentation and behavior options, which can be
controlled by a STYLE attribute. For more details, see Common style attributes.
Groups in grid-based layout
In a LAYOUT tree with GROUP
containers, if you want to include several children in a
GROUP, you can add a VBOX or HBOX
into the GROUP, to define how these form items are aligned.
Note: When defining a
GROUP container, you cannot set the
GRIDCHILDRENINPARENT attribute. This attribute makes
sense only for a group item defined with a layout tag contained in a
GRID area.
Consider using a group layout tag inside a
GRID container, this
layout specification technique is often more appropriate to define
forms:
GRID
{
<G g1 ><G g2 >
[l1 :f1 ][f4 ]
...
<G g3 >
...
Groups in stack-based layout
In a STACK container, GROUP form items are
one of the base concepts used to put stack items together. For more details see Stacked group rendering.
Groups on mobile devices
On mobile devices, groups render according to the platform standards:
- With GMA/Androidâ„¢, groups are visualized
by a simple separator under the group title. Complex layout construction is
supported: groups in groups, groups in a grid, and so on.
- With GMI/iOS, the layout is limited by the platform GUI standards. The only
visible grouping container element is a group. Groups within groups are not
allowed. GMI enforces each form item as a member in a group. There can be group
headers and footers, but no elements in between groups.