*** Netscape 4.x -> Mozilla version x -> latest TB/SM would have the conversion done at mozilla version x stage, or could be done in the profile migration once new SM has new profile location (suiterunner will provide this) - tb already requires profile migration.
** if not, then can we find something that is always called first/make it called first to do the work for us? e.g. nsLDAPPrefsService::migrate?
== Drag n Drop in Address book ==
I put this list together to enable easier formation of what we need to be able to allow/disallow in address book drag n drop.
{| border=1 valign=top
! From !! To !! Copy? !! Move? !! Complete? !!Reason/Notes
|-
| anything || same place || No || No || || Don't really want to be able to create duplicates in this way.
|-
| card in ML || Parent ML || No || No || || ditto
|-
| anything || read only directory || No || No || Yes ||
|-
| mailing list || mailing list || No || No || || We don't support nested mailing lists at the moment ([https://bugzilla.mozilla.org/show_bug.cgi?id=40301 bug 40301])
|-
| card || different AB || Yes || Yes || ||
|-
| card || mailing list || Yes || No || || Cards currently have to exist outside a mailing list for the mailing list to work correctly.
|-
| mailing list || different AB || No || Yes || || We require mailing lists to have unique names. Otherwise composition would get confusing.
|-
| card in ML || other ML || Yes || Yes || ||
|-
| card in ML || other AB || Yes || Yes || ||
|-
| read-only directory item || anywhere || Yes || No || Patch 1 || Can't "move" read-only items.
|}
Some other thoughts/concerns:
* DnD code doesn't currently support re-checking for only move or copy allowed - assumes both. Should be an easy fix (bug 336241).
* In cases of card->mailing list and read-only item-> anywhere, "copy" should be the default action. In other cases I think it should be move. I think this can be done within the limits of the existing code.
== Collected Address Book Removal? ==
