1
* declare war on camelCase variables
1
IMMEDIATE (for next release)
3
* re-import all the test data, having added a TEL to one of the contacts,
4
merging dupes, so we can test merging with cached contacts
5
* add ContactContracts backend
6
* when using ContactContracts provide selection of account to import in to
10
* add facility to enter a group name, that any imported contacts are added to
2
11
* change some public final static ints, that aren't really consts, in to enums
12
* fix: merging an unPREFed TEL will override a preferred phone no. in the phone
3
13
* create a back-end object to read/write to android. This can be overridden to
4
14
use the new ContractsContacts API.
5
15
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
6
are ignored) during the import
16
are ignored) during the import (see TODO comments in the code)
7
17
* add base64 decoding to support (even if to ignore) vcards with image data
8
18
* possible bug: when displaying "aborting import" toaster, make sure the back
9
19
button is enabled and the abort button is hidden (as if abort were pressed)
10
20
since this can happen if, say, the alarm goes off.
11
* in the long term, we need to save/restore state from doit/importer
21
* add facility to be asked whether to import all contacts, not just those that
23
* add facility to import a duplicate contact as a new contact
24
- is this possible? can you have two contacts with the same name in Android?
25
- how would future duplicate merging be handled? you'd have to select which
26
one you wanted to merge in to!
27
* in the long term, we probably need to save/restore state from doit/importer
28
and stop preventing screen rotation on some activities
added
removed
TODO
