3
* import a crap-load of contacts before release!
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 support for arbitrary notes in vCards
6
* add ContactsContract backend
7
? enumerate different account name/type combos and assign them an id
8
? with each cached contact, store the account that it comes from
9
? change contactscache to store names as "associated" data
10
? change contacts cache so that names, organisations, primary phones and
11
emails map to an array of ids (ContactsContract can store multiple
12
contacts with the same identifying detail, the old backend can't)
13
? add selection of account to create contacts in
17
* add a logfile facility
18
* add facility to enter a group name, that any imported contacts are added to
4
19
* change some public final static ints, that aren't really consts, in to enums
5
* does duplicate contact dialog displays UTF-8 name in ASCII?
9
* create a back-end object to read/write to android. This can be overridden to
10
use the new ContractsContacts API.
11
20
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
12
21
are ignored) during the import (see TODO comments in the code)
13
22
* add base64 decoding to support (even if to ignore) vcards with image data
16
25
since this can happen if, say, the alarm goes off.
17
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!
19
32
* in the long term, we probably need to save/restore state from doit/importer
20
33
and stop preventing screen rotation on some activities
added
removed
TODO
