|
The source of event is identified in this field; this
usually involves command or push buttons, images, text boxes, select boxes and
other input items that could be modified, selected, or that could respond to
the click event. The original event source should be shown here. It is
noteworthy, that only events that lead to server side call would be of
interest, Events handled by client script, like JavaScript routines should not
be part of this specification, if they do not contain links or calls to the
server side.
Because event source might propagate multiple events, for proper documentation,
the type of event should be appended to the source name as shown below:
form[categoryForm].element[buttonCancel].click
Without the event types designation, the default is assumed, which would depend
on the source. For images and buttons, that would be the click event.
Beyond the standard HTML elements events, component architecture might
introduce other type of events. The names of these events would normally differ
from client events to avoid ambiguity. The designation of the event type, on
the specific platform, would be used to specify the event. For example, JSF related
events might show like these.
form[categoryForm].element[itemSelect].change
form[categoryForm].element[itemSelect].action
This field allows the quick identification of all page elements that could
trigger events that would demand services from the server.
Page Event
Apart from the event sources on the page, the page could be
associated with events. The exclamation mark "!" is used to represent a page as
the source of the events. There might be specific events, like "!.pageLoad", provided
on specific platforms. There are also events that must occur before the page
load; page designation without the specific event type would imply antecedent
page events.
|
Technologies
