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
* add base64 decoding to support (even if to ignore) vcards with image data
22
* possible bug: when displaying "aborting import" toaster, make sure the back
23
button is enabled and the abort button is hidden (as if abort were pressed)
24
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
* in the long term, we need to save/restore state from doit/importer
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'
added
removed
TODO
