Re: Do we have a commits mailing list?

[Dmitry Blotsky]

The Buildbot announcements that make it to the list signify critical issues: 
build machines going down. I will look into making the emails go to the machine 
owner.

Kindly,
Dmitry

> On May 26, 2015, at 8:28 PM, Carlos Santana  wrote:
> 
> Agree dev@ being noisy with build bot announcements.
> 
> On Thu, May 21, 2015 at 3:11 PM Shazron  wrote:
> 
>> Yup, make sure your sender subscribes by sending an email to
>> commits-subscr...@cordova.apache.org first.
>> Send an email to commits-h...@cordova.apache.org for more info
>> 
>> On Thu, May 21, 2015 at 12:03 PM, Jesse  wrote:
>>> We do. comm...@cordova.apache.org
>>> There is duplication with github, so if it is too noisy you'll need to
>>> setup filters.
>>> 
>>> @purplecabbage
>>> risingj.com
>>> 
>>> On Thu, May 21, 2015 at 11:56 AM, Dmitry Blotsky >> 
>>> wrote:
>>> 
 Hey folks,
 
 Do we have something like a comm...@cordova.apache.org>>> comm...@cordova.apache.org>? If so, do you think we should, so we don't
 keep getting commits and PRs to dev@cordova.apache.org>>> dev@cordova.apache.org>? Or is sending them to dev@ fine?
 
 Kindly,
 Dmitry
 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-camera pull request: CB-8054 Support taking picture...

[ekambarrao]

Github user ekambarrao commented on the pull request:


https://github.com/apache/cordova-plugin-camera/pull/86#issuecomment-105808283
  
muratsu, I have footer in the page where I activate the camera, camera has 
"cancel" but it is going under the footer. How can I control the size of the 
camera screen??


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-contacts pull request: Android - Filter search: Con...

[jonmikelm]

GitHub user jonmikelm opened a pull request:

https://github.com/apache/cordova-plugin-contacts/pull/64

Android - Filter search: Contacts with informed phone number only

When searching for all the contacts in Android, by default all the google 
contacts(Gmail history, etc...) are returned. This causes performance problems 
when the number of contacts is big.

Usually, we only want contacts that have a phone number informed. I have 
addes a new optional boolean parameter to the options object of the "find" 
method: "phoneNumberInformedOnly"

If we send true in this parameter, the where clause of the select to the 
contacts database will include:
  
  "AND (" + ContactsContract.Contacts.HAS_PHONE_NUMBER + " = 1)"
  
This filter is also added if a filter string is sent to the search method.

Use case:

// find all contacts with 'Bob' in any name field
var options  = new ContactFindOptions();
options.multiple = true;
options.phoneNumberInformedOnly = true;
options.desiredFields = [navigator.contacts.fieldType.id];
var fields   = [navigator.contacts.fieldType.displayName, 
navigator.contacts.fieldType.name];
navigator.contacts.find(fields, onSuccess, onError, options);

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jonmikelm/cordova-plugin-contacts master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-contacts/pull/64.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #64


commit 98de740287fa8b70d989d88ddc4352d76b0e295b
Author: jonmikelm 
Date:   2015-05-27T08:12:22Z

phoneNumbersInformedOnly




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Automatic update of files in CrowdIn

[Andrey Kurdumov]

Just read the Tools release are coming.
Would be good if latest docs would be uploaded to CrowdIn?
This give me time in advance to translate before 5.1 release published.

Also could some one review
https://github.com/apache/cordova-docs/pull/289

I continue working on improving tooling for catching errors in translations.


2015-05-27 6:21 GMT+06:00 Steven Gill :

> Not a bad idea. Would be tough to pull off due to apache committer
> restrictions.
>
> To update edge per commit, it would require generating each commit and then
> also having someone with commit access (hosted on the cordova site's svn
> which only committers can publish to I believe) to push it live.
>
> I agree with you that we should be publishing docs more often.
>
> Feel free to look into it. More automation is better here.
>
> For now, just message the list asking for a release (which language, edge,
> specific version, etc). We will try to help you get them out.
>
> -Steve
>
> On Fri, May 22, 2015 at 9:50 PM, Andrey Kurdumov 
> wrote:
>
> > Hi all,
> >
> > During the work on translation, I always in rush to produce it before
> > release, because of docs updated not very often. Maybe we could configure
> > Git to publish docs after commit, so on CrowdIn would be always the
> latest
> > docs?
> >
> > Thanks
> >
>

[GitHub] cordova-windows pull request: CB-9073 Fixes build error when path ...

[vladimir-kotikov]

Github user vladimir-kotikov commented on the pull request:

https://github.com/apache/cordova-windows/pull/85#issuecomment-105848653
  
Yup, this still works fine.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: CB-8889 Persist app/package name and...

[vladimir-kotikov]

GitHub user vladimir-kotikov opened a pull request:

https://github.com/apache/cordova-windows/pull/87

CB-8889 Persist app/package name and product ID during platform update



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-windows CB-8889

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-windows/pull/87.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #87


commit 4786bbfdeea7bac32dfc8e7d1df1537b627dbc38
Author: Vladimir Kotikov 
Date:   2015-05-27T11:22:54Z

CB-8889 Persist app/package name and product ID during platform update




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-contacts pull request: Android - Filter search: Con...

[purplecabbage]

Github user purplecabbage commented on the pull request:


https://github.com/apache/cordova-plugin-contacts/pull/64#issuecomment-105878860
  
Can we make the option param name simply 'hasPhoneNumber'?



---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-contacts pull request: Android - Filter search: Con...

[purplecabbage]

Github user purplecabbage commented on the pull request:


https://github.com/apache/cordova-plugin-contacts/pull/64#issuecomment-105879343
  
Please document the new param and create a JIRA ticket also. This should 
potentially be done on other platforms also. 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Do we have a commits mailing list?

[Carlos Santana]

Make sense Dmitry
On Wed, May 27, 2015 at 3:28 AM Dmitry Blotsky 
wrote:

> The Buildbot announcements that make it to the list signify critical
> issues: build machines going down. I will look into making the emails go to
> the machine owner.
>
> Kindly,
> Dmitry
>
> > On May 26, 2015, at 8:28 PM, Carlos Santana 
> wrote:
> >
> > Agree dev@ being noisy with build bot announcements.
> >
> > On Thu, May 21, 2015 at 3:11 PM Shazron  wrote:
> >
> >> Yup, make sure your sender subscribes by sending an email to
> >> commits-subscr...@cordova.apache.org first.
> >> Send an email to commits-h...@cordova.apache.org for more info
> >>
> >> On Thu, May 21, 2015 at 12:03 PM, Jesse 
> wrote:
> >>> We do. comm...@cordova.apache.org
> >>> There is duplication with github, so if it is too noisy you'll need to
> >>> setup filters.
> >>>
> >>> @purplecabbage
> >>> risingj.com
> >>>
> >>> On Thu, May 21, 2015 at 11:56 AM, Dmitry Blotsky <
> dblot...@microsoft.com
> >>>
> >>> wrote:
> >>>
>  Hey folks,
> 
>  Do we have something like a comm...@cordova.apache.org  comm...@cordova.apache.org>? If so, do you think we should, so we
> don't
>  keep getting commits and PRs to dev@cordova.apache.org  dev@cordova.apache.org>? Or is sending them to dev@ fine?
> 
>  Kindly,
>  Dmitry
> 
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> >> For additional commands, e-mail: dev-h...@cordova.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

[GitHub] cordova-plugin-contacts pull request: Android - Filter search: Con...

[jonmikelm]

Github user jonmikelm commented on the pull request:


https://github.com/apache/cordova-plugin-contacts/pull/64#issuecomment-105889981
  
I changed the param name and readme file. I have also opened a JIRA but I'm 
not sure if I've filled the form correctly. It's the first I open...

https://issues.apache.org/jira/browse/CB-9078



---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: CB-9074 Fixed incorrect parameter er...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-windows/pull/86


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: "Best" place to browse plugins

