Hi,
I have just pushed release v0.3.0 out. Visit the project page at:
http://karra-asynk.appspot.com/ to get the latest downloads and
documentation.
Key improvements are:
1. ASynK now ships with two default sync profiles called: "defgcbb" and
"defgcol", so there is out of the box support for what should be the most
common use cases - synching entire ~/.bbdb or outlook contacts folder with
google contacts. (Thanks to John Wiegley for the idea)
2. ASynK now uses ~/.asynk/ as the directory to store all state
information, logs and backups. Thus you can now have a single installation
of ASynK for all users in your system, and they will each get .asynk/
directory in their home directories. If you have any existing sync profiles
and state, ASynK will notice this, and migrate your current sync state to
the ~/.asynk/ directory. You can override the default directory name by
passing the --user-dir command argument to any invocation of ASynK. (Thanks
to Ivan Miljenovic for the idea)
3. ASynK can now be invoked from anywhere; earlier you had to ensure the
present working directory was the root of the asynk source directory.
(Thanks to Ivan Miljenovic for the idea)
*Important Note*: The above two changes together imply that if you have
existing sync state you want migrated, the first run after your upgrade to
v0.3.0 should be from inside ASynK directory for us to be able to locate
your config and state. Subsequent runs can be done from anywhere and we
will pick up your stuff from ~/.asynk/
4. Bug fix: Google Contacts' multiple group membership information is
now correctly synched back and forth to BBDB and Outlook.
5. Bug fix: The first email address in the BBDB email list is treated as
the primary address, and marked accordingly in Google Contacts. Without
this the order the email addresses in BBDB could have appeared random, and
changing from one sync to another.
Complete ChangeLog is as follows:
=======
Cardassia:ASynK sriramkarra$ git log v0.2.2..v0.3.0
commit 9754ba863aa9ac753cae8724c02c3dd2f70d2640
Author: Sriram Karra <karra....@gmail.com>
Date: Thu Jul 5 15:12:47 2012 +0530
Bumping up version to v0.3.0 for release
commit 3f13dc331e7e758641d066d5f304a463e00a976f
Author: Sriram Karra <karra....@gmail.com>
Date: Thu Jul 5 15:09:11 2012 +0530
Updates to the project website related v0.3.0 releaes
commit 825ec98d8eef67ea8c6e83f3598852c855de5f11
Author: Sriram Karra <karra....@gmail.com>
Date: Thu Jul 5 15:07:14 2012 +0530
Stashing away code to track primary phone number
Similar to an earlier commit where we tracked the primary email
address and made it the first email in the BBDB list, we should be
tracking phone numbers as well. However the primary field for phone
numbers is not really set by Google properly (as best as I can see).
This diff is really an attempted patch which can come in handy if
and when we decide to explore this problem in more detail at some
point.
commit bf3c4a6d7d7afe0cea16da2396a1c481b5ee53a4
Author: Sriram Karra <karra....@gmail.com>
Date: Thu Jul 5 14:42:27 2012 +0530
new test_print_item in test_gc.py to print google contacts.
commit d055a49dbd44709cd15b93a363e6705b852f396c
Author: Sriram Karra <karra....@gmail.com>
Date: Thu Jul 5 12:58:21 2012 +0530
First element of email list in BBDB will be treated as the primary
address
Gmail has a flag to identify the primary email address. In Emacs,
bbdb sets the first email address for tab completion and for completing
using the mail-alias field etc. So preserving this semantics is good.
This is what we acheive with this commit - ensure that the first
email is treated as the primary address - while reading as well as
when writing out to the BBDB database.
commit 039a6a370c9139b6649b83fde41ce8215fd37e27
Author: Sriram Karra <karra....@gmail.com>
Date: Thu Jul 5 08:27:25 2012 +0530
Doc update for default profile run in the Recipes section.
commit e7747466dcced7a2329dead9ff140c7d18f4e2be
Author: Sriram Karra <karra....@gmail.com>
Date: Thu Jul 5 08:19:52 2012 +0530
Doc and README updates for recent changes
- Mention the ~/.asynk/ directory stuff
- Mention the defaut sync profiles
commit 9e486688fc4ba69fb04bc6f3979dc7e440892174
Author: Sriram Karra <karra....@gmail.com>
Date: Tue Jul 3 11:31:01 2012 +0530
Create a test/gold/ regression test suite - albeit with limited
coverage for now
commit 2c6a01b2ae0ad0982bd739dbc431dfc38fd1bcf6
Author: Sriram Karra <karra....@gmail.com>
Date: Tue Jul 3 08:17:15 2012 +0530
Update test_state.py to work with recent changes to state/config jsons
commit 32f1ed7d7f504e9a9dd922da5b7ae5c1ea9d271a
Author: Sriram Karra <karra....@gmail.com>
Date: Tue Jul 3 07:46:42 2012 +0530
Move the unit test code from pimdb_gc.py to test/test_gc.py
commit 3ad3b9f3bc3781018b59f346a256e8be9dfa3ab2
Author: Sriram Karra <karra....@gmail.com>
Date: Mon Jul 2 22:50:37 2012 +0530
Use sane defaults for store and folder ids if they are null in config
This is the final step needed to support a 'sane' sync option
with minimal configuration.
Basically, if a user has just fetched ASynK, the most likely common case
scenario will be to just sync his entire BBDB to the My Contacts folder
in Google Contacts, or defaults contacts folder in Outlook to Google.
With this commit that is possible.
The way this is enabeld is any gc sync profile without a folder id is
synhed to the My Contacts folder. If a store id is also missing a
google contacts username is prompted for, and stored in the default
storeid
field. A similar "logical" thing is done with Outlook.
commit 4894b656b1e507d972f17d2ae539d21a00ee63eb
Author: Sriram Karra <karra....@gmail.com>
Date: Mon Jul 2 22:49:52 2012 +0530
Set the default contacts folder to My Contacts during google contacts
setup
commit 524b65a30f0ea27a5267b78cb547b9df210cea54
Author: Sriram Karra <karra....@gmail.com>
Date: Mon Jul 2 22:47:16 2012 +0530
Two default profiles in state.init.json
- Have a default gc-ol and a gc-bb profile set up in the
initial state json. Just setting th stage for a 'default'
sync profile for newbies or first time users
- helper routines to enable the folder and store ids to be
written to the state.json; so far we did not need this
support
commit c0ef07d4a8c19da32e0350cfb781ac7e32482aa7
Author: Sriram Karra <karra....@gmail.com>
Date: Mon Jul 2 16:48:08 2012 +0530
cleanup Asynk constructor to remove unwanted None value for config
parameter
commit 1fc744792701a696735392aaed987923ac0bb962
Author: Sriram Karra <karra....@gmail.com>
Date: Mon Jul 2 11:35:11 2012 +0530
Store all the group memberships of google contacts
Previously only the "active" folder (i.e. the folder in the currently
processed sync profile) was saved and restored. This meant that any
contact which was marked as being in multiple google contact groups,
lost information about its other group membership. now this is fixed.
commit fabdc0cc2165c7fc4215ba29d9cc559dd28fef0a
Author: Sriram Karra <karra....@gmail.com>
Date: Sun Jul 1 14:05:53 2012 +0530
BBDB Stores can be relative to user home dir
If the BBDB store id starts with ~, then expand it like one
would expect in a unix environment.
commit e59e3c41a88955b13124fe17ce79ab0e2a4f24e7
Author: Sriram Karra <karra....@gmail.com>
Date: Sun Jul 1 12:27:33 2012 +0530
Make ASynK installable in a central directory and have per-user config
dirs
With this change, ASynK will try to use ~/.asynk/ as the configuration
directory to contain config.json and state.json. Also the logs and
backups
directory will be stored here.
Note that this cannot be changed through a config.json variabel as this
directory itself is needed to locate config.json. The following
heuristic is used:
Asynk user directory is set to either ~/.asynk or the value of
--user-dir
command line argument. If ~/.asynk/ is empty then the state.json and
config.json files are copied from the asynk application root directory.
This will help older users to transparently migrate their config and
state
files to the new location without havign to do anything else.
Finally, made asynk.py executable so it can be executed directly.
commit a1876a8d9cebda3873058e7ddc7fefdc2dc18f52
Author: Sriram Karra <karra....@gmail.com>
Date: Sun Jul 1 11:14:47 2012 +0530
Add iso-8859-1 to trial list; unlikely to add coverage, but wth...
commit 70fbf5b3ad9ed27eb74bf514a88d37c85b9cb909
Merge: 7492c2b 733dbfd
Author: Sriram Karra <karra....@gmail.com>
Date: Mon Jun 18 18:41:37 2012 -0700
Merge pull request #14 from jdodds/fix-gmail-nonetype
Make sure that entry.name is valid before dereferencing
commit 733dbfdbe42bd7d90fc6a9734803ebe9565d777e
Author: Jeremiah Dodds <jeremiah.do...@gmail.com>
Date: Mon Jun 18 13:15:31 2012 -0400
make sure that entry.name is truthy before checking values on it
commit 7492c2b2aa6d8ca973bdecb04b4ca4035af2a254
Author: Sriram Karra <karra....@gmail.com>
Date: Sat Jun 16 19:35:33 2012 +0530
GAE: Add links to mailing list and twitter handle
commit ff265360b7d248f9c30c4957fba9c74f71fd9813
Author: Sriram Karra <karra....@gmail.com>
Date: Fri Jun 15 07:36:43 2012 +0530
Bumping up version to v0.2.2+ for development
------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
