So, for example, suppose I decide to make some changes to a contact – I add some email addresses, remove a phone number, and change a birthday. My add-on will be able to calculate diffs between records, and those diffs can be applied on top of records to make changes. I briefly toyed with throwing my own indexing layer on TOP of indexedDB, and then I realized that I was probably reinventing the wheel.Ĭontact records are a representation of the fields and meta data about a contact.

I was originally toying with using indexedDB, but it’s lack of support for substring searches (which is necessary for things like auto-complete) wasn’t very appealing. I’ve chosen to use SQLite (via mozStorage) for the contact database. Here are some highlights, implementation details and unstructured thoughts about the add-on, and where I’m going with it: SQLite Storage Back-end There’s no UI yet, but there are some tests. The add-on is in its very very early stages. I’m calling it “Thunderbird Ensemble”, because every project needs a cool code name. In short, I’m writing an add-on to experiment with approaches to a new address book. I’ve been pretty busy helping to get Instant Messaging shipped for TB 15.īut with IM polished off, I’ve (once again) started refocusing my attention to the address book. I’ve been pretty bad about talking about the address book.

Thunderbird google contacts