[Tommy-Carlos Williams]

+1



> On 26 May 2015, at 21:44, Carlos Santana  wrote:
> 
> I would like to see plugin.cordova.io be a page easy to search and filter
> cordova plugins just like gulp [1], grunt [2], yeoman [3] and bower [4]
> 
> [1]: http://gulpjs.com/plugins
> [2]: http://gruntjs.com/plugins
> [3]: http://yeoman.io/generators
> [4]: http://bower.io/search
> 
> 
> 
> On Sat, May 2, 2015 at 3:57 PM Michael Brooks 
> wrote:
> 
>>> 
>>> The mirroring may not help for search, but my worry is that a lot of
>> folks
>>> would still be on 4.3.0 and when cordova plugins registry becomes read
>>> only, they would not get bug fixes and other plugin updates.
>> 
>> 
>> My experience is this:
>> 
>> - A developer who is willing to upgrade a platform is also willing to
>> upgrading a plugin.
>> - A developer who is *not* willing to upgrade a platform is also *not*
>> willing in upgrading a plugin.
>> 
>> I think it's reasonable to offer a read-only state for the legacy plugin
>> registry. However, it would be helpful for the registry to explain the
>> minimum Cordova version required to support the npm registry.
>> 
>> Michael
>> 
>> On Fri, May 1, 2015 at 9:01 AM, Parashuram N (MS OPEN TECH) <
>> panar...@microsoft.com> wrote:
>> 
>>> The mirroring may not help for search, but my worry is that a lot of
>> folks
>>> would still be on 4.3.0 and when cordova plugins registry becomes read
>>> only, they would not get bug fixes and other plugin updates.
>>> 
>>> -Original Message-
>>> From: Victor Sosa [mailto:sosah.vic...@gmail.com]
>>> Sent: Friday, May 1, 2015 8:59 AM
>>> To: dev@cordova.apache.org
>>> Subject: Re: "Best" place to browse plugins
>>> 
>>> I don't see a value on mirroring either. Instead I'd like to see a good
>>> querying mechanism in NPM, but for that we have to wait :/
>>> 
>>> 2015-05-01 10:55 GMT-05:00 Raymond Camden :
>>> 
 I don't know - if npm is the place, then having a mirror just seems
 like noise. I'd say close it down and put a nice text message up on
 the site explaining where it is at NPM and how to search. (Link to npm
 with the search params included.)
 
 Is there a benefit of having it mirrored?
 
 
 
 On Fri, May 1, 2015 at 10:49 AM, Parashuram N (MS OPEN TECH)
  wrote:
> It would be even better (for backward compatibility reasons) if we
> could
 simply publish on npm, but keep plugins.cordova.io as a
 mirror/redirector, based on the Cordova registry mapper.
> 
> -Original Message-
> From: Gorkem Ercan [mailto:gorkem.er...@gmail.com]
> Sent: Friday, May 1, 2015 8:31 AM
> To: dev@cordova.apache.org
> Subject: Re: "Best" place to browse plugins
> 
> 
> What is the plan for plugins.cordova.io for after the CPR is closed?
> Without knowing if there is a good way to retrieve the list/details
> of
 the cordova plugins from npm.
> I would love it if we could keep it as it is with the data from npm.
> --
> Gorkem
> 
>> On 29 Apr 2015, at 10:57, Raymond Camden wrote:
>> 
>> With plugins at npm now, what is the "best" place for users to
>> browse plugins?
>> 
>> Is it at npm, using the search filter?
>> https://www.npmjs.com/browse/keyword/ecosystem:cordova
>> 
>> Is it plugins.cordova.io?
>> 
>> If it is npm, will there be text added to plugins.cordova.io to
>> tell folks to start using the npm site?
>> 
>> --
>> ===
>> === = Raymond Camden, Developer Advocate for MobileFirst at IBM
>> 
>> Email : raymondcam...@gmail.com
>> Blog : www.raymondcamden.com
>> Twitter: raymondcamden
>> 
>> ---
>> -- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
> 
> 
> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
> 
> 
> 
> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
 
 
 
 --
 ==
 = Raymond Camden, Developer Advocate for MobileFirst at IBM
 
 Email : raymondcam...@gmail.com
 Blog : www.raymondcamden.com
 Twitter: raymondcamden
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
 For additional commands, e-mail: dev-h...@cordova.apache.org
>>> 
>>> 
>>> --
>>> Victor Adrian Sosa Herrera
>>> IBM Software Engineer
>>> Guadalajara, Jalisco
>> 

---

[GitHub] cordova-mobile-spec pull request: CB-9052 Fixed failure when creat...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-mobile-spec/pull/129


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-mobile-spec pull request: CB-8843 Fixed mobilespec tests t...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-mobile-spec/pull/130


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-mobile-spec pull request: CB-9066 Fixed crash on Windows

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-mobile-spec/pull/132


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: Draft implementation for Unified platfor...

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-lib/pull/226#discussion_r31134829
  
