Re: [iOS] Cordova.plist to config.xml - deprecation

The step of having to update the project reference would probably still been confusing / annoying. I've just enhanced the script so that it converts the file and also updates your project file. The upgrade instructions will now be: 1. Drop in new CordovaLib 2. Drop in updated cordova.js 3. Run cor

Re: [iOS] Cordova.plist to config.xml - deprecation

The undesirable behavior with that approach is that the user can be wondering why their changes to the old file are not being picked up. They'll have to migrate sometime, and if we've provided the tool and warn them in release notes and elsewhere, then I think this approach is reasonable. Braden

Re: [iOS] Cordova.plist to config.xml - deprecation

On 12/3/2012 12:02 PM, Braden Shepherdson wrote: Instant migration, with the conversion script. Deprecation policy is good in general, but having both and wondering why your changes to the old one are not propagating is a problem. Therefore I'm for the clean break. Will the conversion script ru

Re: [iOS] Cordova.plist to config.xml - deprecation

Instant migration, with the conversion script. Deprecation policy is good in general, but having both and wondering why your changes to the old one are not propagating is a problem. Therefore I'm for the clean break. Braden On Fri, Nov 30, 2012 at 7:13 PM, Shazron wrote: > I think having the c

Re: [iOS] Cordova.plist to config.xml - deprecation

