[cosmo-dev] Creating Tasks from Lightning
jeffrey at osafoundation.org
Fri Dec 21 12:43:53 PST 2007
>> If, conversely, I create a task in Cosmo. When I reload the collection
>> in Lightning, it displays the task as an *event* and not a task...
> this should only happen if you stamp the item as both an event and a
> task. in that case, Cosmo has to decide how to represent the item in
> iCalendar. CalDAV rules require that the item be represented as an
> event or as a task but not both. if an item is stamped as an event,
> then it is represented in iCalendar as an event, regardless of the
> fact that it might also be stamped as a task. if it is stamped only as
> a task, then it is represented in iCalendar as a task.
> if you want an item to exist in the Cosmo calendar view, you have to
> stamp it as an event. this is one place where Cosmo's design conflicts
> with the iCalendar data model used by iCal and Lightning. it's
I've thought for a while about reversing this behavior in the Desktop,
now that Lightning works with tasks, maybe it's time to discuss it more.
If an item was stamped as a task, we could export it as a VTODO,
regardless of event-ness.
Unfortunately, I think the majority of users don't use the task silo in
their calendar app. For non-task-users like this, if they dabble with
adding the task stamp to events on Cosmo they'll find that the item
disappears from their calendar. Maybe there's just no good way to fix this.
More information about the cosmo-dev