opensubscriber
   Find in this group all groups
 
Unknown more information…

b : bbdb-info@lists.sourceforge.net 15 May 2012 • 5:55PM -0400

Re: Announcing ASynK v0.2.0 - directional sync for BBDB to Google and Outlook
by JJ

REPLY TO AUTHOR
 
REPLY TO GROUP




On Sun, May 13, 2012 1:01 pm, Sriram ET. wrote:
> I am happy to announce release v0.2.0 of ASynK. You can find documentation
> and links to source and pre-packaged bundles at the project page at:
> http://karra-asynk.appspot.com/

Thanks a lot for this gem, Sriram.

I'd like to ask whether you could expand it to enable me to think contacts
between BBDB and an Android phone database.

One might think, the Google contacts functionality takes care of that,
however my user case is slightly different. Basically, I run Android on
the phone, but want to block out Google functionality for certain parts,
specifically, I DON'T want Google to have access to my contacts.

So I only have the contacts locally on the phone and don't sync with Google.

Haven't explored what format the Android contact database is. Would it be
possible to extent ASynK to sync directly between BBDB and the phone's DB?
If not, I assume I could export and import from the phone's DB to a vcard
format, could you then expand ASynK to sync a vcard folder with BBDB?

Thank you very much for your work.
--
JJ


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
bbdb-info@list...
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.