Still trying to customize a field group with dozens of fields, and still hitting issues. Seen that I’m not the only one with this kind of issue.
If you look at the image below, you see a “comment” field with 4 rows on the second column. No row spanning possible so if you look on the left there is a blank area.
What is sad is that with a grid layout it is possible to span col & row. Plus, you can do cool stuff with a grid layout like drag n drop of fields on line and column. And you can adjust heigth and weight of any component with the mouse.
The more we try to use fieldgroup, the more we think that it will never reach the level of features of grid layout, and these features (span, drag, resize) are not really options in a (aspiring) wysiwyg editor.
I would have a simple advice : why write tons of code in FieldGroup to mimic what grid layout is already doing good ? This race will never end IMHO.
That might be a hefty refactoring, but the visual behavior of FieldGroup should just be the GridLayout genuine code. With some additional code to ensure that all actions like e.g moving a component into another column is restricted to be dropped in the field group area.
We studied how to get rid of field groups everywhere and replace with grid layouts, and it fact there is not no much trouble doing so. The main issue is that when Studio add a component after creating a new entity property it does not give it a meaningful name (eg “textField”), so you cannot inject it properly. I open another ticket for that.