syncevolution/src
Patrick Ohly 70edceabd6 logging: record start/end times in SyncReport and print it
Start and end times are defined by the LogDir instance. It needs
access to the SyncReport to record the information there.
2009-04-16 09:26:14 +02:00
..
backends testing: 'text' was incomplete 2009-04-01 16:46:55 +02:00
core logging: record start/end times in SyncReport and print it 2009-04-16 09:26:14 +02:00
default Merge commit 'origin/ui' into ui 2009-04-14 10:58:08 +03:00
gtk-ui dbus client: add README 2009-04-14 10:48:19 +03:00
.cvsignore test for copying via server now transmits testVCard.vcf and also compares against it 2006-03-18 13:35:23 +00:00
async.patch patch switches to async version of the Evolution API 2007-02-22 19:33:21 +00:00
client-test-app.cpp testing: 'text' was incomplete 2009-04-01 16:46:55 +02:00
DBusSyncClient.cpp dbus service: handle suspend request 2009-04-02 20:36:59 +03:00
DBusSyncClient.h dbus service: handle suspend request 2009-04-02 20:36:59 +03:00
Makefile-gen.am dbus client: add and use new widget MuxBin 2009-04-09 17:45:20 +03:00
normalize_vcard.pl license: changed to LGPL v2.1 2009-03-25 14:42:43 +01:00
README.h better explanation what the classes do 2008-08-03 20:26:33 +00:00
shlibs.local reverted to 0.7 packaging 2008-07-03 19:56:15 +00:00
sunbird_client.xml use Synthesis SDK to run a sync session 2009-03-25 14:43:32 +01:00
syncevo-dbus-server.cpp dbus service & client: support webURL and iconURI 2009-04-08 13:49:13 +03:00
syncevo-dbus-server.h dbus service: handle suspend request 2009-04-02 20:36:59 +03:00
syncevolution.cpp copyright updated 2009-03-25 15:21:04 +01:00
syncevolution.xml ical20: moved VTIMEZONE before VEVENT/VTODO 2009-04-06 18:12:35 +02:00
valgrind.supp first working version of SyncSource for Evolution contacts (requires Sync4j C++ API 2.0, not currently available) 2005-11-05 22:04:33 +00:00

/**
 * @mainpage Getting Started
 *
 * This documentation for SyncEvolution and the Funambol C++ Client
 * API was generated automatically from the source code.
 *
 * While most of the classes in SyncEvolution are documented, very
 * little effort was spent on organizing this information in a coherent
 * way. If you are a developer who wants to write a SyncML client based
 * on the SyncEvolution framework, then you should have a look at
 * the following classes:
 * - TrackingSyncSource is the most convenient class to derive from.
 * - EvolutionSyncSource is a bit more general.
 * - RegisterSyncSource adds additional sources to the framework.
 *
 * The following classes help with testing your derived classes:
 * - RegisterSyncSourceTest is what you have to use.
 * - TestEvolution uses that information.
 * - ClientTest, LocalTests, SyncTests are used by TestEvolution.
 *
 * The FileSyncSource is a good example to get started.
 */