My experience with Cordova (and other tools for that matter) is that it
makes no sense to change tool generated files.
If the tool is improved you do not benefit from this improvement because
your modified files will be changed by the new version.
If you change a tool generated file you are out.
Github user sgrebnov commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/57#discussion_r14868912
--- Diff: cordova-lib/src/cordova/metadata/ios_parser.js ---
@@ -217,6 +220,38 @@ module.exports.prototype = {
self.update_overrides();
GitHub user G3z opened a pull request:
https://github.com/apache/cordova-wp8/pull/45
small fix for spaces in path
this fixes the error about missing create.js if user has a space in his
home folder
You can merge this pull request into a Git repository by running:
$ git pull
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-app-hello-world/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
Github user JohnMcLear commented on the pull request:
https://github.com/apache/cordova-app-hello-world/pull/8#issuecomment-48886202
Thanks guys :)
---
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
Github user AxelNennker closed the pull request at:
https://github.com/apache/cordova-docs/pull/219
---
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 AxelNennker commented on the pull request:
https://github.com/apache/cordova-docs/pull/219#issuecomment-48887679
This PR changes too many files.
I will resubmit it after I have cleaned up my fork of cordova-docs.
---
If your project is set up for it, you can reply to
GitHub user AxelNennker opened a pull request:
https://github.com/apache/cordova-docs/pull/220
CB-3571: update the docs for the splash screens
The former documentation for splash screens was for the Phonegap build
system.
The pull request updates the documentation to describe
I closed my former PR #219, deleted my fork of cordova-docs, reforked,
updated images.md, pushed and created another PR:
https://github.com/apache/cordova-docs/pull/220
Which now only has one changed file.
Axel
2014-07-14 1:30 GMT+02:00 Ray Camden rayca...@adobe.com:
Thank you - I finally
Hi,
I would like to subscribe for the mailing lists.
--
*Rahul Pandey*
*General Manager IT*
*Application Nexus Webservices Pvt. Ltd.*
101-105, Center One,
Next to Ashoka Buildcon,
Ashoka Marg, Nasik - 422 011
Maharashtra. INDIA
Office:+91-253-2236556
Mobile: +91-9665993073
GitHub user sgrebnov opened a pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/53
CB- 5109 Windows 8.1 - InAppBrowser.
https://issues.apache.org/jira/browse/CB-5109
Adds support of 'x-ms-webview' available in Windows 8.1 and Windows Phone
8.1.
Github user sgrebnov commented on the pull request:
https://github.com/apache/cordova-docs/pull/220#issuecomment-48901707
Axel, could you please
1. swap Windows Phone8 and Windows8 sections so that they follow the same
order as in Icons section, + use the same order in 'Supported
Thx Axel. Reviewed, looks good to me. Added a few notes to github.
-Sergey
-Original Message-
From: Axel Nennker [mailto:ignisvul...@gmail.com]
Sent: Monday, July 14, 2014 3:33 PM
To: dev
Subject: Re: recent tools update, Splash screen support
I closed my former PR #219, deleted my fork
Tests on Windows:
I've compared Wercker and Appveyor and as for me it looks like Appveyor is a
better option to proceed for Windows since
1. Wercker's existing windows boxes doesn't support building of Windows 8.1
and WP 8.1 apps due to absence of Windows 8.1 and WP 8.1 SDKs on the boxes.
2.
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-js/pull/68
---
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-android/pull/103
---
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-android/pull/100
---
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-mobile-spec/pull/71
---
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
Okay, so here are the current proposals for handling Ray's issue (thanks
Ray!):
1. Update docs at commit-time and release-time. At commit-time,
documentation changes can be marked with coming soon, or removed in next
release, or whatever the relevant message is. At release-time, docs are
Just wondering if we already had the Monthly hangouts for this month. We
usually have it on 15th every month, right ?
Also, I remember that from the last hangout, we had trouble getting more than
10 people into the hangout. Do we want to try alternate solutions (Webex, Lync,
or a conference
The call is scheduled for tomorrow evening.
On 14 Jul 2014 11:44, Parashuram Narasimhan (MS OPEN TECH)
panar...@microsoft.com wrote:
Just wondering if we already had the Monthly hangouts for this month. We
usually have it on 15th every month, right ?
Also, I remember that from the last
GitHub user AMAdacto opened a pull request:
https://github.com/apache/cordova-plugin-device/pull/16
Added Name into device property for iOS
Added device name property
You can merge this pull request into a Git repository by running:
$ git pull
I think we can also use a combination of these. For small changes where it
makes sense, just push to master and be conscious of its effect on the
current tools release out in the wild. If the change is significant and
inline documentation gets hairy, just create a branch.
A side benefit of
Personally I'd rather not have any coming soon paragraphs in the doc text. As
a user, if I'm at the docs, I don't care what is coming next. I'm trying to
solve a problem I have *now*, or trying to build now. Anything that is coming
soon is a distractor.
Do I feel strongly about it? No, but I'd
I agree. I think 3 is my preferred option; I think it lends itself best to
a sustainable and straightforward workflow.
Docs fixes relevant to the current release of the CLI and each platform can
be committed directly to master. Unreleased changes can be committed to
the appropriate branch, and
I would prefer to have the 'coming soon' stuff more visible.
I like the idea that when looking for how to do something, its easy to see
improvements that have already landed - and I can possibly get just by
grabbing a bleeding edge plugin/tool.
On Mon, Jul 14, 2014 at 1:25 PM, Max Woghiren
anyone want to take a stab at an agenda? (no major blockers/issues for us
in Vancouver/SF atm)
On Mon, Jul 14, 2014 at 8:49 AM, David Kemp drk...@chromium.org wrote:
The call is scheduled for tomorrow evening.
On 14 Jul 2014 11:44, Parashuram Narasimhan (MS OPEN TECH)
panar...@microsoft.com
think that sort of thing belongs to a preview blog post written by the
person promising it will land not our canonical docs
On Mon, Jul 14, 2014 at 10:30 AM, David Kemp drk...@chromium.org wrote:
I would prefer to have the 'coming soon' stuff more visible.
I like the idea that when looking
I added a couple of items for 3.6.0 release for Windows Universal apps. We also
decided to talk about the min/max Android and iOS versions right (Joe's
questions about this) ?
@Lisa, would this be too early to talk about configurable folders in the CLI?
-Original Message-
From:
I have logged an issue related to this [1]
On 3.5.0-0.2.6, I can no longer specify a single default icon for Android.
Is this by design?
The docs imply it should be possible and it worked on 3.5.0-0.2.4
[1] https://issues.apache.org/jira/browse/CB-7132
On Sun, Jun 22, 2014 at 5:38 AM, Axel
Joe is still PTO (and hopefully enjoying the shit out of it) so that'll
have to wait
On Mon, Jul 14, 2014 at 10:48 AM, Parashuram Narasimhan (MS OPEN TECH)
panar...@microsoft.com wrote:
I added a couple of items for 3.6.0 release for Windows Universal apps. We
also decided to talk about the
Please send an email to the appropriate mailing list subscription
address as described on our homepage:
http://cordova.apache.org/index.html#mailing-list
On Mon, Jul 14, 2014 at 3:40 AM, Rahul Pandey
rahu...@applicationnexus.com wrote:
Hi,
I would like to subscribe for the mailing lists.
--
Github user clelland commented on the pull request:
https://github.com/apache/cordova-plugin-file/pull/60#issuecomment-48936357
Wow, thanks for taking that on; it's a lot of work!
(I had previously done most of this last year, on
There's probably a better place for that information. Also, in practice,
you can imagine how coming soon documentation could be kind of clunky,
especially in cases where it's just a behavior change (right now, X does Y
and Z; soon it will do K as well, and M instead of Y).
I'm sure such changes
Github user agrieve commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48938359
Change needs to be rebased I need to you confirm you've signed Apache's
ICLA http://www.apache.org/licenses/#clas
---
If your project is set up for it, you can
We should just use Travis for quick sanity check tests.
re: integration testing
Getting into all the other build+test options is too close to Medic. Unless
we plan to abandon Medic, we should focus on getting Medic+BuildBot working
perfectly across all platforms, then possibly even reporting back
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-file/pull/60
---
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-ios/pull/99
---
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
https://issues.apache.org/jira/browse/CB-7000
They were documented in 2.x, but not in 3.x.
According to the deprecation policy
(http://wiki.apache.org/cordova/DeprecationPolicy), it will be
deprecated in the next release (changes are already in trunk), and
removed in 3.9.0.
If it was a publicly
Github user agrieve commented on a diff in the pull request:
https://github.com/apache/cordova-ios/pull/97#discussion_r14897935
--- Diff: CordovaLib/Classes/CDVCommandDelegateImpl.m ---
@@ -107,6 +107,10 @@ - (BOOL)isValidCallbackId:(NSString *)callbackId
return
I would suggest that we have every right to drop these in 3.9.0, as you
say, but that in the interest of maintaining goodwill with the community,
this should be a 4.0 change.
If 4.0 also comes with iOS8 WKWebView support, then this has a strong
parallel with Cordova-Android 4.0.x -- the overall
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-globalization/pull/15
---
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 purplecabbage commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48949233
I think this needs to be discussed more before merged, this seems to
potentially break stuff, and the benefit has not clearly been discussed. ( or
No, I'm actually back this week. I'll be in Portland next week for
OSCON, so my availability will be even more sporatic than it is now.
I'll be available for the hangout tomorrow.
On Mon, Jul 14, 2014 at 10:56 AM, Brian LeRoux b...@brian.io wrote:
Joe is still PTO (and hopefully enjoying the
Makes sense - no point in landing this early anyway which will create
friction because of rules. I'll change the removal to 4.0
On Mon, Jul 14, 2014 at 12:35 PM, Ian Clelland iclell...@chromium.org wrote:
I would suggest that we have every right to drop these in 3.9.0, as you
say, but that in
Sergey, can we set up AppVeyor to run the npm test of cordova-lib?
If yes, it would be an excellent option - we will have cordova-lib jasmine
tests running on windows, which otherwise happens rarely for all of us who
develop on Mac or Linux.
On Mon, Jul 14, 2014 at 2:54 PM, Jesse
Github user infil00p commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48951400
init() has been recently deprecated. I'm not convinced that this is
solving a problem that we currently have. I'm not in favour of having
Factories just
Which time slot is this one?
On 15 Jul 2014 05:49, Joe Bowser bows...@gmail.com wrote:
No, I'm actually back this week. I'll be in Portland next week for
OSCON, so my availability will be even more sporatic than it is now.
I'll be available for the hangout tomorrow.
On Mon, Jul 14, 2014 at
http://wiki.apache.org/cordova/Google%20Hangout%20Discussion%20Notes
7PM EST
@purplecabbage
risingj.com
On Mon, Jul 14, 2014 at 1:11 PM, Tommy Williams to...@devgeeks.org wrote:
Which time slot is this one?
On 15 Jul 2014 05:49, Joe Bowser bows...@gmail.com wrote:
No, I'm actually back
Github user qwe2 commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48953658
The idea was that I needed a more modular way of creating plugins that I
had more control over than just relying on Cordova to instantiate arbitrary
classes with
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14900988
--- Diff: plugin.xml ---
@@ -70,6 +70,20 @@
/js-module
/platform
+!-- firefoxos --
+platform
Github user martincgg commented on the pull request:
https://github.com/apache/cordova-plugin-file/pull/60#issuecomment-48954105
The last commit on which is based is after this one:
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14901564
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -0,0 +1,214 @@
+/*
+ *
+ * Licensed to the Apache Software Foundation
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48955669
Thanks István,
I think what I was missing in your pull-request and problem description, is
how your plugin uses the factory to do something that it
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14902768
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -0,0 +1,214 @@
+/*
+ *
+ * Licensed to the Apache Software Foundation
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48958012
I recommend you continue to use a parameter-less constructor and provide
some other interface for setting values in another plugin. You are destined
for
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14903106
--- Diff: doc/index.md ---
@@ -194,6 +197,11 @@ options:
- The `formatLength` option supports only `short` and `full` values.
Github user qwe2 commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48957070
The simplest example that comes to mind would be the need to be able to
pass additional parameters to a custom set of plugins or do something with them
at
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14903135
--- Diff: doc/index.md ---
@@ -194,6 +197,11 @@ options:
- The `formatLength` option supports only `short` and `full` values.
I added something about a default secure configuration: no whitelist, no
permissions, etc., that hopefully plays into the whitelist-as-a-plugin
topic that I don't think was ever resolved. Maybe this can be a more
general discussion about security but probably not.
On Mon, Jul 14, 2014 at 4:16
Github user perilousleigh commented on the pull request:
https://github.com/apache/cordova-lib/pull/30#issuecomment-48961753
After checking the code it doesn't look like it's expecting the land or
port prefixes in the density attribute. So removing the orientation prefix
and just
GitHub user AxelNennker opened a pull request:
https://github.com/apache/cordova-lib/pull/58
CB-7132: fix regression regarding default resources
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AxelNennker/cordova-lib master
Github user AxelNennker commented on the pull request:
https://github.com/apache/cordova-lib/pull/30#issuecomment-48963855
@perilousleigh
On Android the default splash screen are in the land/port directories.
The example above uses the same directories.
Please add output
I agree with the core message from Axel, but I'd refrase that last line as:
The bottom line is: either use Cordova CLI or not.
Cordova can still be used without the CLI portion just as well, which
should suffice Jan for his needs.
However, I'll add that you can still use Cordova with the CLI
GitHub user cordoval opened a pull request:
https://github.com/apache/cordova-cli/pull/184
adding .gush.yml for contribuing
|Q|A |
|--- |---|
|Bug Fix? |no |
|New Feature? |no |
|BC Breaks? |no |
@Shazron: Is there any option to subscribe cordova mailing list, but with
receiving only e-mails from threads which I sent message into?
It uses ezmlm, so unless there is a way through it, probably not.
On Mon, Jul 14, 2014 at 3:46 PM, Jan Velecký vve...@seznam.cz wrote:
@Shazron: Is there any option to subscribe cordova mailing list, but with
receiving only e-mails from threads which I sent message into?
If you're touching any non-www project files (that is *.xml, *.plist, *.m,
*.java etc...) or are using an IDE you should not be using cordova-cli and
switch to single platform development. Browse the documentation and there
is always the equivalent platform command available to you. Example:
Sooo.. translation:
“If you aren’t just making a test / example app…”
??
Unless a lot has changed that I don’t know about, it is still impossible to
make an app all the way to market without modifying those non-www files using
the CLI.
There are fantastic workarounds available (mostly hooks,
Github user kamrik commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/58#discussion_r14914123
--- Diff: cordova-lib/src/cordova/metadata/android_parser.js ---
@@ -42,6 +42,12 @@ module.exports = function android_parser(project) {
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-statusbar/pull/4
---
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 asfgit closed the pull request at:
https://github.com/apache/cordova-js/pull/73
---
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-plugin-file/pull/57
---
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-android/pull/105
---
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-file/pull/24
---
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-android/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
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-android/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
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-inappbrowser/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 agrieve commented on the pull request:
https://github.com/apache/cordova-android/pull/97#issuecomment-48985460
Sounds like maybe we abandon this PR.
Plugins have an initialize() method that you can override to do extra
constructor-time logic.
I've tweaked the API
Github user clelland commented on the pull request:
https://github.com/apache/cordova-plugin-file/pull/60#issuecomment-48985942
Yeah, the URL/URI messages have been there a long time; I just figured I'd
take the opportunity to clean them up now, especially as the console log is
much
Merge artefact.
Am 15.07.2014 03:46 schrieb kamrik g...@git.apache.org:
Github user kamrik commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/58#discussion_r14914123
--- Diff: cordova-lib/src/cordova/metadata/android_parser.js ---
@@ -42,6 +42,12
Could you please give an example which files you need to change and why?
(Preferably Android)
Thanks
Axel
Am 15.07.2014 02:23 schrieb tommy-carlos williams to...@devgeeks.org:
Sooo.. translation:
“If you aren’t just making a test / example app…”
??
Unless a lot has changed that I don’t
82 matches
Mail list logo
