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
16
* possible bug: when displaying "aborting import" toaster, make sure the back
6
* pull ContactData out in to its own class, and share that class with export
8
* rename wizard activity classes (append "Wizard"), so you can tell them apart
10
* handle large screen sizes (don't worry about xlarge)
11
* reorganise intro page (licence on separate tab)
12
* add account selection (instead of it being hardcoded to the phone-only), for
13
use with ContactsContract backend
14
* add a logfile facility
15
* add facility to enter a group name, that any imported contacts are added to
16
* change some public final static ints, that aren't really consts, in to enums
17
* add warnings when email addresses, phone numbers, etc, fail sanitisation
18
(and are ignored) during the import (see TODO comments in the code)
19
* add base64 decoding to support (even if to ignore) vcards with image data
20
* possible bug: when displaying "aborting import" toaster, make sure the back
17
21
button is enabled and the abort button is hidden (as if abort were pressed)
18
22
since this can happen if, say, the alarm goes off.
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
23
* add facility to be asked to confirm each contact import (or show the prompt
24
if the contact is a dupe)
25
* add facility to import a duplicate contact as a new, renamed contact
26
- renamed contacts would have to be re-dupe checked
27
* in the long term, we probably need to save/restore state from doit/importer
26
28
and stop preventing screen rotation on some activities
added
removed
TODO
