Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of agrieve@google.com designates
 209.85.192.181 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
In-Reply-To: 
 <CADVgkyNjnu2==PO9gsJog1PhNcC03kGZGJ0yA8ofbBp+L1Fh6A@mail.gmail.com>
References: 
 <CAEeF2TeTjq48hnPqJVnNSt=FXDr2N6RyEJj9-Ew9RPcmXALQiQ@mail.gmail.com>
 <CE2AB77A.23BD9%fil@adobe.com>
 <CADVgkyNjnu2==PO9gsJog1PhNcC03kGZGJ0yA8ofbBp+L1Fh6A@mail.gmail.com>
From: Andrew Grieve <agrieve@chromium.org>
Date: Mon, 12 Aug 2013 10:30:42 -0400
Message-ID: 
 <CABiQX1W-yB54u5tn3UvGwCNQtuc3CVMkSkBv94yJsOAbgju6uw@mail.gmail.com>
Subject: Re: Cordova-js in a 3.0 world
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7b86f77e49228704e3c0f9a0

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

On Fri, Aug 9, 2013 at 6:30 PM, Brian LeRoux <b@brian.io> wrote:

> I'm very interested in the idea of getting as much of our architecture
> broken into discreetly reusable bits.
>
> Feels like those might be just best as vanilla node modules.
>
> On Fri, Aug 9, 2013 at 3:13 PM, Filip Maj <fil@adobe.com> wrote:
> > Ideas are neat, sure :) what I want to know is what caused the ideas to
> > come up in the first place? What scenarios exist that these cases would
> be
> > beneficial? I am simply searching for grounding, not shooting them down.
> >
> > On 8/9/13 2:18 PM, "Michal Mocny" <mmocny@chromium.org> wrote:
> >
> >>Andrew originally wrote: "Of these, the only one I think is actually a
> >>good
> >>idea is #1, but thought it might be neat to talk about the others."
> >>
> >>
> >>On Fri, Aug 9, 2013 at 3:04 PM, Filip Maj <fil@adobe.com> wrote:
> >>
> >>>
> >>> >Idea #1: Separate plugin helper APIs into distinct plugins
> >>>
> >>> Makes perfect sense to me.
> >>>
> >>> >Idea #2: Separate exec bridge into a plugin
> >>>
> >>> What's the rationale behind this?
> >>>
> >>> >Idea #3: Put the pluginloader with plugman so that it can load the
> exec
> >>> >bridge plugins
> >>>
> >>> I think the concept of loading plugins belongs in the JS, so it should
> >>> remain in cordova-js.
> >>>
> >>> >Idea #4: Put start-up logic in a plugin
> >>>
> >>> It sounds like ideas 2-4 are all related. What is your vision here,
> >>>Andrew?
> >>>
> >>>
> >
>

I was trying to see how much of cordova-js could be split out.

e.g. Maybe we could even get to the point where we don't have a cordova-js
so that platform JS is closer to the native platform code.
e.g. Maybe we wouldn't have to copy in cordova.js for each platform
release, and instead just have a platform depend on a plugin
"cordova-plugin-corejs". We could then have JS patch release updates happen
independently from the native code. Right now plugins are easier to update
than platforms.

--047d7b86f77e49228704e3c0f9a0--