+1 transition period. +1 to combining plugins.xml and cordova.xml into config.xml
Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jul 10, 2012 at 12:15 PM, Michael Brooks <[email protected]> wrote: > +1 transition period. > +1 using build.phonegap.com/ docs as a reference point. > > We should take steps to feed out experiences and input back into the W3C > Community Group (Native Web group) and eventually see it pushed into the > main W3C Widget Configuration Document. > > Michael > > On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <[email protected]> wrote: > >> +1 transition period. >> >> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml. >> >> We should definitely have a discussion about formatting! Starting point in >> my mind would be build.phonegap.com docs for their use of config.xml. Off >> the top of my head and from 35,000 feet: >> >> - <plugin> elements from plugins.xml map to <feature> elements in W3C >> config.xml. >> - <access> elements from cordova.xml already follow the <access> element >> in config.xml. >> - same for <preference> >> >> P.S. BlackBerry WebWorks already does all of this so we get it "for free." >> >> On 7/9/12 4:25 PM, "Brian LeRoux" <[email protected]> wrote: >> >> >thinking we should add support for config.xml before we remove >> >anything...have a transition period ala deprecation policy >> > >> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <[email protected]> wrote: >> >> Hey >> >> >> >> Are we just merging the blacklist and the cordova.xml to make it one >> >> config.xml, or are we having a discussion about the format? Given >> >> the timeframe for this release, is this something that we want to have >> >> for 2.0? >> >> >> >> Joe >> >>
