|
talx x1.0.5 | ||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||
See:
Description
| Class Summary | |
| ChangeFinishedEvent | Signals change in controller state. |
| ComposeMailEvent | This class is a Think And Link Event which is sent out in response to the compose window closing either because the message is being sent or because the composition is being aborted. |
| ComposerActionEvent | An ActionEvent that signals a change in the composer text. |
| ControllerChangeEvent | Signals a change in the GUI mandated by the controller. |
| DeleteMailEvent | Fired when a message is deleted. |
| EraseEvent | This class defines an erase Event in a reply pane. |
| GameChangedEvent | |
| GameChangeProposedEvent | |
| IllegalActionEvent | An ActionEvent that indicates a previous action was illegal. |
| MessageActionEvent | An ActionEvent that also contains a message. |
| NewMailEvent | Fired when a new message arrives into the model. |
| PersonActionEvent | An ActionEvent that also contains a person. |
| ReadMailEvent | Fired when a message is placed in the reader. |
| TALEvent | This class defines a basic Event object for the Think And Link email client. |
| TALMailEvent | A basic Event object that contains a message. |
| TALPeopleMailEvent | Generic events that contain a list of people and a message. |
Provides system notification classes for use in other packages. The Think-and-Link system uses the Event-Listener pattern to convey messages between the controller, model and view, and to communicate within the model. Pluggable features may also generate events to alert the controller to important system events.
The controller listens for action events and uses the ActionHandlers to translate those into controller change events that are sent to the visual components. Pluggable features that wish to communicate with the controller must do so by sending an ActionEvent through the ActionDispatcher. This assumes that the controller is currently using an ActionHandler that will react to such an ActionEvent.
The model uses a filter stack with the TransportModel in the middle between the incoming filter stack and the outgoing filter stack. The TransportModel API acts as a bridge between the controller and the transport system, but the model communicates internally and to the view components through events.
|
talx x1.0.5 | ||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||
© 2001-2005 University of Oregon.
Eugene OR 97403, U.S.A. All Rights Reserved.