1
* VcardImporter.Vcard.finaliseParsing() should be renamed to finalise() to
2
override Importer.ContactData.finalise(), if Java will permit us to do that
3
(fnaliseParsing() throws stuff that finalise() doesn't), and should call
5
* rename Importer.isImportRequired() to checkForDuplicate() and make it private.
6
This should be called from Importer.importContact(), which should then call
7
skipContact() to update the UI and return if checkForDuplicate() returns
9
* ContactData.finalise should create a ContactsCache.CacheIdentifier and throw
10
ContactCannotBeIdentifiedException() if that fails, which can be picked up
11
in Vcard.finalise(). Importer.importContact() and the renamed
12
Importer.checkForDuplicates() should use the ContactData's CacheIdentifier
13
and not create their own. This will also ensure that ContactData.finalise()
14
has been correctly called (or the identifier would be null).
15
* import a crap-load of contacts before release!
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
16
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
17
11
* create a back-end object to read/write to android. This can be overridden to
18
12
use the new ContractsContacts API.
19
13
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
20
are ignored) during the import
14
are ignored) during the import (see TODO comments in the code)
21
15
* add base64 decoding to support (even if to ignore) vcards with image data
22
16
* possible bug: when displaying "aborting import" toaster, make sure the back
23
17
button is enabled and the abort button is hidden (as if abort were pressed)
24
18
since this can happen if, say, the alarm goes off.
25
19
* add facility to be asked whether to import all contacts, not just those that
27
* in the long term, we need to save/restore state from doit/importer
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
26
and stop preventing screen rotation on some activities
added
removed
TODO
