Btw, who will publish cordova-windows to npm? Since the name is not taken (we
previously used cordova-windows8) I can do this, I'm also fine if someone else
who is more experienced in such things will do this.
Windows platform looks like as 100% ready for tagging, Jesse has added Release
notes
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-windows/pull/41
---
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-windows/pull/40
---
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/50
---
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 jsoref opened a pull request:
https://github.com/apache/cordova-blackberry/pull/176
CB-7409 update CORDOVA_HOME_DIR based on npm_cache
CB-7411 Make version in version script easier to replace by coho
You can merge this pull request into a Git repository by running:
Hopefully this gets resolved soon. Seeing how it is a BB only issue, it
won't hinder other platforms from tagging.
On Tue, Aug 26, 2014 at 1:53 PM, Josh Soref wrote:
> There's still a problem w/ blackberry10.
>
> We have code that assumes the location of the blackberry10 code in
> ~/.cordova/li
Okay, JS, mobile-spec and hello world app have all been tagged.
Go ahead and tag your platforms using the commands from
https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md#branch--tag-for-cordova-js-cordova-mobile-spec-and-cordova-app-hello-world.
Just replace 3.5.0
There's still a problem w/ blackberry10.
We have code that assumes the location of the blackberry10 code in
~/.cordova/lib/blackberry10,
https://issues.apache.org/jira/browse/CB-7409
I found this while working on the version script (which we should have
replaced a while ago…).
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-ubuntu/pull/8
---
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 i
I have created the master issue, tagging the js, mobile-spec and hello
world app now.
https://issues.apache.org/jira/browse/CB-7383
Following steps from
https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md
On Tue, Aug 26, 2014 at 1:20 PM, Parashuram Narasimhan (MS
GitHub user jsoref opened a pull request:
https://github.com/apache/cordova-lib/pull/79
CB-7382 Clean up lazy_load: Platform()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jsoref/cordova-lib cb_7382
Alternatively you can revi
Given that both the blockers are now closed, will we be starting a vote thread
next?
-Original Message-
From: Bryan Higgins [mailto:br...@bryanhiggins.net]
Sent: Tuesday, August 26, 2014 1:05 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
BB10 should be good to go n
Github user jsoref closed the pull request at:
https://github.com/apache/cordova-lib/pull/75
---
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 jsoref commented on the pull request:
https://github.com/apache/cordova-lib/pull/75#issuecomment-53483421
This was fixed by
apache/cordova-blackberry@8f9248654791f820490919a876d06bba591f6f6c
---
If your project is set up for it, you can reply to this email and have your
r
Github user nicola commented on the pull request:
https://github.com/apache/cordova-firefoxos/pull/20#issuecomment-53481813
This is outdated, I will write a new PR with using the new little libraries
I made
---
If your project is set up for it, you can reply to this email and have yo
Github user nicola closed the pull request at:
https://github.com/apache/cordova-firefoxos/pull/20
---
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 featu
Github user nicola commented on the pull request:
https://github.com/apache/cordova-firefoxos/pull/20#issuecomment-53481359
I packaged that into https://github.com/nicola/moz-discover-ports
---
If your project is set up for it, you can reply to this email and have your
reply appear on
BB10 should be good to go now.
I published cordova-blackberry10 as a package [1]. We had already updated
the name in package.json due to the strict name checking in CLI, so this
had to be done anyway.
Adding all packages to bundledDependencies works around the 'npm install'
problem [2].
[1] http
The whitelist changes are in, in cordova-android and in cordova-docs now,
so I'm closing that blocker.
On Tue, Aug 26, 2014 at 3:23 PM, Parashuram Narasimhan (MS OPEN TECH) <
panar...@microsoft.com> wrote:
> We found a few issues with Windows Phone 8.1 (whitelist does not allow
> HTTP) that Serg
We found a few issues with Windows Phone 8.1 (whitelist does not allow HTTP)
that Sergey discussed and is fixing.
-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com]
Sent: Tuesday, August 26, 2014 11:54 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I
I was reacting to this in your e-mail:
> The user may choose to check in the user specific config if the entire team
> decides to use that as a project structure. They would not check the
> user-config in cases where individual users use different IDEs.
There should be one directory structure d
I'm running mobile-spec (plugins + non-plugins + automatic + manual +
platforms) with master on Android and finding a few failing tests, but they are
getting fixed. With an impending 3.6.0 release soon, I would assume many others
are doing the same. But perhaps that's not a good assumption.
On
Github user jsoref commented on the pull request:
https://github.com/apache/cordova-lib/pull/75#issuecomment-53469939
@kamrik: i couldn't figure out how in the world to get require()-d npm to
do what I wanted. I even asked in #npm and didn't get any useful responses. (I
was told to tr
I don't understand how to do that.
I don't know what to do.
I don't have whatever permissions are necessary to do it.
No. If someone has the necessary bits, then sure, I guess.
Also, Bryan just got back from his vacation today, so hopefully someone
can do something about it.
On 8/26/14, 2:42 PM,
In the issue, @kamrik suggested a possible quick fix. Can we do that so that
releasing 3.6.0 is not blocked ?
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Wednesday, August 20, 2014 10:56 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
Para
It is the latter. The idea is that there is a default directory structure that
shall be defined by Cordova CLI, and the IDE can modify it, call tasks like
prepare or compile directly from cordova-lib. The IDE could do clever things
like copy only modified files, use symlinks, etc. From the hango
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-js/pull/79
---
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 e
Github user rodms10 commented on the pull request:
https://github.com/apache/cordova-lib/pull/77#issuecomment-53460632
This looks good, thanks for the fix!
---
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 d
GitHub user surajpindoria opened a pull request:
https://github.com/apache/cordova-js/pull/79
CB-7332: Fixed Windows path issues and improved handling transforms of
'module.clobbers' statements
You can merge this pull request into a Git repository by running:
$ git pull https
Github user surajpindoria closed the pull request at:
https://github.com/apache/cordova-js/pull/77
---
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 featu
Thanks, Ian! On Android 4.4, I'm now getting no failures with the all the
automatic tests (new-style plugin tests and old-style non-plugin tests).
Now to start poking at the manual tests...
On Aug 26, 2014, at 11:27 AM, Ian Clelland wrote:
> The other issue should be resolved now, but if someo
Hi, Parashuram
Which device did you try to run your profiling on? Difference between
Android chromium and Amazon Chromium could be underneath chromium version.
KK based android is based on v30. Amazon started with v25 and is now upto
v34 on some devices. Also, amazon' s port has some of the HTML5
The other issue should be resolved now, but if someone with a WP8 device
can test it out as well, it'd be appreciated.
On Tue, Aug 26, 2014 at 9:04 AM, Marcel Kinard wrote:
> I figured out why the values for device.* weren't getting set causing the
> yellow box in mobile-spec to be mostly empty
Yeah this is a platform restriction exclusively related to the security model
related to referencing JavaScript code that is not inside the app package.
There are no restrictions on XHR style calls or general content. At the moment
you need to include that content in a webview control (custom x-
Hmm, I'd like to add Mozilla team as well.
Piotr Zalewa
and Rodrigo Silveira
Thanks
Dnia Fri Aug 15 20:10:36 2014 Joe Bowser pisze:
Technically, companies don't join Apache projects, individuals do.
Furthermore, opinions of contributors may not reflect those of the company
that they work for
Github user sgrebnov commented on the pull request:
https://github.com/apache/cordova-cli/pull/191#issuecomment-53421487
requires administrative privileges to add plugin with -link option (I think
is ok and nothing we can do here), otherwise works as expected
* tested with cordova
Github user sgrebnov commented on the pull request:
https://github.com/apache/cordova-cli/pull/191#issuecomment-53418500
I'll try the code...will report results soon
---
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
Github user smistry-toushay commented on the pull request:
https://github.com/apache/cordova-cli/pull/191#issuecomment-53417619
@purplecabbage unfortunately I do not have access to a windows machine to
test on. I've tested it on OS X. It should have the same behaviour as the
```link``
Wow -- it seems very heavy-handed to force that on app developers (how do
you build a web browsing app in that case?)
Does that apply to all network requests, or just the pages that can be
loaded into the main application window?
Your solution seems like a good one, though; just filter the unusab
I figured out why the values for device.* weren't getting set causing the
yellow box in mobile-spec to be mostly empty. Self-inflicted mistake on my
side. Please disregard.
On Aug 25, 2014, at 5:39 PM, Marcel Kinard wrote:
> Yes, all the other automated tests (except the 4 File tests as previo
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-inappbrowser/pull/58
---
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
Github user zalun commented on the pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/58#issuecomment-53408390
Looks good! - merging
---
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 d
Windows 8.1 and Phone 8.1 requires https for access rules[1], http is not
supported anymore. I've sent PR below [2] to prevent build failure and trace
warning message for this case. One of real cases where it is required is mobile
spec app which cannot' be built since it defines the following ru
GitHub user sgrebnov opened a pull request:
https://github.com/apache/cordova-windows/pull/41
CB-7377 Whitelist. Windows build error due to 'invalid URI rules in
config.xml
https://issues.apache.org/jira/browse/CB-7377
Added logic to filter https:// access rules only.
You
44 matches
Mail list logo
