NotifySharp
From NDesk
Revision as of 15:28, 1 October 2006 (edit) Slomo (Talk | contribs) ← Previous diff |
Current revision (21:52, 2 October 2006) (edit) (undo) Alp (Talk | contribs) |
||
Line 1: | Line 1: | ||
- | notify-sharp is a C# client implementation for [http://trac.galago-project.org/wiki/DesktopNotifications Desktop Notifications], i.e. notification-daemon. It's API is inspired by the [http://www.galago-project.org/docs/api/libnotify/ libnotify] API. | + | notify-sharp is a C# client implementation for [http://trac.galago-project.org/wiki/DesktopNotifications Desktop Notifications], i.e. notification-daemon. It is inspired by the [http://www.galago-project.org/docs/api/libnotify/ libnotify] API. |
Desktop Notifications provide a standard way of doing passive pop-up notifications on the Linux desktop. These are designed to notify the user of something without interrupting their work with a dialog box that they must close. Passive popups can automatically disappear after a short period of time. | Desktop Notifications provide a standard way of doing passive pop-up notifications on the Linux desktop. These are designed to notify the user of something without interrupting their work with a dialog box that they must close. Passive popups can automatically disappear after a short period of time. |
Current revision
notify-sharp is a C# client implementation for Desktop Notifications, i.e. notification-daemon. It is inspired by the libnotify API.
Desktop Notifications provide a standard way of doing passive pop-up notifications on the Linux desktop. These are designed to notify the user of something without interrupting their work with a dialog box that they must close. Passive popups can automatically disappear after a short period of time.
[edit] Status
Finished implementing version 0.9 of the specification. notify-sharp will be released once DBusSharp is released.
There are currently some differences between the specification and notification-daemon that need to be fixed but as notify-sharp follows notification-daemon's behaviour instead of the specification's there should be no problems in the future.
In the future, properties for new, standardized hints will be added.