--- Diff: cordova-lib/src/cordova/metadata/PlatformHandler.js ---
@@ -0,0 +1,100 @@
+/**
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+*/
+
+/* jshint sub:true */
+
+'use strict';
+
+var path = require('path');
+var shell = require('shelljs');
+var util = require('../util');
+var ParserHelper = require('./parserhelper/ParserHelper');
+
+/**
+ * Base module for platform parsers
+ *
+ * @param {String} [platform]Platform name (e.g. android)
+ * @param {String} [projectPath] path/to/platform/project
+ */
+function PlatformHandler (platform, projectPath) {
+
+this.platform = platform || '';
+this.root = this.path = projectPath || '';
+
+// Extend with a ParserHelper instance
+Object.defineProperty(this, 'helper', {
+value: new ParserHelper(this.platform),
+enumerable: true,
+configurable: false,
+writable: false
--- End diff --

We can always change behavior of `parser` if we'll have any problems later 
so i would prefer to leave it as-is.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: Draft implementation for Unified platfor...

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-lib/pull/226#discussion_r31134853
  
--- Diff: cordova-lib/src/cordova/metadata/PlatformHandler.js ---
@@ -0,0 +1,100 @@
+/**
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+*/
+
+/* jshint sub:true */
+
+'use strict';
+
+var path = require('path');
+var shell = require('shelljs');
+var util = require('../util');
+var ParserHelper = require('./parserhelper/ParserHelper');
+
+/**
+ * Base module for platform parsers
+ *
+ * @param {String} [platform]Platform name (e.g. android)
+ * @param {String} [projectPath] path/to/platform/project
+ */
+function PlatformHandler (platform, projectPath) {
+
+this.platform = platform || '';
+this.root = this.path = projectPath || '';
+
+// Extend with a ParserHelper instance
+Object.defineProperty(this, 'helper', {
+value: new ParserHelper(this.platform),
+enumerable: true,
+configurable: false,
+writable: false
+});
+}
+
+/**
+ * Base implementation for getConfigXml. Assumes that config.xml
+ * is placed at the root of project.
+ * @return {String} Path to platform's config.xml file
+ */
+PlatformHandler.prototype.getConfigXml = function() {
+return  path.join(this.root, 'config.xml');
+};
+
+/**
+ * Base implementation for getWwwDir. Assumes that
+ * www directory is placed at the root of project.
+ * @return {String} Path to platform's www directory.
+ */
+PlatformHandler.prototype.getWwwDir = function() {
+return  path.join(this.root, 'www');
+};
+
+/**
+ * Base implementation for getCordovaJsSrc. Assumes that cordova.js
+ * source is placed at the root of platform's source dir.
+ * @return {String} Path to platform's 'cordova-js-src' folder.
+ */
+PlatformHandler.prototype.getCordovaJsSrc = function(platformSource) {
+return path.resolve(platformSource, 'cordova-js-src');
+};
+
+/**
+ * Base implementation for updateWww.
+ */
+PlatformHandler.prototype.updateWww = function() {
+var projectRoot = util.isCordova(this.root);
+var appWww = util.projectWww(projectRoot);
+var platformWww = path.join(this.root, 'platform_www');
--- End diff --

Updated.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-geolocation pull request: CB-8845 Pended tests for ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-geolocation/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 if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-file pull request: CB-8844 Increased timeout for as...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-file/pull/116


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: Draft implementation for Unified platfor...

[vladimir-kotikov]

Github user vladimir-kotikov commented on the pull request:

https://github.com/apache/cordova-lib/pull/226#issuecomment-105921556
  
Yeah, reworking tests will be painful.
BTW, i'm still wondering that so small number of tests is became failing.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-device-motion pull request: CB-8842 Return cached v...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-device-motion/pull/30


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-file-transfer pull request: CB-8951 (wp8) Handle ex...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-file-transfer/pull/84


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: Draft implementation for Unified pla...

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-windows/pull/84#discussion_r31137262
  
--- Diff: template/cordova/Api.js ---
@@ -0,0 +1,54 @@
+
+/*jshint node: true*/
+
+var path = require('path');
+
+var buildImpl = require('./lib/build');
+var requirementsImpl = require('./lib/check_reqs');
+
+function PlatformApi () {
+// Set up basic properties. They probably will be overridden if this 
API is used by cordova-lib
+this.root = path.join(__dirname, '..', '..');
+this.platform = 'windows';
+
+if (this.constructor.super_){
+// This should only happen if this class is being instantiated 
from cordova-lib
+// In this case the arguments is being passed from cordova-lib as 
well,
+// so we don't need to care about whether they're correct ot not
+this.constructor.super_.apply(this, arguments);
+}
+}
+
+PlatformApi.prototype.build = function(context) {
+var buildOptions = context && context.options || [];
+return buildImpl.run(buildOptions);
+};
+
+PlatformApi.prototype.requirements = function () {
+return requirementsImpl.check_all();
+};
+
+function PlatformHandler() {
--- End diff --

> we need to first move all/most of the code from 
cordova/metadata/windows_parser to this file before it gets fully operational

This is correct. However, this shouldn't be a problem, because 
PlatformHandler interface is quite similar to platform parsers in 
cordova/metadata.

Regarding `PlatformHandler` and `PlatformApi` as 2 separate classes - I 
like your idea, but I would like to have a bit more feedback on this. The 
reason why it is implemented this way - i've tried to avoid changes that will 
break compatibility and obstruct the transition to new Api, so now they acts 
like former `PlatformProject` and its `parser` property.

BTW, another possible approach here, we're  thought about, was removing 
`parser` property at all and replace it and its methods with single `prepare()` 
methods which will act more like a "black box" - like `build()`, `run()` and 
others works now.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: "Best" place to browse plugins

[Kerri Shotts]

+1

I’ve used both Gulp & Yeoman’s search, and prefer both to NPM (although it’s 
not difficult to be better than NPM’s search).

I also think close association with the brand and site are important. For those 
users who don’t know about Node & NPM yet, it’s quickly apparent that there’s a 
large community creating plugins for Cordova, and for everyone else, we have a 
URL that helps reinforce the Cordova name. NPM would still be canonical, of 
course.

(Now if NPM improved their search and did some nice work around ecosystems, 
perhaps the above wouldn’t be necessary. But I’m not going to hold my breath…)




On May 27, 2015 at 8:19:35 AM, Tommy-Carlos Williams (to...@devgeeks.org) wrote:

+1  



> On 26 May 2015, at 21:44, Carlos Santana  wrote:  
>  
> I would like to see plugin.cordova.io be a page easy to search and filter  
> cordova plugins just like gulp [1], grunt [2], yeoman [3] and bower [4]  
>  
> [1]: http://gulpjs.com/plugins  
> [2]: http://gruntjs.com/plugins  
> [3]: http://yeoman.io/generators  
> [4]: http://bower.io/search  
>  
>  
>  
> On Sat, May 2, 2015 at 3:57 PM Michael Brooks   
> wrote:  
>  
>>>  
>>> The mirroring may not help for search, but my worry is that a lot of  
>> folks  
>>> would still be on 4.3.0 and when cordova plugins registry becomes read  
>>> only, they would not get bug fixes and other plugin updates.  
>>  
>>  
>> My experience is this:  
>>  
>> - A developer who is willing to upgrade a platform is also willing to  
>> upgrading a plugin.  
>> - A developer who is *not* willing to upgrade a platform is also *not*  
>> willing in upgrading a plugin.  
>>  
>> I think it's reasonable to offer a read-only state for the legacy plugin  
>> registry. However, it would be helpful for the registry to explain the  
>> minimum Cordova version required to support the npm registry.  
>>  
>> Michael  
>>  
>> On Fri, May 1, 2015 at 9:01 AM, Parashuram N (MS OPEN TECH) <  
>> panar...@microsoft.com> wrote:  
>>  
>>> The mirroring may not help for search, but my worry is that a lot of  
>> folks  
>>> would still be on 4.3.0 and when cordova plugins registry becomes read  
>>> only, they would not get bug fixes and other plugin updates.  
>>>  
>>> -Original Message-  
>>> From: Victor Sosa [mailto:sosah.vic...@gmail.com]  
>>> Sent: Friday, May 1, 2015 8:59 AM  
>>> To: dev@cordova.apache.org  
>>> Subject: Re: "Best" place to browse plugins  
>>>  
>>> I don't see a value on mirroring either. Instead I'd like to see a good  
>>> querying mechanism in NPM, but for that we have to wait :/  
>>>  
>>> 2015-05-01 10:55 GMT-05:00 Raymond Camden :  
>>>  
 I don't know - if npm is the place, then having a mirror just seems  
 like noise. I'd say close it down and put a nice text message up on  
 the site explaining where it is at NPM and how to search. (Link to npm  
 with the search params included.)  
  
 Is there a benefit of having it mirrored?  
  
  
  
 On Fri, May 1, 2015 at 10:49 AM, Parashuram N (MS OPEN TECH)  
  wrote:  
> It would be even better (for backward compatibility reasons) if we  
> could  
 simply publish on npm, but keep plugins.cordova.io as a  
 mirror/redirector, based on the Cordova registry mapper.  
>  
> -Original Message-  
> From: Gorkem Ercan [mailto:gorkem.er...@gmail.com]  
> Sent: Friday, May 1, 2015 8:31 AM  
> To: dev@cordova.apache.org  
> Subject: Re: "Best" place to browse plugins  
>  
>  
> What is the plan for plugins.cordova.io for after the CPR is closed?  
> Without knowing if there is a good way to retrieve the list/details  
> of  
 the cordova plugins from npm.  
> I would love it if we could keep it as it is with the data from npm.  
> --  
> Gorkem  
>  
>> On 29 Apr 2015, at 10:57, Raymond Camden wrote:  
>>  
>> With plugins at npm now, what is the "best" place for users to  
>> browse plugins?  
>>  
>> Is it at npm, using the search filter?  
>> https://www.npmjs.com/browse/keyword/ecosystem:cordova  
>>  
>> Is it plugins.cordova.io?  
>>  
>> If it is npm, will there be text added to plugins.cordova.io to  
>> tell folks to start using the npm site?  
>>  
>> --  
>> ===  
>> === = Raymond Camden, Developer Advocate for MobileFirst at IBM  
>>  
>> Email : raymondcam...@gmail.com  
>> Blog : www.raymondcamden.com  
>> Twitter: raymondcamden  
>>  
>> ---  
>> -- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org  
>> For additional commands, e-mail: dev-h...@cordova.apache.org  
>  
>   
> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org  
> For ad

[GitHub] cordova-windows pull request: Draft implementation for Unified pla...

[kamrik]

Github user kamrik commented on a diff in the pull request:

https://github.com/apache/cordova-windows/pull/84#discussion_r31144880
  
--- Diff: template/cordova/Api.js ---
@@ -0,0 +1,54 @@
+
+/*jshint node: true*/
+
+var path = require('path');
+
+var buildImpl = require('./lib/build');
+var requirementsImpl = require('./lib/check_reqs');
+
+function PlatformApi () {
+// Set up basic properties. They probably will be overridden if this 
API is used by cordova-lib
+this.root = path.join(__dirname, '..', '..');
+this.platform = 'windows';
+
+if (this.constructor.super_){
+// This should only happen if this class is being instantiated 
from cordova-lib
+// In this case the arguments is being passed from cordova-lib as 
well,
+// so we don't need to care about whether they're correct ot not
+this.constructor.super_.apply(this, arguments);
+}
+}
+
+PlatformApi.prototype.build = function(context) {
+var buildOptions = context && context.options || [];
+return buildImpl.run(buildOptions);
+};
+
+PlatformApi.prototype.requirements = function () {
+return requirementsImpl.check_all();
+};
+
+function PlatformHandler() {
--- End diff --

The only reason I kept the parser property when switching to 
PlatformProject was backwards compatibility as well, with the hope to deprecate 
it once the rest of the code is changed to use methods of the PlatformProject 
directly. Actually there are very few direct calls to the parser left in 
cordova-lib, it's mostly used by the tests (which will have to change anyway).

The "prepare" has several sub-steps which might be interesting to the 
outside user as separate steps:
 * apply plugin config munges
 * apply config.xml based config changes to global project files
 * copy www
So I'm not sure prepare should be a single black box, but the above steps 
should definitely be methods of the PlatformApi rather than of some sub-object, 
and there can be a "prepare" method that executes all 3 of those steps for 
convenience.

Here is an example usage of a PlatformProject from a gulp file with 
separate calls to the above 3 stages.
https://github.com/kamrik/cordova-api-example/blob/master/gulpfile.js#L105
The plugin config munges are applied as part of gulp "create" task, and the 
other two as part of gulp "build" task. This allows for a much faster build for 
projects with many plugins. But slower for adding/removing plugins (which is a 
less frequent operation).

Whichever direction you decide to take it, thanks for picking up this API 
work!


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-media pull request: CB-9079 Increased timeout for p...

[alsorokin]

GitHub user alsorokin opened a pull request:

https://github.com/apache/cordova-plugin-media/pull/55

CB-9079 Increased timeout for playback tests

https://issues.apache.org/jira/browse/CB-9079

This is a fix for failing tests on 
http://ci.apache.org/builders/cordova-android-win

I was unable to reproduce the failures on any of my devices or emulators, 
but given that spec.17 fails with "Error creating Media object" message, I am 
pretty confident that this is a timeout issue.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-plugin-media CB-9079

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-media/pull/55.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #55


commit fea7609c450a1f7e608d187b7a413dbd0746a31a
Author: alsorokin 
Date:   2015-05-27T15:21:52Z

CB-9079 Increased timeout for playback tests




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Couple questions

[Murat Sutunc]

Hey everyone,
I've two simple questions:

1)  How do we close github issues? There are PRs that are older than a year 
and there's no need for having them around. In fact having them around for so 
long can be discouraging to new contributors.

2)  If we want to add pictures to plugin documentation, where should we 
store the pictures? Currently the English doc lives under plugin\README.md, 
translations live under plugin\doc\language\index.md. Should I go ahead and 
create an images folder under docs or will it break some automation we have?

Sorry for the noise :)

Thanks,
Murat

Re: Couple questions

[Shazron]

1) We can't directly. Some have resorted to updating some doc (maybe
we need a dummy doc) and add the text (closes #XX) where XX is the PR
number.
2) Not sure about the breakage part. But I would put it under docs for sure.

On Wed, May 27, 2015 at 9:40 AM, Murat Sutunc  wrote:
> Hey everyone,
> I've two simple questions:
>
> 1)  How do we close github issues? There are PRs that are older than a 
> year and there's no need for having them around. In fact having them around 
> for so long can be discouraging to new contributors.
>
> 2)  If we want to add pictures to plugin documentation, where should we 
> store the pictures? Currently the English doc lives under plugin\README.md, 
> translations live under plugin\doc\language\index.md. Should I go ahead and 
> create an images folder under docs or will it break some automation we have?
>
> Sorry for the noise :)
>
> Thanks,
> Murat

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Couple questions

