3
3
* re-import all the test data, having added a TEL to one of the contacts,
4
4
merging dupes, so we can test merging with cached contacts
5
* add support for arbitrary notes in vCards
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)
9
12
* add account selection (instead of it being hardcoded to the phone-only), for
10
13
use with ContactsContract backend
11
14
* add a logfile facility
12
15
* add facility to enter a group name, that any imported contacts are added to
13
16
* change some public final static ints, that aren't really consts, in to enums
14
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
15
are ignored) during the import (see TODO comments in the code)
17
* add warnings when email addresses, phone numbers, etc, fail sanitisation
18
(and are ignored) during the import (see TODO comments in the code)
16
19
* add base64 decoding to support (even if to ignore) vcards with image data
17
20
* possible bug: when displaying "aborting import" toaster, make sure the back
18
21
button is enabled and the abort button is hidden (as if abort were pressed)
19
22
since this can happen if, say, the alarm goes off.
20
* add facility to be asked whether to import all contacts, not just those that
22
* add facility to import a duplicate contact as a new contact
23
- is this possible? can you have two contacts with the same name in Android?
24
- how would future duplicate merging be handled? you'd have to select which
25
one you wanted to merge in to!
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
26
27
* in the long term, we probably need to save/restore state from doit/importer
27
28
and stop preventing screen rotation on some activities