Well, when I need something test quickly or check something with trial and
error procedure, I don't like to use cordova run.
On Android, in most cases I need modificate androidmanifest.xml, rarely
config.xml. Modifications of androidmanifest are, how I told, preserved,
only formatting (and
Assuming that splash screens and icons finally work in 3.5.x (so, only as of a
few weeks ago… not everyone’s projects are that new) –
Android:
AndroidManifest.xml:
android:versionCode
(and possibly) android:minSdkVersion
ant.properties
android signing info
This is
+ custom protocol handling
+ document type registration
+ guid app id changes, or assigning different signing credentials
There are numerous last mile steps we are not involved in, which is why I wish
more committers were submitting apps to more stores, at least to see the
process.
Sent from
+1 This
On 15 July 2014 at 20:31:07, purplecabbage (purplecabb...@gmail.com) wrote:
There are numerous last mile steps we are not involved in, which is why I wish
more committers were submitting apps to more stores, at least to see the
process.
+ ios background modes
2014-07-15 12:36 GMT+02:00 tommy-carlos williams to...@devgeeks.org:
+1 This
On 15 July 2014 at 20:31:07, purplecabbage (purplecabb...@gmail.com) wrote:
There are numerous last mile steps we are not involved in, which is why I
wish more committers were submitting
From looking at the code it seems that versionCode is handled on Android:
https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/metadata/android_parser.js#L225
There is a email thread about minSdkVersion and an quite recent issue:
Never said this stuff couldn’t be fixed.
I have been actively advocating for it to be fixed.
Only wanted to spread some light on this statement:
If you're touching any non-www project files (that is *.xml, *.plist, *.m,
*.java etc...) or are using an IDE you should not be using cordova-cli and
I think I've read somewhere you can change some things in the info.plist on
phonegap build, why can't we?
El martes, 15 de julio de 2014, tommy-carlos williams to...@devgeeks.org
escribió:
Never said this stuff couldn’t be fixed.
I have been actively advocating for it to be fixed.
Only
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.
I agree with the core message from Axel, but I'd refrase that last line as:
The bottom line is: either use Cordova CLI or not.
Cordova can still be used without the CLI portion just as well, which
should suffice Jan for his needs.
However, I'll add that you can still use Cordova with the CLI
If you're touching any non-www project files (that is *.xml, *.plist, *.m,
*.java etc...) or are using an IDE you should not be using cordova-cli and
switch to single platform development. Browse the documentation and there
is always the equivalent platform command available to you. Example:
Sooo.. translation:
“If you aren’t just making a test / example app…”
??
Unless a lot has changed that I don’t know about, it is still impossible to
make an app all the way to market without modifying those non-www files using
the CLI.
There are fantastic workarounds available (mostly hooks,
Could you please give an example which files you need to change and why?
(Preferably Android)
Thanks
Axel
Am 15.07.2014 02:23 schrieb tommy-carlos williams to...@devgeeks.org:
Sooo.. translation:
“If you aren’t just making a test / example app…”
??
Unless a lot has changed that I don’t
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
14 matches
Mail list logo