[Victor Sosa]

Hello Murat.
I can speak on Translation side. No, adding changing images won't break the
translated documents. In fact, in translation process, we take the text
blocks only, not multimedia, HTML format or whatsoever. Lisa can correct me
though.

On Wed, May 27, 2015 at 11:40 AM Murat Sutunc  wrote:

> Hey everyone,
> I've two simple questions:
>
> 1)  How do we close github issues? There are PRs that are older than a
> year and there's no need for having them around. In fact having them around
> for so long can be discouraging to new contributors.
>
> 2)  If we want to add pictures to plugin documentation, where should
> we store the pictures? Currently the English doc lives under
> plugin\README.md, translations live under plugin\doc\language\index.md.
> Should I go ahead and create an images folder under docs or will it break
> some automation we have?
>
> Sorry for the noise :)
>
> Thanks,
> Murat
>

[GitHub] cordova-docs pull request: CB-8900: Documentation for the platform...

[TimBarham]

Github user TimBarham commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/292#discussion_r31158610
  
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,82 @@
+---
+license: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+---
+
+# Platforms and Plugins Version Management
+From version 4.3.0 onwards, Cordova provides the ability to save and 
restore platforms and plugins. 
+
+This feature allows developers to save and restore their app to a known 
state without having to check in all of the platform and plugin source code.
+
+The 'save' command stores details about the app's platform and plugin 
versions in config.xml.
+The 'restore' step happens automatically when a **'cordova prepare'** is 
issued, making use of information previously saved in the config.xml file.
+
+One scenario where save/restore capabilities come in handy is in large 
teams that work on an app, with each team member focusing on a platform or 
plugin. This feature makes it easier to share the project and reduce the amount 
of redundant code that is checked in the repository.
+
+
+## Platform Versioning
+
+### Saving platforms
+To save a platform, you issue the following command :
+
+$ cordova platform add ] | directory | git_url> 
--save
+
+After running the above command, the resulting config.xml looks like :
+
+
+...
+
+...
+
+
+
+Some examples :
+  * **'cordova platform add android --save'** => retrieves the pinned 
version of the android platform, adds it to the project and then updates 
config.xml.
+  * **'cordova platform add android@3.7.0 --save'** => retrieves the 
android platform, version 3.7.0 from npm, adds it to the project and then 
updates config.xml.
+  * **'cordova platform add 
https://github.com/apache/cordova-android.git​ --save'** => clones the 
specified cordova-android git repository, adds the android platform to the 
project, then updates config.xml and point its version to the specified git-url.
+  * **'cordova platform add C:/path/to/android/platform --save'** => 
retrieves the android platform from the specified directory, adds it to the 
project, then updates config.xml and point to the directory.
+
+### Mass saving platforms on an existing project
+The '--save' flag describe above is only useful when you remember to use 
it during the platform addition.
--- End diff --

Typo: 'describe**d**'


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-8900: Documentation for the platform...

[TimBarham]

Github user TimBarham commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/292#discussion_r31158552
  
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,82 @@
+---
+license: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+---
+
+# Platforms and Plugins Version Management
+From version 4.3.0 onwards, Cordova provides the ability to save and 
restore platforms and plugins. 
+
+This feature allows developers to save and restore their app to a known 
state without having to check in all of the platform and plugin source code.
+
+The 'save' command stores details about the app's platform and plugin 
versions in config.xml.
+The 'restore' step happens automatically when a **'cordova prepare'** is 
issued, making use of information previously saved in the config.xml file.
+
+One scenario where save/restore capabilities come in handy is in large 
teams that work on an app, with each team member focusing on a platform or 
plugin. This feature makes it easier to share the project and reduce the amount 
of redundant code that is checked in the repository.
+
+
+## Platform Versioning
+
+### Saving platforms
+To save a platform, you issue the following command :
+
+$ cordova platform add ] | directory | git_url> 
--save
+
+After running the above command, the resulting config.xml looks like :
+
+
+...
+
+...
+
+
+
+Some examples :
+  * **'cordova platform add android --save'** => retrieves the pinned 
version of the android platform, adds it to the project and then updates 
config.xml.
+  * **'cordova platform add android@3.7.0 --save'** => retrieves the 
android platform, version 3.7.0 from npm, adds it to the project and then 
updates config.xml.
+  * **'cordova platform add 
https://github.com/apache/cordova-android.git​ --save'** => clones the 
specified cordova-android git repository, adds the android platform to the 
project, then updates config.xml and point its version to the specified git-url.
--- End diff --

