GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-ios/pull/103
CB-7493 Adds test-build command to package.json
Fix for https://issues.apache.org/jira/browse/CB-7493
\+ bonus - travis configuration file.
Succesful build log:
Here are the results of some tests on iOS8, hopefully they will be useful
to someone! :)
I need to do some more useful tests on DOM related stuff as it was
mentioned here already JS speed is not usually the bottleneck in Cordova
apps. Unless you're doing crazy crypto like some people :)
Github user difa1 commented on the pull request:
https://github.com/apache/cordova-js/pull/80#issuecomment-55110115
Thanks for the fix :+1: Hope you get acceptance for this before iOS 8 will
be released :D
---
If your project is set up for it, you can reply to this email and have
+1
- Verified signatures and hashes for cordova-blackberry10
- Ran mobile spec
On Tue, Sep 9, 2014 at 9:43 PM, Andrew Grieve agri...@chromium.org wrote:
Updated the release post to trim down the Android section.
On Mon, Sep 8, 2014 at 9:27 PM, Marcel Kinard cmarc...@gmail.com wrote:
And
On Wed, Sep 10, 2014 at 4:11 AM, Ross Gerbasi rgerb...@gmail.com wrote:
Here are the results of some tests on iOS8, hopefully they will be useful
to someone! :)
I need to do some more useful tests on DOM related stuff as it was
mentioned here already JS speed is not usually the bottleneck in
Joe's future prediction skills were wrong iOS will never adopt NFC, so I
don't think that will ever be core. :(
Unfortunately there are no NFC APIs in the iOS 8 SDK.
Maybe iOS 9...
On Wed, Sep 10, 2014 at 11:34 AM, Lisa Seacat DeLuca ldel...@us.ibm.com
wrote:
Joe's future prediction skills were wrong iOS will never adopt NFC, so I
don't think that will ever be core. :(
Yeah, my guess is they didn't want to tip their hand in revealing Apple Pay
early nor the presence of NFC enabled iPhones, and the development of the
SDK had to be locked down for release next week.
As usual, we all should file radars to Apple requesting access to this SDK,
the more the better
Ross - shoot. Arrgh I may have mixed up my test apps :( I should emblazon
WKWebView or UIWebView at the start of the app. Thank goodness for peer
review...
On Wed, Sep 10, 2014 at 1:11 AM, Ross Gerbasi rgerb...@gmail.com wrote:
Here are the results of some tests on iOS8, hopefully they will be
Github user clambertus commented on the pull request:
https://github.com/apache/cordova-plugin-test-framework/pull/4#issuecomment-55138873
test jira integration comment
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
If you have a chance can you re-run the tests and make sure I didn't screw
anything up? :)
-ross
On Wed, Sep 10, 2014 at 11:04 AM, Shazron shaz...@gmail.com wrote:
Ross - shoot. Arrgh I may have mixed up my test apps :( I should emblazon
WKWebView or UIWebView at the start of the app. Thank
Github user martincgg commented on the pull request:
https://github.com/apache/cordova-plugin-test-framework/pull/4#issuecomment-55140469
Wow this is good, Thanks Jason.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Can you put this on its own branch before it lands in 4.0.x? That'd be
awesome!
On Tue, Sep 9, 2014 at 5:32 PM, Andrew Grieve agri...@chromium.org wrote:
For cordova-android 4.0, I'd like to go as far as just deleting the
KeepRunning preference.
Apps get a pause event when they are
Ross can you clarify your results for Objectstore ArrayBuffer?
Notes:
- Objectstore ArrayBuffer is only supported in Safari WKWebView App
iPod Touch iOS 8 *Safari*
UserAgent - Mozilla/5.0 (iPod touch; CPU iPhone OS 8_0 like Mac OS X)
AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0
Yeah sorry :( I mixed those up there, it got pretty late when I was writing
all this up.
OS Arraybuffer is support in the WKWebView and Safari, it is not available
in a HomeScreen app or the UIWebView. According to HTML5 Test running in
those environments.
Apologies for the confusion.
-ross
On
Also for those interested in Browser features this is what we gained from
iOS 7 Safari to iOS 8 Safari. I have not had a chance to test all these new
features in UIWebView or Homescreen yet to confirm they all have them. I
only know indexedDB for now is only working in WKWebView and Safari.
-
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-plugin-test-framework/pull/5
Updated test-framework docs
Updated information about tests being stored as nested plugins, and changed
'test' directory to 'tests'.
You can merge this pull request into a Git
GitHub user zalun opened a pull request:
https://github.com/apache/cordova-plugin-globalization/pull/22
CB-7515 [FFOS Globalization] Fix l10n ready event
You can merge this pull request into a Git repository by running:
$ git pull
Github user zalun closed the pull request at:
https://github.com/apache/cordova-plugin-globalization/pull/22
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
I don't think there'd be much value in that. It'll be a single commit
that almost entirely just deletes lines.
What do you think about the never auto-pausing on backgrounding? or
about auto-pausing when intent sending?
On Wed, Sep 10, 2014 at 12:32 PM, Joe Bowser bows...@gmail.com wrote:
Can
I think this needs to be thought through more, and I'm extremely wary when
you say this is a single commit, especially based on the last couple of
months and how long it took 3.6 to go through. Given that we have people
travelling halfway across the planet who intend to show people their work
in
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/22#discussion_r17386903
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -24,12 +24,25 @@ var GlobalizationError =
require('./GlobalizationError');
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/22#discussion_r17386918
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -24,12 +24,25 @@ var GlobalizationError =
require('./GlobalizationError');
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/22#discussion_r17386923
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -24,12 +24,25 @@ var GlobalizationError =
require('./GlobalizationError');
Question is, do you consider the fact that bugs are introduced discovered
(possibly with pain) a sign that the system is broken, or a sign that the
system is working?
I sense that Andrew worries that if work has to land on a feature branch of
this feature branch, it won't get eyeballs.
I sense
On Wed, Sep 10, 2014 at 1:46 PM, Michal Mocny mmo...@chromium.org wrote:
Question is, do you consider the fact that bugs are introduced discovered
(possibly with pain) a sign that the system is broken, or a sign that the
system is working?
Given when they are discovered (right before
I consider 4 a release branch. Merge in tested green lit code to your
hearts desire but 4.0 is definitely not a feature. It should be always in a
releasable state.
On Sep 10, 2014 1:53 PM, Michal Mocny mmo...@chromium.org wrote:
Question is, do you consider the fact that bugs are introduced
Github user zalun commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/22#discussion_r17391437
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -24,12 +24,25 @@ var GlobalizationError =
require('./GlobalizationError');
var
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/22#discussion_r17391733
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -24,12 +24,25 @@ var GlobalizationError =
require('./GlobalizationError');
+1
Esp for the iOS 8 fixes for Geolocation and Camera. I'll focus on those.
On Tue, Sep 9, 2014 at 7:01 AM, Marcel Kinard cmarc...@gmail.com wrote:
Then I would suggest that folks work on the outstanding pull requests for
the plugins, such as merging in whatever they think is ready or closing
Hey,
I have been working for the past few weeks on getting cordova-browser up and
running, along with a few plugins to go with it. Everything is currently
pushed and ready to be used. I have added support for the following plugins:
- camera
- device
- device-motion
- device-orientation
-
Getting off track here a bit.
Here's what I'm suggesting with my original email:
https://github.com/agrieve/cordova-android/compare/apache:4.0.x...no_disable_timers?expand=1
I was further asking if there was any use in ever pausing timers (aka,
removing the KeepRunning preference).
On Wed,
Pausing timers means that the JS isn't running in the background at all.
This now means that the Javascript is running constantly, regardless of
whether it's an event. This means that setInterval is still running. This
could break people's applications.
On Wed, Sep 10, 2014 at 5:29 PM, Andrew
Big -1 for breaking current background behaviour.
Or am I misunderstanding?
On 11 Sep 2014 10:34, Joe Bowser bows...@gmail.com wrote:
Pausing timers means that the JS isn't running in the background at all.
This now means that the Javascript is running constantly, regardless of
whether
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-test-framework/pull/5
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Hi Sergey, I am moving, so mobile only until next week. My high level browse of
your code seemed fine though.
On Sep 9, 2014, at 1:13 AM, sgrebnov g...@git.apache.org wrote:
Github user sgrebnov commented on the pull request:
36 matches
Mail list logo
