But if you want a better webview and still use phonegap api you can try
project crosswalk
Enviado desde mi Windows PhoneFrom: Carlos Santana
Sent: 9/2/2014 5:29
To: dev@cordova.apache.org
Subject: Re: Cordova and Android 4.4 (KitKat)
From
GitHub user puneetgkaur opened a pull request:
https://github.com/apache/cordova-lib/pull/83
Adding the sugar platform to cordova
Hello all,
We have worked on building the cordova layer for the sugarlabs platform.We
have also tried and tested it.
You can see the
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-wp8/pull/53
CB-7444 Fixes XHR callback failure when requested file doesn't exists
Fix for https://issues.apache.org/jira/browse/CB-7444
You can merge this pull request into a Git repository by
+1
- Verified signatures and hashes for cordova-blackberry
- Verified sha1 match tag 3.6.0
- Ran mobile spec on various BB10 devices and OS versions
Steve - I added you as an owner for cordova-blackberry10 on npm. The
cordova-blackberry package should probably be unpublished.
On Tue, Sep 2,
I see cordova cli rc on npm, I want to test it using npm but I get errors.
Maybe cordova-lib should be also posted to npm but not make it latest until
we release.
I get this errors:
$ npm install cordova@rc
npm ERR! Error: version not found: cordova-lib@0.21.8
On Tue, Sep 2, 2014 at 9:29 AM,
I was able to get the traces from a real Kindle Fire device, and also get
benchmarks. I installed a Chromium shell, and ran the commands, that are an
equivalent of
adb shell am broadcast -a org.chromium.chrome.testshell.GPU_PROFILER_START.
This was using a Chrome shell, and I was wondering
Or you can try out the 4.0.x branch and get involved in that effort.
Crosswalk currently works, and GeckoView is a Work in Progress.
On Tue, Sep 2, 2014 at 12:52 AM, julio cesar sanchez jcesarmob...@gmail.com
wrote:
But if you want a better webview and still use phonegap api you can try
We cannot post to npm without the vote passing. There is a bunch of crazy
overhead tag bs we could do, but then we would not be voting on the final
released binaries.
Just test with --usegit
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana csantan...@gmail.com wrote:
Agree with Jesse. If you still want to test it, I tried doing it with a private
npm registry, and changed my npm to pick up from that registry. I did not see a
lot of value added though. I did this when I was playing with the idea of using
npm to use plugins.
-Original Message-
From:
Actually, I like Carlos suggestion.
We have already been publishing to npm under the RC tag for testing (not
releasing to public but just for dev testing).
The last few releases you could go npm install cordova@rc and that would
download the RC version of cordova that we were voting on.
I went
Github user ldeluca commented on the pull request:
https://github.com/apache/cordova-docs/pull/230#issuecomment-54189011
@Watabe08 We don't handle translations like this in Cordova. We use the
crowdin tool to easily translate using their tool and then migrate the
translations into
We could ask Apache folk for clarification, but if I understand the
requirements for release process correct, I think publishing an rc and
voting on it would be totally acceptable provided that:
(a) *exactly* the tarball that went up to RC is used as the final release,
so that signatures match.
.. Looks like cordova-cli still has a VERSION file set to 3.5.0-0.2.4. Is
it even used?
.. and cordova-cli deps on cordova-lib which deps on cordova-js which has
VERSION file set to 3.6.0-dev.
On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny mmo...@chromium.org wrote:
We could ask Apache folk
Looks like CLI VERSION file is incorrect :( Didn't get updated. Also looks
like the zip i uploaded for the CLI got generated incorrectly. Need to take
a deeper look.
I don't see cordova-js 3.6.0-dev Version file anywhere.
I'm also running into an issue with firefoxos testing. Looks like it can't
Another mistake I found, wp8's package.json was set to 3.6.0-dev on the
3.6.x branch. I had to update that to publish to npm under rc tag.
This vote is going to need to get restarted, but I suggest we continue to
test what is uploaded to see if any more fixes are needed.
On Tue, Sep 2, 2014 at
I was just trying to validate what we put in npmjs.org matches what is
located on [1]
If both matches then it doesn't matter how you do your testing with npm or
the content of [1].
I'm guessing that everyone is testing using [1] and not apache git checkout
hash from this email. But if they match
I think validation should be part of VOTE, actually as the first step to
testing a release. No sense testing a proposed release if its not known to
be the right thing.
We have a coho command that does verify-archive and I usually start testing
with running that, perhaps now we need to add a coho
Github user sgrebnov closed the pull request at:
https://github.com/apache/cordova-lib/pull/82
---
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 if the feature
This won't be an issue until a plugins release, but in the plugins should the
version of the test plugin (cordova-plugin-*/tests/plugin.xml) also be
incremented at the same time and to the same value as the plugin itself?
On Sep 2, 2014, at 1:57 PM, Steven Gill stevengil...@gmail.com wrote:
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-plugin-file-transfer/pull/41
Fixed some tests for wp8
- spec 7 changed to check for x-wmapp:0/ in case of wp
- spec 27 marked pending on wp due to lack of implementation
You can merge this pull request
Anytime we have a mistake that can easily be avoided or validated by
automation, it would seem to be a good thing to automate.
Today I had a thought about adding another option to createmobilespec.js to
instantiate the test project from whatever is in cordova-dist-dev and the rest
from npm /
If we restart the thread, will we be able to complete it before Steven gone on
vacation or someone else will be able to accomplish this?
Thx!
Sergey
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Tuesday, September 2, 2014 9:57 PM
To: dev@cordova.apache.org
I will get the blog post + updated dists ready and start the vote thread.
Someone else will have to close the vote thread + publish packages blog
post.
Any volunteers for that? Jesse? I need to add whoever it is to all of the
npm repos.
On Tue, Sep 2, 2014 at 11:58 AM, Sergey Grebnov (Akvelon)
Restarting the vote will not allow us to complete it before Steve is on
vacation, but assuming the vote passes, we can still release it regardless.
If the only issues that come up today are administrative, I would like to
recommend that we do a quick vote, on the assumption that the
Yes. I can do that.
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 12:44 PM, Steven Gill stevengil...@gmail.com wrote:
I will get the blog post + updated dists ready and start the vote thread.
Someone else will have to close the vote thread + publish packages blog
post.
Any volunteers
lazynessI used to have a link bookmarked on stackoverflow/lazyness
Here are two links that mentions overall which devices have that problem:
http://stackoverflow.com/q/23205511
http://stackoverflow.com/q/11134903
The devices I have in hand that show that behaviour, however, are Samsung
Galaxy S2
GitHub user eymorale opened a pull request:
https://github.com/apache/cordova-plugin-file-transfer/pull/42
CB-7423 fix spec28,29 lastProgressEvent not visible to afterEach functio...
...n
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user eymorale opened a pull request:
https://github.com/apache/cordova-plugin-file/pull/78
CB-7423 encode path before attempting to resolve
For some of the tests in mobilespec, files aren't getting deleted at
cleanup so you get a PATH_EXISTS error on the second run. The
Github user eymorale commented on the pull request:
https://github.com/apache/cordova-plugin-file-transfer/pull/42#issuecomment-54218903
This fixes a test issue that was throwing a ReferenceError to
lastProgressEvent in specs 28 and 29
---
If your project is set up for it, you can
I would also be willing to do it, so feel free to use me now or in the future.
On Sep 2, 2014, at 3:46 PM, Jesse purplecabb...@gmail.com wrote:
Yes. I can do that.
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 12:44 PM, Steven Gill stevengil...@gmail.com wrote:
I will get the
I'm officially closing this vote thread, new one will be up shortly.
Thanks Marcel :). I'll make sure to add you to the repos just in case too.
On Tue, Sep 2, 2014 at 2:46 PM, Marcel Kinard cmarc...@gmail.com wrote:
I would also be willing to do it, so feel free to use me now or in the
Please review and vote on this 3.6.0 Cadence Release.
Release issue: https://issues.apache.org/jira/browse/CB-7383
Repos ready to be released have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
The packages were published from their corresponding git tags:
GitHub user stevengill opened a pull request:
https://github.com/apache/cordova-coho/pull/37
Added proper npm publishing info
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stevengill/cordova-coho patch-15
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-coho/pull/37
---
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 if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-file-transfer/pull/42
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-coho/pull/38
---
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 if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-wp8/pull/53
---
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 if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-docs/pull/229
---
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 if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/81
---
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 if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/80
---
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 if the feature is
Hey All,
Quick update for everyone
Marcel has volunteered to finish off the 3.6.0 release. Make sure to email
the list with any questions. I'm sure someone will be able to help you. I
have added you + others to all of our npm packages.
The 3.6.0 vote is ongoing and should be finished by Friday.
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-camera/pull/46
---
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 if the
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-camera/pull/44
---
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 if the
43 matches
Mail list logo
