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!
16
* change some public final static ints, that aren't really consts, in to enums
17
* create a back-end object to read/write to android. This can be overridden to
18
use the new ContractsContacts API.
19
* add warnings when email addresses, phone numbers, etc, fail sanitisation (and
20
are ignored) during the import
21
1
* add base64 decoding to support (even if to ignore) vcards with image data
2
* add support for contacts with no N/FN name. In the absence of a name, the
3
android contacts list displays the organisation, and in the absence of that,
4
it displays the primary number. The solution seem to be to create a better
5
contact cache (or perhaps a manager that is also responsible for writing the
6
new contacts back to android)
7
* it'll also need to import organisations and primary numbers
8
* when reading vcf phone no.s, make sure they are imported in the same order
9
they appear in in the vcf. The first one will be the primary number.
10
* switch to the new contacts API
11
* don't try to do anything clever with phone no.s that are name-less, but
12
appear in existing contacts that (now) have a name
22
13
* possible bug: when displaying "aborting import" toaster, make sure the back
23
14
button is enabled and the abort button is hidden (as if abort were pressed)
24
15
since this can happen if, say, the alarm goes off.
25
* add facility to be asked whether to import all contacts, not just those that
27
16
* in the long term, we need to save/restore state from doit/importer