Alarm notification should be changed to an interactive notification

[Nekhelesh Ramananthan]

As per the latest design spec, the snap notification that is shown when an alarm is triggered will be replaced with a interactive notification. The design spec for the interactive notification is shown at [1].

Please ensure that the strings shown in the spec are translatable. The timing of how long the notification should be shown are similar to the snap notification behavior we have atm.

https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_00

[Charles Kerr (charlesk)]

Just to be clear, this means the whole launching-the-clock-app option is going away...

[Nekhelesh Ramananthan (nik90)]

Well we will still be doing the launch-the-clock-app option when a user clicks on an alarm in the datetime-indicator. But yes the interactive notifications themselves will not launch the clock app anymore.

[Charles Kerr (charlesk)]

This MP switches the notification from a Snap to Interactive; however, it regresses on bug #1324580 in that the notification times out quickly, ignoring the duration suggested by ubuntu-clock-app.

This may be by design for Interactive notifications in unity-notifications, as NotificationServer::buildNotification() doesn't use the timeout hint in Interactive mode. Indeed, the timeout hint's key is "x-canonical-snap-decisions-timeout"

The simplest way to satisfy both tickets would be to add a couple of lines to NotificationServer::buildNotification() so timeouts aren't limited to snap decisions. I don't know if/how that affects other design constraints in unity-notifications... adding MacSlow to the ticket for another opinion.

[Charles Kerr (charlesk)]

Closing this ticket as Invalid as per this comment in by nik90 in the MP:

> I had a discussion today with the designers and Mirco Mueller about the alarm notifications. The conclusion was the following,
>
> - Alarm notification will remain as Snap Notifications with the buttons "Snooze" and "Ok" shown like in the design spec at https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g36c1a0cdd_010 as interactive notifications will not provide support for custom timeouts.
>
> - Pressing "Ok" will dismiss the alarm as expected.
>
> - Pressing "Snooze" will dismiss the snap notification for the snooze duration of 5 mins (default) and then show the snap notification again. This process will keep repeating until the alarm timeout setting set by the clock app (30 mins by default).
>
> - The snooze duration will need to be exposed as a setting option via dbus so that the clock app can expose that in the UI for the user to change if required. The design spec for this can be found at https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024
>
> With that I am disapproving this MP.