Note that this doesn't actually work. When adding a platform from a 
location (other than a local folder), you currently have to specify the 
platform name. So this should be:

**cordova platform add 
android@https://github.com/apache/cordova-android.git​ --save**


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-8900: Documentation for the platform...

[TimBarham]

Github user TimBarham commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/292#discussion_r31158760
  
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,82 @@
+---
+license: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+---
+
+# Platforms and Plugins Version Management
+From version 4.3.0 onwards, Cordova provides the ability to save and 
restore platforms and plugins. 
+
+This feature allows developers to save and restore their app to a known 
state without having to check in all of the platform and plugin source code.
+
+The 'save' command stores details about the app's platform and plugin 
versions in config.xml.
+The 'restore' step happens automatically when a **'cordova prepare'** is 
issued, making use of information previously saved in the config.xml file.
+
+One scenario where save/restore capabilities come in handy is in large 
teams that work on an app, with each team member focusing on a platform or 
plugin. This feature makes it easier to share the project and reduce the amount 
of redundant code that is checked in the repository.
+
+
+## Platform Versioning
+
+### Saving platforms
+To save a platform, you issue the following command :
+
+$ cordova platform add ] | directory | git_url> 
--save
+
+After running the above command, the resulting config.xml looks like :
+
+
+...
+
+...
+
+
+
+Some examples :
+  * **'cordova platform add android --save'** => retrieves the pinned 
version of the android platform, adds it to the project and then updates 
config.xml.
+  * **'cordova platform add android@3.7.0 --save'** => retrieves the 
android platform, version 3.7.0 from npm, adds it to the project and then 
updates config.xml.
+  * **'cordova platform add 
https://github.com/apache/cordova-android.git​ --save'** => clones the 
specified cordova-android git repository, adds the android platform to the 
project, then updates config.xml and point its version to the specified git-url.
+  * **'cordova platform add C:/path/to/android/platform --save'** => 
retrieves the android platform from the specified directory, adds it to the 
project, then updates config.xml and point to the directory.
+
+### Mass saving platforms on an existing project
+The '--save' flag describe above is only useful when you remember to use 
it during the platform addition.
+If you have a pre-existing project and you want to mass-save all existing 
platforms in it, you can use :
--- End diff --

"mass-save all" is a bit superfluous - how about just "you want to save all 
existing platforms" (although "existing" is perhaps a little unclear - perhaps 
"installed" or "currently added" or something).


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-8900: Documentation for the platform...

[TimBarham]

Github user TimBarham commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/292#discussion_r31159121
  
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,82 @@
+---
+license: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+---
+
+# Platforms and Plugins Version Management
+From version 4.3.0 onwards, Cordova provides the ability to save and 
restore platforms and plugins. 
+
+This feature allows developers to save and restore their app to a known 
state without having to check in all of the platform and plugin source code.
+
+The 'save' command stores details about the app's platform and plugin 
versions in config.xml.
+The 'restore' step happens automatically when a **'cordova prepare'** is 
issued, making use of information previously saved in the config.xml file.
+
+One scenario where save/restore capabilities come in handy is in large 
teams that work on an app, with each team member focusing on a platform or 
plugin. This feature makes it easier to share the project and reduce the amount 
of redundant code that is checked in the repository.
+
+
+## Platform Versioning
+
+### Saving platforms
+To save a platform, you issue the following command :
+
+$ cordova platform add ] | directory | git_url> 
--save
+
+After running the above command, the resulting config.xml looks like :
+
+
+...
+
+...
+
+
+
+Some examples :
+  * **'cordova platform add android --save'** => retrieves the pinned 
version of the android platform, adds it to the project and then updates 
config.xml.
+  * **'cordova platform add android@3.7.0 --save'** => retrieves the 
android platform, version 3.7.0 from npm, adds it to the project and then 
updates config.xml.
+  * **'cordova platform add 
https://github.com/apache/cordova-android.git​ --save'** => clones the 
specified cordova-android git repository, adds the android platform to the 
project, then updates config.xml and point its version to the specified git-url.
+  * **'cordova platform add C:/path/to/android/platform --save'** => 
retrieves the android platform from the specified directory, adds it to the 
project, then updates config.xml and point to the directory.
+
+### Mass saving platforms on an existing project
+The '--save' flag describe above is only useful when you remember to use 
it during the platform addition.
+If you have a pre-existing project and you want to mass-save all existing 
platforms in it, you can use :
+
+$ cordova platform save
+
+
+### Updating / Removing platforms
+It is also possible to update/delete from config.xml during the commands 
'cordova platform update' and 'cordova platform remove' :
+
+$ cordova platform update ] | directory | git_url> 
--save
+$ cordova platform remove  --save
+Some examples :
+  * **'cordova platform update android --save'** => In addition to 
updating the android platform to the pinned version, update config.xml entry
+  * **'cordova platform update android@3.8.0 --save'** => In addition to 
updating the android platform to version 3.8.0, update config.xml entry
+  * **'cordova platform update /path/to/android/platform --save'** => In 
addition to updating the android platform to version in the folder, update 
config.xml entry
+  * **'cordova platform remove android --save'** => Removes the android 
platform from the project and deletes its entry from config.xml.
+
+
+### Restoring platforms
+  * Platforms are automatically restored from config.xml when the 
**'cordova prepare'** command is run.
+  * If you add a platform without specifying a version/folder/git_url, the 
version of the platform that would get added would be one compatible to the one 
in config.xml **if found**.
--- End diff --

How about something like:

If you add a platform without specifying a 

[GitHub] cordova-plugin-media pull request: Fixed the problem with multiple...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-media/pull/33


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-media pull request: CB-9079 Increased timeout for p...

[sgrebnov]

Github user sgrebnov commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/55#issuecomment-106011984
  
merged to master


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: CSP question

[Raymond Camden]

On Tue, May 26, 2015 at 7:12 PM, Steven Gill  wrote:
> Thanks for the blog post Ray! Link for the lazy
> http://www.raymondcamden.com/2015/05/25/important-information-about-cordova-5

Thanks - I was the lazy one for forgetting to post it back here. ;)

-- 
===
Raymond Camden, Developer Advocate for MobileFirst at IBM

Email : raymondcam...@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: CB-8627: Only update fetch.json when plu...

[omefire]

GitHub user omefire opened a pull request:

https://github.com/apache/cordova-lib/pull/228

CB-8627: Only update fetch.json when plugins are successfully installed.

CB-8627: Only update fetch.json when plugins are successfully installed.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-lib CB-8627

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-lib/pull/228.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #228


commit cfbf601e578aab54a2d601065922f42ba56592d5
Author: Omar Mefire 
Date:   2015-05-27T18:25:50Z

CB-8627: Only update fetch.json when plugins are successfully installed.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: CB-8627: Only update fetch.json when plu...

[omefire]

Github user omefire commented on the pull request:

https://github.com/apache/cordova-lib/pull/228#issuecomment-106026407
  
This change makes sure that the fetch.json file only gets updated with 
plugin information once the plugin has been successfully installed. fetch.json 
is considered the source of truth with regards to what plugins are installed.

One particular case this change addresses is that a case of missing 
variables during `cordova plugin add` (e.g: for plugins like facebook-plugin) 
will not end up with fetch.json modified even though the plugin addition failed.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: CB-9073 Fixes build error when path ...

