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
'\\ No newline at end of file'
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
13
* possible bug: when displaying "aborting import" toaster, make sure the back
14
button is enabled and the abort button is hidden (as if abort were pressed)
15
since this can happen if, say, the alarm goes off.
16
* in the long term, we need to save/restore state from doit/importer
added
removed
TODO
