Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of agrieve@google.com designates
 209.85.214.175 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
In-Reply-To: 
 <CAM1AYQAUTTPbjrCL_QRGG-rss-nNnJW3gTcyysefrgPgzaaOpA@mail.gmail.com>
References: <CC63D9FA.C5EC%fil@adobe.com>
 <CAM1AYQAUTTPbjrCL_QRGG-rss-nNnJW3gTcyysefrgPgzaaOpA@mail.gmail.com>
From: Andrew Grieve <agrieve@chromium.org>
Date: Wed, 29 Aug 2012 22:56:01 -0400
Message-ID: 
 <CABiQX1WXP-L+i=5dhxHkrkA9jN-bokdy__0XY0HQ8DHCr=pzgQ@mail.gmail.com>
Subject: Re: [iOS] Echo Plugin
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d0447868ff89d3604c872d1eb

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

Agree that this plugin is useless outside of testing. The relevant testing
code is in mobile-spec, and the idea is that any platform that adds an echo
plugin will be able to benchmark their bridge using the mobile-spec page.
I'm also planning on adding an automated mobile-spec test that loops
through all bridge modes and ensures that they work (for all platforms that
support multiple modes).

I didn't want to add another step that would be needed in order for the
mobile-spec to work. There is already:
 - generate a project
 - link in the mobile-spec directory
 - Generate and copy in fresh JS
 - add sites to whitelist

Quite likely the command-line tools could make this easier though... Then
we could write a script to generate the mobile-spec project?

For now, I was thinking the echo plugin would exist, but not be required to
be implemented by all platforms, and that we would not document it. I don't
think there's much risk of project making use of it, so it will be easy to
move it out once things are in place.


On Wed, Aug 29, 2012 at 8:20 PM, Simon MacDonald
<simon.macdonald@gmail.com>wrote:

> The same plugin exists in Android and I agree with you Fil. This stuff
> should get moved off to a testing directory. In fact the Android repo has a
> test sub-directory it would fit right into.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
> On Wed, Aug 29, 2012 at 5:38 PM, Filip Maj <fil@adobe.com> wrote:
>
> > I noticed there was an additional plugin added to the core iOS plugins.
> > May I ask why?
> >
> > At this point if we're adding (core) plugins to implementations, keeping
> > with the cross-platform spirit of the project, at the least all other
> > implementations should have it as well, and it should be documented,
> > unless we are covering/polyfilling some specific issue/weakness in a
> > platform.
> >
> > I don't think having this plugin be a part of the core iOS framework
> helps
> > 99.9% of users consuming cordova. Just adds more kbs to the framework. If
> > it is for testing/benchmark purposes then it should exist in a
> > testing/benchmark project.
> >
> >
>

--f46d0447868ff89d3604c872d1eb--