You mean mapping from config.xml to plist / androidmanifest / whatever right? If so yes we need that :)
In the future when we ship without core plugins it should also, on android at least, add appropriate permissions for the various plugins. -d On Friday, March 22, 2013, Filip Maj wrote: > The platforms already look at config.xml at runtime to load plugins, set > certain app preferences, etc. > > The one thing that this current functionality can't do (in most cases I > think) is changing certain bits of app metadata before compile-time. > Things like app package/id and app name. Maybe other stuff down the road > like splash screens and icons as well. > > So a question brought up in the meeting today is: should we add another > project-level script that will handle this (and presumably be called by > the `build`/`compile` script) > > On 3/22/13 10:32 AM, "Brian LeRoux" <[email protected] <javascript:;>> wrote: > > >Right now the cordova-cli has a lot of logic looking at parsing the > >config.xml and some stuff is existing in the platforms. This is more > >of a discussion thread for that. I don't have any concrete to talk > >about here but Fil can elaborate. > >
