| 2013-09-25 20:26:02 |
Ted Gould |
bug |
|
|
added bug |
| 2013-09-25 20:26:17 |
Ted Gould |
bug task added |
|
url-dispatcher |
|
| 2013-09-25 20:26:31 |
Ted Gould |
bug task added |
|
indicator-datetime |
|
| 2013-09-25 20:30:44 |
Ted Gould |
url-dispatcher: assignee |
|
Ted Gould (ted) |
|
| 2013-09-25 20:30:54 |
Ted Gould |
indicator-datetime: assignee |
|
Charles Kerr (charlesk) |
|
| 2013-09-25 20:43:35 |
Ted Gould |
description |
For the design in the datetime indicator we need to be able to click on events in the calendar, and have them show up in the calendar application. For all other things similar to this we're using an URL to ensure proper execution and containment, that also makes sense here. I was unable to find any official prior art on a URL format to use for this, so I'm reverting to some adhoc prior art that Evolution uses.
Evolution supports a URL calendar:/// which can then take two parameters of starttime and endtime, which as a group show how much time to show and where to start end the view. For instance, a week long retreat might make more sense to show in week view, but a 15 minute meeting will be shown in day view. I think that the caller doesn't need to make that choice, but instead provide the time they're interested in.
The parameters starttime and endtime both take an integer value of the number of seconds since unix epoch in the UTC timezone. Evolution also supports a special value of "0" to mean today for quick access. |
For the design in the datetime indicator we need to be able to click on events in the calendar, and have them show up in the calendar application. For all other things similar to this we're using an URL to ensure proper execution and containment, that also makes sense here. I was unable to find any official prior art on a URL format to use for this, so I'm reverting to some adhoc prior art that Evolution uses.
Evolution supports a URL calendar:/// which can then take two parameters of starttime and endtime, which as a group show how much time to show and where to start end the view. For instance, a week long retreat might make more sense to show in week view, but a 15 minute meeting will be shown in day view. I think that the caller doesn't need to make that choice, but instead provide the time they're interested in.
The parameters starttime and endtime both take an integer value of the number of seconds since unix epoch in the UTC timezone. If no parameters are given it just pops up today. |
|
| 2013-09-25 20:56:01 |
Charles Kerr |
description |
For the design in the datetime indicator we need to be able to click on events in the calendar, and have them show up in the calendar application. For all other things similar to this we're using an URL to ensure proper execution and containment, that also makes sense here. I was unable to find any official prior art on a URL format to use for this, so I'm reverting to some adhoc prior art that Evolution uses.
Evolution supports a URL calendar:/// which can then take two parameters of starttime and endtime, which as a group show how much time to show and where to start end the view. For instance, a week long retreat might make more sense to show in week view, but a 15 minute meeting will be shown in day view. I think that the caller doesn't need to make that choice, but instead provide the time they're interested in.
The parameters starttime and endtime both take an integer value of the number of seconds since unix epoch in the UTC timezone. If no parameters are given it just pops up today. |
For the design in the datetime indicator we need to be able to click on events in the calendar, and have them show up in the calendar application. For all other things similar to this we're using an URL to ensure proper execution and containment, that also makes sense here. I was unable to find any official prior art on a URL format to use for this, so I'm reverting to some adhoc prior art that Evolution uses.
Evolution supports a URL calendar:/// which can then take two parameters of starttime and endtime, which as a group show how much time to show and where to start end the view. For instance, a week long retreat might make more sense to show in week view, but a 15 minute meeting will be shown in day view. I think that the caller doesn't need to make that choice, but instead provide the time they're interested in.
In evolution, the parameters starttime and endtime are both ISO 8601 date/time strings as parsed by libecal's time_from_isodate() function, are separately optional: one or both or neither can be provided.
If no parameters are provided to evolution, it pops up a planner showing today. |
|
| 2013-09-26 11:10:13 |
David Planella |
ubuntu-calendar-app: status |
New |
Triaged |
|
| 2013-09-26 11:10:24 |
David Planella |
ubuntu-calendar-app: importance |
Undecided |
High |
|
| 2013-09-26 12:32:07 |
Riccardo Padovani |
ubuntu-calendar-app: assignee |
|
Riccardo Padovani (rpadovani) |
|
| 2013-09-26 12:50:21 |
Launchpad Janitor |
branch linked |
|
lp:~ted/url-dispatcher/calendar-url |
|
| 2013-09-26 12:56:41 |
Ted Gould |
url-dispatcher: importance |
Undecided |
High |
|
| 2013-09-26 12:56:41 |
Ted Gould |
url-dispatcher: status |
New |
In Progress |
|
| 2013-09-27 09:30:23 |
Riccardo Padovani |
branch linked |
|
lp:~rpadovani/ubuntu-calendar-app/1231136 |
|
| 2013-09-27 09:30:32 |
Riccardo Padovani |
ubuntu-calendar-app: status |
Triaged |
In Progress |
|
| 2013-09-27 20:59:00 |
PS Jenkins bot |
url-dispatcher: status |
In Progress |
Fix Committed |
|
| 2013-10-03 14:52:17 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/saucy-proposed/url-dispatcher |
|
| 2013-10-03 14:52:41 |
Launchpad Janitor |
url-dispatcher (Ubuntu): status |
New |
Fix Released |
|
| 2013-10-04 13:33:22 |
Charles Kerr |
indicator-datetime: status |
New |
In Progress |
|
| 2013-10-04 13:34:36 |
Charles Kerr |
indicator-datetime: importance |
Undecided |
High |
|
| 2013-10-07 13:11:14 |
Ted Gould |
url-dispatcher: status |
Fix Committed |
Fix Released |
|
| 2013-10-16 16:52:02 |
Ubuntu Phone Apps Jenkins Bot |
ubuntu-calendar-app: status |
In Progress |
Fix Committed |
|
| 2014-01-27 14:35:47 |
David Planella |
ubuntu-calendar-app: status |
Fix Committed |
Fix Released |
|
