1
* declare war on camelCase variables
1
IMMEDIATE (for next release)
3
* re-import all the test data, skipping dupes, so we can test caching
4
* re-import all the test data, having added a TEL to one of the contacts,
5
merging dupes, so we can test merging with cached contacts
6
* things to check from test data
7
- if there is a dupe that is merged contains a TEL, does that take
8
preference over the existing contact's preferred TEL?
9
* "TEL;TYPE=WORK;TYPE=FAX:" is imported as "work", not "work fax"!
10
* after correcting the "TYPE=WORK;TYPE=FAX" issue, check that when two numbers
11
appear, the first a fax, the second a normal number, but neither is
12
preferred, the normal number takes precedence
13
* "EMAIL;TYPE=INTERNET;TYPE=WORK:" imports a "home" email address
2
14
* change some public final static ints, that aren't really consts, in to enums
3
18
* create a back-end object to read/write to android. This can be overridden to
4
19
use the new ContractsContacts API.
5
20
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
6
are ignored) during the import
21
are ignored) during the import (see TODO comments in the code)
7
22
* add base64 decoding to support (even if to ignore) vcards with image data
8
23
* possible bug: when displaying "aborting import" toaster, make sure the back
9
24
button is enabled and the abort button is hidden (as if abort were pressed)
10
25
since this can happen if, say, the alarm goes off.
11
* in the long term, we need to save/restore state from doit/importer
26
* add facility to be asked whether to import all contacts, not just those that
28
* add facility to import a duplicate contact as a new contact
29
- is this possible? can you have two contacts with the same name in Android?
30
- how would future duplicate merging be handled? you'd have to select which
31
one you wanted to merge in to!
32
* in the long term, we probably need to save/restore state from doit/importer
33
and stop preventing screen rotation on some activities
added
removed
TODO
