40db68c937
Step information 'waiting' is appended into status for the progress spinner. The spinner should be disabled unless 'waiting' is explicitly appended in the status. 'waiting' means the dbus server is blocked and waiting for something, typically IO events, such as sending data, waiting for response. Once it is absent from status, the dbus server is done with waiting. Change corresponding unit tests in the test-dbus.py for statuses have been changed. |
||
---|---|---|
.. | ||
backends | ||
dbus | ||
gdbus | ||
gtk-ui | ||
syncevo | ||
templates | ||
.cvsignore | ||
async.patch | ||
client-test-app.cpp | ||
CmdlineSyncClient.cpp | ||
CmdlineSyncClient.h | ||
Makefile-gen.am | ||
org.syncevolution.service.in | ||
README.h | ||
README.templates | ||
shlibs.local | ||
sunbird_client.xml | ||
syncclient_sample_config.xml | ||
syncevo-dbus-server.cpp | ||
syncevolution.cpp | ||
valgrind.supp |
The configuration templates in "templates" get installed into $(datadir)/syncevolution/templates. When adding/changing a new server, then only enter the properties which need to be changed here so that the default values can be used for the remaining properties. An icon can be added here for servers. The file name must start with "icon". Server configurations must be kept in sync in three different places: - here (if a server is installed as files) - in SyncEvolutionConfig.cpp's EvolutionSyncConfig::createServerTemplate() - in SyncEvolutionCmdline.cpp's test server configs - in test/test-dbus.py testGetConfigsTemplates() Note that server icons must come with a suitable license that allows redistribution.