calendar ics bug

It is not the problem that it misinterprets DTEND, it doesn't interpret it at all, it only uses DTSTART and adds a duration of 1 to it.

In Open ERP's internal representation a meeting has got a duration, not an end-time.
However, in Open ERP's .ics file a DTEND is used.

Checked it again by just modifying the imported (online) calendar: Open ERP listens to the DTEND, but incorrectly: A BUG!

I changed a one hour during activity into 3 hour during (in the Lightning client). Automatically the online ICS gets updated correctly. But then, when viewing the calendar interface in the Open ERP client only displays a 2 hour during event.. strange, very very strange...
See my attachment: on the left Lightning, in the middle Open ERP and on the right the ICS file on the Open ERP server.

Thanks Stephane,
Do you think this will solve both problems?

Hannes

I found that the mappings in Open ERP are not optimal: For example a Meeting is mapped with it's deadline towards DTEND (ICS).
It's better to use the Duration and Start date to compute the end-date of a Meeting instead of using the Deadline.

I think ICS also supports DURATION as an attribute. If someone can add this field to the ICS fields in Open ERP, then this may solve part of the problem.

You are right that ICS provides DURATION, We can add,
But as ics vevent can not have Both DURATION AND DTEND properties at a time, we should avoid selecting both in mapping lines..

Hello Hannes,
We appreciate your interest and inputs.
For the sake of usability, we shift this to 6.0 and it will contain every possible configuration for this utility.
Keep posting on this thread for more of your golden suggestions.
You may use the caldav module from addons branch of trunk(to be stable 6.0).
Thanks a lot.