cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <shaz...@gmail.com>
Subject Re: [iOS] Cordova.plist to config.xml - deprecation
Date Tue, 27 Nov 2012 21:30:15 GMT
So... we are still supporting Cordova.plist as per the deprecation policy
right?


On Wed, Nov 21, 2012 at 1:12 PM, Joe Bowser <bowserj@gmail.com> wrote:

> No.  cordova.xml and plugins.xml STILL work.  This was done before our
> deprecation policy.
>
> On Wed, Nov 7, 2012 at 12:00 PM, Anis KADRI <anis.kadri@gmail.com> wrote:
> > Didn't Android just switch from plugins.xml + cordova.xml -> config.xml
> > without deprecating anything ?
> >
> >
> > On Wed, Nov 7, 2012 at 11:53 AM, Filip Maj <fil@adobe.com> wrote:
> >
> >> IMO we should support both for at least a point revision or two and
> >> deprecate appropriately..
> >>
> >> On 11/7/12 11:49 AM, "Anis KADRI" <anis.kadri@gmail.com> wrote:
> >>
> >> >Because generation McDonald's wants everything yesterday! Users don't
> like
> >> >to think too much [1]
> >> >
> >> >[1] http://www.amazon.com/Dont-Make-Me-Think-Usability/dp/0321344758
> >> >
> >> >
> >> >On Wed, Nov 7, 2012 at 11:44 AM, Jesse <purplecabbage@gmail.com>
> wrote:
> >> >
> >> >> I would go cold turkey.
> >> >> Not sure why you need to write a cli tool, just instruct users that
> in
> >> >> version 2.3 and beyond, they must use config.xml, and tell them if
> >> >> they are migrating, they will have to put their data in the new
> >> >> format.
> >> >>
> >> >> Not sure why we keep insisting on doing everything for everyone.  but
> >> >> meh, I'm grumpy and old ...
> >> >>
> >> >> On Wed, Nov 7, 2012 at 11:25 AM, Shazron <shazron@gmail.com>
wrote:
> >> >> > Do we want to still support the .plist (thus deprecate) or go
cold
> >> >>turkey
> >> >> > and support config.xml only?
> >> >> >
> >> >> > I'd rather go cold turkey and write a cli tool to convert a
> >> >>Cordova.plist
> >> >> > -> config.xml, which shouldn't be hard.
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> @purplecabbage
> >> >> risingj.com
> >> >>
> >>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message