Re: [Android] Evaulate Javascript and Threading
On Thu, Nov 21, 2013 at 11:08 AM, Ian Clelland iclell...@chromium.org wrote: I've seen that show up in the API docs, and it looks like a much saner way to execute JS in the WebView -- almost akin to iOS's stringByEvaluatingJavascriptString, except that the result is *also* returned to the browser, and not into native code. BTW: loadUrl(javascript://foo()) calls stringByEvaluatingJavascriptString, and it's not thread-safe, which is why it interferes with the UI thread and causes keyboards to disappear and all that stuff. Apparently you can in theory take down a whole device with it on iOS according to some couch guy I met at CascadiaJS a week or so ago. The problem is obviously backwards-compatibility. If we can't use it on newer devices, then is there any point in having it in the code? Yes! We can choose to use this the same way we choose other techniques now. Just because we have to make it work with all the versions of Cordova doesn't mean that we can't use the latest features. That's why we have things like reflection. This is how we had things like geolocation back when we supported Android 1.5 and 1.6. Besides being miles better aesthetically, does it give us any performance / reduce odd quirks / anything that would make it worth the extra code complexity? That's the question that I'm asking. Also, I think we should make the chrome debugger a preference to be turned on and off, but that's another thread. So, this is 4.4 only, but should we start adding this to our bag of JS tricks? http://developer.android.com/reference/android/webkit/WebView.html#evaluateJavascript(java.lang.String, android.webkit.ValueCallbackjava.lang.String)
Re: [Android] Evaulate Javascript and Threading
On Thu, Nov 21, 2013 at 2:16 PM, Joe Bowser bows...@gmail.com wrote: On Thu, Nov 21, 2013 at 11:08 AM, Ian Clelland iclell...@chromium.org wrote: I've seen that show up in the API docs, and it looks like a much saner way to execute JS in the WebView -- almost akin to iOS's stringByEvaluatingJavascriptString, except that the result is *also* returned to the browser, and not into native code. BTW: loadUrl(javascript://foo()) calls stringByEvaluatingJavascriptString, and it's not thread-safe, which is why it interferes with the UI thread and causes keyboards to disappear and all that stuff. Apparently you can in theory take down a whole device with it on iOS according to some couch guy I met at CascadiaJS a week or so ago. Nice... I wish I could have made it out to that :| The problem is obviously backwards-compatibility. If we can't use it on newer devices, then is there any point in having it in the code? Yes! We can choose to use this the same way we choose other techniques now. Just because we have to make it work with all the versions of Cordova doesn't mean that we can't use the latest features. That's why we have things like reflection. This is how we had things like geolocation back when we supported Android 1.5 and 1.6. Besides being miles better aesthetically, does it give us any performance / reduce odd quirks / anything that would make it worth the extra code complexity? That's the question that I'm asking. I guess we're asking the same question, then :) I haven't seen anything that suggests that it will enable anything new, that we can't already do. If it doesn't, then I don't see any point in writing a separate code path just for 4.4+ devices; it will just be more code. On the other hand, if it *does* allow exciting new things, (and I'm hoping it does,) then we should check it out :) Also, I think we should make the chrome debugger a preference to be turned on and off, but that's another thread. We should have that thread, too. Ian So, this is 4.4 only, but should we start adding this to our bag of JS tricks? http://developer.android.com/reference/android/webkit/WebView.html#evaluateJavascript(java.lang.String , android.webkit.ValueCallbackjava.lang.String)
Re: [Android] Evaulate Javascript and Threading
I've seen that show up in the API docs, and it looks like a much saner way to execute JS in the WebView -- almost akin to iOS's stringByEvaluatingJavascriptString, except that the result is *also* returned to the browser, and not into native code. Certainly better than setting the WebView's document.location in any case. The problem is obviously backwards-compatibility. If we can't use it on newer devices, then is there any point in having it in the code? Besides being miles better aesthetically, does it give us any performance / reduce odd quirks / anything that would make it worth the extra code complexity? Ian On Thu, Nov 21, 2013 at 1:49 PM, Joe Bowser bows...@gmail.com wrote: So, this is 4.4 only, but should we start adding this to our bag of JS tricks? http://developer.android.com/reference/android/webkit/WebView.html#evaluateJavascript(java.lang.String , android.webkit.ValueCallbackjava.lang.String)
Re: Cordova Debug Mode
On Thu, Nov 21, 2013 at 11:37 AM, Ian Clelland iclell...@chromium.orgwrote: David and I were talking about this this morning, and since Joe brought it up as well, we should probably get the list involved. I think that there is some value in having Debug and Release builds of Cordova projects. I don't know if the platforms have any way to do this already, but it seems like there are a lot of behaviours that are incredibly useful for testing and development, which shouldn't ever be enabled in released applications. Off the top of my head: * All of our Console / ADB / NSLog Logging If you disable logging by default, make it a preference somewhere. Because I always wanted console/Java logging in production Android apps to capture wtf was going on for my users all the time. * Enabling the remote debugger in Android 4.4+ * (maybe) disabling the network whitelist I'm sure there are others -- we have a plugin for chrome.alarm that is *supposed* to have a 1-minute minimum timeout, but I'd love to be able to make that 1/4s in debug mode only. Would it make sense to have a build flag for this? cordova build --debug, cordova build --release; something like that (bikeshed colours welcome). I don't think that config.xml is the place for it; it seems like it should be lower than that, but I'm not exactly sure how it should be set. There will probably need to be platform-specific implementations, but it would be good to have a cross-platform way of turning it on and off. Thoughts? Ian
[Android] Evaulate Javascript and Threading
So, this is 4.4 only, but should we start adding this to our bag of JS tricks? http://developer.android.com/reference/android/webkit/WebView.html#evaluateJavascript(java.lang.String, android.webkit.ValueCallbackjava.lang.String)
Re: Review Request 15750: Adding/Removing custom frameworks to iOS projects
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/#review29231 --- I share Ian's concern about the removal. Though possibly since these are custom, bundled frameworks, there will never be any overlap. If so, then it's fine. - Braden Shepherdson On Nov. 21, 2013, 3:26 a.m., Anis Kadri wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/ --- (Updated Nov. 21, 2013, 3:26 a.m.) Review request for cordova, Max Woghiren and Braden Shepherdson. Bugs: CB-5238 https://issues.apache.org/jira/browse/CB-5238 Repository: cordova-plugman Description --- Adding/Removing custom frameworks to iOS projects node-xcode 0.6.3 needs to be pushed to npm for this to be tested. Custom frameworks can be defined in plugin.xml like so: framework src=src/ios/Custom.framework custom=true if @custom=true is not defined, plugman will think it is a System framework and will therefore fail to add it properly. Diffs - spec/platforms/ios.spec.js cb7460d spec/plugins/ChildBrowser/plugin.xml 512c02f spec/plugins/DummyPlugin/plugin.xml fad5072 spec/plugins/FaultyPlugin/plugin.xml 30af6e7 spec/util/config-changes.spec.js 5e46b69 src/install.js c0a4de9 src/platforms/ios.js 065c4a7 src/uninstall.js 11ff7fb src/util/config-changes.js 0239b61 Diff: https://reviews.apache.org/r/15750/diff/ Testing --- Thanks, Anis Kadri
3.2.0 blog review
posted below in markdown: The [Apache Cordova](http://cordova.apache.org/) team has just released Cordova 3.2.0. Woo Hoo! This release has various bug fixes and enhancements for all of the platforms. To upgrade a 3.2 project (replace `android` with the platform you want to update): npm install -g cordova cd my_project cordova platform update android For non-CLI projects or for pre-3.0 projects, refer to the [upgrade guides]( http://cordova.apache.org/docs/en/3.2.0/guide_platforms_index.md.html). Please report any bugs on our [issue tracker]( https://issues.apache.org/jira/browse/CB). !--more-- ## What's new in Android * Set VERSION to 3.2.0 (via coho) * Update JS snapshot to version 3.2.0 (via coho) * CB-5301 add missing license headers * CB-5349: fixed regression in update script * Set VERSION to 3.2.0-rc1 (via coho) * Update JS snapshot to version 3.2.0-rc1 (via coho) * CB-5193 Fix Android WebSQL sometime throwing SECURITY_ERR. * CB-5191 Deprecate url-filter * Updating shelljs to 0.2.6. Copy now preserves mode bits. * CB-4872 - moved version script to promise model * CB-4872 - make sure to copy over version scripts to project * [CB-4872] - added android version scripts * CB-5117: Output confirmation message if check_reqs passes. * Refactoring Android project-level and platform scripts to use Q.js * Updating to latest shelljs, old version doesn't preserve +x bits * Remove cordova.xml fallback from Config.java (it was removed from PluginManager for 3.0) * CB-5080 Find resources in a way that works with aapt's --rename-manifest-package * Update JS snapshot to version 3.2.0-dev (via coho) * Remove a couple incorrect lines from RELEASENOTES.md * CB-4961: shell.js returns the full path on ls, rebuilding the full path isn't really needed * Updating README.md to have latest Android SDK * CB-4527: This was an easy fix, since the script deletes batch files * [CB-4892] Fix create script only escaping the first space instead of all spaces. * Fix update script to clobber cordova.js file (missing -f) * Add missing copyright header for Whitelist.java. * [CB-4832] Add 3.1.0 RELEASENOTES.md * Update JS snapshot to version 3.2.0-dev (via coho) * Set VERSION to 3.2.0-dev (via coho) ## What's new in iOS * CB-5124 - Remove splashscreen config.xml values from iOS Configuration Docs, move to plugin docs * CB-5229 - cordova/emulate important improvements (stderr, check ios-sim before build) * CB-5058 - CordovaLib xcode project gets assigned problematic Build Active Architecture Only settings. * CB-5217 - cordova emulate ios doesn't exit * CB-4805 - Update cordova/run and cordova/lib/install-device to use latest ios-deploy for iOS 7 * CB-5103 - Fix cordova/run: --emulate should be --emulator (fix CLI usage) * CB-4872 - added iOS sdk version scripts * CB-5099 - Add missing icons especially iOS 7 120x120 icon to default template * CB-5037 - Fix bridge sometimes not resetting properly during page transitions * CB-4990 - Can't run emulator from cordova cli * CB-4978 - iOS - Remove HideKeyboardFormAccessoryBar and KeyboardShrinksView preferences in config.xml * CB-4935 - iOS - Remove Keyboard preferences code into its own plugin * Make CDVWebViewDelegate able to load pages after a failed load. * Prevented automatic logging of whitelist failures. ## What's new in Windows Phone 7 8 * CB-5418 BrowserMouseHelper fails on WP8 for WP7 apps * Update to 3.2.0 * CB-5437 Inconsistent default new project names for wp7 and wp8 visual studio templates * update js and template defs for 3.2.0-rc1 * Fixes the invalid pattern used to test msbuild availability * Fixes the invalid pattern used to test msbuild availability * CB-5076 String.Format issue causing exception in exception handler * Update regex to handle international version strings * CB-4872 changed version script file location to right spot and modified sdk version output * CB-4872 - added os version and edition check * CB-4872: Added wp7 and wp8 sdk version * [CB-3621] backbutton events can now throw an exception to let the native side know that it should e * [CB-3621] backbutton events can now throw an exception to let the native side know that it should e * [CB-4850] only write device guid if it does not exist * added case-insensitivity to check_reqs for wp8, just like @albanf did for wp7 * Version check regexps should be case insensitive * pulled in and re-jiggered templates * removed risky regex template version number replacement, and added XMLDOM versions (cherry picked ## What's new in Windows 8 * update for 3.2.0 * update js for 3.2.0-rc1 * CB-5024 Localized output of msbuild -v was not properly parsed. ## What's new in BlackBerry 10 * CB-5433 init.bat use %USERPROFILE% on Windows * updated and tested for 3.2.0 release * Fix unit tests * CB-5317 Move signing warn logic to build/run scripts * CB-5329 re-adds rim-permissions element to config.xml, which plugman installation scripts require * CB-5313 BalckBerry10 cordova.js wrong version number for
Re: Review Request 15750: Adding/Removing custom frameworks to iOS projects
On Nov. 21, 2013, 3:44 a.m., Ian Clelland wrote: The documentation should probably be clear that 'custom=false' will *also* designate a custom framework -- I suspect that some people will try that, rather than simply removing the attribute. Also, what happens if two plugins depend on the same framework? It looks like uninstalling either of them will remove the framework, but I'm not certain. Max Woghiren wrote: Will having two plugins depend on the same framework work to begin with? It looks like it will fail with target destination [path] already exists. I thought about that as well, (that's why the what happens if is there,) but I figured breaking on removal was a more serious bug :) If we go ahead with this for a v1 implementation, then a solution would just be to have a dedicated plugin to manage the framework, and then plugins depending on the framework would depend on that plugin instead. - Ian --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/#review29208 --- On Nov. 21, 2013, 3:26 a.m., Anis Kadri wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/ --- (Updated Nov. 21, 2013, 3:26 a.m.) Review request for cordova, Max Woghiren and Braden Shepherdson. Bugs: CB-5238 https://issues.apache.org/jira/browse/CB-5238 Repository: cordova-plugman Description --- Adding/Removing custom frameworks to iOS projects node-xcode 0.6.3 needs to be pushed to npm for this to be tested. Custom frameworks can be defined in plugin.xml like so: framework src=src/ios/Custom.framework custom=true if @custom=true is not defined, plugman will think it is a System framework and will therefore fail to add it properly. Diffs - spec/platforms/ios.spec.js cb7460d spec/plugins/ChildBrowser/plugin.xml 512c02f spec/plugins/DummyPlugin/plugin.xml fad5072 spec/plugins/FaultyPlugin/plugin.xml 30af6e7 spec/util/config-changes.spec.js 5e46b69 src/install.js c0a4de9 src/platforms/ios.js 065c4a7 src/uninstall.js 11ff7fb src/util/config-changes.js 0239b61 Diff: https://reviews.apache.org/r/15750/diff/ Testing --- Thanks, Anis Kadri
pause/resume download using FileTransfer
I’m working on an iOS Cordova app. Is it possible to pause a download and then resume it using FileTransfer? Does the abort() command delete the partially-downloaded file, or is it possible to resume the download by calling download() a second time using the same file path? Has anyone else done this? Thanks! - Nick
Should a Plugin Release be put out now with 3.2.0 ?
It's being 4 weeks since last plugin release. According to [1] it should happen weekly. It will be cool to see new version of platform 3.2.0 being release/tested with latest plugin code bug fixes [1]: http://wiki.apache.org/cordova/VersioningAndReleaseStrategy -- Carlos Santana csantan...@gmail.com
Re: Review Request 15750: Adding/Removing custom frameworks to iOS projects
On Nov. 21, 2013, 3:44 a.m., Ian Clelland wrote: The documentation should probably be clear that 'custom=false' will *also* designate a custom framework -- I suspect that some people will try that, rather than simply removing the attribute. Also, what happens if two plugins depend on the same framework? It looks like uninstalling either of them will remove the framework, but I'm not certain. Max Woghiren wrote: Will having two plugins depend on the same framework work to begin with? It looks like it will fail with target destination [path] already exists. Ian Clelland wrote: I thought about that as well, (that's why the what happens if is there,) but I figured breaking on removal was a more serious bug :) If we go ahead with this for a v1 implementation, then a solution would just be to have a dedicated plugin to manage the framework, and then plugins depending on the framework would depend on that plugin instead. Good call—that'll work. - Max --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/#review29208 --- On Nov. 21, 2013, 3:26 a.m., Anis Kadri wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/ --- (Updated Nov. 21, 2013, 3:26 a.m.) Review request for cordova, Max Woghiren and Braden Shepherdson. Bugs: CB-5238 https://issues.apache.org/jira/browse/CB-5238 Repository: cordova-plugman Description --- Adding/Removing custom frameworks to iOS projects node-xcode 0.6.3 needs to be pushed to npm for this to be tested. Custom frameworks can be defined in plugin.xml like so: framework src=src/ios/Custom.framework custom=true if @custom=true is not defined, plugman will think it is a System framework and will therefore fail to add it properly. Diffs - spec/platforms/ios.spec.js cb7460d spec/plugins/ChildBrowser/plugin.xml 512c02f spec/plugins/DummyPlugin/plugin.xml fad5072 spec/plugins/FaultyPlugin/plugin.xml 30af6e7 spec/util/config-changes.spec.js 5e46b69 src/install.js c0a4de9 src/platforms/ios.js 065c4a7 src/uninstall.js 11ff7fb src/util/config-changes.js 0239b61 Diff: https://reviews.apache.org/r/15750/diff/ Testing --- Thanks, Anis Kadri
Re: Cordova Debug Mode
On Thu, Nov 21, 2013 at 12:58 PM, Ian Clelland iclell...@chromium.orgwrote: On Thu, Nov 21, 2013 at 3:22 PM, Lindsey Simon lsi...@commoner.com wrote: On Thu, Nov 21, 2013 at 11:37 AM, Ian Clelland iclell...@chromium.org wrote: David and I were talking about this this morning, and since Joe brought it up as well, we should probably get the list involved. I think that there is some value in having Debug and Release builds of Cordova projects. I don't know if the platforms have any way to do this already, but it seems like there are a lot of behaviours that are incredibly useful for testing and development, which shouldn't ever be enabled in released applications. Off the top of my head: * All of our Console / ADB / NSLog Logging If you disable logging by default, make it a preference somewhere. Because I always wanted console/Java logging in production Android apps to capture wtf was going on for my users all the time. Do you mean console.log() statements from application code? Those should definitely be allowed, and if you have the console plugin installed, then they can go to the device's log. I meant that we could shut up all of the logging that goes on inside Cordova and inside our plugins. If *those* messages are still useful in production apps, then we should clean them up a bit :) Ah, no worries then - you mean internal logging ;) Carry on.
Re: Cordova Debug Mode
On Thu, Nov 21, 2013 at 2:56 PM, Joe Bowser bows...@gmail.com wrote: On Thu, Nov 21, 2013 at 11:37 AM, Ian Clelland iclell...@chromium.org wrote: Would it make sense to have a build flag for this? cordova build --debug, cordova build --release; something like that (bikeshed colours welcome). I don't think that config.xml is the place for it; it seems like it should be lower than that, but I'm not exactly sure how it should be set. Considering that we have to add Java code to get this to work, it either has to be in the XML, or we're going to have to check the AndroidManifest to see if we're in debug mode, like what we already do for SSL errors. If we could set that flag in the manifest from the CLI (as part of prepare, or as part of build) then that would probably do it. There will probably need to be platform-specific implementations, but it would be good to have a cross-platform way of turning it on and off. The CLI doesn't have a way to actually release software, so I assume that ALL builds created by it are Debug Builds. True. There should be a thread about that, too :)
Cordova Debug Mode
David and I were talking about this this morning, and since Joe brought it up as well, we should probably get the list involved. I think that there is some value in having Debug and Release builds of Cordova projects. I don't know if the platforms have any way to do this already, but it seems like there are a lot of behaviours that are incredibly useful for testing and development, which shouldn't ever be enabled in released applications. Off the top of my head: * All of our Console / ADB / NSLog Logging * Enabling the remote debugger in Android 4.4+ * (maybe) disabling the network whitelist I'm sure there are others -- we have a plugin for chrome.alarm that is *supposed* to have a 1-minute minimum timeout, but I'd love to be able to make that 1/4s in debug mode only. Would it make sense to have a build flag for this? cordova build --debug, cordova build --release; something like that (bikeshed colours welcome). I don't think that config.xml is the place for it; it seems like it should be lower than that, but I'm not exactly sure how it should be set. There will probably need to be platform-specific implementations, but it would be good to have a cross-platform way of turning it on and off. Thoughts? Ian
Re: Review Request 15750: Adding/Removing custom frameworks to iOS projects
On Nov. 21, 2013, 3:44 a.m., Ian Clelland wrote: The documentation should probably be clear that 'custom=false' will *also* designate a custom framework -- I suspect that some people will try that, rather than simply removing the attribute. Also, what happens if two plugins depend on the same framework? It looks like uninstalling either of them will remove the framework, but I'm not certain. Will having two plugins depend on the same framework work to begin with? It looks like it will fail with target destination [path] already exists. - Max --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/#review29208 --- On Nov. 21, 2013, 3:26 a.m., Anis Kadri wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15750/ --- (Updated Nov. 21, 2013, 3:26 a.m.) Review request for cordova, Max Woghiren and Braden Shepherdson. Bugs: CB-5238 https://issues.apache.org/jira/browse/CB-5238 Repository: cordova-plugman Description --- Adding/Removing custom frameworks to iOS projects node-xcode 0.6.3 needs to be pushed to npm for this to be tested. Custom frameworks can be defined in plugin.xml like so: framework src=src/ios/Custom.framework custom=true if @custom=true is not defined, plugman will think it is a System framework and will therefore fail to add it properly. Diffs - spec/platforms/ios.spec.js cb7460d spec/plugins/ChildBrowser/plugin.xml 512c02f spec/plugins/DummyPlugin/plugin.xml fad5072 spec/plugins/FaultyPlugin/plugin.xml 30af6e7 spec/util/config-changes.spec.js 5e46b69 src/install.js c0a4de9 src/platforms/ios.js 065c4a7 src/uninstall.js 11ff7fb src/util/config-changes.js 0239b61 Diff: https://reviews.apache.org/r/15750/diff/ Testing --- Thanks, Anis Kadri
Re: Cordova IOS
Elie, this mailing list is for the discussion of developing Cordova itself. I'd suggest that you ask this question where the Cordova consumers hang out: https://groups.google.com/forum/?fromgroups#!forum/phonegap On Nov 21, 2013, at 5:36 AM, Elie Najem e...@dowgroup.com wrote: Dear all, I'll be very thankful if you can help regarding the below issue: How can i avoid the white screen after the splash screen? I'm using cordova 3.0.1 and Xcode 5 Thanks in advance
Re: 3.2.0 blog review
+1 on blog post and this time including plugin versions On Thu, Nov 21, 2013 at 6:37 PM, Steven Gill stevengil...@gmail.com wrote: posted below in markdown: The [Apache Cordova](http://cordova.apache.org/) team has just released Cordova 3.2.0. Woo Hoo! This release has various bug fixes and enhancements for all of the platforms. To upgrade a 3.2 project (replace `android` with the platform you want to update): npm install -g cordova cd my_project cordova platform update android For non-CLI projects or for pre-3.0 projects, refer to the [upgrade guides]( http://cordova.apache.org/docs/en/3.2.0/guide_platforms_index.md.html). Please report any bugs on our [issue tracker]( https://issues.apache.org/jira/browse/CB). !--more-- ## What's new in Android * Set VERSION to 3.2.0 (via coho) * Update JS snapshot to version 3.2.0 (via coho) * CB-5301 add missing license headers * CB-5349: fixed regression in update script * Set VERSION to 3.2.0-rc1 (via coho) * Update JS snapshot to version 3.2.0-rc1 (via coho) * CB-5193 Fix Android WebSQL sometime throwing SECURITY_ERR. * CB-5191 Deprecate url-filter * Updating shelljs to 0.2.6. Copy now preserves mode bits. * CB-4872 - moved version script to promise model * CB-4872 - make sure to copy over version scripts to project * [CB-4872] - added android version scripts * CB-5117: Output confirmation message if check_reqs passes. * Refactoring Android project-level and platform scripts to use Q.js * Updating to latest shelljs, old version doesn't preserve +x bits * Remove cordova.xml fallback from Config.java (it was removed from PluginManager for 3.0) * CB-5080 Find resources in a way that works with aapt's --rename-manifest-package * Update JS snapshot to version 3.2.0-dev (via coho) * Remove a couple incorrect lines from RELEASENOTES.md * CB-4961: shell.js returns the full path on ls, rebuilding the full path isn't really needed * Updating README.md to have latest Android SDK * CB-4527: This was an easy fix, since the script deletes batch files * [CB-4892] Fix create script only escaping the first space instead of all spaces. * Fix update script to clobber cordova.js file (missing -f) * Add missing copyright header for Whitelist.java. * [CB-4832] Add 3.1.0 RELEASENOTES.md * Update JS snapshot to version 3.2.0-dev (via coho) * Set VERSION to 3.2.0-dev (via coho) ## What's new in iOS * CB-5124 - Remove splashscreen config.xml values from iOS Configuration Docs, move to plugin docs * CB-5229 - cordova/emulate important improvements (stderr, check ios-sim before build) * CB-5058 - CordovaLib xcode project gets assigned problematic Build Active Architecture Only settings. * CB-5217 - cordova emulate ios doesn't exit * CB-4805 - Update cordova/run and cordova/lib/install-device to use latest ios-deploy for iOS 7 * CB-5103 - Fix cordova/run: --emulate should be --emulator (fix CLI usage) * CB-4872 - added iOS sdk version scripts * CB-5099 - Add missing icons especially iOS 7 120x120 icon to default template * CB-5037 - Fix bridge sometimes not resetting properly during page transitions * CB-4990 - Can't run emulator from cordova cli * CB-4978 - iOS - Remove HideKeyboardFormAccessoryBar and KeyboardShrinksView preferences in config.xml * CB-4935 - iOS - Remove Keyboard preferences code into its own plugin * Make CDVWebViewDelegate able to load pages after a failed load. * Prevented automatic logging of whitelist failures. ## What's new in Windows Phone 7 8 * CB-5418 BrowserMouseHelper fails on WP8 for WP7 apps * Update to 3.2.0 * CB-5437 Inconsistent default new project names for wp7 and wp8 visual studio templates * update js and template defs for 3.2.0-rc1 * Fixes the invalid pattern used to test msbuild availability * Fixes the invalid pattern used to test msbuild availability * CB-5076 String.Format issue causing exception in exception handler * Update regex to handle international version strings * CB-4872 changed version script file location to right spot and modified sdk version output * CB-4872 - added os version and edition check * CB-4872: Added wp7 and wp8 sdk version * [CB-3621] backbutton events can now throw an exception to let the native side know that it should e * [CB-3621] backbutton events can now throw an exception to let the native side know that it should e * [CB-4850] only write device guid if it does not exist * added case-insensitivity to check_reqs for wp8, just like @albanf did for wp7 * Version check regexps should be case insensitive * pulled in and re-jiggered templates * removed risky regex template version number replacement, and added XMLDOM versions (cherry picked ## What's new in Windows 8 * update for 3.2.0 * update js for 3.2.0-rc1 * CB-5024 Localized output of msbuild -v was not properly parsed. ## What's new in BlackBerry 10 * CB-5433 init.bat use %USERPROFILE% on Windows * updated and tested for 3.2.0
Re: Cordova Debug Mode
On Thu, Nov 21, 2013 at 11:37 AM, Ian Clelland iclell...@chromium.org wrote: Would it make sense to have a build flag for this? cordova build --debug, cordova build --release; something like that (bikeshed colours welcome). I don't think that config.xml is the place for it; it seems like it should be lower than that, but I'm not exactly sure how it should be set. Considering that we have to add Java code to get this to work, it either has to be in the XML, or we're going to have to check the AndroidManifest to see if we're in debug mode, like what we already do for SSL errors. There will probably need to be platform-specific implementations, but it would be good to have a cross-platform way of turning it on and off. The CLI doesn't have a way to actually release software, so I assume that ALL builds created by it are Debug Builds.
Review Request 15775: Add --src --link to cordova create
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15775/ --- Review request for cordova. Summary (updated) - Add --src --link to cordova create Bugs: CB-4153 https://issues.apache.org/jira/browse/CB-4153 Repository: cordova-cli Description (updated) --- Add --src --link to cordova create. Both --src and --source are accepted. The path is passed via the lib.www.uri of the configuration object that is later written to .cordova/config.json. Cordova will keep going into child www folder(s) of the provided path. Diffs - doc/help.txt 1019200 src/cli.js 86477e4 src/create.js 1fdc271 Diff: https://reviews.apache.org/r/15775/diff/ Testing (updated) --- npm test; cordova -d create TstApp --source=some/www --link a bunch of other cordova commands in the app Thanks, Mark Koudritsky
Re: Cordova Debug Mode
On Thu, Nov 21, 2013 at 3:22 PM, Lindsey Simon lsi...@commoner.com wrote: On Thu, Nov 21, 2013 at 11:37 AM, Ian Clelland iclell...@chromium.org wrote: David and I were talking about this this morning, and since Joe brought it up as well, we should probably get the list involved. I think that there is some value in having Debug and Release builds of Cordova projects. I don't know if the platforms have any way to do this already, but it seems like there are a lot of behaviours that are incredibly useful for testing and development, which shouldn't ever be enabled in released applications. Off the top of my head: * All of our Console / ADB / NSLog Logging If you disable logging by default, make it a preference somewhere. Because I always wanted console/Java logging in production Android apps to capture wtf was going on for my users all the time. Do you mean console.log() statements from application code? Those should definitely be allowed, and if you have the console plugin installed, then they can go to the device's log. I meant that we could shut up all of the logging that goes on inside Cordova and inside our plugins. If *those* messages are still useful in production apps, then we should clean them up a bit :)
Re: pause/resume download using FileTransfer
FileTransfer deletes partially downloaded files on abort() -- there is a test in Mobile Spec for this behaviour. You could certainly start the download again, but it wouldn't resume; it would start again at the beginning :( I don't know if there is a universal way to do this -- the way that makes sense to me would be to include a Range header in the request, and look for a 206 response code. A 200 would mean that the server didn't support it, and that we should start writing from the beginning. I have no idea if this is how resuming download clients actually implement this in practise, though, or if there is some other protocol used. If we add this, we would need to make specific pause() and resume() methods, I think -- it's important on mobile devices to remove unneeded files, as the user generally can't do it by themselves (and space is very limited). Similarly, if you were to call download() with a file in place already, we'd have no way to know if that was due to a partial download, or whether it was an old version that needs to be replaced. (There's an additional issue of how to handle resources that may have changed in the meantime -- there's a dance we can do with If-Range headers and Etags, but it starts getting complicated quickly, and we're not storing any of that info right now.) Ian On Thu, Nov 21, 2013 at 2:27 PM, Nick Burka n...@silverorange.com wrote: I’m working on an iOS Cordova app. Is it possible to pause a download and then resume it using FileTransfer? Does the abort() command delete the partially-downloaded file, or is it possible to resume the download by calling download() a second time using the same file path? Has anyone else done this? Thanks! - Nick
