| commit | 31d8da1c4c1d30c6e68a37a01da0a4cfbfe593ac | |
| author | Chris Frey <cdfrey@foursquare.net> | |
| Wed, 23 May 2012 06:29:30 +0000 (23 02:29 -0400) | ||
| committer | Chris Frey <cdfrey@foursquare.net> | |
| Wed, 23 May 2012 06:29:30 +0000 (23 02:29 -0400) | ||
| tree | 832c3e5fe8b0374215b312ea8d746f60bb44c812 | treesnapshot (tar.gz zip) |
| parent | 023236bba0e9ce74f59238391e76d8d99b6619bf | commitdiff |
desktop: added concept of configured PST type mask
For example, in the Evolution plugin config, it may be difficult for the
end user to find the correct config for Memos or Calendar, if the
autodetect code doesn't work for them on their system. If the user
just doesn't care about syncing that particular object, it should be
possible to use an empty string, and then disable the corresponding
sync type.
By adding the concept of configured sync types to the plugin classes,
and ANDing the supported sync types with the configured ones, it is
possible to make these configuration possibilities more intuitive
and automatic.
For example, in the Evolution plugin config, it may be difficult for the
end user to find the correct config for Memos or Calendar, if the
autodetect code doesn't work for them on their system. If the user
just doesn't care about syncing that particular object, it should be
possible to use an empty string, and then disable the corresponding
sync type.
By adding the concept of configured sync types to the plugin classes,
and ANDing the supported sync types with the configured ones, it is
possible to make these configuration possibilities more intuitive
and automatic.