Changes between Version 2 and Version 3 of CoreLibrary/EventCore

Timestamp:

10/01/12 13:26:15 (12 years ago)

Author:

sherbold

Comment:

--

CoreLibrary/EventCore

@@ -7 +7 @@
 Since GUIs (both on Desktops and the form of Websites) are one of the main targets of quality assurance tools for event-driven software, the Event Core component also defines generalizations of the '''{{{IEventType}}}''' and '''{{{IEventTarget}}}''' interfaces that build the foundation to describe events of GUI applications. 
 
+For the event types, the basic interactions with users through common Human-Computer-Interfaces are defined, i.e., for mouse and keyboard interactions. All of the interactions implement a common interface '''{{{IInteraction}}}'''. If additional GUI interactions are implemented as !EventBench plug-ins, they should also implement the '''{{{IInteraction}}}''' interface. 
 [[Image(EventTypes.png, nolink, align=center)]]
+Furthermore, the event core provides a couple of tools to enhance sequences of these GUI events.
+[[Image(EventTypesTools.png, nolink, align=center)]]
 
+The Event Core provides interfaces for common GUI elements, e.g., buttons ('''{{{IButton}}}'''). All of the common GUI elements have the same ancestor, the '''{{{IGUIElement}}}''' interface. Furthermore, the Event Core contains a '''{{{GUIModel}}}''' class. This class is used to manage and maintain the structure of known GUI elements internally. It requires that all GUI element implementation (including those located in the !EventBench Plug-ins components) implement the '''{{{IGUIElement}}}''' interface.
 [[Image(EventTargets.png, nolink, align=center)]]