Yeah and it pissed off users, esp since the docs weren't updated :) On 11/7/12 12:00 PM, "Anis KADRI" <[email protected]> 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 <[email protected]> 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" <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 >> >> >> >>