[nikhilkh]

Github user nikhilkh commented on the pull request:

https://github.com/apache/cordova-windows/pull/85#issuecomment-106028591
  
LGTM


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-8783 Document iOS specific callback ...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-docs/pull/276#issuecomment-106066558
  
By silent consensus -- I'll just add the "all" option for iOS and document 
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 have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request:

[wildabeast]

Github user wildabeast commented on the pull request:


https://github.com/apache/cordova-lib/commit/60f19284ce5b8e265e2348ba88907fc47af42007#commitcomment-11395737
  
In cordova-lib/src/plugman/platforms/android.js:
In cordova-lib/src/plugman/platforms/android.js on line 150:
This is breaking us ... why not update the sub-library for 3.6.3, 3.7.0, 
etc?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-media pull request: fix record and play NullPointer...

[uareurapid]

GitHub user uareurapid opened a pull request:

https://github.com/apache/cordova-plugin-media/pull/56

fix record and play NullPointerException

I´ve came across a use case where i always get a NullPointerException:

1 - Start recording audio file
2 - Stop recording
3 - Play the recorded file

When the recording ends, the status is set to "MEDIA_STOPPED", if i try to 
play the recorded file right afterwards, a NullPointerException is thrown at 
line 494 of readyPlayer(...). This happens because the file name is the same as 
the audioFile, and the corresponding switch/case assumes that in this case it 
means that this particular file has already been played before, which is not 
true. At this point there is no "player" object but only a "recorder", 
therefore the exception. With a simple check on the recorder and player it is 
possible to play the newly recorded file without any issues.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/uareurapid/cordova-plugin-media master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-media/pull/56.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #56


commit f977aa7c56a7cb50190dfbb393f09e3314b9f509
Author: uareurapid 
Date:   2015-05-27T22:21:24Z

fix record and play NullPointerException




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Support needed

[Mohamed Ali]

Hello Team,
I'm developing a crossplatform application using cordova 
(Visual studio hyprid multi device application).
I need to open the camera inside of the application without launching the 
camera application.

Requirements:

1-  Back camera should be opened in a frame inside of the page

2-  User can capture photos and videos.

I found "navigator.getUserMedia" that is opening the front camera. Is there any 
way to open the rear camera instead?

Needed platforms:
Android
IPhones

Could you please help?


Thanks & Best Regards,

Mohamed Ali , PMP
Project Manager
[Description: email-logo-smaller.jpg]
M: +20 122 0488  334 |  T: +202 2671 4091 |  F: +202 2670 6016
E:   mohamed_...@omsme.com  |  
www.omsme.com  |



DISCLAIMER:
The Information contained in this transmission may be confidential and legally 
privileged. If you are not the intended recipient, please advise the sender and 
delete this transmission and all copies. Any views or opinions expressed in 
this email are solely by the author and not necessarily those of OMS. OMS is 
not responsible for any political, religious, racial or partisan opinion in any 
correspondence conducted by its domain users. Therefore, any such opinion 
expressed, whether explicitly or implicitly, in any said correspondence is not 
to be interpreted as that of OMS.

[Vote] Tools Release May 27th

[Steven Gill]

Please review and vote on this Tools Release
by replying to this email (and keep discussion on the DISCUSS thread)

Release issue: https://issues.apache.org/jira/browse/CB-9087

Both tools have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-9087/

The packages were published from their corresponding git tags:

cordova-js: 4.0.0 (706c4a8936)
cordova-lib: 5.1.0 (d57d70bbc9)
cordova-plugman: 0.23.2 (d02fcbc8d1)
cordova-cli: 5.1.0 (98fece9a55)

Upon a successful vote I will upload the archives to dist/, publish
them to NPM, and post the corresponding blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran unit tests and saw that they were all building
* Build a cordova project for ios and android and added a plugin.

[GitHub] cordova-coho pull request: Update tools-release-process.md

[stevengill]

GitHub user stevengill opened a pull request:

https://github.com/apache/cordova-coho/pull/81

Update tools-release-process.md



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/stevengill/cordova-coho patch-36

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-coho/pull/81.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #81


commit 0a5bcbec89e2cfd97763d5bbc53c5a7cc551168f
Author: Steve Gill 
Date:   2015-05-28T00:00:12Z

Update tools-release-process.md




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-coho pull request: Update tools-release-process.md

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-coho/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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: [BUG] Fail to build Mobilespec with --thirdpartyplugins (CB-9032)

[Nikhil Khandelwal]

Joe, Andrew, Ian, Michael: I'm hoping one of you can plug this documentation 
gap since you are most knowledgeable about changes from Cordova-android 3.7 to 
4.0.

Thanks,
Nikhil


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Friday, May 15, 2015 4:23 PM
To: dev@cordova.apache.org
Subject: Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins (CB-9032)

I agree.  This is something that I believe that is in the tracker.  The real 
problem with this is that we have no idea what our public API looks like for 
plugin developers, or any documentation as to what the best practices for 
plugin developers are.  As far as regular non-plugin devs are concerned, we 
didn't actually have a breaking API change for Cordova-Android 4.0.0 other than 
the whitelists, which we made into a plugin.

One of the things that we actually fixed/improved in Cordova-Android 4.0, the 
third-party Java dependencies, has no documentation, and we're basically 
directing people to Crosswalk as the way to do this.  We should really be 
adding the documentation, and if anyone wants to take that on, that'd be 
awesome.

On Fri, May 15, 2015 at 4:06 PM Nikhil Khandelwal 
wrote:

> Is there a list of cordova-android 4.0 APIs that have been removed? I 
> think a migration guide from Androind 3.7.1 => Androind 4.0.0 would be 
> super useful.
>
> Thanks,
> Nikhil
>
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Friday, May 15, 2015 7:02 AM
> To: dev@cordova.apache.org
> Subject: Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins
> (CB-9032)
>
> Hey
>
> I just took a look at those, and those are all the methods we decided 
> to remove when we changed the API for Cordova-Android 4.0.  We have no 
> plans on bringing those methods back, so I'm going to close the issue.  
> I recommend filing issues with those repositories to get them to 
> update their plugins to the current API.
>
> On Fri, May 15, 2015 at 1:37 AM Lin, Wanming 
> wrote:
>
> > Hello,
> >
> > It is failed to build Mobilespec with "--thirdpartyplugins" on 
> > Cordova CLI
> > 5.0.0 and latest commit of cordova-mobile-spec.
> > I've filed a JIRA bug: 
> > https://issues.apache.org/jira/browse/CB-9032,
> > could anyone help take a look? Many thanks in advance!
> >
> > Thanks,
> > Wanming
> >
> > 
> > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

[GitHub] cordova-coho pull request: Series of improvements to the list-pull...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-coho/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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: Support needed

[Ryan J. Salva]

Mohamed,

If you check the documentation available for the Camera plugin at 
https://github.com/apache/cordova-plugin-camera#options, you'll find an option 
for cameraDirection.

-
cameraDirection: Choose the camera to use (front- or back-facing). The default 
is BACK. Defined in  navigator.camera.Direction  (Number)

Camera.Direction = {
BACK : 0,  // Use the back-facing camera
FRONT : 1  // Use the front-facing camera
};
-

Hope this helps.
rjs

Ryan J. Salva  |  Principal Program Manager Lead
Visual Studio Tools for Apache Cordova
rsa...@microsoft.com
425 706 5270 office
206 612 5079 mobile



My team is hiring. 

From: Mohamed Ali [mailto:mohamed_...@omsme.com] 
Sent: Wednesday, May 27, 2015 4:19 PM
To: dev@cordova.apache.org; dev-ow...@cordova.apache.org
Cc: Samah Seddik
Subject: Support needed

Hello Team,
    I'm developing a crossplatform application using cordova 
(Visual studio hyprid multi device application).
I need to open the camera inside of the application without launching the 
camera application.

