** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) => Zsombor Egri (zsombi)
--
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/1373987
Title:
Cread/Read/Update/Delete API for alarms
Status in The Date and Time Indicator:
Triaged
Status in Calendar application for Ubuntu devices:
Invalid
Status in Ubuntu UI Toolkit:
Triaged
Status in “ubuntu-ui-toolkit” package in Ubuntu:
Triaged
Bug description:
As described in bug #1361702 we currently require "magic" tags in our
VTODO events in order to treat clock-app alarms differently from other
todo events imported from other calendar sources. This special
treatment has to exist in both indicator-datetime and ubuntu-calendar-
app.
In the #ubuntu-app-devel discussion on Sept 24, zsombi, mihir, nik90
and I agreed that it would make more sense to decouple the alarms from
EDS altogether.
Earlier this year there was an aborted attempt to get a public "clean
C" API for this into platform-API. That could be revived.
However, since that time the datetime alarm service has become the de-
facto location for alarms and provides a DBus API for setting alarm
duration, vibrate mode, default alarm sounds, and the like. The
general agreement in the #ubuntu-app-devel discussion was that this
API could be extended with an alarm create/read/update/delete API.
This latter option should be picked up post-RTM so that we can remove
the temporary workarounds implemented for bug #1361702.
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1373987/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