I think having the conversion script makes sense (and you've already implemented it, thanks Andrew). Supporting both can cause confusion. So what is the consensus if any here. On Thu, Nov 29, 2012 at 10:40 AM, Andrew Grieve wrote: > Copying from the JIRA issue to this thread: > > I think su

Re: [iOS] Cordova.plist to config.xml - deprecation

Here it is: https://github.com/imhotep/plugman/commits/master I still need to add the ability to install plugins that have a plugins-plist tag to cordova 2.3.0 projects (that don't have the plists anymore). On Thu, Nov 29, 2012 at 10:40 AM, Andrew Grieve wrote: > Copying from the JIRA issue to

Re: [iOS] Cordova.plist to config.xml - deprecation

Copying from the JIRA issue to this thread: I think supporting both was one of the things that upset users when Android > made the switch (at least, it upset me). What happened was that I ended up > having both files present, and the code was silently using one and not the > other, and I couldn't

Re: [iOS] Cordova.plist to config.xml - deprecation

Oh, sweet. I'm glad I went to lunch instead of working on it further :P Braden On Thu, Nov 29, 2012 at 12:47 PM, Anis KADRI wrote: > I've already started working on pluginstall…which btw is now called > plugmanas it has diverged > significantly from the origi

Re: [iOS] Cordova.plist to config.xml - deprecation

I've already started working on pluginstall…which btw is now called plugmanas it has diverged significantly from the original tool. I am expecting to commit the code sometime today. On Thu, Nov 29, 2012 at 8:38 AM, Braden Shepherdson wrote: > The code I checked

Re: [iOS] Cordova.plist to config.xml - deprecation

The code I checked in, which is now tagged, is expecting config.xml only. It wouldn't be terribly hard to support plists too, but I agree that a clean change is less confusing. I think a conversion script is overkill, it only takes about three to convert one to the other (30 seconds if you vim mac

Re: [iOS] Cordova.plist to config.xml - deprecation

Nice. On 11/27/12 1:40 PM, "Shazron" wrote: >Yup -- I think it can work like this - firstly iOS would try to use >config.xml, not found? use Cordova.plist. If it uses Cordova.plist, we >print the deprecation message. > > >On Tue, Nov 27, 2012 at 1:36 PM, Filip Maj wrote: > >> I would recommend

Re: [iOS] Cordova.plist to config.xml - deprecation

Yup -- I think it can work like this - firstly iOS would try to use config.xml, not found? use Cordova.plist. If it uses Cordova.plist, we print the deprecation message. On Tue, Nov 27, 2012 at 1:36 PM, Filip Maj wrote: > I would recommend that approach. > > No way to add messages for deprecati

Re: [iOS] Cordova.plist to config.xml - deprecation

I would recommend that approach. No way to add messages for deprecation though, right? Maybe on startup of the app (how currently it says something like Device: YES or something in the logs), say something like "cordova.plist is gone soon dude" On 11/27/12 1:30 PM, "Shazron" wrote: >So... we ar

Re: [iOS] Cordova.plist to config.xml - deprecation

So... we are still supporting Cordova.plist as per the deprecation policy right? On Wed, Nov 21, 2012 at 1:12 PM, Joe Bowser 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 wrote: > > Didn't A

Re: [iOS] Cordova.plist to config.xml - deprecation

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 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

Re: [iOS] Cordova.plist to config.xml - deprecation

Made a bug for this: https://issues.apache.org/jira/browse/CB-1893 On Thu, Nov 8, 2012 at 2:12 PM, Shazron wrote: > It won't have to special case dealing with some stupid .plist format. And > the rest of your args have been clarified by Fil. > > > On Thu, Nov 8, 2012 at 10:35 AM, Jesse MacFadye

Re: [iOS] Cordova.plist to config.xml - deprecation

It won't have to special case dealing with some stupid .plist format. And the rest of your args have been clarified by Fil. On Thu, Nov 8, 2012 at 10:35 AM, Jesse MacFadyen wrote: > Pluginstall will always have to special case iOS(all of them really), > because it must modify the project(s) > >

Re: [iOS] Cordova.plist to config.xml - deprecation

At least for the plugin mappings, as long as the service name as consumed by JS is identical across all platform implementations, the plugin class name can and needs to be platform specific. On 11/8/12 10:35 AM, "Jesse MacFadyen" wrote: >Pluginstall will always have to special case iOS(all of th

Re: [iOS] Cordova.plist to config.xml - deprecation

Pluginstall will always have to special case iOS(all of them really), because it must modify the project(s) Also, are we planning on replacing feature names in a cross device way? How do we resolve this:? iOS: Notification CDVNotification Android: Also there are various other differences that ar

Re: [iOS] Cordova.plist to config.xml - deprecation

Hi Becky - yes Cordova.plist will go away entirely and it is to be replaced by config.xml that follows the w3c widget spec, and the format would be common among all the platforms (all the major ones currently). A dev can certainly update the .xml from Xcode but it will be plain text editing instead

Re: [iOS] Cordova.plist to config.xml - deprecation

No reason, it's just more work to re-factor but no biggie. Not sure if Android's previous cordova.xml was deprecated as well or went cold turkey -- I assumed there was no deprecation. On Thu, Nov 8, 2012 at 4:23 AM, Brian LeRoux wrote: > any reason why we should not follow our deprec policy her

Re: [iOS] Cordova.plist to config.xml - deprecation

Ok, I'm a bit confused. Are we suggesting to get rid of the cordova.plist entirely? Does that mean that if a dev wants to change one of those settings they have to leave Xcode and modify config.xml and update the project? That certainly doesn't seems a bit cumbersome and not taking advantage of

Re: [iOS] Cordova.plist to config.xml - deprecation

any reason why we should not follow our deprec policy here? On Wed, Nov 7, 2012 at 12:20 PM, Filip Maj wrote: > Yeah and it pissed off users, esp since the docs weren't updated :) > > On 11/7/12 12:00 PM, "Anis KADRI" wrote: > > >Didn't Android just switch from plugins.xml + cordova.xml -> con

Re: [iOS] Cordova.plist to config.xml - deprecation

Yeah and it pissed off users, esp since the docs weren't updated :) On 11/7/12 12:00 PM, "Anis KADRI" 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 wrote: > >> IMO we should support

Re: [iOS] Cordova.plist to config.xml - deprecation

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 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" wrote

Re: [iOS] Cordova.plist to config.xml - deprecation

On 7 November 2012 11:44, Jesse 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 w

Re: [iOS] Cordova.plist to config.xml - deprecation

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" 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/0

Re: [iOS] Cordova.plist to config.xml - deprecation

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 wrote: > I would go cold turkey. > Not sure why you need to write a cli tool, just instru

Re: [iOS] Cordova.plist to config.xml - deprecation

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.

[iOS] Cordova.plist to config.xml - deprecation

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.