incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Becky Gibson (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-223) Add support for iOS contact groups
Date Tue, 07 Feb 2012 17:14:59 GMT


Becky Gibson commented on CB-223:

Yes, categories was not part of the August, 2010 W3C Contacts API specification so it did
not get implemented.   We did add the field into the Contacts object when we updated to the
Dec, 2010, version of the spec. but it didn't get implemented.  

We can easily find a list of all groups and get members of the group.  However, there does
not seem to be a direct correlation from a person record to a group record - making determining
what group a person record belongs to a fairly difficult search.  Thus, any time that categories
is added as a search term, it is going to require a more complicated search algorithm. 
> Add support for iOS contact groups
> ----------------------------------
>                 Key: CB-223
>                 URL:
>             Project: Apache Callback
>          Issue Type: New Feature
>          Components: iOS
>    Affects Versions: 1.4.0
>         Environment: iOS
>            Reporter: Robert La Ferla
>            Assignee: Shazron Abdullah
>            Priority: Minor
>              Labels: addressbook, categories, contacts, groups, ios
> Contacts on iOS are organized by group.  There is the default group "All Contacts" plus
any custom groups that the user set up.  Contacts retrieved by Apache Cordova / phonegap do
not contain which group they are in. 
> I believe that iOS groups are analogous to phonegap contact categories and thus should
be mapped to them.  If not, another property should be created.
> From the Cordova docs:
> "categories: An array of all the contacts user defined categories. (ContactField[])"
> In the iOS AddressBook API, the function ABAddressBookCopyArrayOfAllGroups() gets the
list of groups.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message