Resolution: Won't Fix
Affects Version/s: None
Fix Version/s: Not version specific
Security Level: Public (Public: Anyone can view)
KULRICE-12607 Table Layout in KRAD Library broken KULRICE-7888 Css box layout classes are appearing more than once in items of a collection KULRICE-9956 Table Layouts - MultiRow bombs out to exception report KULRICE-11685 Improve grid layout responsiveness and configuration KULRICE-9652 Add layout & grid classes to UIF KULRICE-7589 applyDefaultCellWidths property on table layout manager is not working properly KULRICE-13271 Item Css demo is not working in Box Layout Manager demo KULRICE-8409 Same height box layout support for Horizontal box layouts KULRICE-8420 Horizontal layout does not work within a collection item KULRICE-4725 Provide more default layout options and ability to specify custom layout
KAI Review Status:Not Required
KTI Review Status:Not Required
Currently in order for layout properties to be specified on group items they must be added to component base. This is confusing (and bad design) since they properties only apply when that layout manager is applied.
Instead we can introduce a nested property of ComponentBase that will be of type LayoutItemOptions. The concrete subclass will be created by calling the layout manager getLayoutItemOptions method for the layout manager defined on a group. This will happen during the bean post processing.
The concrete subclass will be:
Properties will then be specified in the XML with layoutItemOptions.colSpan (for nested) or by the nested bean (in which case the correct parent must be selected):
<property name="colSpan" value="2"/>