syncevolution/src
2008-08-09 09:06:09 +00:00
..
backends disable linked item testing: file backend does not support the special semantic 2008-08-05 20:09:49 +00:00
core CLIENT_TEST_EVOLUTION_USER/PASSWORD and warning about init order 2008-08-09 09:06:09 +00: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 added CLIENT_TEST_EVOLUTION_USER/PASSWORD so that backends which require authentication can now also be tested 2008-08-09 08:57:30 +00:00
Makefile-gen.am added missing imemo20.ics test cases to build 2008-08-05 20:11:11 +00:00
normalize_vcard.pl Algorithm::Diff: check whether files really have changed 2007-03-25 18:05:51 +00: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
sync4j-client-api-sdkcpp_3_0_6a.diff fix for #304805: testing return code of SyncClient::beginSync() 2006-03-26 17:17:06 +00:00
syncevolution.cpp adapted to the extended printLine() method 2008-04-07 17:51:17 +00:00
testCalendar.ics added test case with BYSETPOS=-1 2006-06-17 16:17:11 +00:00
TestMain.cpp copyright transfer to Funambol 2006-12-10 17:35:20 +00:00
testMemo.ics added testing of memos 2007-01-04 22:13:09 +00:00
testTask.ics relax comparison of RRULE BYDAY, modified task test case to always use its own VTIMEZONE 2006-06-15 16:15:37 +00:00
testVCard.vcf workaround for Funambol 3.0 trailing = parser bug 2007-03-24 17:14:53 +00: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.
 */