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
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
1
* add support for contacts with no N/FN name. In the absence of a name, the
2
android contacts list displays the organisation, and in the absence of that,
3
it displays the primary number. The solution seem to be to create a better
4
contact cache (or perhaps a manager that is also responsible for writing the
5
new contacts back to android)
6
* it'll also need to import organisations and primary numbers
7
* when reading vcf phone no.s, make sure they are imported in the same order
8
they appear in in the vcf. The first one will be the primary number.
9
* switch to the new contacts API
10
* don't try to do anything clever with phone no.s that are name-less, but
11
appear in existing contacts that (now) have a name
12
* possible bug: when displaying "aborting import" toaster, make sure the back
21
13
button is enabled and the abort button is hidden (as if abort were pressed)
22
14
since this can happen if, say, the alarm goes off.
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
28
and stop preventing screen rotation on some activities
15
* in the long term, we need to save/restore state from doit/importer
added
removed
TODO
