Re: [Evolution-hackers] Syncing with Evolution, reloading calendar without linking to gnome libs?
- From: Reinhold Kainhofer <reinhold kainhofer com>
- To: evolution-hackers lists ximian com
- Subject: Re: [Evolution-hackers] Syncing with Evolution, reloading calendar without linking to gnome libs?
- Date: Tue, 4 May 2004 15:11:42 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, 04. May 2004 14:36, you wrote:
> On Tue, 2004-05-04 at 12:51 +0200, Reinhold Kainhofer wrote:
> > So, my question now is, how can I make evolution reload the calendar
> > without having to link to all the gnome / evolution libraries, which is
> > clearly out of option for kpilot ?
>
> if you are going to modify evolution's calendar files, you'd better do
> it via the evolution API.
Hmm, this is clearrly out of scope for a conduit that's supposed to sync with
an ics file (or more generally, any KCal::Calendar derived class, like kde's
resource calendar consisting of data from several different places) ... Too
bad, kpilot then won't be able to sync to evolution :-((
It might be of interest for kitchensync, though, or for a calendar and
contacts resource for KDE's resource framework.
How does the evolution API work exactly? And what's the communication
protocol? I hope we don't have to link to all gnome libraries just to be able
to read the evolution calendar/addressbook...
Is there any introduction and further documentation available?
Thanks,
Reinhold
PS: Please note that I have absolutely no experience with gnome (neither using
nor programming), and I have only tried evolution very few times, but never
really used it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAl5aOTqjEwhXvPN0RAhxEAJ43tiapt51k04BO9PdADNao3/K99wCgrINs
JROjHLcSNM1/+/yO9hLWZDs=
=X/kx
-----END PGP SIGNATURE-----
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]