Milestone
0.3.1
“This is a really critical step. Sync is a major component of Ensemble, and we need to get this right.”

Do plan any synchronization capabilities of the address book with an external server? This is not an request or something like that, i was just interesting if this is in on our roadmap.

Regards,

Konstantin

User selectable phone prefix+area code display formats. Seriously. This needs to happen.

As an example, in my current address book, I have contacts whose numbers are presented in the following ways;

8881112222
(888)-111-2222
(888) 111-2222
+1 (888)-111-2222
+1-(888)-111-2222
etc.etc…..

As you can see, this is obnoxious to look at, and while I and many others love and appreciate the FLOSS philosophy, sometimes being able to enforce a particular standard, even if it is a choice of many different standards, is a better solution than to present none at all.

Thanks, and thank you for all your hard work!

For details see:
http://java.net/nonav/projects/jitsi/lists/users/archive/2013-01/message/60

Thanks a lot for all those updates.

It is REALLY GOOD, and I really mean REALLY, REALLY GOOD, to sense that this time (with you) there is some serious work done on this TB AB.
I hope Mozilla let’s you stay on this project and bringing it to the finish line. Like until it is merged into the core code.

Since I am not a programmer / coder and I can’t help you on this front. But let just my (supportive) words assure you, that we appreciate your work VERY, VERY much.

And if there is a chance to test the add-on in a save manner (like with a secondary AB, beside the AB with live data, or something alike), then I would be glad to do some testing.

Good luck with with those new JS code, hoping it takes some monkeys of your shoulder.

Looking forward to the first beta (test) release.

Thanks.

-Rolf

I’ve been traveling for a few days, and I’ve recently begun exploring an alternative implementation approach for the address book. Up until now, I’ve been developing my own utilities for manipulating contacts, and had begun writing my own code to save those contacts to the database.

A colleague of mine has introduced me to Backbone.js and Underscore.js, and I’m currently evaluating them as possible replacements for my hand-rolled approach.

I hope to have a roadmap, as well as a structure for getting the community involved soon. Soon, as in end of October, if I’m lucky / things go my way. That’s tentative, and please don’t hold me to that.

-Mike

The way I’ve been approaching the new address book is to maintain contacts in an intermediate format (a Javascript object, easily serializable to JSON, and highly interoperable with DOM Contact).

Exporting and importing from various sources is a requirement of my design, and the ability to register connectors to various source types is also a requirement.

For static files, VCard, CSV and LDIF are on my export radar – both for individual and groups of contacts.

I’m developing this feature as an add-on simply to make it easier to iterate on the design and (eventually) allow people to try it and give me feedback without having to prepare special builds. The eventual goal is to merge what I create (or a feature equivalent representation) into the core code.

I’m hoping to have the code in a state where the community can get more involved soon!

-Mike

Thanks. Bit by bit it’s moving forward.