Requirements:
1- Back camera should be opened in a frame inside of the page
2- User can capture photos and videos.

I found "navigator.getUserMedia" that is opening the front camera. Is there any 
way to open the rear camera instead?

Needed platforms:
Android
IPhones

Could you please help?


Thanks & Best Regards,

Mohamed Ali , PMP
Project Manager
 
M: +20 122 0488  334 |  T: +202 2671 4091 |  F: +202 2670 6016 
E:   mohamed_...@omsme.com  |  www.omsme.com  |  



DISCLAIMER:
The Information contained in this transmission may be confidential and legally 
privileged. If you are not the intended recipient, please advise the sender and 
delete this transmission and all copies. Any views or opinions expressed in 
this email are solely by the author and not necessarily those of OMS. OMS is 
not responsible for any political, religious, racial or partisan opinion in any 
correspondence conducted by its domain users. Therefore, any such opinion 
expressed, whether explicitly or implicitly, in any said correspondence is not 
to be interpreted as that of OMS.



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Building cordova.js on first build

[Andrew Grieve]

Certainly would be nice to have the create scripts generate cordova.js in
the same way CLI does. Maybe have the create script call into cordova-js?

Would it make sense in this case to have platforms depend on cordova-js,
rather than the other way around?

Having cordova-js depend on platforms means:
- we have pinned versions of platforms in cordova-lib
- we have pinned versions of platforms in cordova-js
- cordova-lib depends on cordova-js, meaning platforms are double-pinned?

Is it possible that the pinned versions could get out of sync? Seems
possible...

I think there's probably two ways that we can simplify the dependencies:
1. Have platforms depend on cordova-js, and have their create script know
how to generate a cordova.js
2. Have platforms' create script require a --path-to-cordova-js flag.

We could actually do both, since in CLI we don't download package
dependencies when adding downloading platform packages.

On Tue, May 26, 2015 at 9:14 PM, Murat Sutunc  wrote:

> I think this would be a valuable addition to coho.
>
> +1
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Tuesday, May 26, 2015 5:40 PM
> To: dev@cordova.apache.org
> Subject: Re: Building cordova.js on first build
>
> npm linking is suggested when testing platform specific JS changes.
>
> cordova-coho's prepare-release-branch command will generate cordova.js and
> move it over to the platform, as well as other things, when doing a
> release. It might be worth breaking out the generating and moving JS part
> of that step in coho to make that command standalone so platform developers
> could do cordova-coho update-js -r windows to generate + copy cordova.js
> into cordova-windows (sibling to cordova-coho).
>
>
>
>
>
> On Tue, May 26, 2015 at 5:25 PM, Murat Sutunc 
> wrote:
>
> > Thanks Steven for clarifying this for me.
> >
> > For now I'll update the www\cordova.js manually for the windows platform.
> > Windows cordova.js is outdated and I'm hitting a bug.
> >
> > Personally, I'm +1 with auto generating cordova.js but it's not as
> > easy as I originally thought because of the dependencies.
> >
> > Currently, updating cordova.js is also not so trivial. We have a
> > folder structure like this:
> >
> > Cordova Project
> > ├─┬ cordova-js @ Dev (local) Version
> > │ └── cordova-windows @ NPM Version
> > └── cordova-windows @ Dev (local) Version
> >
> > For platform developers the easiest workflow is to npm-link
> > cordova-js\cordova-windows to cordova-windows. Once linked you have to
> > grunt compile cordova-js and manually move file over cordova-windows.
> >
> > On second thought, regenerating cordova.js from cordova-cli is not a
> > great idea. For browserify workflow it makes a lot of sense because we
> > don't know which plugins the user has but otherwise the file is static.
> >
> > -Original Message-
> > From: Steven Gill [mailto:stevengil...@gmail.com]
> > Sent: Tuesday, May 26, 2015 5:10 PM
> > To: dev@cordova.apache.org
> > Subject: Re: Building cordova.js on first build
> >
> > If people are into it, I can handle this one as I am very familiar
> > with the code base since I just did it for the browserify workflow.
> >
> > On Tue, May 26, 2015 at 4:15 PM, Steven Gill 
> > wrote:
> >
> > > Hey Murat,
> > >
> > > By two files you mean cordova-js-src and www\cordova.js I assume.
> > > The www\cordova.js file is generated and updated on each release of
> > > the platform. It will use cordova-js-src to build it when available
> > > (instead of legacy-exe version)
> > >
> > > Problem with removing www\cordova.js and building it on runtime is
> > > that we loose support of platforms being able to build cordova
> > > projects independently of cordova-cli. We would have to have
> > > cordova.js as a dependency for each platform to be able to keep the
> > > ./bin/create scripts still having access to a cordova.js file.
> > >
> > > Right now, the browserify way builds cordova.js at runtime with the
> > > CLI by grabbing cordova-js-src from platform_www of added platforms
> > > or from cordovajs/src/legacy-exec if cordova-js-src doesn't exist
> > > (older
> > > platforms) . Because of this, we already have cordovajs as a
> > > dependency of cordova-lib. So theoretically, we could build
> > > cordova.js at runtime for non-browserify use case using a similar
> workflow.
> > >
> > > I think we should keep the www\cordova.js for now, and add
> > > non-browserify runtime cordova.js generation behind a flag so we can
> > > test it out. I see the value in it because we have use cases where
> > > we update the platform specific JS (in cordova-js-src) but can't
> > > test without generating a new cordova.js and moving it over to our
> platforms.
> > >
> > > Obviously using the --browserify flag will also work for you to be
> > > able to test those platform specific changes.
> > >
> > > On Tue, May 26, 2015 at 3:31 PM, Murat Sutunc
> > > 
> > > wrote:
> > >
> > >> Hey there,
> > >> I've a quick qu

Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins (CB-9032)

[Andrew Grieve]

I'm wary of creating any docs for the Java APIs, since I think they will
inevitably get out of sync with the real code (it's hard enough getting
code comments to match the code).

