public interface UiWidget extends UiFeatureMessages, UiFeatureEvent, UiFeatureMode, AttributeWriteHtmlId, AttributeWriteTooltip, AttributeWriteVisibleAdvanced, AttributeWriteEnabled, AttributeWriteStylesAdvanced, AttributeWriteDisposed, AttributeReadModified, AttributeReadAriaRole, AbstractValidatableObject
Native widgetscan be
UiWidgetFactorythat has implementations for all supported toolkits (technically via
UiWidgetFactoryNative). This way you can decide which native toolkit you like to use just by configuration and classpath (See
UiWidgetthat are no longer needed what is generally a good idea. Further for toolkits such as GWT there are strict limitations for the client-side code. The mmm project provides abstraction for various technology specific areas to fill the gaps for you. Use mmm-service for client/server communication and
mmm-client-dialogfor history-management, embedding, etc.
UiWidgetcan only be used once in a client application. Even if you want to have the exact same button twice on the screen you need to create two distinct instances.
UiWidgetand all its sub-interfaces are
|Modifier and Type||Field and Description|
HTML_ATTRIBUTE_ID, ID_SEPARATOR, PROPERTY_ID
PROPERTY_STYLES, STYLE_PATTERN_MULTIPLE, STYLE_PATTERN_SINGLE
|Modifier and Type||Method and Description|
This method gets the
getVisibleFlag, isVisible, setVisible, setVisible
nullif NOT attached to the UI or if this is a root widget (e.g.
UiContext. This is the container with central components for the UI and client infrastructure. E.g. it contains the
widget-factorythat created this
UiWidget. It may be used internally in
UiWidgetimplementations as well as externally to create new
UiWidgets (typically children).
Copyright © 2001–2014 mmm-Team. All rights reserved.