Config.xml introduces redundancy in terms of specifying app metadata in some cases. How are we going to consolidate the two places where some app info can be specified?
Specifically, I am thinking of app name: you can use either the create script to specify the app name, and now presumably also specify it via config.xml. I can see the create script writing out a config.xml with the specified name. What about later on (say you want to change the app name in an already-generated project)? Are we going to provide tooling that will look inside the config.xml and update the relevant native bits? On 6/11/12 4:50 PM, "Brian LeRoux" <[email protected]> wrote: >We have a proliferation of manifest-like files that are, mostly, XML. > >iOS >- [APP_NAME]-Info.plist >- Cordova.plist > >Android >- plugins.xml >- cordova.xml > >BlackBerry >- config.xml <---yay >- plugins.xml <---wait, wat > >WindowsPhone >- ? > >Bada >- config.xml <--- yay > >* * * >I created a parent issue [1] to resolve these into the W3C Widget >Specification config.xml [2]. I think the best way would be to keep >the existing files but add support for the config.xml file (which >compiles into the other files). There is prior-art in the form of >PhoneGap/Build [3]. > >This will have the added benefit of bringing more of the small >inconsistencies to light (such as the plugin load issue recently >discussed that uncovered this one)! > > >[1] https://issues.apache.org/jira/browse/CB-888 >[2] http://www.w3.org/TR/widgets/ >[3] https://build.phonegap.com/docs/config-xml
