Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of simon.macdonald@gmail.com
 designates 209.85.160.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAE6O_-Y=zZsbh88TOWiJsnjdLsBgSR1ZrvNnzPuguA75111XWA@mail.gmail.com>
References: <21F4B96DB2DB41D4AE30869499851D87@mg-crea.com>
 <CAM1AYQCkqF4zK_TyFpGo1k7GBVc79P5oWTnAimOYAOUO0mcGKg@mail.gmail.com>
 <CAE6O_-Y=zZsbh88TOWiJsnjdLsBgSR1ZrvNnzPuguA75111XWA@mail.gmail.com>
From: Simon MacDonald <simon.macdonald@gmail.com>
Date: Mon, 20 Aug 2012 06:51:26 -0400
Message-ID: 
 <CAM1AYQCTtH-ZRZeMyu2jFrKBY0S2rK5Vo4VT4r7h4KuO+BCcaA@mail.gmail.com>
Subject: Re: Adding a new option to the W3C contactOptions item
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b33da8edb069304c7b04b3c

--047d7b33da8edb069304c7b04b3c
Content-Type: text/plain; charset=ISO-8859-1

Looking at the bigger picture we need to do a full review of all of the W3C
API's we've already implemented and see which ones need to be updated and
start scheduling them.

Simon Mac Donald
http://hi.im/simonmacdonald


On Mon, Aug 20, 2012 at 12:50 AM, Shazron <shazron@gmail.com> wrote:

> 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.macdonald@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 <olivier@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
> >>
>

--047d7b33da8edb069304c7b04b3c--