1
* bug: when displaying "aborting import" toaster, make sure the back button is
2
enabled and the abort button is hidden (as if abort were pressed) since this
3
can happen if, say, the alarm goes off.
4
* bug: ImportContacts "master" class doesn't save/restore the state stack due to
5
what looks like some android wierdness. Get rid of this class and startup on
6
the Intro activity, opening new activities directly from the "next" button
7
handler instead of reporting back tot he master class. You might want to try
8
an experiment: what order does onPause/onResume get called in both parent
9
and child activities when one activity is started from another?
10
* add browse button to vcf import location field
11
* in the long term, we need to save/restore state from doit/importer
b'\\ No newline at end of file'
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 ContactContracts backend
6
* when using ContactContracts provide selection of account to import in to
10
* change some public final static ints, that aren't really consts, in to enums
11
* fix: merging an unPREFed TEL will override a preferred phone no. in the phone
12
* create a back-end object to read/write to android. This can be overridden to
13
use the new ContractsContacts API.
14
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
15
are ignored) during the import (see TODO comments in the code)
16
* add base64 decoding to support (even if to ignore) vcards with image data
17
* possible bug: when displaying "aborting import" toaster, make sure the back
18
button is enabled and the abort button is hidden (as if abort were pressed)
19
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!
26
* in the long term, we probably need to save/restore state from doit/importer
27
and stop preventing screen rotation on some activities
added
removed
TODO
