Github user zalun closed the pull request at:
https://github.com/apache/cordova-plugin-network-information/pull/9
---
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,
Github user zalun commented on the pull request:
https://github.com/apache/cordova-plugin-geolocation/pull/17#issuecomment-42288344
Please ship it
---
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
Github user cristi-badila closed the pull request at:
https://github.com/apache/cordova-plugin-file/pull/21
---
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 Jonasei opened a pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/43
Added handeling of tel: and mailto: URLs in WP8
You can merge this pull request into a Git repository by running:
$ git pull
It's because you can supply a URL *or* a local path. Maybe you could switch
on the presence of http: / https:
On Mon, May 5, 2014 at 4:07 PM, Martin Gonzalez Glez
martin.c.glez.g...@gmail.com wrote:
I'm not sure why is an url.parse, but unless that I'm wrong about it, the
custom libraries
The person who filed the ticket can re-open.
On Mon, May 5, 2014 at 5:46 PM, Mark Koudritsky kam...@google.com wrote:
The mirroring should've been already working. I left a comment on the INFRA
ticket that was use to create the repo. Looks like I don't have the
permissions to reopen that
+dev@
Hi Michael, thanks for pointing that out. I've just made a change to master
to fix the docs. The correct value is bundle.
I don't think you'll be able to do what you want though. This location is
read-only. What you could do instead is copy your assets to the PERSISTENT
filesystem
BTW: Have you signed the ICLA yet? If not we should get that taken care of
ASAP
Intel has signed the CCLA as corporate contributor. So I assume I think I don't
need to sign ICLA, correct?
Thanks,
-ningxin
On May 5, 2014 5:56 PM, Hu, Ningxin ningxin...@intel.com wrote:
Ian,
I
Any updates for me?
--
Gorkem
On Fri, Apr 18, 2014 at 10:21 PM, Michal Mocny mmo...@chromium.org wrote:
On Fri, Apr 18, 2014 at 4:11 PM, Gorkem Ercan gorkem.er...@gmail.com
wrote:
On Thu, Apr 17, 2014 at 3:46 PM, Michal Mocny mmo...@chromium.org
wrote:
Took a quick glance. General
Hi everyone,
After Ray's great work on the Next Steps article, I decided to finally
start the Whitlist and Security Guide doc, located here:
https://docs.google.com/document/d/13C6ZUZiqP83MQX0MvFlyVUZef-nT4cJwyd-qSvXLkK4/edit#
This is an attempt to resolve CB-2179 and CB-5786, and will also be
BTW: Have you signed the ICLA yet? If not we should get that taken care
of
ASAP
Hu, Ningxin wrote:
Intel has signed the CCLA as corporate contributor. So I assume I think
I don't need to sign ICLA, correct?
http://www.apache.org/licenses/#clas
Note that a Corporate CLA does not remove
This plugin is helpful though I can't help but wonder if we can't shoehorn
into specs (or at least provide spec feedback).
Right now all config is done w/ config.xml instead of programmatic (?)
On Tue, May 6, 2014 at 7:06 AM, Andrew Grieve agri...@chromium.org wrote:
Closer than ever to
Hey
Here's where the logs are for pluggable_webview:
https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=shortlog;h=refs/heads/pluggable_webview
The repo URL itself is located here:
https://git-wip-us.apache.org/repos/asf/cordova-android.git
Basically, once we're confident enough
Oops! Sorry this was supposed to be private. Please don't respond here.
-Steve
On Tue, May 6, 2014 at 11:57 AM, Steven Gill stevengil...@gmail.com wrote:
Hello Piotr!
The Apache Cordova Project Management Committee (PMC) hereby offers
you committer privileges to the project, as well as
Hello Piotr!
The Apache Cordova Project Management Committee (PMC) hereby offers
you committer privileges to the project, as well as membership in the
PMC. These privileges are offered on the understanding that you'll use
them reasonably and with common sense. We like to work on trust rather
than
Although https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;a=summary
has number of commits, https://github.com/apache/cordova-lib is empty. That
makes pull requests difficult. ;-)
Is there some config that needs to be performed by Infra or us? I'm not
familiar with how the replication
Yeah, it's a good idea to sign the ICLA -- if nothing else, it makes it
really obvious that you know you are deliberately contributing code to an
Apache project, and then we can feel much more comfortable accepting your
contributions. It's something that we've required from all contributors,
and
My understanding is that as a corporate contributor, you need both a CCLA from
your corporation and an ICLA as an individual in that corporation. See the
Contributor License Agreement section of http://www.apache.org/licenses/ .
On May 6, 2014, at 11:18 AM, Hu, Ningxin ningxin...@intel.com
There are two types of config for file:
1. You can do is disable parts of the filesystem (doubt anyone would do
this)
2. You can switch where PERSISTENT filesystem maps to (sane place vs legacy
place)
What's missing is a way to retrieve the paths that you might want. No
configuration required for
ya I agree the cordova global is fine, I guess, but kind of retro and
annoying (and a candidate for grab bag property anti-pattern)
On Tue, May 6, 2014 at 10:16 AM, purplecabbage purplecabb...@gmail.comwrote:
Good work.
APIs need better names/signatures I think. Will see what I come up with.
Apparently re-opening the issue is clicking on the WaitingForInfra button:
https://issues.apache.org/jira/browse/INFRA-7596
On Tue, May 6, 2014 at 12:40 PM, Marcel Kinard cmarc...@gmail.com wrote:
Although
https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;a=summary has
number of
Hey
I know that for some reason, we decided to use node 0.11 for coho, but
the thing is that it means that we can't run the Unit Tests on
cordova-js now. At least on my machine, coho will now always fail
because of either named branch errors or Unit Test errors. This seems
to be some weird
That is a very good point! I say it is good enough for now. Something to
flag for our W3C friends to look at and consider in the spec.
On Tue, May 6, 2014 at 1:43 PM, Andrew Grieve agri...@chromium.org wrote:
There are two types of config for file:
1. You can do is disable parts of the
I've found it persistently odd that of all things to choose to be lax on it
would be a CLA. It should be considered a MUST even if sometimes people say
it isn't.
On Tue, May 6, 2014 at 12:50 PM, Ian Clelland iclell...@chromium.orgwrote:
Yeah, it's a good idea to sign the ICLA -- if nothing
I had the same problem with nodejs 0.11, using url.parse module and
running the Unit Test on cordova-js, those are failing with nodejs 0.11.13,
but with 0.11.12 it works fine.
Nodejs 0.11 it's working unestable, they are going to release one more
11.xx version before nodejs 0.12 (According to
We shouldn't be depending on unstable versions of node, imo.
Being able to switch versions is not a solution.
@purplecabbage
risingj.com
On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez
martin.c.glez.g...@gmail.com wrote:
I had the same problem with nodejs 0.11, using url.parse module
OK, so using 0.11.12 does work to get coho working. Does anyone other
than me think that this is completely stupid?
On Tue, May 6, 2014 at 3:47 PM, Jesse purplecabb...@gmail.com wrote:
We shouldn't be depending on unstable versions of node, imo.
Being able to switch versions is not a solution.
Agree guys we shouldn't be depending on unstable node versions to work,
just sharing what it worked for me. I think coho has been using node 0.11
since the last clean up a few days ago.
Hey Joe, I've just shared with you my findings, it's not the best solution
I know that, but it worked for me.
Thanks for sharing Martin!
I also am on the train that we shouldn't be using unstable versions of
node. I don't know if the landscape has changed since I started using node,
but I was always taught to stick to even version numbers.
On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez
I got excited and tried to use the latest version of coho but when I saw
that it was using an odd version I just gave up.
On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote:
Thanks for sharing Martin!
I also am on the train that we shouldn't be using unstable versions
30 matches
Mail list logo
