Thanks Simon for the research into this. I think it makes sense to add this functionality as part of the "extras" intent as you specified, I like this approach.
On Sun, Aug 19, 2012 at 7:55 PM, Simon MacDonald <simon.macdon...@gmail.com> wrote: > It's true. It is a major pain for Android as well where your contacts can > be from Google, Exchange, Twitter, Facebook, etc. I'm not a big fan of > trying of deviating from the W3C spec. Whenever we've done that we end up > running into problems see Media and FileTransfer for instance. > > Instead, if you look at the latest version of the Contacts API spec: > > http://www.w3.org/TR/contacts-api/ > > You now search for contacts using WebIntents ( > http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html). It > would make more sense to me that we move towards the new spec. As part of > that spec when searching for a contact you can pass in "extras" one of > those "extras" could be the contact account type that you want to search > for. > > Comments? > > Simon Mac Donald > http://hi.im/simonmacdonald > > > On Sat, Aug 18, 2012 at 6:12 PM, Olivier Louvignes <oliv...@mg-crea.com>wrote: > >> I've needed to be able to filter the "account source" when using >> `navigator.contacts.find(contactFields, contactSuccess, contactError, >> contactFindOptions);`. >> So I created a patch a submitted a PR on github ( >> https://github.com/apache/incubator-cordova-ios/pull/33). However, Becky >> Gibson was reluctant to proceed with the merge as it deviated from the W3C >> spec. >> So I've been asked to bring this up here for further debate : >> >> My point : >> >> Every mobile OS as a per-account contact setup, being able to filter out >> some accounts (ie. Exchange) can lead to a real boost in performance for >> our mobile apps (as a few thousand contacts eat up quite a lot of memory >> once loaded). >> Wouldn't it be cordova's role, to implement this (in a non-breaking way) & >> to bring this up to the W3C as something needed that requires >> standardization? Browser vendors do not wait for the W3C to freeze things. >> >> Regards, >> Olivier >>
