Not sure if we agreed or there was a consensus on having one xml file to rule them all, and the timeline. If so, jira issues should be created
On Thu, Jun 7, 2012 at 11:45 AM, Brian LeRoux <[email protected]> wrote: > this is getting meta. maybe we should make it transport agnostic so > that ppl could use json or yaml. > > /me ducks > > (In seriousness having one xml file for this business would make good sense.) > > On Thu, Jun 7, 2012 at 11:35 AM, Dave Johnson <[email protected]> > wrote: >> Speaking of which, we should probably merge plugins.xml and >> cordova.xml on android. >> >> On Fri, Jun 8, 2012 at 4:26 AM, Shazron <[email protected]> wrote: >>> Yeah we are switching I believe, so maybe this should be a 2.0 or post >>> 2.0 item then since it's a breaking change? >>> >>> >>> On Thu, Jun 7, 2012 at 11:20 AM, Patrick Mueller <[email protected]> wrote: >>>> On Thu, Jun 7, 2012 at 9:08 AM, Simon MacDonald >>>> <[email protected]>wrote: >>>> >>>>> On Android if you want to load a plugin on start up of the app you >>>>> just need to tag the plugin with the "onload" attribute set to "true". >>>>> For instance: >>>>> >>>>> <plugin name="SplashScreen" value="org.apache.cordova.SplashScreen" >>>>> onload="true"/> >>>>> >>>>> Note: this is an example. The SplashScreen plugin is not setup this >>>>> way in plugins.xml. >>>>> >>>> >>>> Perhaps we should just use plugins.xml or whatever for iOS, instead of the >>>> .plist. We have to switch from the .plist to >something<, eventually, >>>> right? >>>> >>>> -- >>>> Patrick Mueller >>>> http://muellerware.org
