cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve H (JIRA)" <>
Subject [jira] [Updated] (CB-5671) facilitate dynamic loading of cordova plugins
Date Thu, 06 Mar 2014 14:38:43 GMT


Steve H updated CB-5671:

    Attachment: Screen Shot 2014-03-06 at 8.49.27 AM.png

[~agrieve] Yeah, 3.4.0   I've attached this screenshot of the debugger.  

> facilitate dynamic loading of cordova plugins
> ---------------------------------------------
>                 Key: CB-5671
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: CordovaJS
>    Affects Versions: 3.2.0
>         Environment: any
>            Reporter: Jon Whitlock
>            Assignee: Andrew Grieve
>              Labels: javascript
>         Attachments: Screen Shot 2014-03-06 at 8.49.27 AM.png
> Problem: Cordova expects resources to be loaded off the device filesystem.
> 1) On iOS this is very risky due to the turnaround time pushing hotfixes through the
App store.
> 2) In complex JS applications one needs to use a loader like require.js to manage async
loading (especially on mobile) & module dependancy management (as cordova does internally).
> 3) When integrating with many 3rd-party services like auth/"social login" one needs to
have a public-facing page to call back to.
> Use case: We have a bunch of prereqs before cordova.js loads, so we have to load cordova.js
using require.js.  However to show localised error messages we need the preferred language
from the device to know which language to show messaging in, so we need cordova loaded as
part of auth prerequisites.
> Problematic Assumptions:
> a) findCordovaPath() assumes a script tag in the document loaded cordova.js -- not the
case with require.js or similar.
> b) injectPluginScript() assumes that cordova_plugins.js is in the same dir as cordova.js
> So using plugins & dynamically loading Cordova is terminal, unless I hack findCordovaPath()
to return (in our case) the path where cordova.js is to be found -- which is defined in a
JS configuration file.
> I think it would be more robust to define the location of those file(s) in a config file
somewhere -- which could also facilitate dynamic loading of cordova.

This message was sent by Atlassian JIRA

View raw message