I don't understand at all what you're suggesting. Nobody is proposing adding any new files.
We have a bug filed to remove the unused accidental duplicates, other than that I don't think much is going to change here. At least we'd need a compelling reason to be moving and renaming files. In the non-CLI world, there's one file to edit, done. In the CLI world, there's still one file to edit (top-level www/config.xml) and the rest is CLI magic you don't need to care about as an app developer. I don't see how we can improve on one central place to edit. Braden On Thu, Sep 26, 2013 at 2:05 PM, Carlos Santana <csantan...@gmail.com>wrote: > we have one config.xml today lets keep it but lets not add a different file > with same name config.xml in a different location. > > maybe I got completely lost in your explanation, sorry :-( > > > On Thu, Sep 26, 2013 at 2:01 PM, Braden Shepherdson <bra...@chromium.org > >wrote: > > > I'm not sure which file you're suggesting that we rename. We have talked > in > > the past about moving the top-level one out of www and calling it app.xml > > or similar. I don't think there are any plans to rename the > > platform-specific ones. > > > > Braden > > > > > > On Thu, Sep 26, 2013 at 1:59 PM, Carlos Santana <csantan...@gmail.com > > >wrote: > > > > > 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> > > > > > > > > > -- > Carlos Santana > <csantan...@gmail.com> >
