net.sf.mmm.client.ui.api.handler.action

Interface UiHandlerAction

All Superinterfaces:

UiHandler

All Known Subinterfaces:

UiHandlerActionApply, UiHandlerActionApprove, UiHandlerActionCancel, UiHandlerActionClose, UiHandlerActionConfirm, UiHandlerActionDelete, UiHandlerActionDown, UiHandlerActionNext, UiHandlerActionOpen, UiHandlerActionPrevious, UiHandlerActionPreviousNext, UiHandlerActionRemove, UiHandlerActionSave, UiHandlerActionStartEdit, UiHandlerActionStopEdit, UiHandlerActionSubmit, UiHandlerActionUp

All Known Implementing Classes:

UiWidgetCustomEditor.UiHandler

public interface UiHandlerAction
extends UiHandler

This is the marker interface for a UiHandler of a specific action. The action is invoked by a triggering widget, typically a button. It takes the UiEvent (will be e.g. an instance of UiEventClick) as a single argument. Therefore a UiHandlerAction can be used to create a triggering widget (typically a button) with all its aspects (label with NLS, icon, tooltip) to make your life easier. Further these aspects can be maintained at a single place in the code and allows a consistent user experience throughout your entire application.
Most action handlers have a corresponding UiHandlerObject. Typically an action triggering UI element like a button itself does not know the object on which the action is invoked and therefore calls a UiHandlerAction without any data. This is implemented by some higher level place that knows how to get the data corresponding data from the view. With this data it delegates to the UiHandlerObject that may invoke a remote service to save, delete, or perform whatever operation with this object.

Since:

1.0.0

Author:

Joerg Hohwiller (hohwille at users.sourceforge.net)