I think some beefed up Javadocs might be nice, but I think plugin
developers should just read through Cordova's code to see how it works
(there's not that much of it).

I found learning how cordova-android works was vastly easier than learning
how "Android development" works (intents, activities, resources, services,
etc), so I'm not convinced that there's any low-hanging fruit here.



On Wed, May 27, 2015 at 8:59 PM, Nikhil Khandelwal 
wrote:

> Joe, Andrew, Ian, Michael: I'm hoping one of you can plug this
> documentation gap since you are most knowledgeable about changes from
> Cordova-android 3.7 to 4.0.
>
> Thanks,
> Nikhil
>
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Friday, May 15, 2015 4:23 PM
> To: dev@cordova.apache.org
> Subject: Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins
> (CB-9032)
>
> I agree.  This is something that I believe that is in the tracker.  The
> real problem with this is that we have no idea what our public API looks
> like for plugin developers, or any documentation as to what the best
> practices for plugin developers are.  As far as regular non-plugin devs are
> concerned, we didn't actually have a breaking API change for
> Cordova-Android 4.0.0 other than the whitelists, which we made into a
> plugin.
>
> One of the things that we actually fixed/improved in Cordova-Android 4.0,
> the third-party Java dependencies, has no documentation, and we're
> basically directing people to Crosswalk as the way to do this.  We should
> really be adding the documentation, and if anyone wants to take that on,
> that'd be awesome.
>
> On Fri, May 15, 2015 at 4:06 PM Nikhil Khandelwal 
> wrote:
>
> > Is there a list of cordova-android 4.0 APIs that have been removed? I
> > think a migration guide from Androind 3.7.1 => Androind 4.0.0 would be
> > super useful.
> >
> > Thanks,
> > Nikhil
> >
> >
> > -Original Message-
> > From: Joe Bowser [mailto:bows...@gmail.com]
> > Sent: Friday, May 15, 2015 7:02 AM
> > To: dev@cordova.apache.org
> > Subject: Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins
> > (CB-9032)
> >
> > Hey
> >
> > I just took a look at those, and those are all the methods we decided
> > to remove when we changed the API for Cordova-Android 4.0.  We have no
> > plans on bringing those methods back, so I'm going to close the issue.
> > I recommend filing issues with those repositories to get them to
> > update their plugins to the current API.
> >
> > On Fri, May 15, 2015 at 1:37 AM Lin, Wanming 
> > wrote:
> >
> > > Hello,
> > >
> > > It is failed to build Mobilespec with "--thirdpartyplugins" on
> > > Cordova CLI
> > > 5.0.0 and latest commit of cordova-mobile-spec.
> > > I've filed a JIRA bug:
> > > https://issues.apache.org/jira/browse/CB-9032,
> > > could anyone help take a look? Many thanks in advance!
> > >
> > > Thanks,
> > > Wanming
> > >
> > > 
> > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
> >
>

Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins (CB-9032)

[Joe Bowser]

The bigger issue is the question of what is a public API.  Android used
public docs to delineate between public and private APIs and I think we
should do the same, mostly because I want to draw a line between what we
can and can't support and not have everything in third-party tests break
because of a single contributor's opinion.

This also means that when we do deprecate something, we write why. Of
course, we're tight on resources so if anyone wants to take that on, it
would be great. It's been on our to-do list for years and has never
happened.

On Wed, May 27, 2015, 8:05 PM Andrew Grieve  wrote:

> I'm wary of creating any docs for the Java APIs, since I think they will
> inevitably get out of sync with the real code (it's hard enough getting
> code comments to match the code).
>
> I think some beefed up Javadocs might be nice, but I think plugin
> developers should just read through Cordova's code to see how it works
> (there's not that much of it).
>
> I found learning how cordova-android works was vastly easier than learning
> how "Android development" works (intents, activities, resources, services,
> etc), so I'm not convinced that there's any low-hanging fruit here.
>
>
>
> On Wed, May 27, 2015 at 8:59 PM, Nikhil Khandelwal  >
> wrote:
>
> > Joe, Andrew, Ian, Michael: I'm hoping one of you can plug this
> > documentation gap since you are most knowledgeable about changes from
> > Cordova-android 3.7 to 4.0.
> >
> > Thanks,
> > Nikhil
> >
> >
> > -Original Message-
> > From: Joe Bowser [mailto:bows...@gmail.com]
> > Sent: Friday, May 15, 2015 4:23 PM
> > To: dev@cordova.apache.org
> > Subject: Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins
> > (CB-9032)
> >
> > I agree.  This is something that I believe that is in the tracker.  The
> > real problem with this is that we have no idea what our public API looks
> > like for plugin developers, or any documentation as to what the best
> > practices for plugin developers are.  As far as regular non-plugin devs
> are
> > concerned, we didn't actually have a breaking API change for
> > Cordova-Android 4.0.0 other than the whitelists, which we made into a
> > plugin.
> >
> > One of the things that we actually fixed/improved in Cordova-Android 4.0,
> > the third-party Java dependencies, has no documentation, and we're
> > basically directing people to Crosswalk as the way to do this.  We should
> > really be adding the documentation, and if anyone wants to take that on,
> > that'd be awesome.
> >
> > On Fri, May 15, 2015 at 4:06 PM Nikhil Khandelwal <
> nikhi...@microsoft.com>
> > wrote:
> >
> > > Is there a list of cordova-android 4.0 APIs that have been removed? I
> > > think a migration guide from Androind 3.7.1 => Androind 4.0.0 would be
> > > super useful.
> > >
> > > Thanks,
> > > Nikhil
> > >
> > >
> > > -Original Message-
> > > From: Joe Bowser [mailto:bows...@gmail.com]
> > > Sent: Friday, May 15, 2015 7:02 AM
> > > To: dev@cordova.apache.org
> > > Subject: Re: [BUG] Fail to build Mobilespec with --thirdpartyplugins
> > > (CB-9032)
> > >
> > > Hey
> > >
> > > I just took a look at those, and those are all the methods we decided
> > > to remove when we changed the API for Cordova-Android 4.0.  We have no
> > > plans on bringing those methods back, so I'm going to close the issue.
> > > I recommend filing issues with those repositories to get them to
> > > update their plugins to the current API.
> > >
> > > On Fri, May 15, 2015 at 1:37 AM Lin, Wanming 
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > It is failed to build Mobilespec with "--thirdpartyplugins" on
> > > > Cordova CLI
> > > > 5.0.0 and latest commit of cordova-mobile-spec.
> > > > I've filed a JIRA bug:
> > > > https://issues.apache.org/jira/browse/CB-9032,
> > > > could anyone help take a look? Many thanks in advance!
> > > >
> > > > Thanks,
> > > > Wanming
> > > >
> > > > 
> > > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > > >
> > >
> >
>

Re: Support needed

[julio cesar sanchez]

This isn't a support mail, you should ask on stackoverflow.

But that's hiw the plugin works, it launchs the camera app, if you don't
want that you can create your own plugin. I've seen ine that shows the
camera inside of a canvas element, as far as I know, that's the only way to
show the camera inside the html


El jueves, 28 de mayo de 2015, Ryan J. Salva 
escribió:

> Mohamed,
>
> If you check the documentation available for the Camera plugin at
> https://github.com/apache/cordova-plugin-camera#options, you'll find an
> option for cameraDirection.
>
> -
> cameraDirection: Choose the camera to use (front- or back-facing). The
> default is BACK. Defined in  navigator.camera.Direction  (Number)
>
> Camera.Direction = {
> BACK : 0,  // Use the back-facing camera
> FRONT : 1  // Use the front-facing camera
> };
> -
>
> Hope this helps.
> rjs
>
> Ryan J. Salva  |  Principal Program Manager Lead
> Visual Studio Tools for Apache Cordova
> rsa...@microsoft.com 
> 425 706 5270 office
> 206 612 5079 mobile
>
>
>
> My team is hiring.
>
> From: Mohamed Ali [mailto:mohamed_...@omsme.com ]
> Sent: Wednesday, May 27, 2015 4:19 PM
> To: dev@cordova.apache.org ; dev-ow...@cordova.apache.org
> 
> Cc: Samah Seddik
> Subject: Support needed
>
> Hello Team,
> I'm developing a crossplatform application using cordova
> (Visual studio hyprid multi device application).
> I need to open the camera inside of the application without launching the
> camera application.
>
> Requirements:
> 1- Back camera should be opened in a frame inside of the page
> 2- User can capture photos and videos.
>
> I found "navigator.getUserMedia" that is opening the front camera. Is
> there any way to open the rear camera instead?
>
> Needed platforms:
> Android
> IPhones
>
> Could you please help?
>
>
> Thanks & Best Regards,
>
> Mohamed Ali , PMP
> Project Manager
>
> M: +20 122 0488  334 |  T: +202 2671 4091 |  F: +202 2670 6016
> E:   mohamed_...@omsme.com   |  www.omsme.com  |
>
>
>
> DISCLAIMER:
> The Information contained in this transmission may be confidential and
> legally privileged. If you are not the intended recipient, please advise
> the sender and delete this transmission and all copies. Any views or
> opinions expressed in this email are solely by the author and not
> necessarily those of OMS. OMS is not responsible for any political,
> religious, racial or partisan opinion in any correspondence conducted by
> its domain users. Therefore, any such opinion expressed, whether explicitly
> or implicitly, in any said correspondence is not to be interpreted as that
> of OMS.
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org 
> For additional commands, e-mail: dev-h...@cordova.apache.org
> 
>
>

[GitHub] cordova-windows pull request: CB-8889 Persist app/package name and...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-windows/pull/87


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: CB-9073 Fixes build error when path ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-windows/pull/85


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-android pull request: CB-3360 Set custom User-Agent

[delijati]

Github user delijati commented on the pull request:

https://github.com/apache/cordova-android/pull/162#issuecomment-106200325
  
This solution is not sufficient for my needs i need to set the User-Agent 
from JS. 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org