As part of the address book backend work, the addressLists
property
still returns an nsIMutableArray, but the mutable methods have no
effect. You should check your extension code does not use them.
GL
On Tue Oct 15 2019 22:06:03 GMT-0400 (Eastern Standard Time), Geoff
Lankow geoff@thunderbird.net wrote:
As part of the address book backend work, the addressLists
property
still returns an nsIMutableArray, but the mutable methods have no
effect. You should check your extension code does not use them.
Is there a doc somewhere that describes the current effort,
specifically, the design, of the new Address Book model?
One thing I'd very much like to see is doing away with separate address
books, and just use tags (Personal, Work, etc), with the ability to
Create/Add/Pin Tag Groups (for lack of a better term - this is just a
named group of one or more tags) to the sidebar (or a toolbar) as a
button so you can quickly/easily select the view of your Addresses in
the Address Book (singular).
I hope that was clear.
Thanks
On 22/10/2019 02:19, Tanstaafl wrote:
On Tue Oct 15 2019 22:06:03 GMT-0400 (Eastern Standard Time), Geoff
Lankow geoff@thunderbird.net wrote:
As part of the address book backend work, the addressLists
property
still returns an nsIMutableArray, but the mutable methods have no
effect. You should check your extension code does not use them.
Is there a doc somewhere that describes the current effort,
specifically, the design, of the new Address Book model?
No there is not, because it doesn't exist yet. Current work is to
migrate away from using Mork databases in the back end.
I posted about this here in August: "Roadmap towards a Mork-free address
book back-end".
Beyond that is unclear. I believe there are moves at Council to provide
more manpower (or womanpower, just as good) for the address book effort.
GL
On Mon Oct 21 2019 17:33:52 GMT-0400 (Eastern Standard Time), Geoff
Lankow geoff@thunderbird.net wrote:
On 22/10/2019 02:19, Tanstaafl wrote:
Is there a doc somewhere that describes the current effort,
specifically, the design, of the new Address Book model?
No there is not, because it doesn't exist yet. Current work is to
migrate away from using Mork databases in the back end.
I posted about this here in August: "Roadmap towards a Mork-free address
book back-end".
Beyond that is unclear. I believe there are moves at Council to provide
more manpower (or womanpower, just as good) for the address book effort.
Got it, thanks Geoff.
Hi Geoff,
thanks for the info (I am a bit late, sorry).
If the mutable methods have no effect anymore, what is the correct way
to do it now? For WX I assume there is no change and we use
MailingListNode::contacts, but how do we do it in WX Experiments?
Thanks,
John
Am 16.10.2019 um 04:06 schrieb Geoff Lankow:
As part of the address book backend work, the addressLists
property
still returns an nsIMutableArray, but the mutable methods have no
effect. You should check your extension code does not use them.
GL
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
Assuming you have an nsIDirectory, use the addCard and deleteCards
methods, or the addMailList and deleteDirectory methods for handling
mailing lists.
GL
On 06/11/2019 04:31, John Bieling wrote:
Hi Geoff,
thanks for the info (I am a bit late, sorry).
If the mutable methods have no effect anymore, what is the correct way
to do it now? For WX I assume there is no change and we use
MailingListNode::contacts, but how do we do it in WX Experiments?
Thanks,
John
Am 16.10.2019 um 04:06 schrieb Geoff Lankow:
As part of the address book backend work, the addressLists
property
still returns an nsIMutableArray, but the mutable methods have no
effect. You should check your extension code does not use them.
GL
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net