maybe a new file cordova.xml for CLI scenario?
On Thu, Sep 26, 2013 at 1:40 PM, Braden Shepherdson <bra...@chromium.org>wrote: > This discussion is getting a little tangled, with CLI and not-CLI and so > on. I'm trying to bring together the current situation: > > In CLI: there is a top level myproject/www/config.xml. This file is > *accidentally* copied into www/config.xml in each platform. > > A **totally different file** with the same name is also generated by the > CLI, based on settings from the defaults.xml, plugin <config-file> edits, > and the top-level config.xml. This file is placed in > platforms/android/res/xml/config.xml on Android, in > platforms/ios/MyProject/config.xml on iOS, and other places. > > I repeat, the platforms/android/res/xml/config.xml and > platforms/android/assets/www/config.xml are **different**. > > It's the top-level www/config.xml that we want to give <platform> tag > support to, so that you can set platform-specific things without editing > the config.xml files inside those platforms. > > Not-CLI: Just the latter file, in eg. res/xml/config.xml. Edited by hand, > always specific to this platform. > > As far as the standards, it's the latter, res/xml/config.xml, that sort-of > matches the widget spec. The top-level Cordova one doesn't, and we're > moving farther away with adding <platform> tags. > > Braden > > > On Thu, Sep 26, 2013 at 1:28 PM, Jonathan Bond-Caron < > jbo...@gdesolutions.com> wrote: > > > On Thu Sep 26 10:18 AM, Braden Shepherdson wrote: > > > I am strongly opposed to splitting into one file per platform. We want > > to support > > > <platform> tags in config.xml, which will allow platform-specific > > content within > > > the single config.xml. > > > > > > > +1, a single configuration file not in the www/ folder > > > > > -- Carlos Santana <csantan...@gmail.com>
