Since we can output fieldgroups as a div, they can serve as containers to create a multi column layout if the right css is made available. Create nice forms or layouts for easy positioning of elements of a node, user etc. in any view mode (build mode in Drupal 6).

The solution lies in the #region key available in the form and which module will make use of it. There is even a chance that #regions is not even needed at all and can be ditched completely. In this case we could talk about regions as "static fieldgroups" where static means "level0" and "fixed in sorting".

This could lead to a change in the name of this module to something more abstract like "Group", although "Group" implies that we are planning to group not only fields ... but for instance blocks, views or nodes and that is not the case. So in my opionion we still should have "group" and we need "fields". A group is not a field, and a region is not a field, however a region can be a "group type".

Comments

Stalski’s picture

The original blog post can be found here: http://realize.be/state-fieldgroup-module-drupal-7

Stalski’s picture

Version: » 7.x-1.x-dev
Status: Active » Closed (fixed)

The choice has been made to have Display suite work with real regions and not field_group static groups. No dependency is achieved by this and that can only be a good thing. Field group will only group fields with attention to display.