[Evolution-hackers] [evolution-kolab] Datastructures for calendar data
- From: Hendrik Helwich <h helwich tarent de>
- To: evolution-hackers gnome org
- Subject: [Evolution-hackers] [evolution-kolab] Datastructures for calendar data
- Date: Mon, 27 Sep 2010 15:54:59 +0200
Hi evolution hackers,
while working on a plugin [1] to connect eds to a kolab server, i need to
convert evolution contacts, events, tasks and notes to a kolab email (and
back).
Right now the idea is to use the class EContact for evolution contacts and
ECalComponent for evolution events, tasks and notes.
I now noticed, that an event in an evolution iCalendar file contains a
VTIMEZONE and a VEVENT block, and the VEVENT block depends to a timezone
which is defined in the VTIMEZONE block.
The ECalComponent seems to hold only one block of an iCalendar object and it
is therefore not possible to get all the informations of an evolution event
from one ECalComponent.
What would be the best datastructure to convert from/to an evolution event?
* A List of ECalComponent?
* One ECalComponent which is created from a List of ECalComponents by
converting local time to UTC time?
* iCalendar Strings?
Regards,
Hendrik
[1] http://sourceforge.net/projects/evolution-kolab/
--
tarent Gesellschaft für Softwareentwicklung und IT-Beratung mbH
Geschäftsführer: Boris Esser, Elmar Geese
HRB AG Bonn 5168 - USt-ID (VAT): DE122264941
Heilsbachstraße 24, 53123 Bonn, Telefon: +49 228 52675-0
Thiemannstraße 36 a, 12059 Berlin, Telefon: +49 30 5682943-30
Internet: http://www.tarent.de/ • Telefax: +49 228 52675-25
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]