The notification message can consist of several parts: caption, description and icon. It is usually used with only caption - one should be wary of filling the notification with too much information.
The notification message tries to be as unobtrusive as possible, while still drawing needed attention. There are several basic types of messages that can be used in different situations:
In addition to the basic pre-configured types, a Notification can also be configured to show up in a custom position, for a specified time (or until clicked), and with a custom stylename. An icon can also be added.
Implementations of this interface may provide additional methods relevant to the specific form of notification taking place.
Revisions:
20020329 Adrian Brock:
20020710 Adrian Brock:
The representation of the test notification
@author Mulesoft Inc. @since 3.3.2INotification implementation. PureMVC does not rely upon underlying event models such as the one provided with Flash, and ActionScript 3 does not have an inherent event model.
The Observer Pattern as implemented within PureMVC exists to support event-driven communication between the application and the actors of the MVC triad.
Notifications are not meant to be a replacement for Events in Flex/Flash/Apollo. Generally, IMediator implementors place event listeners on their view components, which they then handle in the usual way. This may lead to the broadcast of Notifications to trigger ICommands or to communicate with other IMediators. IProxy and ICommand instances communicate with each other and IMediators by broadcasting INotifications.
A key difference between Flash Events and PureMVC Notifications is that Events follow the 'Chain of Responsibility' pattern, 'bubbling' up the display hierarchy until some parent component handles the Event, while PureMVC Notifications follow a 'Publish/Subscribe' pattern. PureMVC classes need not be related to each other in a parent/child relationship in order to communicate with one another using Notifications.
@see org.puremvc.java.patterns.observer.Observer Observer
This class represents a notification that will be delivered to users. This is a general concept and it has no knowledge of the possible ways to be delivered (see {@link NotificationChannel}) or of the users who should receive it (see {@link NotificationDispatcher}).
When creating a new notification, it is strongly advised to give a default message that can be used by channels that don't want to specifically format messages for different notification types. You can use {@link Notification#setDefaultMessage(String)} for that purpose.
@since 2.10 | |
| |
| |
| |
| |
| |
| |
| |
| |
| |