You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2014/02/10 16:51:20 UTC
[jira] [Commented] (CB-5995) Plugin spec config-file target could
also point to an html file
[ https://issues.apache.org/jira/browse/CB-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896707#comment-13896707 ]
Andrew Grieve commented on CB-5995:
-----------------------------------
As a work-around for now, you can add a native side to your plugin that the JS side can use (via exec()) to get this value.
Longer term, I agree that we should have a JS API for accessing config.xml information.
> Plugin spec config-file target could also point to an html file
> ---------------------------------------------------------------
>
> Key: CB-5995
> URL: https://issues.apache.org/jira/browse/CB-5995
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugman
> Affects Versions: 3.3.0
> Reporter: Sebastien
> Labels: features
>
> I wrote the GapReload (https://github.com/fingerproof/cordova-plugin-gapreload) plugin which used to access www/config.xml to read CLI passed values.
> But since Cordova 3.3, this file has been moved to the project root and I can't access stuff outside the www folder using pure JavaScript.
> So here are the ideas I came up with:
> - Allow plugins to also add stuff to html files (config-file target="www/index.html"), not only xml and plist files. This should be relatively easy to implement, right?
> - Or write a plugin that would provide JavaScript developers with access to CLI passed plugins options inside the app itself.
> Please, could you consider implementing at least the first one? Thanks.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)