touch-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

See also: https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1426519

I think what we want to do is move the logic out of datetime if possible
so that datetime can move from seeing things as "everything's a clock-
app alarm or calendar event" to being a passthrough with less hardcoded
logic in it. The rationale for this is we now want to add support for
the reminder app, and we also want to support 3rd party apps.

So this bug has the right idea, but it would be better if, instead of a
unique ID that datetime had to be coded to understand, that ui-toolkit
or clock-app generated a url that datetime could blindly pass to url-
dispatch().

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1426361

Title:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm instead of just the alarm index that varies
  based on the alarm date dynamically.

  Use Case: Bug 1387210 Indicator-datetime will pass the
  QOrganizerItemId (unique alarm ID) to clock app when the user clicks
  on an alarm in the indicator-datetime. But the current Alarms API does
  not allow clock app to open the alarm using that unique ID which
  results in clock app not knowing which alarm to show to the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1426361/+subscriptions