Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Platform UI/Notifications"

(Mylyn)
(Mylyn)
Line 12: Line 12:
 
* Actions/commands associated with the event (e.g., click the incoming arrow to mark the task as read).
 
* Actions/commands associated with the event (e.g., click the incoming arrow to mark the task as read).
  
<center>[[Image:Notification.jpg]]</center>
+
<center>
 +
[[Image:Notification.jpg]]</center>
  
 
== Jazz ==
 
== Jazz ==

Revision as of 14:25, 2 September 2008

Some applications need to inform the user of events in the workbench that may require attention, whether or not the workbench is visible. An increasingly standard way of doing this is to use a desktop notification popup, often appearing for a fixed amount of time in the bottom-right hand of the window.

Ideally this mechanism would use the native Os mechanism for notifications. However, we do not yet have standard APIs for notifications on Windows, Linux or Mac (Growl is popular on Mac, but not part of the OS). Eclipse projects such as Mylyn make heavy use notifications, as do Eclipse-based products such as Jazz and Tasktop. To avoid the usability problems of having various plug-ins' notifications using different mechanisms, we should provide a common notification API.

Status

Mylyn

The Mylyn Commons API component currently provides the desktop notification popup used by Mylyn, implemented via bug 177974. The notification popup and notification manager are currently provisional. Popups fade into view, are sticky when the mouse is over them, and fade out if the mouse has exited or the set amount of time has elapsed. They support:

  • Different types of notification events (e.g., overdue tasks, new comments on bugs).
  • A default action for each event, invoked by clicking the events' hyperlink or icon (e.g., opening a task editor).
  • Actions/commands associated with the event (e.g., click the incoming arrow to mark the task as read).
Notification.jpg

Jazz

 Ben: please fill out

Requirements

 DRAFT

Platform should provide:

  • A common notification service that dispatches notifications to a presentation layer. We need to figure out if there is overlap with the status service.
  • A generic notification popup suitable for us by RCP and SDK-based applications.

Extensions can provide:

  • Integration with OS-specific notification mechansims (e.g., Growl).
  • New notification popup UIs with additional features (e.g., richer interaction).

References

Back to the top