1
* add support for contacts with no N/FN name. The contacts list displays the
2
primary number instead of a name, but the existing contact detection will
3
need to be fixed-up. See Importer::isImportRequired().
5
* have a second list (beside _contact) that maps organisation names to ids
6
that is used when a contact has no other name
7
* have a third list (beside _contact and the above list) that maps the
8
primary phone no.s to ids, where the contact has no name or organisation
9
* when reading vcf phone no.s, make sure they are imported in the same order
10
they appear in in the vcf. The first on will become the primary when the
11
contact has no name or organisation
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
9
* change some public final static ints, that aren't really consts, in to enums
10
* fix: merging an unPREFed TEL will override a preferred phone no. in the phone
11
* create a back-end object to read/write to android. This can be overridden to
12
use the new ContractsContacts API.
13
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
14
are ignored) during the import (see TODO comments in the code)
15
* add base64 decoding to support (even if to ignore) vcards with image data
12
16
* possible bug: when displaying "aborting import" toaster, make sure the back
13
17
button is enabled and the abort button is hidden (as if abort were pressed)
14
18
since this can happen if, say, the alarm goes off.
15
* in the long term, we need to save/restore state from doit/importer
19
* add facility to be asked whether to import all contacts, not just those that
21
* add facility to import a duplicate contact as a new contact
22
- is this possible? can you have two contacts with the same name in Android?
23
- how would future duplicate merging be handled? you'd have to select which
24
one you wanted to merge in to!
25
* in the long term, we probably need to save/restore state from doit/importer
26
and stop preventing screen rotation on some activities
added
removed
TODO
