Well, ok --- so the idea of config.xml support is that it adheres to the proj goal of being standards based impl for web tech. There is much debate of the perfection of various manifests (and even debatable there is a standard at all).
Creating our own standard could even be construed as a solution! On Mon, Jun 11, 2012 at 3:29 PM, Shazron <[email protected]> wrote: > To build in support now? I like Patrick's suggestion of adding a > "+LoadAtStart" to the plugin identifier, it is least intrusive. > > On Mon, Jun 11, 2012 at 3:23 PM, Brian LeRoux <[email protected]> wrote: >> how much effort we looking at? the reason I ask is that we could keep >> around support for the older files if we do it post 2.x but if we do >> this for 2.x we can remove those files... >> >> >> On Mon, Jun 11, 2012 at 3:02 PM, Shazron <[email protected]> wrote: >>> Defer to 2.0.0 for config.xml support. >>> >>> On Sun, Jun 10, 2012 at 10:56 PM, Filip Maj <[email protected]> wrote: >>>> Is it time to bring in config.xml? We have phonegap-build stuff that uses >>>> this already [1]. BlackBerry webworks uses it [2]. It is a W3C spec [3]. >>>> >>>> 'bout time. >>>> >>>> [1] https://build.phonegap.com/docs/config-xml >>>> [2] >>>> https://developer.blackberry.com/html5/documentation/ww_developing/working_ >>>> with_config_xml_file_1866970_11.html >>>> [3] http://www.w3.org/TR/widgets/ >>>> >>>> On 6/7/12 12:34 PM, "Simon MacDonald" <[email protected]> wrote: >>>> >>>>>Yup, we should break stuff for the 2.0 release so it will be >>>>>consistent going forward. >>>>> >>>>>Simon Mac Donald >>>>>http://hi.im/simonmacdonald >>>>> >>>>> >>>>>On Thu, Jun 7, 2012 at 3:14 PM, Brian LeRoux <[email protected]> wrote: >>>>>> If we're going to break stuff 2.x is the time. >>>>>> >>>>>> On Thu, Jun 7, 2012 at 11:57 AM, Shazron <[email protected]> wrote: >>>>>>> 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 >>>>
