Currently MultiFormView uses VerticalLayout so as to make it look better in certain contexts

• e.g. narrow choose audience dialog in pages app to allow trait fields to expand through whole row,

but it makes more sense to have it as FormLayout in other

• e.g. Persona app traits tab to achieve horizontal alignment of fields.

We can imagine that in certain cases it might be beneficial to be able to layout the entry components as e.g. tiles/columns etc.

All that speaks for adopting the layout producer concept introduced for the general form view. Not to mention that doing so will increase consistency and predictability among different form implementations.

High-level steps to accomplish:

• consider changes to MultiFormView definition
• extract layouting logic into a dedicated layout producer.
• consider potential problems or handling move/delete actions (may require additional API to be added directly to MultiFormView).
• consider 1-2 alternative layout producer impls