public class HtmlDivLayout extends HtmlLayout
| Constructor and Description |
|---|
HtmlDivLayout() |
| Modifier and Type | Method and Description |
|---|---|
void |
layoutWidget(StaticXmlWidget widget,
String elementName,
Map<String,String> attributes,
StaticXmlWidget container,
StaticHtmlMetawidget metawidget)
Layout the given widget within the given container, using the given
elementName and attributes as a guide and the given Metawidget to access
additional services if needed (such as state saving)
|
createLabel, getWidgetId, layoutLabelpublic void layoutWidget(StaticXmlWidget widget, String elementName, Map<String,String> attributes, StaticXmlWidget container, StaticHtmlMetawidget metawidget)
LayoutlayoutWidget is called immediately after WidgetBuilder.buildWidget and WidgetProcessor.processWidget, and before the next widget is generated. An alternate design would be to 'collect' all widgets generated by buildWidget and processWidget, then iterate over them separately for the layout. If you prefer this approach, you can simulate it by having layoutWidget do nothing but 'remember' each widget, then iterate over them in endContainerLayout (see the AdvancedLayout interface). However not all UI frameworks allow this approach, because they do not suport widgets being instantiated independent of a layout, nor moved between layouts (e.g. SWT)
widget - the widget to layout. Never nullelementName - XML node name of the business field. Typically 'entity',
'property' or 'action'. Never nullattributes - attributes of the widget to layout. Never null. This Map is
modifiable - changes will be passed to subsequent
WidgetProcessors and Layoutscontainer - the container to add to. This is often the same as the given
Metawidgetmetawidget - the Metawidget to use to access additional services. Never
nullCopyright © 2015. All Rights Reserved.