cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Axel Nennker <>
Subject Re: One platform development vs. Cordova CLI
Date Mon, 14 Jul 2014 08:35:22 GMT
My experience with Cordova (and other tools for that matter) is that it
makes no sense to change tool generated files.
If the tool is improved you do not benefit from this improvement because
your modified files will be changed by the new version.
If you change a tool generated file you are out.
When we started using Cordova me and other colleagues thought that our
project "needs" to change Cordova generated files too.
In each case this turned out to be wrong.
Most of the times writing a Cordova plugin is the solution.

The bottom line is: either use Cordova or not. (or send a pull request to
improve it)


2014-07-13 22:18 GMT+02:00 Jan Veleck√Ĺ <>:

> Hello,
> there is serious backlog when using CLI in case one platform development.
> In
> this case is better to change platform project config.xml instead of whole
> project config.xml. Problem is what prepare should do, and what prepare
> actually do. (And prepare is also run if we do build.) At this moment,
> prepare in CLI does clean & copy...
> Also prepare does it in different way in Android, than in iOS.
> On Android, config.xml and androidmanifest.xml is probably recreated
> (destroy previous formatting, what a feature...) and then probably add
> differences, so changes and new options are preserved, however nobody wanna
> read it...
> On iOS, config.xml is completely recreated, no any option is preserved...
> So, there are 2 questions...
> If is Android CLI too clever to do preserve changes created by user, why it
> ruins my formatting (new lines, maybe also tabulators)?
> Why is iOS CLI such a stupid? Why it is not able to do it like Android CLI
> (at least)?

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