dx-packages team mailing list archive

[Nekhelesh Ramananthan <krnekhelesh@xxxxxxxxx>]

** Changed in: ubuntu-clock-app
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1354400

Title:
  Implement Alarm Snooze functionality

Status in Clock application for Ubuntu devices:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  -----  Background Info -----
  Currently the snap notification shown when an alarm is triggered shows the buttons "Ok" and "Show" which both does the same thing which is to dismiss the alarm.  Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the "Snooze" functionality and replace the "Show" button with "Snooze".

  However "Snooze" was decided to be implemented as part of the SDK
  Alarms API which is worked on by zsombor. As per the blueprint at [1],
  the snooze functionality was to be implemented in revision 0.2 (post-
  RTM).  However we require a solution to the above issue before RTM.

  ----- Proposed Solution -----
  It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below.

  1. Provide a settings option in dbus to set the snooze duration that
  the clock app can expose in the settings page to allow the user to
  choose the snooze duration. This is shown in [2]. The snooze duration
  options will be 2, 4, 5 and 10 minutes.

  2. On pressing the "Ok" button in the snap notification, the alarm
  will be dismissed permanently for the day.

  3. If the user pressed "Snooze", then indicator-datetime should
  dismiss the snap notification and show it again after the snooze
  duration. This process will be repeated until the alarm timeout
  defined by the user in the clock app settings. By default that timeout
  is 30 minutes.

  This will require a Go/No-Go decision from Charles Kerr regarding the
  implementation in indicator-datetime since as mentioned above this
  will be a workaround and workaround are not permanent solutions.

  [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api
  [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+subscriptions