Default Alarm frequency should be 'null' (one off)

[Giorgio Venturi]

Default Alarm frequency should be null (one-off). Setting up a frequency should be optional. By default, if the alarm goes off, it must be turned on manually, unless a frequency is set

[Nekhelesh Ramananthan (nik90)]

There are a couple of design questions I had during the implementation,

- If the frequency is set to "Never", in the alarm list page do we also display "Never" below the alarm label? Or should we display today's day since it will ring today as a one time alarm?

- How does a user differentiate between a single alarm and a repeating alarm?

- What should happen if a user sets this alarm before the current local time? So for instance if the current local time is 16:00 and the user is trying to set an alarm for 13:00, the SDK will reject them. Should we display a message saying that the time is invalid and to try again?

Note: This wasn't an issue with repeating alarms since if you set an alarm for an earlier time, it rings next week.

[Giorgio Venturi (giorgio-venturi-deactivatedaccount)]

Good points.
1) If set to 'never' (i.e. no frequency selected) then it should not display anything in a second line
2) Picker can be set to have a lower and upper limit, so the lower limit should be set against the current time

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:ubuntu-clock-app at revision 76, scheduled for release in ubuntu-clock-app, milestone rtm