incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <>
Subject Re: [iOS] Echo Plugin
Date Thu, 30 Aug 2012 02:56:01 GMT
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

> 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
> On Wed, Aug 29, 2012 at 5:38 PM, Filip Maj <> 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.
> >
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message