cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Braden Shepherdson <bra...@chromium.org>
Subject Re: [iOS] Cordova.plist to config.xml - deprecation
Date Tue, 04 Dec 2012 22:31:21 GMT
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


On Tue, Dec 4, 2012 at 5:22 PM, Marcel Kinard <cmarcelk@gmail.com> wrote:

> 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 run automatically if the customer has a plist
> file and no xml file on 2.3? If not, then customers will be broken without
> explicit action on their part (even though the action is small). That's not
> deprecation.
>
> Is there something undesirable with the following? This sounds more
> graceful from a customer perspective.
>
>
> On 11/27/2012 4: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.
>>
>
>

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