st causes your
> .js file to be executed after cordova.js is parsed.
>
> I think with this, you could layer on another module loading system if you
> wanted something outside of the cordova.define() system.
>
> Does that make sense?
>
>
>
>
> On Fri, Jun 21, 2013
t use alternate module
> package definitions?
>
>
> On Fri, Jun 21, 2013 at 9:39 AM, J Prince wrote:
>
> > Hi Andrew,
> >
> > My main point was to make the actual plugin javascript definitions more
> > flexible.
> > That way it would support more unusual
; about the native side of the plugins?
>
> One thing I think maybe we should add is the ability to disable the
> start-up plugin_loader.js logic for when people want to package the .js
> themselves.
>
>
>
>
>
> On Fri, Jun 21, 2013 at 8:30 AM, J Prince wrote:
>
> >
as needed.
>
> My suggested approach would result in plugins that could be loaded in
> multiple different ways including (but not limited to); "classic"
> window.plugins, cordova.define and require.js
>
>
> > -Original Message-
> > From: J Prince [ma
ll your requirements.
>
>
> -Original Message-
> From: J Prince [mailto:princej.w...@hotmail.co.uk]
> Sent: Monday, June 17, 2013 7:27 AM
> To: dev@cordova.apache.org
> Subject: RE: Suggestion - pluginLoader
>
> There are a few main reasons.
>
> 1. Th
There are a few main reasons.
1. The app I am working on is an Enterprise app. We are designing the app as a
Cordova shell that re-directs to all the html content. This means that we have
to dynamically load a different cordova.js (depending on platform) following
the redirect.
So we are actual
In my project I wanted to dynamically load plugin modules (with require.js).
However the current suggested module definition
(https://github.com/phonegap/phonegap-plugins/wiki/Defining-Your-Cordova-Plugin-As-A-Cordova-Module)
does not suit this approach.
I would like to suggest an alternative a
