[GitHub] cordova-windows pull request: CB-7985 Make windows platform suppor...

[daserge]

Github user daserge commented on the pull request:

https://github.com/apache/cordova-windows/pull/51#issuecomment-62513685
  
Hello Jesse,
Added the name, 
Thanks!


---
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-7985 Make windows platform suppor...

[purplecabbage]

Github user purplecabbage commented on the pull request:

https://github.com/apache/cordova-windows/pull/51#issuecomment-62489706
  
Hi @daserge 
Thanks for the commit! 
Can you please add your real name to your github profile so I can resolve 
your github user account to a signed iCLA? I know I've seen and accepted pull 
requests from you before, but I would like the tracking to be as easy as 
possible to resolve.  I would have to do more digging if this was a bigger pull 
request, and I know you have some waiting in other repos.


---
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-7985 Make windows platform suppor...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Add comment section at end of build.grad...

[fujunwei]

Github user fujunwei commented on the pull request:

https://github.com/apache/cordova-lib/pull/117#issuecomment-62483257
  
> @clelland  What happens on upgrade, if a project already has a 
platforms/android/build.gradle file? Do we need to put some code in to either 
replace build.gradle or add the two guard lines in the right place? Or do we 
tell affected people to copy it or recreate their projects?

Add the two lines automatically when upgrade the project.


---
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: [VOTE] Tools Release

[Steven Gill]

Those instructions look good to me

-Steve

On Mon, Nov 10, 2014 at 3:54 PM, Mark Koudritsky  wrote:

> Ok, published new packages and a new vote thread.
>
> Thinking about fixes the the release doc [1].
>
> We need some clear instructions for the case when releasing with an update
> from an existing branch. Does the following sound right?
> Assuming a micro version bump is needed from 4.1.0 to 4.1.1.
>
> * On master, changed 4.1.1-dev in package.json to 4.1.2-dev, commit and
> push
> * On 4.1.x branch
>   - merge any required fixes
>   - change 4.1.0 to 4.1.1
>   - change versions in package.json dependencies appropriately
>   - commit
>   - git tag 4.1.1
>   - git push && git push --tags  (assumes upstream is set properly)
>
>
>
> https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md
>
> On Mon, Nov 10, 2014 at 5:22 PM, Steven Gill 
> wrote:
>
> > In terms of having to bump the version when you have to retag an rc that
> > has been published to npm:
> >
> > The reason why this is necessary is because we want to test exactly what
> we
> > vote on. We push the tgz file that we are voting on to npm under the rc
> > flag. The alternative would be to extract it, change the version in
> > package.json to include `-rc1` to it and then publish (or do this step
> > before building the archive). We would then have to make sure the
> > dependency is correctly set for repos that rely on lib (cli would have to
> > change cordova-lib dependency to include -rc1 to the version for it).
> >
> > This opens us up to errors in the release process and is not worth it.
> > Re-tagging shouldn't happen often. When it does, it should be fairly
> quick
> > as long as we are using release branches (which we are doing according to
> > release doc).
> >
> > On Mon, Nov 10, 2014 at 2:16 PM, Mark Koudritsky 
> > wrote:
> >
> > > This vote is cancelled.
> > >
> > > Blocking issue https://issues.apache.org/jira/browse/CB-8000
> > > Will post a new vote with updated packages
> > >
> > > On Mon, Nov 10, 2014 at 12:34 PM, Sergey Grebnov (Akvelon) <
> > > v-seg...@microsoft.com> wrote:
> > >
> > > > Thank you Mark; Resending link to the fix here since looks like I
> > > answered
> > > > not to the latest email last time.
> > > > https://github.com/apache/cordova-lib/pull/118/
> > > >
> > > > Thx!
> > > > Sergey
> > > > -Original Message-
> > > > From: Mark Koudritsky [mailto:kam...@google.com]
> > > > Sent: Monday, November 10, 2014 9:14 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: Re: [VOTE] Tools Release
> > > >
> > > > Yep, the hash as a versions seems like something that should break
> the
> > > npm
> > > > download as well.
> > > > Sergey, I'll merge your patch and republish rc packages.
> > > > Maria, thanks for finding this.
> > > >
> > > > Note, the lib will have a different version number 4.1.1 because npm
> > > > forbids uploading anything with the same version string more than
> once
> > > [1].
> > > > We should come up with some procedure of promoting RCs that would not
> > > > necessitate bumping the version.
> > > >
> > > > One option is to download the package with x.y.z-rcN from npm, and
> > have a
> > > > script that unpacks it, strips the -rcN and repacks the same files
> > back.
> > > > (not sure how to deal with signing in this case).
> > > >
> > > > [1] - https://github.com/npm/npm-registry-couchapp/issues/148
> > > >
> > > > On Mon, Nov 10, 2014 at 12:06 PM, Sergey Grebnov (Akvelon) <
> > > > v-seg...@microsoft.com> wrote:
> > > >
> > > > > I've found the case will submit the patch shortly - Jira +PR to
> > master
> > > > >
> > > > > Problem cause: we've recently got rid of subdirs for wp8 and
> windows
> > > > > but still have them defined in tools.
> > > > >
> > > > >
> > https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cord
> > > > > ova/platformsConfig.json#L53
> > > > >
> > > > > Thx!
> > > > > Sergey
> > > > > -Original Message-
> > > > > From: Steven Gill [mailto:stevengil...@gmail.com]
> > > > > Sent: Monday, November 10, 2014 8:57 AM
> > > > > To: dev@cordova.apache.org
> > > > > Subject: RE: [VOTE] Tools Release
> > > > >
> > > > > Definitely a problem. Thanks for testing and finding it!
> > > > >
> > > > > -1
> > > > > On Nov 10, 2014 8:51 AM, "Maria Bukharina"
> > > > > 
> > > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I've tried to create app with this rc and discover that adding
> wp8
> > > > > > and windows platforms with --usegit key fails:
> > > > > >
> > > > > > cordova platform add wp8 --usegit
> > > > > > Creating wp8 project...
> > > > > > Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command
> > > > > > failed with exit code ENOENT
> > > > > >  at ChildProcess.whenDone
> > > > > >
> > > > >
> > (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\
> > > > > superspawn.js:135:23)
> > > > > >  at ChildProcess.EventEmitter.emit (events.js:95:17)
> > > 

Re: [VOTE] Tools Release

[Mark Koudritsky]

Ok, published new packages and a new vote thread.

Thinking about fixes the the release doc [1].

We need some clear instructions for the case when releasing with an update
from an existing branch. Does the following sound right?
Assuming a micro version bump is needed from 4.1.0 to 4.1.1.

* On master, changed 4.1.1-dev in package.json to 4.1.2-dev, commit and push
* On 4.1.x branch
  - merge any required fixes
  - change 4.1.0 to 4.1.1
  - change versions in package.json dependencies appropriately
  - commit
  - git tag 4.1.1
  - git push && git push --tags  (assumes upstream is set properly)


https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md

On Mon, Nov 10, 2014 at 5:22 PM, Steven Gill  wrote:

> In terms of having to bump the version when you have to retag an rc that
> has been published to npm:
>
> The reason why this is necessary is because we want to test exactly what we
> vote on. We push the tgz file that we are voting on to npm under the rc
> flag. The alternative would be to extract it, change the version in
> package.json to include `-rc1` to it and then publish (or do this step
> before building the archive). We would then have to make sure the
> dependency is correctly set for repos that rely on lib (cli would have to
> change cordova-lib dependency to include -rc1 to the version for it).
>
> This opens us up to errors in the release process and is not worth it.
> Re-tagging shouldn't happen often. When it does, it should be fairly quick
> as long as we are using release branches (which we are doing according to
> release doc).
>
> On Mon, Nov 10, 2014 at 2:16 PM, Mark Koudritsky 
> wrote:
>
> > This vote is cancelled.
> >
> > Blocking issue https://issues.apache.org/jira/browse/CB-8000
> > Will post a new vote with updated packages
> >
> > On Mon, Nov 10, 2014 at 12:34 PM, Sergey Grebnov (Akvelon) <
> > v-seg...@microsoft.com> wrote:
> >
> > > Thank you Mark; Resending link to the fix here since looks like I
> > answered
> > > not to the latest email last time.
> > > https://github.com/apache/cordova-lib/pull/118/
> > >
> > > Thx!
> > > Sergey
> > > -Original Message-
> > > From: Mark Koudritsky [mailto:kam...@google.com]
> > > Sent: Monday, November 10, 2014 9:14 AM
> > > To: dev@cordova.apache.org
> > > Subject: Re: [VOTE] Tools Release
> > >
> > > Yep, the hash as a versions seems like something that should break the
> > npm
> > > download as well.
> > > Sergey, I'll merge your patch and republish rc packages.
> > > Maria, thanks for finding this.
> > >
> > > Note, the lib will have a different version number 4.1.1 because npm
> > > forbids uploading anything with the same version string more than once
> > [1].
> > > We should come up with some procedure of promoting RCs that would not
> > > necessitate bumping the version.
> > >
> > > One option is to download the package with x.y.z-rcN from npm, and
> have a
> > > script that unpacks it, strips the -rcN and repacks the same files
> back.
> > > (not sure how to deal with signing in this case).
> > >
> > > [1] - https://github.com/npm/npm-registry-couchapp/issues/148
> > >
> > > On Mon, Nov 10, 2014 at 12:06 PM, Sergey Grebnov (Akvelon) <
> > > v-seg...@microsoft.com> wrote:
> > >
> > > > I've found the case will submit the patch shortly - Jira +PR to
> master
> > > >
> > > > Problem cause: we've recently got rid of subdirs for wp8 and windows
> > > > but still have them defined in tools.
> > > >
> > > >
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cord
> > > > ova/platformsConfig.json#L53
> > > >
> > > > Thx!
> > > > Sergey
> > > > -Original Message-
> > > > From: Steven Gill [mailto:stevengil...@gmail.com]
> > > > Sent: Monday, November 10, 2014 8:57 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: RE: [VOTE] Tools Release
> > > >
> > > > Definitely a problem. Thanks for testing and finding it!
> > > >
> > > > -1
> > > > On Nov 10, 2014 8:51 AM, "Maria Bukharina"
> > > > 
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I've tried to create app with this rc and discover that adding wp8
> > > > > and windows platforms with --usegit key fails:
> > > > >
> > > > > cordova platform add wp8 --usegit
> > > > > Creating wp8 project...
> > > > > Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command
> > > > > failed with exit code ENOENT
> > > > >  at ChildProcess.whenDone
> > > > >
> > > >
> (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\
> > > > superspawn.js:135:23)
> > > > >  at ChildProcess.EventEmitter.emit (events.js:95:17)
> > > > >  at Process.ChildProcess._handle.onexit
> > > > > (child_process.js:805:12)
> > > > >
> > > > >
> > > > > Seemed that file platformConfig.json in
> > > > > .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and
> > > > > windows
> > > > > platforms:
> > > > > for wp8 there are wrong version and subdirectory properties:
> > > > > "wp8": {

[VOTE] Tools Release, take 2

[Mark Koudritsky]

Please review and vote on this Tools Release.

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

Packages have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
And to npm under @rc tag

To test them out you can use:
npm -g uninstall cordova
npm -g install cordova@rc

The packages were published from their corresponding git tags:
cordova-js: 3.7.2 (7afadfc044)
cordova-lib: 4.1.1 (5e695e5e1e)
cordova-plugman: 0.22.15 (93fd1e49aa)
cordova-cli: 4.1.1 (5859fa3aa7)

Upon a successful vote I will upload the archives to dist/, publish them to
NPM (under @latest tag), and post the corresponding blog post.

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


I vote +1:
* Ran coho audit-license-headers over the relevant repos
* tested with npm test and mobilespec on Android

Re: [iOS 8] WKWebView moving forward

[tommy-carlos williams]

Yeah… I’ll try to report some of it and get back to you.

-- 
tommy-carlos williams

On 11 November 2014 at 09:50:55, Shazron (shaz...@gmail.com) wrote:

Bug report? Or email me personally. Which ones besides the ones that will  
have problems as we discussed on this thread.  

On Mon, Nov 10, 2014 at 2:41 PM, tommy-carlos williams   
wrote:  

> I had much less success… it doesn’t play well with other legacy plugins,  
> does it?  
>  
>  
>  
> --  
> tommy-carlos williams  
>  
> On 11 November 2014 at 03:00:30, Michal Mocny (mmo...@chromium.org) wrote:  
>  
> Success! I did indeed have to add the framework manually.  
>  
> Thanks for instructions.  
>  
> On Thu, Nov 6, 2014 at 7:49 PM, Shazron  wrote:  
>  
> > There have been major changes to the `wkwebview` branch of `cordova-ios`.  
> > The `WKWebView` functionality has been moved to a plugin in the  
> > `cordova-plugins` repo.  
> >  
> > So, for now you can do:  
> >  
> > cordova create wkwvtest test.project wkwvtest  
> > cd wkwvtest  
> > cordova platform add ios@wkwebview --usegit  
> > cordova plugin add  
> > https://github.com/apache/cordova-plugins.git#master:wkwebview-engine  
> >  
> > Modify the root `config.xml` and edit this value to:  
> >  
> > http://localhost:0"; />  
> >  
> > Then:  
> >  
> > cordova emulate  
> >  
> > You might get a build error, this is a `plugman` bug that doesn't install  
> > `WebKit.framework` properly even though it is defined in plugin.xml. You  
> > might have to do a:  
> >  
> > open -a Xcode platforms/ios  
> >  
> > ...and add the framework manually.  
> >  
> > On Thu, Nov 6, 2014 at 11:15 AM, Shazron  wrote:  
> >  
> > > Thanks Tony - I'll look at that PR when I have some time.  
> > >  
> > > Yesterday I did some major work to isolate the webviews into plugins  
> > > (CDVWKWebViewEngine, CDVUIWebViewEngine). This way we can reduce the  
> risk  
> > > by extracting the WKWebView items into a plugin, and the core has no  
> > > dependency on WebKit.framework anymore, plus speedy (well, speedier)  
> > > updates if it needs updating. The CDVUIWebViewEngine will remain in the  
> > > core as the default engine. I'm still working on this, but it already  
> > works  
> > > currently. I'm abstracting things out more, and removing code from the  
> > > CDVViewController which has become unwieldy.  
> > >  
> > > Swapping out engines would use the preference:  
> > >   
> > >  
> > > Any new web engine needs to implement the new CDVWebViewEngineProtocol  
> > > protocol, and installed as a plugin.  
> > >  
> > > On Mon, Nov 3, 2014 at 6:55 PM, Homer, Tony   
> > wrote:  
> > >  
> > >> I have already forked it and made the changes in a topic branch.  
> > >> I was originally thinking that I would make 2 topic branches: 1 for  
> > >> localhost-only and 1 for auth tokens.  
> > >> However, after I finished the first set of changes I realized that the  
> > >> second set would be dependent on the first.  
> > >> I’ll submit a pull request tomorrow for you to look at - I’ll be happy  
> > to  
> > >> redo it as multiple branches if that makes sense.  
> > >>  
> > >> I got a little sidetracked with local web server plugin, but I’ve also  
> > >> forked cordova-ios and made a topic branch from wkwebview.  
> > >> I'll start working on some of the changes I proposed earlier in this  
> > >> thread tomorrow (for plugins like camera that return file:// urls,  
> > etc.).  
> > >>  
> > >> Tony  
> > >>  
> > >> On 11/3/14, 7:23 PM, "Shazron"  wrote:  
> > >>  
> > >> >Thanks Tony for all the investigation. Please do fork the local web  
> > >> server  
> > >> >plugin and put all your work in topic branches for eventual pull  
> > requests  
> > >> >to the main repo.  
> > >> >  
> > >> >This is precisely why the local web server is a plugin, and not in  
> the  
> > >> >core. I don't profess to be a security expert, and we can update this  
> > >> >plugin to cover most of the security cases or someone else can  
> provide  
> > >> >their better plugin. I don't think this needs to be bulletproof, not  
> > that  
> > >> >we can entirely be (has there ever been a Security Update by Apple  
> that  
> > >> >*didn't* include a WebKit vulnerability?)  
> > >> >  
> > >> >I'd like to get the cordova-ios/wkwebview branch back into the  
> mainline  
> > >> as  
> > >> >soon as possible, but under an experimental flag (--experimental ?)  
> > for  
> > >> >bin/create. This will choose a new template that has WebKit.framework  
> > in  
> > >> >it, which will also define a macro to conditionally compile the new  
> > bits  
> > >> >in  
> > >> >(I haven't added the macros yet in the topic branch).  
> > >> >  
> > >> >  
> > >> >  
> > >> >  
> > >> >On Mon, Nov 3, 2014 at 7:27 AM, Homer, Tony   
> > >> wrote:  
> > >> >  
> > >> >> I spent a lot of time thinking about ways to avoid replay attacks  
> for  
> > >> >>the  
> > >> >> local web server plugin this weekend.  
> > >> >>  
> > >> >> Specifically, I f

Re: [iOS 8] WKWebView moving forward

[Shazron]

Bug report? Or email me personally. Which ones besides the ones that will
have problems as we discussed on this thread.

On Mon, Nov 10, 2014 at 2:41 PM, tommy-carlos williams 
wrote:

> I had much less success… it doesn’t play well with other legacy plugins,
> does it?
>
>
>
> --
> tommy-carlos williams
>
> On 11 November 2014 at 03:00:30, Michal Mocny (mmo...@chromium.org) wrote:
>
> Success! I did indeed have to add the framework manually.
>
> Thanks for instructions.
>
> On Thu, Nov 6, 2014 at 7:49 PM, Shazron  wrote:
>
> > There have been major changes to the `wkwebview` branch of `cordova-ios`.
> > The `WKWebView` functionality has been moved to a plugin in the
> > `cordova-plugins` repo.
> >
> > So, for now you can do:
> >
> > cordova create wkwvtest test.project wkwvtest
> > cd wkwvtest
> > cordova platform add ios@wkwebview --usegit
> > cordova plugin add
> > https://github.com/apache/cordova-plugins.git#master:wkwebview-engine
> >
> > Modify the root `config.xml` and edit this value to:
> >
> > http://localhost:0"; />
> >
> > Then:
> >
> > cordova emulate
> >
> > You might get a build error, this is a `plugman` bug that doesn't install
> > `WebKit.framework` properly even though it is defined in plugin.xml. You
> > might have to do a:
> >
> > open -a Xcode platforms/ios
> >
> > ...and add the framework manually.
> >
> > On Thu, Nov 6, 2014 at 11:15 AM, Shazron  wrote:
> >
> > > Thanks Tony - I'll look at that PR when I have some time.
> > >
> > > Yesterday I did some major work to isolate the webviews into plugins
> > > (CDVWKWebViewEngine, CDVUIWebViewEngine). This way we can reduce the
> risk
> > > by extracting the WKWebView items into a plugin, and the core has no
> > > dependency on WebKit.framework anymore, plus speedy (well, speedier)
> > > updates if it needs updating. The CDVUIWebViewEngine will remain in the
> > > core as the default engine. I'm still working on this, but it already
> > works
> > > currently. I'm abstracting things out more, and removing code from the
> > > CDVViewController which has become unwieldy.
> > >
> > > Swapping out engines would use the preference:
> > > 
> > >
> > > Any new web engine needs to implement the new CDVWebViewEngineProtocol
> > > protocol, and installed as a plugin.
> > >
> > > On Mon, Nov 3, 2014 at 6:55 PM, Homer, Tony 
> > wrote:
> > >
> > >> I have already forked it and made the changes in a topic branch.
> > >> I was originally thinking that I would make 2 topic branches: 1 for
> > >> localhost-only and 1 for auth tokens.
> > >> However, after I finished the first set of changes I realized that the
> > >> second set would be dependent on the first.
> > >> I’ll submit a pull request tomorrow for you to look at - I’ll be happy
> > to
> > >> redo it as multiple branches if that makes sense.
> > >>
> > >> I got a little sidetracked with local web server plugin, but I’ve also
> > >> forked cordova-ios and made a topic branch from wkwebview.
> > >> I'll start working on some of the changes I proposed earlier in this
> > >> thread tomorrow (for plugins like camera that return file:// urls,
> > etc.).
> > >>
> > >> Tony
> > >>
> > >> On 11/3/14, 7:23 PM, "Shazron"  wrote:
> > >>
> > >> >Thanks Tony for all the investigation. Please do fork the local web
> > >> server
> > >> >plugin and put all your work in topic branches for eventual pull
> > requests
> > >> >to the main repo.
> > >> >
> > >> >This is precisely why the local web server is a plugin, and not in
> the
> > >> >core. I don't profess to be a security expert, and we can update this
> > >> >plugin to cover most of the security cases or someone else can
> provide
> > >> >their better plugin. I don't think this needs to be bulletproof, not
> > that
> > >> >we can entirely be (has there ever been a Security Update by Apple
> that
> > >> >*didn't* include a WebKit vulnerability?)
> > >> >
> > >> >I'd like to get the cordova-ios/wkwebview branch back into the
> mainline
> > >> as
> > >> >soon as possible, but under an experimental flag (--experimental ?)
> > for
> > >> >bin/create. This will choose a new template that has WebKit.framework
> > in
> > >> >it, which will also define a macro to conditionally compile the new
> > bits
> > >> >in
> > >> >(I haven't added the macros yet in the topic branch).
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >On Mon, Nov 3, 2014 at 7:27 AM, Homer, Tony 
> > >> wrote:
> > >> >
> > >> >> I spent a lot of time thinking about ways to avoid replay attacks
> for
> > >> >>the
> > >> >> local web server plugin this weekend.
> > >> >>
> > >> >> Specifically, I felt like there should be a way to take advantage
> of
> > >> the
> > >> >> fact that the client and the server are running in the same
> process.
> > >> >> I thought this might enable some kind of sideband (non-http)
> > >> >> authentication possibility.
> > >> >> The 2 possibilities I was most interested in, but eventually
> > concluded
> > >> >>are
> > >> >> not practical were:
> > >> >> 1. unique token per htt

Re: [iOS 8] WKWebView moving forward

[tommy-carlos williams]

I had much less success… it doesn’t play well with other legacy plugins, does 
it?



-- 
tommy-carlos williams

On 11 November 2014 at 03:00:30, Michal Mocny (mmo...@chromium.org) wrote:

Success! I did indeed have to add the framework manually.  

Thanks for instructions.  

On Thu, Nov 6, 2014 at 7:49 PM, Shazron  wrote:  

> There have been major changes to the `wkwebview` branch of `cordova-ios`.  
> The `WKWebView` functionality has been moved to a plugin in the  
> `cordova-plugins` repo.  
>  
> So, for now you can do:  
>  
> cordova create wkwvtest test.project wkwvtest  
> cd wkwvtest  
> cordova platform add ios@wkwebview --usegit  
> cordova plugin add  
> https://github.com/apache/cordova-plugins.git#master:wkwebview-engine  
>  
> Modify the root `config.xml` and edit this value to:  
>  
> http://localhost:0"; />  
>  
> Then:  
>  
> cordova emulate  
>  
> You might get a build error, this is a `plugman` bug that doesn't install  
> `WebKit.framework` properly even though it is defined in plugin.xml. You  
> might have to do a:  
>  
> open -a Xcode platforms/ios  
>  
> ...and add the framework manually.  
>  
> On Thu, Nov 6, 2014 at 11:15 AM, Shazron  wrote:  
>  
> > Thanks Tony - I'll look at that PR when I have some time.  
> >  
> > Yesterday I did some major work to isolate the webviews into plugins  
> > (CDVWKWebViewEngine, CDVUIWebViewEngine). This way we can reduce the risk  
> > by extracting the WKWebView items into a plugin, and the core has no  
> > dependency on WebKit.framework anymore, plus speedy (well, speedier)  
> > updates if it needs updating. The CDVUIWebViewEngine will remain in the  
> > core as the default engine. I'm still working on this, but it already  
> works  
> > currently. I'm abstracting things out more, and removing code from the  
> > CDVViewController which has become unwieldy.  
> >  
> > Swapping out engines would use the preference:  
> >   
> >  
> > Any new web engine needs to implement the new CDVWebViewEngineProtocol  
> > protocol, and installed as a plugin.  
> >  
> > On Mon, Nov 3, 2014 at 6:55 PM, Homer, Tony   
> wrote:  
> >  
> >> I have already forked it and made the changes in a topic branch.  
> >> I was originally thinking that I would make 2 topic branches: 1 for  
> >> localhost-only and 1 for auth tokens.  
> >> However, after I finished the first set of changes I realized that the  
> >> second set would be dependent on the first.  
> >> I’ll submit a pull request tomorrow for you to look at - I’ll be happy  
> to  
> >> redo it as multiple branches if that makes sense.  
> >>  
> >> I got a little sidetracked with local web server plugin, but I’ve also  
> >> forked cordova-ios and made a topic branch from wkwebview.  
> >> I'll start working on some of the changes I proposed earlier in this  
> >> thread tomorrow (for plugins like camera that return file:// urls,  
> etc.).  
> >>  
> >> Tony  
> >>  
> >> On 11/3/14, 7:23 PM, "Shazron"  wrote:  
> >>  
> >> >Thanks Tony for all the investigation. Please do fork the local web  
> >> server  
> >> >plugin and put all your work in topic branches for eventual pull  
> requests  
> >> >to the main repo.  
> >> >  
> >> >This is precisely why the local web server is a plugin, and not in the  
> >> >core. I don't profess to be a security expert, and we can update this  
> >> >plugin to cover most of the security cases or someone else can provide  
> >> >their better plugin. I don't think this needs to be bulletproof, not  
> that  
> >> >we can entirely be (has there ever been a Security Update by Apple that  
> >> >*didn't* include a WebKit vulnerability?)  
> >> >  
> >> >I'd like to get the cordova-ios/wkwebview branch back into the mainline  
> >> as  
> >> >soon as possible, but under an experimental flag (--experimental ?)  
> for  
> >> >bin/create. This will choose a new template that has WebKit.framework  
> in  
> >> >it, which will also define a macro to conditionally compile the new  
> bits  
> >> >in  
> >> >(I haven't added the macros yet in the topic branch).  
> >> >  
> >> >  
> >> >  
> >> >  
> >> >On Mon, Nov 3, 2014 at 7:27 AM, Homer, Tony   
> >> wrote:  
> >> >  
> >> >> I spent a lot of time thinking about ways to avoid replay attacks for  
> >> >>the  
> >> >> local web server plugin this weekend.  
> >> >>  
> >> >> Specifically, I felt like there should be a way to take advantage of  
> >> the  
> >> >> fact that the client and the server are running in the same process.  
> >> >> I thought this might enable some kind of sideband (non-http)  
> >> >> authentication possibility.  
> >> >> The 2 possibilities I was most interested in, but eventually  
> concluded  
> >> >>are  
> >> >> not practical were:  
> >> >> 1. unique token per http request - not practical because there is no  
> >> per  
> >> >> http request event available  
> >> >> 2. a whitelist of “remote” ports - not practical because there is no  
> >> >> simple way to get a list of ports 

Re: [VOTE] Tools Release

[Steven Gill]

In terms of having to bump the version when you have to retag an rc that
has been published to npm:

The reason why this is necessary is because we want to test exactly what we
vote on. We push the tgz file that we are voting on to npm under the rc
flag. The alternative would be to extract it, change the version in
package.json to include `-rc1` to it and then publish (or do this step
before building the archive). We would then have to make sure the
dependency is correctly set for repos that rely on lib (cli would have to
change cordova-lib dependency to include -rc1 to the version for it).

This opens us up to errors in the release process and is not worth it.
Re-tagging shouldn't happen often. When it does, it should be fairly quick
as long as we are using release branches (which we are doing according to
release doc).

On Mon, Nov 10, 2014 at 2:16 PM, Mark Koudritsky  wrote:

> This vote is cancelled.
>
> Blocking issue https://issues.apache.org/jira/browse/CB-8000
> Will post a new vote with updated packages
>
> On Mon, Nov 10, 2014 at 12:34 PM, Sergey Grebnov (Akvelon) <
> v-seg...@microsoft.com> wrote:
>
> > Thank you Mark; Resending link to the fix here since looks like I
> answered
> > not to the latest email last time.
> > https://github.com/apache/cordova-lib/pull/118/
> >
> > Thx!
> > Sergey
> > -Original Message-
> > From: Mark Koudritsky [mailto:kam...@google.com]
> > Sent: Monday, November 10, 2014 9:14 AM
> > To: dev@cordova.apache.org
> > Subject: Re: [VOTE] Tools Release
> >
> > Yep, the hash as a versions seems like something that should break the
> npm
> > download as well.
> > Sergey, I'll merge your patch and republish rc packages.
> > Maria, thanks for finding this.
> >
> > Note, the lib will have a different version number 4.1.1 because npm
> > forbids uploading anything with the same version string more than once
> [1].
> > We should come up with some procedure of promoting RCs that would not
> > necessitate bumping the version.
> >
> > One option is to download the package with x.y.z-rcN from npm, and have a
> > script that unpacks it, strips the -rcN and repacks the same files back.
> > (not sure how to deal with signing in this case).
> >
> > [1] - https://github.com/npm/npm-registry-couchapp/issues/148
> >
> > On Mon, Nov 10, 2014 at 12:06 PM, Sergey Grebnov (Akvelon) <
> > v-seg...@microsoft.com> wrote:
> >
> > > I've found the case will submit the patch shortly - Jira +PR to master
> > >
> > > Problem cause: we've recently got rid of subdirs for wp8 and windows
> > > but still have them defined in tools.
> > >
> > > https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cord
> > > ova/platformsConfig.json#L53
> > >
> > > Thx!
> > > Sergey
> > > -Original Message-
> > > From: Steven Gill [mailto:stevengil...@gmail.com]
> > > Sent: Monday, November 10, 2014 8:57 AM
> > > To: dev@cordova.apache.org
> > > Subject: RE: [VOTE] Tools Release
> > >
> > > Definitely a problem. Thanks for testing and finding it!
> > >
> > > -1
> > > On Nov 10, 2014 8:51 AM, "Maria Bukharina"
> > > 
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I've tried to create app with this rc and discover that adding wp8
> > > > and windows platforms with --usegit key fails:
> > > >
> > > > cordova platform add wp8 --usegit
> > > > Creating wp8 project...
> > > > Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command
> > > > failed with exit code ENOENT
> > > >  at ChildProcess.whenDone
> > > >
> > > (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\
> > > superspawn.js:135:23)
> > > >  at ChildProcess.EventEmitter.emit (events.js:95:17)
> > > >  at Process.ChildProcess._handle.onexit
> > > > (child_process.js:805:12)
> > > >
> > > >
> > > > Seemed that file platformConfig.json in
> > > > .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and
> > > > windows
> > > > platforms:
> > > > for wp8 there are wrong version and subdirectory properties:
> > > > "wp8": {
> > > > "hostos": ["win32"],
> > > > "parser": "./metadata/wp8_parser",
> > > > "url":
> > > > "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git
> > > > ",
> > > > "version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
> > > > "altplatform": "wp",
> > > > "subdirectory": "3.7.0"
> > > > },
> > > >
> > > > windows for now doesn't contain subfolder "windows":
> > > > "windows": {
> > > > "hostos": ["win32"],
> > > > "parser": "./metadata/windows_parser",
> > > > "url": "
> > > > https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
> > > > "version": "3.7.0",
> > > > "subdirectory": "windows"
> > > > },
> > > >
> > > > What's your opinion, is it critical for release?
> > > >
> > > >
> > > > Thanks,
> > > > Maria
> > > >
> > > > -Original Message-
> > > > From: Mark Koudritsky [mailto:kam...@google.com]
> > > > Sent: Saturda

Re: [VOTE] Tools Release

[Mark Koudritsky]

This vote is cancelled.

Blocking issue https://issues.apache.org/jira/browse/CB-8000
Will post a new vote with updated packages

On Mon, Nov 10, 2014 at 12:34 PM, Sergey Grebnov (Akvelon) <
v-seg...@microsoft.com> wrote:

> Thank you Mark; Resending link to the fix here since looks like I answered
> not to the latest email last time.
> https://github.com/apache/cordova-lib/pull/118/
>
> Thx!
> Sergey
> -Original Message-
> From: Mark Koudritsky [mailto:kam...@google.com]
> Sent: Monday, November 10, 2014 9:14 AM
> To: dev@cordova.apache.org
> Subject: Re: [VOTE] Tools Release
>
> Yep, the hash as a versions seems like something that should break the npm
> download as well.
> Sergey, I'll merge your patch and republish rc packages.
> Maria, thanks for finding this.
>
> Note, the lib will have a different version number 4.1.1 because npm
> forbids uploading anything with the same version string more than once [1].
> We should come up with some procedure of promoting RCs that would not
> necessitate bumping the version.
>
> One option is to download the package with x.y.z-rcN from npm, and have a
> script that unpacks it, strips the -rcN and repacks the same files back.
> (not sure how to deal with signing in this case).
>
> [1] - https://github.com/npm/npm-registry-couchapp/issues/148
>
> On Mon, Nov 10, 2014 at 12:06 PM, Sergey Grebnov (Akvelon) <
> v-seg...@microsoft.com> wrote:
>
> > I've found the case will submit the patch shortly - Jira +PR to master
> >
> > Problem cause: we've recently got rid of subdirs for wp8 and windows
> > but still have them defined in tools.
> >
> > https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cord
> > ova/platformsConfig.json#L53
> >
> > Thx!
> > Sergey
> > -Original Message-
> > From: Steven Gill [mailto:stevengil...@gmail.com]
> > Sent: Monday, November 10, 2014 8:57 AM
> > To: dev@cordova.apache.org
> > Subject: RE: [VOTE] Tools Release
> >
> > Definitely a problem. Thanks for testing and finding it!
> >
> > -1
> > On Nov 10, 2014 8:51 AM, "Maria Bukharina"
> > 
> > wrote:
> >
> > > Hi all,
> > >
> > > I've tried to create app with this rc and discover that adding wp8
> > > and windows platforms with --usegit key fails:
> > >
> > > cordova platform add wp8 --usegit
> > > Creating wp8 project...
> > > Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command
> > > failed with exit code ENOENT
> > >  at ChildProcess.whenDone
> > >
> > (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\
> > superspawn.js:135:23)
> > >  at ChildProcess.EventEmitter.emit (events.js:95:17)
> > >  at Process.ChildProcess._handle.onexit
> > > (child_process.js:805:12)
> > >
> > >
> > > Seemed that file platformConfig.json in
> > > .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and
> > > windows
> > > platforms:
> > > for wp8 there are wrong version and subdirectory properties:
> > > "wp8": {
> > > "hostos": ["win32"],
> > > "parser": "./metadata/wp8_parser",
> > > "url":
> > > "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git
> > > ",
> > > "version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
> > > "altplatform": "wp",
> > > "subdirectory": "3.7.0"
> > > },
> > >
> > > windows for now doesn't contain subfolder "windows":
> > > "windows": {
> > > "hostos": ["win32"],
> > > "parser": "./metadata/windows_parser",
> > > "url": "
> > > https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
> > > "version": "3.7.0",
> > > "subdirectory": "windows"
> > > },
> > >
> > > What's your opinion, is it critical for release?
> > >
> > >
> > > Thanks,
> > > Maria
> > >
> > > -Original Message-
> > > From: Mark Koudritsky [mailto:kam...@google.com]
> > > Sent: Saturday, November 8, 2014 01:17
> > > To: dev@cordova.apache.org
> > > Subject: [VOTE] Tools Release
> > >
> > > Please review and vote on this Tools Release.
> > >
> > > Release issue: https://issues.apache.org/jira/browse/CB-7988
> > >
> > > Packages have been published to dist/dev:
> > > https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
> > > And to npm under @rc tag
> > >
> > > To test them out you can use:
> > > npm -g uninstall cordova
> > > npm -g install cordova@rc
> > >
> > > The packages were published from their corresponding git tags:
> > >
> > > cordova-js: 3.7.2 (7afadfc044)
> > > cordova-lib: 4.1.0 (0141806d73)
> > > cordova-plugman: 0.22.14 (cdb84dda53)
> > > cordova-cli: 4.1.0 (e33cfc90a0)
> > >
> > > Upon a successful vote I will upload the archives to dist/, publish
> > > them to NPM (under @latest tag), and post the corresponding blog post.
> > >
> > > Voting guidelines:
> > > https://github.com/apache/cordova-coho/blob/master/docs/release-voti
> > > ng
> > > .md
> > >
> > > Voting will go on for a minimum of 48 hours.
> > >
> > > I vote +1:
> > > * Ran coho audit-

Re: CB-7927

[Shazron]

Hi Kamil,
Yes a pull request is ideal way. See:
https://github.com/apache/cordova-plugin-file/blob/master/CONTRIBUTING.md



On Sun, Nov 9, 2014 at 11:54 PM, Kamil Durkiewicz 
wrote:

> Hi,
>
> There is a bug in the File plugin that is quite severe from a point of view
> of a project I'm currently in:
>
> https://issues.apache.org/jira/browse/CB-7927
>
> I've attached a patch file to the Jira issue. This fix is also available on
> my fork of the plugin:
>
>
> https://github.com/durkiewicz/cordova-plugin-file/commit/51435803f877c32f810de0ec5d1f89422d1719b2
>
> What can I do to make these changes applied? Can I create a pull request?
> (I have already signed the ICLA).
>
> Thanks,
>
> Kamil Durkiewicz
>

[GitHub] cordova-lib pull request: CB-8000 Fix --usegit option when adding ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-8000 Fix --usegit option when adding ...

[kamrik]

Github user kamrik commented on the pull request:

https://github.com/apache/cordova-lib/pull/118#issuecomment-62464427
  
Looks good. Pushing 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: Review: Tools Release blog post

[Shazron]

Added some lines: https://github.com/cordova/apache-blog-posts/pull/20

On Mon, Nov 10, 2014 at 1:23 PM, Mark Koudritsky  wrote:

> Incorporated pull request from Josh and Marcel, added the CB-7890 to
> notable changes in the lib, bumped micro numbers for versions that will
> have to be changed.
>
> Published it in github/cordova/apache-blog-posts at
>
> https://github.com/cordova/apache-blog-posts/blob/master/2014-11-10-tools-release.md
> Please review.
>
> Steve, thanks for adding me to the org.
>
> Deleted my fork of the blog posts repo at github/kamrik.
>
> On Mon, Nov 10, 2014 at 2:54 PM, Josh Soref  wrote:
>
> > I'm assuming I can't push there either...
> >
> > On 11/10/14, 2:41 PM, "Steven Gill"  wrote:
> >
> > >Mark, I added you as owner to that Org.
> > >
> > >-Steve
> > >
> > >On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky 
> > >wrote:
> > >
> > >> I got a permission denied error when trying to push to origin. Didn't
> > >> invest the time to investigate it. Does this repo live on GitHub or is
> > >>it
> > >> only mirrored there?
> > >> Cloned it using `grunt cloneBlog` according to instructions at
> > >> https://svn.apache.org/repos/asf/cordova/site/README.md
> > >>
> > >> On Mon, Nov 10, 2014 at 1:00 PM, Marcel Kinard 
> > >>wrote:
> > >>
> > >> > https://github.com/kamrik/apache-blog-posts/pull/2
> > >> >
> > >> > BTW, is there a reason to do the work on kamrik/master instead of
> > >> > origin/topicBranch or origin/master? I think I have content from
> > >> Parashuram
> > >> > that you don't.
> > >> >
> > >> > On Nov 10, 2014, at 11:31 AM, Josh Soref 
> > >>wrote:
> > >> >
> > >> > > To be fair, if you missed it, others will too, which argues that
> it
> > >> > should
> > >> > > be reorganized.
> > >> > >
> > >> > > I've done a PR for the other bits, but someone should consider
> this
> > >> > point.
> > >> > >
> > >> > > On 11/10/14, 11:27 AM, "Marcel Kinard" 
> wrote:
> > >> > >
> > >> > >> Ah, missed that.
> > >> > >>
> > >> > >> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky  >
> > >> > wrote:
> > >> > >>
> > >> > >>> The two items under "Platform updates" are already links to
> those
> > >>two
> > >> > >>> posts.
> > >> >
> > >> >
> > >>
> >
> >
>

Re: cordova 64-bit support

[Joe Bowser]

+1

I think we really need more data.  I know that in Marcel's case, there's
the Asia-Pacific customer, but I have no idea how big that customer base
is.  The only numbers I have are the Play Store. and I think the same thing
goes for iOS and the App Store.  In Android's case, there's a lot of
third-party manufacturers who don't pass CTS.  I personally don't want to
support any android device that can't pass CTS (that includes the Android
emulator), since that means that we're supporting a new platform that may
or may not be Android-like.

At least with iOS, we know that iOS has no weird surprises like SDK classes
not existing.

On Mon Nov 10 2014 at 11:17:28 AM Shazron  wrote:

> We'll delay this decision for another time, in a proper thread without
> hijacking this one.
>
> On Mon, Nov 10, 2014 at 8:37 AM, Marcel Kinard  wrote:
>
> > My customers still need iOS 6. Specifically the ones in the Asia-Pacific
> > area. The feedback we are getting from there is that end users hold on
> the
> > devices for longer periods than compared to North America / Europe, and
> > they are also less likely to perform os upgrades even when available.
> >
> > Not all areas of the world behave the same.
> >
> > My team can help with iOS 6 testing, we have devices here. If there is
> not
> > a technical reason to remove iOS 6 support, my preference is to keep it
> in
> > a while longer.
> >
> > On Nov 10, 2014, at 11:10 AM, Ian Clelland 
> wrote:
> >
> > > I know that's been our Android policy; I though that iOS was roughly
> "we
> > > support the current release and the one previous release", which would
> > mean
> > > that we're already good to start just supporting iOS 7 and 8
> exclusively.
> > >
> > > (Not that it's a big difference -- a 1-month delay is about what it
> would
> > > take to get another cordova-ios release out anyway :) )
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

Re: Review: Tools Release blog post

[Mark Koudritsky]

Incorporated pull request from Josh and Marcel, added the CB-7890 to
notable changes in the lib, bumped micro numbers for versions that will
have to be changed.

Published it in github/cordova/apache-blog-posts at
https://github.com/cordova/apache-blog-posts/blob/master/2014-11-10-tools-release.md
Please review.

Steve, thanks for adding me to the org.

Deleted my fork of the blog posts repo at github/kamrik.

On Mon, Nov 10, 2014 at 2:54 PM, Josh Soref  wrote:

> I'm assuming I can't push there either...
>
> On 11/10/14, 2:41 PM, "Steven Gill"  wrote:
>
> >Mark, I added you as owner to that Org.
> >
> >-Steve
> >
> >On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky 
> >wrote:
> >
> >> I got a permission denied error when trying to push to origin. Didn't
> >> invest the time to investigate it. Does this repo live on GitHub or is
> >>it
> >> only mirrored there?
> >> Cloned it using `grunt cloneBlog` according to instructions at
> >> https://svn.apache.org/repos/asf/cordova/site/README.md
> >>
> >> On Mon, Nov 10, 2014 at 1:00 PM, Marcel Kinard 
> >>wrote:
> >>
> >> > https://github.com/kamrik/apache-blog-posts/pull/2
> >> >
> >> > BTW, is there a reason to do the work on kamrik/master instead of
> >> > origin/topicBranch or origin/master? I think I have content from
> >> Parashuram
> >> > that you don't.
> >> >
> >> > On Nov 10, 2014, at 11:31 AM, Josh Soref 
> >>wrote:
> >> >
> >> > > To be fair, if you missed it, others will too, which argues that it
> >> > should
> >> > > be reorganized.
> >> > >
> >> > > I've done a PR for the other bits, but someone should consider this
> >> > point.
> >> > >
> >> > > On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:
> >> > >
> >> > >> Ah, missed that.
> >> > >>
> >> > >> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky 
> >> > wrote:
> >> > >>
> >> > >>> The two items under "Platform updates" are already links to those
> >>two
> >> > >>> posts.
> >> >
> >> >
> >>
>
>

Re: Review: Tools Release blog post

[Josh Soref]

I'm assuming I can't push there either...

On 11/10/14, 2:41 PM, "Steven Gill"  wrote:

>Mark, I added you as owner to that Org.
>
>-Steve
>
>On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky 
>wrote:
>
>> I got a permission denied error when trying to push to origin. Didn't
>> invest the time to investigate it. Does this repo live on GitHub or is
>>it
>> only mirrored there?
>> Cloned it using `grunt cloneBlog` according to instructions at
>> https://svn.apache.org/repos/asf/cordova/site/README.md
>>
>> On Mon, Nov 10, 2014 at 1:00 PM, Marcel Kinard 
>>wrote:
>>
>> > https://github.com/kamrik/apache-blog-posts/pull/2
>> >
>> > BTW, is there a reason to do the work on kamrik/master instead of
>> > origin/topicBranch or origin/master? I think I have content from
>> Parashuram
>> > that you don't.
>> >
>> > On Nov 10, 2014, at 11:31 AM, Josh Soref 
>>wrote:
>> >
>> > > To be fair, if you missed it, others will too, which argues that it
>> > should
>> > > be reorganized.
>> > >
>> > > I've done a PR for the other bits, but someone should consider this
>> > point.
>> > >
>> > > On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:
>> > >
>> > >> Ah, missed that.
>> > >>
>> > >> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky 
>> > wrote:
>> > >>
>> > >>> The two items under "Platform updates" are already links to those
>>two
>> > >>> posts.
>> >
>> >
>>

Re: Review: Tools Release blog post

[Steven Gill]

Mark, I added you as owner to that Org.

-Steve

On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky  wrote:

> I got a permission denied error when trying to push to origin. Didn't
> invest the time to investigate it. Does this repo live on GitHub or is it
> only mirrored there?
> Cloned it using `grunt cloneBlog` according to instructions at
> https://svn.apache.org/repos/asf/cordova/site/README.md
>
> On Mon, Nov 10, 2014 at 1:00 PM, Marcel Kinard  wrote:
>
> > https://github.com/kamrik/apache-blog-posts/pull/2
> >
> > BTW, is there a reason to do the work on kamrik/master instead of
> > origin/topicBranch or origin/master? I think I have content from
> Parashuram
> > that you don't.
> >
> > On Nov 10, 2014, at 11:31 AM, Josh Soref  wrote:
> >
> > > To be fair, if you missed it, others will too, which argues that it
> > should
> > > be reorganized.
> > >
> > > I've done a PR for the other bits, but someone should consider this
> > point.
> > >
> > > On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:
> > >
> > >> Ah, missed that.
> > >>
> > >> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky 
> > wrote:
> > >>
> > >>> The two items under "Platform updates" are already links to those two
> > >>> posts.
> >
> >
>

Re: Review: Tools Release blog post

[Mark Koudritsky]

I got a permission denied error when trying to push to origin. Didn't
invest the time to investigate it. Does this repo live on GitHub or is it
only mirrored there?
Cloned it using `grunt cloneBlog` according to instructions at
https://svn.apache.org/repos/asf/cordova/site/README.md

On Mon, Nov 10, 2014 at 1:00 PM, Marcel Kinard  wrote:

> https://github.com/kamrik/apache-blog-posts/pull/2
>
> BTW, is there a reason to do the work on kamrik/master instead of
> origin/topicBranch or origin/master? I think I have content from Parashuram
> that you don't.
>
> On Nov 10, 2014, at 11:31 AM, Josh Soref  wrote:
>
> > To be fair, if you missed it, others will too, which argues that it
> should
> > be reorganized.
> >
> > I've done a PR for the other bits, but someone should consider this
> point.
> >
> > On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:
> >
> >> Ah, missed that.
> >>
> >> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky 
> wrote:
> >>
> >>> The two items under "Platform updates" are already links to those two
> >>> posts.
>
>

[GitHub] cordova-plugin-statusbar pull request: CB-7986 Add cordova-plugin-...

[daserge]

GitHub user daserge opened a pull request:

https://github.com/apache/cordova-plugin-statusbar/pull/18

CB-7986 Add cordova-plugin-statusbar support for Windows Phone 8.1

Added Windows Phone 8.1 support
Updated the documentation

[JIRA issue](https://issues.apache.org/jira/browse/CB-7986)

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

$ git pull https://github.com/MSOpenTech/cordova-plugin-statusbar CB-7986

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

https://github.com/apache/cordova-plugin-statusbar/pull/18.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 #18


commit a6344f14f99c19d60a783d92a742285fa3c62fca
Author: daserge 
Date:   2014-11-10T19:20:42Z

CB-7986 Add cordova-plugin-statusbar support for Windows Phone 8.1

Added Windows Phone 8.1 support
Updated the documentation




---
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: cordova 64-bit support

[Shazron]

We'll delay this decision for another time, in a proper thread without
hijacking this one.

On Mon, Nov 10, 2014 at 8:37 AM, Marcel Kinard  wrote:

> My customers still need iOS 6. Specifically the ones in the Asia-Pacific
> area. The feedback we are getting from there is that end users hold on the
> devices for longer periods than compared to North America / Europe, and
> they are also less likely to perform os upgrades even when available.
>
> Not all areas of the world behave the same.
>
> My team can help with iOS 6 testing, we have devices here. If there is not
> a technical reason to remove iOS 6 support, my preference is to keep it in
> a while longer.
>
> On Nov 10, 2014, at 11:10 AM, Ian Clelland  wrote:
>
> > I know that's been our Android policy; I though that iOS was roughly "we
> > support the current release and the one previous release", which would
> mean
> > that we're already good to start just supporting iOS 7 and 8 exclusively.
> >
> > (Not that it's a big difference -- a 1-month delay is about what it would
> > take to get another cordova-ios release out anyway :) )
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: cordova 64-bit support

[Josh Soref]

Marcel Kinard wrote:
> I suspect there will be many more questions around iOS 64-bit.
> I think it deserves a blog entry.

Seems reasonable

>I've drafted one here:
>https://github.com/cordova/apache-blog-posts/blob/ios64bit/2014-11-11-ios-
>64bit.md
>
>Feedback desired. I'd like to see this published in the next few days.
>Thanks!

PR sent.


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

CB-7927

[Kamil Durkiewicz]

Hi,

There is a bug in the File plugin that is quite severe from a point of view
of a project I'm currently in:

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

I've attached a patch file to the Jira issue. This fix is also available on
my fork of the plugin:

https://github.com/durkiewicz/cordova-plugin-file/commit/51435803f877c32f810de0ec5d1f89422d1719b2

What can I do to make these changes applied? Can I create a pull request?
(I have already signed the ICLA).

Thanks,

Kamil Durkiewicz

Re: Review: Tools Release blog post

[Jesse]

This was a huge security hole fix that should be mentioned most likely. 

https://github.com/apache/cordova-lib/commit/281aee737dbe5143c9cb5957359ed5df6298a154

This landed quietly, but ultimately tooling released before this commit could 
read private user data, copy it to the project folder and upload it with hooks, 
or install anything anywhere ... probably worth a mention. 

> On Nov 10, 2014, at 10:17 AM, Josh Soref  wrote:
> 
> I only did the PR there because that's what I saw advertised.
> 
> I don't really care where it is done :)
> 
>> On 11/10/14, 1:00 PM, "Marcel Kinard"  wrote:
>> 
>> https://github.com/kamrik/apache-blog-posts/pull/2
>> 
>> BTW, is there a reason to do the work on kamrik/master instead of
>> origin/topicBranch or origin/master? I think I have content from
>> Parashuram that you don't.
>> 
>>> On Nov 10, 2014, at 11:31 AM, Josh Soref  wrote:
>>> 
>>> To be fair, if you missed it, others will too, which argues that it
>>> should
>>> be reorganized.
>>> 
>>> I've done a PR for the other bits, but someone should consider this
>>> point.
>>> 
 On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:
 
 Ah, missed that.
 
 On Nov 10, 2014, at 11:20 AM, Mark Koudritsky 
 wrote:
 
> The two items under "Platform updates" are already links to those two
> posts.
> 
> 
> -
> 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

Re: cordova 64-bit support

[Marcel Kinard]

I suspect there will be many more questions around iOS 64-bit. I think it 
deserves a blog entry.

I've drafted one here: 
https://github.com/cordova/apache-blog-posts/blob/ios64bit/2014-11-11-ios-64bit.md

Feedback desired. I'd like to see this published in the next few days. Thanks!

On Nov 7, 2014, at 2:04 PM, Marcel Kinard  wrote:

> I suspect Vidiraj's question was driven by this: 
> https://developer.apple.com/news/?id=10202014a

Re: Review: Tools Release blog post

[Josh Soref]

I only did the PR there because that's what I saw advertised.

I don't really care where it is done :)

On 11/10/14, 1:00 PM, "Marcel Kinard"  wrote:

>https://github.com/kamrik/apache-blog-posts/pull/2
>
>BTW, is there a reason to do the work on kamrik/master instead of
>origin/topicBranch or origin/master? I think I have content from
>Parashuram that you don't.
>
>On Nov 10, 2014, at 11:31 AM, Josh Soref  wrote:
>
>> To be fair, if you missed it, others will too, which argues that it
>>should
>> be reorganized.
>> 
>> I've done a PR for the other bits, but someone should consider this
>>point.
>> 
>> On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:
>> 
>>> Ah, missed that.
>>> 
>>> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky 
>>>wrote:
>>> 
 The two items under "Platform updates" are already links to those two
 posts.
>


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

Re: Review: Tools Release blog post

[Marcel Kinard]

https://github.com/kamrik/apache-blog-posts/pull/2

BTW, is there a reason to do the work on kamrik/master instead of 
origin/topicBranch or origin/master? I think I have content from Parashuram 
that you don't.

On Nov 10, 2014, at 11:31 AM, Josh Soref  wrote:

> To be fair, if you missed it, others will too, which argues that it should
> be reorganized.
> 
> I've done a PR for the other bits, but someone should consider this point.
> 
> On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:
> 
>> Ah, missed that.
>> 
>> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky  wrote:
>> 
>>> The two items under "Platform updates" are already links to those two
>>> posts.

RE: [VOTE] Tools Release

[Sergey Grebnov (Akvelon)]

Thank you Mark; Resending link to the fix here since looks like I answered not 
to the latest email last time.
https://github.com/apache/cordova-lib/pull/118/

Thx!
Sergey
-Original Message-
From: Mark Koudritsky [mailto:kam...@google.com] 
Sent: Monday, November 10, 2014 9:14 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] Tools Release

Yep, the hash as a versions seems like something that should break the npm 
download as well.
Sergey, I'll merge your patch and republish rc packages.
Maria, thanks for finding this.

Note, the lib will have a different version number 4.1.1 because npm forbids 
uploading anything with the same version string more than once [1].
We should come up with some procedure of promoting RCs that would not 
necessitate bumping the version.

One option is to download the package with x.y.z-rcN from npm, and have a 
script that unpacks it, strips the -rcN and repacks the same files back.
(not sure how to deal with signing in this case).

[1] - https://github.com/npm/npm-registry-couchapp/issues/148

On Mon, Nov 10, 2014 at 12:06 PM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> I've found the case will submit the patch shortly - Jira +PR to master
>
> Problem cause: we've recently got rid of subdirs for wp8 and windows 
> but still have them defined in tools.
>
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cord
> ova/platformsConfig.json#L53
>
> Thx!
> Sergey
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Monday, November 10, 2014 8:57 AM
> To: dev@cordova.apache.org
> Subject: RE: [VOTE] Tools Release
>
> Definitely a problem. Thanks for testing and finding it!
>
> -1
> On Nov 10, 2014 8:51 AM, "Maria Bukharina" 
> 
> wrote:
>
> > Hi all,
> >
> > I've tried to create app with this rc and discover that adding wp8 
> > and windows platforms with --usegit key fails:
> >
> > cordova platform add wp8 --usegit
> > Creating wp8 project...
> > Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command 
> > failed with exit code ENOENT
> >  at ChildProcess.whenDone
> >
> (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\
> superspawn.js:135:23)
> >  at ChildProcess.EventEmitter.emit (events.js:95:17)
> >  at Process.ChildProcess._handle.onexit
> > (child_process.js:805:12)
> >
> >
> > Seemed that file platformConfig.json in 
> > .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and 
> > windows
> > platforms:
> > for wp8 there are wrong version and subdirectory properties:
> > "wp8": {
> > "hostos": ["win32"],
> > "parser": "./metadata/wp8_parser",
> > "url":
> > "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git
> > ",
> > "version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
> > "altplatform": "wp",
> > "subdirectory": "3.7.0"
> > },
> >
> > windows for now doesn't contain subfolder "windows":
> > "windows": {
> > "hostos": ["win32"],
> > "parser": "./metadata/windows_parser",
> > "url": "
> > https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
> > "version": "3.7.0",
> > "subdirectory": "windows"
> > },
> >
> > What's your opinion, is it critical for release?
> >
> >
> > Thanks,
> > Maria
> >
> > -Original Message-
> > From: Mark Koudritsky [mailto:kam...@google.com]
> > Sent: Saturday, November 8, 2014 01:17
> > To: dev@cordova.apache.org
> > Subject: [VOTE] Tools Release
> >
> > Please review and vote on this Tools Release.
> >
> > Release issue: https://issues.apache.org/jira/browse/CB-7988
> >
> > Packages have been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
> > And to npm under @rc tag
> >
> > To test them out you can use:
> > npm -g uninstall cordova
> > npm -g install cordova@rc
> >
> > The packages were published from their corresponding git tags:
> >
> > cordova-js: 3.7.2 (7afadfc044)
> > cordova-lib: 4.1.0 (0141806d73)
> > cordova-plugman: 0.22.14 (cdb84dda53)
> > cordova-cli: 4.1.0 (e33cfc90a0)
> >
> > Upon a successful vote I will upload the archives to dist/, publish 
> > them to NPM (under @latest tag), and post the corresponding blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voti
> > ng
> > .md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * tested with npm test and mobilespec on Android
> >
>
> -
> 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-8000 Fix --usegit option when adding ...

[sgrebnov]

GitHub user sgrebnov opened a pull request:

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

CB-8000 Fix --usegit option when adding windows and wp8

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

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

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

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

https://github.com/apache/cordova-lib/pull/118.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 #118


commit b3a94e79aa1bd24bfa9699c73e3cf2f866291a79
Author: sgrebnov 
Date:   2014-11-10T17:23:57Z

CB-8000 Fix --usegit option when adding windows and wp8




---
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: [VOTE] Tools Release

[Sergey Grebnov (Akvelon)]

Here is a proposed fix
https://github.com/apache/cordova-lib/pull/118

Fix --usegit option when adding windows and wp8
https://issues.apache.org/jira/browse/CB-8000

Thx!
-Sergey
-Original Message-
From: Sergey Grebnov (Akvelon) 
Sent: Monday, November 10, 2014 9:06 AM
To: dev@cordova.apache.org
Subject: RE: [VOTE] Tools Release

I've found the case will submit the patch shortly - Jira +PR to master

Problem cause: we've recently got rid of subdirs for wp8 and windows but still 
have them defined in tools.
https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platformsConfig.json#L53

Thx!
Sergey
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Monday, November 10, 2014 8:57 AM
To: dev@cordova.apache.org
Subject: RE: [VOTE] Tools Release

Definitely a problem. Thanks for testing and finding it!

-1
On Nov 10, 2014 8:51 AM, "Maria Bukharina" 
wrote:

> Hi all,
>
> I've tried to create app with this rc and discover that adding wp8 and 
> windows platforms with --usegit key fails:
>
> cordova platform add wp8 --usegit
> Creating wp8 project...
> Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command failed 
> with exit code ENOENT
>  at ChildProcess.whenDone
> (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\superspawn.js:135:23)
>  at ChildProcess.EventEmitter.emit (events.js:95:17)
>  at Process.ChildProcess._handle.onexit
> (child_process.js:805:12)
>
>
> Seemed that file platformConfig.json in 
> .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and 
> windows
> platforms:
> for wp8 there are wrong version and subdirectory properties:
> "wp8": {
> "hostos": ["win32"],
> "parser": "./metadata/wp8_parser",
> "url": 
> "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git
> ",
> "version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
> "altplatform": "wp",
> "subdirectory": "3.7.0"
> },
>
> windows for now doesn't contain subfolder "windows":
> "windows": {
> "hostos": ["win32"],
> "parser": "./metadata/windows_parser",
> "url": "
> https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
> "version": "3.7.0",
> "subdirectory": "windows"
> },
>
> What's your opinion, is it critical for release?
>
>
> Thanks,
> Maria
>
> -Original Message-
> From: Mark Koudritsky [mailto:kam...@google.com]
> Sent: Saturday, November 8, 2014 01:17
> To: dev@cordova.apache.org
> Subject: [VOTE] Tools Release
>
> Please review and vote on this Tools Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7988
>
> Packages have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
> And to npm under @rc tag
>
> To test them out you can use:
> npm -g uninstall cordova
> npm -g install cordova@rc
>
> The packages were published from their corresponding git tags:
>
> cordova-js: 3.7.2 (7afadfc044)
> cordova-lib: 4.1.0 (0141806d73)
> cordova-plugman: 0.22.14 (cdb84dda53)
> cordova-cli: 4.1.0 (e33cfc90a0)
>
> Upon a successful vote I will upload the archives to dist/, publish 
> them to NPM (under @latest tag), 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
> * tested with npm test and mobilespec on Android
>

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

Re: [VOTE] Tools Release

[Mark Koudritsky]

Yep, the hash as a versions seems like something that should break the npm
download as well.
Sergey, I'll merge your patch and republish rc packages.
Maria, thanks for finding this.

Note, the lib will have a different version number 4.1.1 because npm
forbids uploading anything with the same version string more than once [1].
We should come up with some procedure of promoting RCs that would not
necessitate bumping the version.

One option is to download the package with x.y.z-rcN from npm, and have a
script that unpacks it, strips the -rcN and repacks the same files back.
(not sure how to deal with signing in this case).

[1] - https://github.com/npm/npm-registry-couchapp/issues/148

On Mon, Nov 10, 2014 at 12:06 PM, Sergey Grebnov (Akvelon) <
v-seg...@microsoft.com> wrote:

> I've found the case will submit the patch shortly - Jira +PR to master
>
> Problem cause: we've recently got rid of subdirs for wp8 and windows but
> still have them defined in tools.
>
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platformsConfig.json#L53
>
> Thx!
> Sergey
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Monday, November 10, 2014 8:57 AM
> To: dev@cordova.apache.org
> Subject: RE: [VOTE] Tools Release
>
> Definitely a problem. Thanks for testing and finding it!
>
> -1
> On Nov 10, 2014 8:51 AM, "Maria Bukharina" 
> wrote:
>
> > Hi all,
> >
> > I've tried to create app with this rc and discover that adding wp8 and
> > windows platforms with --usegit key fails:
> >
> > cordova platform add wp8 --usegit
> > Creating wp8 project...
> > Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command failed
> > with exit code ENOENT
> >  at ChildProcess.whenDone
> >
> (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\superspawn.js:135:23)
> >  at ChildProcess.EventEmitter.emit (events.js:95:17)
> >  at Process.ChildProcess._handle.onexit
> > (child_process.js:805:12)
> >
> >
> > Seemed that file platformConfig.json in
> > .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and
> > windows
> > platforms:
> > for wp8 there are wrong version and subdirectory properties:
> > "wp8": {
> > "hostos": ["win32"],
> > "parser": "./metadata/wp8_parser",
> > "url":
> > "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git
> > ",
> > "version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
> > "altplatform": "wp",
> > "subdirectory": "3.7.0"
> > },
> >
> > windows for now doesn't contain subfolder "windows":
> > "windows": {
> > "hostos": ["win32"],
> > "parser": "./metadata/windows_parser",
> > "url": "
> > https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
> > "version": "3.7.0",
> > "subdirectory": "windows"
> > },
> >
> > What's your opinion, is it critical for release?
> >
> >
> > Thanks,
> > Maria
> >
> > -Original Message-
> > From: Mark Koudritsky [mailto:kam...@google.com]
> > Sent: Saturday, November 8, 2014 01:17
> > To: dev@cordova.apache.org
> > Subject: [VOTE] Tools Release
> >
> > Please review and vote on this Tools Release.
> >
> > Release issue: https://issues.apache.org/jira/browse/CB-7988
> >
> > Packages have been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
> > And to npm under @rc tag
> >
> > To test them out you can use:
> > npm -g uninstall cordova
> > npm -g install cordova@rc
> >
> > The packages were published from their corresponding git tags:
> >
> > cordova-js: 3.7.2 (7afadfc044)
> > cordova-lib: 4.1.0 (0141806d73)
> > cordova-plugman: 0.22.14 (cdb84dda53)
> > cordova-cli: 4.1.0 (e33cfc90a0)
> >
> > Upon a successful vote I will upload the archives to dist/, publish
> > them to NPM (under @latest tag), 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
> > * tested with npm test and mobilespec on Android
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

RE: [VOTE] Tools Release

[Sergey Grebnov (Akvelon)]

I've found the case will submit the patch shortly - Jira +PR to master

Problem cause: we've recently got rid of subdirs for wp8 and windows but still 
have them defined in tools.
https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platformsConfig.json#L53

Thx!
Sergey
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Monday, November 10, 2014 8:57 AM
To: dev@cordova.apache.org
Subject: RE: [VOTE] Tools Release

Definitely a problem. Thanks for testing and finding it!

-1
On Nov 10, 2014 8:51 AM, "Maria Bukharina" 
wrote:

> Hi all,
>
> I've tried to create app with this rc and discover that adding wp8 and 
> windows platforms with --usegit key fails:
>
> cordova platform add wp8 --usegit
> Creating wp8 project...
> Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command failed 
> with exit code ENOENT
>  at ChildProcess.whenDone
> (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\superspawn.js:135:23)
>  at ChildProcess.EventEmitter.emit (events.js:95:17)
>  at Process.ChildProcess._handle.onexit 
> (child_process.js:805:12)
>
>
> Seemed that file platformConfig.json in 
> .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and 
> windows
> platforms:
> for wp8 there are wrong version and subdirectory properties:
> "wp8": {
> "hostos": ["win32"],
> "parser": "./metadata/wp8_parser",
> "url": 
> "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git
> ",
> "version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
> "altplatform": "wp",
> "subdirectory": "3.7.0"
> },
>
> windows for now doesn't contain subfolder "windows":
> "windows": {
> "hostos": ["win32"],
> "parser": "./metadata/windows_parser",
> "url": "
> https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
> "version": "3.7.0",
> "subdirectory": "windows"
> },
>
> What's your opinion, is it critical for release?
>
>
> Thanks,
> Maria
>
> -Original Message-
> From: Mark Koudritsky [mailto:kam...@google.com]
> Sent: Saturday, November 8, 2014 01:17
> To: dev@cordova.apache.org
> Subject: [VOTE] Tools Release
>
> Please review and vote on this Tools Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7988
>
> Packages have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
> And to npm under @rc tag
>
> To test them out you can use:
> npm -g uninstall cordova
> npm -g install cordova@rc
>
> The packages were published from their corresponding git tags:
>
> cordova-js: 3.7.2 (7afadfc044)
> cordova-lib: 4.1.0 (0141806d73)
> cordova-plugman: 0.22.14 (cdb84dda53)
> cordova-cli: 4.1.0 (e33cfc90a0)
>
> Upon a successful vote I will upload the archives to dist/, publish 
> them to NPM (under @latest tag), 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
> * tested with npm test and mobilespec on Android
>

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

RE: [VOTE] Tools Release

[Steven Gill]

Definitely a problem. Thanks for testing and finding it!

-1
On Nov 10, 2014 8:51 AM, "Maria Bukharina" 
wrote:

> Hi all,
>
> I've tried to create app with this rc and discover that adding wp8 and
> windows platforms with --usegit key fails:
>
> cordova platform add wp8 --usegit
> Creating wp8 project...
> Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command failed
> with exit code ENOENT
>  at ChildProcess.whenDone
> (d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\superspawn.js:135:23)
>  at ChildProcess.EventEmitter.emit (events.js:95:17)
>  at Process.ChildProcess._handle.onexit (child_process.js:805:12)
>
>
> Seemed that file platformConfig.json in
> .\cordova-lib\cordova-lib\src\cordova has invalid data for wp8 and windows
> platforms:
> for wp8 there are wrong version and subdirectory properties:
> "wp8": {
> "hostos": ["win32"],
> "parser": "./metadata/wp8_parser",
> "url": "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git
> ",
> "version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
> "altplatform": "wp",
> "subdirectory": "3.7.0"
> },
>
> windows for now doesn't contain subfolder "windows":
> "windows": {
> "hostos": ["win32"],
> "parser": "./metadata/windows_parser",
> "url": "
> https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
> "version": "3.7.0",
> "subdirectory": "windows"
> },
>
> What's your opinion, is it critical for release?
>
>
> Thanks,
> Maria
>
> -Original Message-
> From: Mark Koudritsky [mailto:kam...@google.com]
> Sent: Saturday, November 8, 2014 01:17
> To: dev@cordova.apache.org
> Subject: [VOTE] Tools Release
>
> Please review and vote on this Tools Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7988
>
> Packages have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
> And to npm under @rc tag
>
> To test them out you can use:
> npm -g uninstall cordova
> npm -g install cordova@rc
>
> The packages were published from their corresponding git tags:
>
> cordova-js: 3.7.2 (7afadfc044)
> cordova-lib: 4.1.0 (0141806d73)
> cordova-plugman: 0.22.14 (cdb84dda53)
> cordova-cli: 4.1.0 (e33cfc90a0)
>
> Upon a successful vote I will upload the archives to dist/, publish them
> to NPM (under @latest tag), 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
> * tested with npm test and mobilespec on Android
>

RE: [VOTE] Tools Release

[Maria Bukharina]

Hi all,

I've tried to create app with this rc and discover that adding wp8 and windows 
platforms with --usegit key fails:

cordova platform add wp8 --usegit
Creating wp8 project...
Error:.cordova\lib\wp\cordova\4.1.0\bin\create: Command failed with 
exit code ENOENT
 at ChildProcess.whenDone 
(d:\Projects\cordova\cordova4.1\cordova-lib-4.1.0\package\src\cordova\superspawn.js:135:23)
 at ChildProcess.EventEmitter.emit (events.js:95:17)
 at Process.ChildProcess._handle.onexit (child_process.js:805:12)


Seemed that file platformConfig.json in .\cordova-lib\cordova-lib\src\cordova 
has invalid data for wp8 and windows platforms:
for wp8 there are wrong version and subdirectory properties:
"wp8": {
"hostos": ["win32"],
"parser": "./metadata/wp8_parser",
"url": "https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git";,
"version": "b2b1e6185444e0dd6a6b9b19df9005cfc5bc5d80",
"altplatform": "wp",
"subdirectory": "3.7.0"
},

windows for now doesn't contain subfolder "windows":
"windows": {
"hostos": ["win32"],
"parser": "./metadata/windows_parser",
"url": "https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git";,
"version": "3.7.0",
"subdirectory": "windows"
},

What's your opinion, is it critical for release?


Thanks,
Maria

-Original Message-
From: Mark Koudritsky [mailto:kam...@google.com] 
Sent: Saturday, November 8, 2014 01:17
To: dev@cordova.apache.org
Subject: [VOTE] Tools Release

Please review and vote on this Tools Release.

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

Packages have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-7988/
And to npm under @rc tag

To test them out you can use:
npm -g uninstall cordova
npm -g install cordova@rc

The packages were published from their corresponding git tags:

cordova-js: 3.7.2 (7afadfc044)
cordova-lib: 4.1.0 (0141806d73)
cordova-plugman: 0.22.14 (cdb84dda53)
cordova-cli: 4.1.0 (e33cfc90a0)

Upon a successful vote I will upload the archives to dist/, publish them to NPM 
(under @latest tag), 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
* tested with npm test and mobilespec on Android

Re: cordova 64-bit support

[Marcel Kinard]

My customers still need iOS 6. Specifically the ones in the Asia-Pacific area. 
The feedback we are getting from there is that end users hold on the devices 
for longer periods than compared to North America / Europe, and they are also 
less likely to perform os upgrades even when available.

Not all areas of the world behave the same.

My team can help with iOS 6 testing, we have devices here. If there is not a 
technical reason to remove iOS 6 support, my preference is to keep it in a 
while longer.

On Nov 10, 2014, at 11:10 AM, Ian Clelland  wrote:

> I know that's been our Android policy; I though that iOS was roughly "we
> support the current release and the one previous release", which would mean
> that we're already good to start just supporting iOS 7 and 8 exclusively.
> 
> (Not that it's a big difference -- a 1-month delay is about what it would
> take to get another cordova-ios release out anyway :) )


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

Re: Review: Tools Release blog post

[Josh Soref]

To be fair, if you missed it, others will too, which argues that it should
be reorganized.

I've done a PR for the other bits, but someone should consider this point.

On 11/10/14, 11:27 AM, "Marcel Kinard"  wrote:

>Ah, missed that.
>
>On Nov 10, 2014, at 11:20 AM, Mark Koudritsky  wrote:
>
>> The two items under "Platform updates" are already links to those two
>>posts.
>> 
>> On Mon, Nov 10, 2014 at 10:56 AM, Marcel Kinard 
>>wrote:
>> 
>>> You mention near the top that the iOS, Windows, and WP8 platforms are
>>> updated, but there isn't mention of what that is. One could infer that
>>>this
>>> release has those updates, but I realize it's just changing the default
>>> versions of those platforms on an "add". How about linking to those
>>>posts:
>>> 
>>> 
>>>http://cordova.apache.org/announcements/2014/11/06/cordova-ios-3.7.0.htm
>>>l
>>> 
>>> 
>>>http://cordova.apache.org/announcements/2014/11/06/cordova-wp-windows-3.
>>>7.0.html
>>> 
>>> On Nov 7, 2014, at 5:22 PM, Mark Koudritsky  wrote:
>>> 
 Please review and send PRs!
 
>>> 
>>>https://github.com/kamrik/apache-blog-posts/blob/master/2014-11-10-tools
>>>-release.md
>>> 
>>> 
>
>
>-
>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

Re: Review: Tools Release blog post

[Marcel Kinard]

Ah, missed that.

On Nov 10, 2014, at 11:20 AM, Mark Koudritsky  wrote:

> The two items under "Platform updates" are already links to those two posts.
> 
> On Mon, Nov 10, 2014 at 10:56 AM, Marcel Kinard  wrote:
> 
>> You mention near the top that the iOS, Windows, and WP8 platforms are
>> updated, but there isn't mention of what that is. One could infer that this
>> release has those updates, but I realize it's just changing the default
>> versions of those platforms on an "add". How about linking to those posts:
>> 
>> http://cordova.apache.org/announcements/2014/11/06/cordova-ios-3.7.0.html
>> 
>> http://cordova.apache.org/announcements/2014/11/06/cordova-wp-windows-3.7.0.html
>> 
>> On Nov 7, 2014, at 5:22 PM, Mark Koudritsky  wrote:
>> 
>>> Please review and send PRs!
>>> 
>> https://github.com/kamrik/apache-blog-posts/blob/master/2014-11-10-tools-release.md
>> 
>> 


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

Re: Review: Tools Release blog post

[Mark Koudritsky]

The two items under "Platform updates" are already links to those two posts.

On Mon, Nov 10, 2014 at 10:56 AM, Marcel Kinard  wrote:

> You mention near the top that the iOS, Windows, and WP8 platforms are
> updated, but there isn't mention of what that is. One could infer that this
> release has those updates, but I realize it's just changing the default
> versions of those platforms on an "add". How about linking to those posts:
>
> http://cordova.apache.org/announcements/2014/11/06/cordova-ios-3.7.0.html
>
> http://cordova.apache.org/announcements/2014/11/06/cordova-wp-windows-3.7.0.html
>
> On Nov 7, 2014, at 5:22 PM, Mark Koudritsky  wrote:
>
> > Please review and send PRs!
> >
> https://github.com/kamrik/apache-blog-posts/blob/master/2014-11-10-tools-release.md
>
>

Re: cordova 64-bit support

[Ian Clelland]

I know that's been our Android policy; I though that iOS was roughly "we
support the current release and the one previous release", which would mean
that we're already good to start just supporting iOS 7 and 8 exclusively.

(Not that it's a big difference -- a 1-month delay is about what it would
take to get another cordova-ios release out anyway :) )

On Mon Nov 10 2014 at 10:30:35 AM Michal Mocny  wrote:

> Our policy has historically been to drop support if usage is under 5%.
> There some amount of leeway in judgement here as well: is it trivial to
> continue support or causing us pain?
>
> For iOS, 5% of usage comes from iOS6 or below as reported by
> https://developer.apple.com/support/appstore/.  I'd venture and say thats
> almost all iOS 6, which puts us right on the border.
>
> That said, the support story for cordova is: all existing apps continue to
> work, if you want to target the older platform you can continue to use an
> older cordova-ios, so I think we can be bold here.  1 more month of iphone
> sales and itll be <5% usage for iOS6 ;)
>
> -Michal
>
> On Sun, Nov 9, 2014 at 6:20 PM, julio cesar sanchez <
> jcesarmob...@gmail.com>
> wrote:
>
> > Apple just says "earlier" 5%. That should be iOS 5 and iOS 6
> >
> > El domingo, 9 de noviembre de 2014, Terence M. Bandoian <
> tere...@tmbsw.com
> > >
> > escribió:
> >
> > > It might make sense to consider dropping support for an iOS version
> when
> > > usage, as reported by Apple, drops below a certain level.
> > >
> > > -Terence Bandoian
> > >
> > >
> > > On 11/8/2014 5:13 PM, julio cesar sanchez wrote:
> > >
> > >> iOS 5 support was removed on cordova 3.5, released on may 2014, I
> think
> > >> it's too soon to remove iOS 6 support with all the devices left behind
> > >> (iphone 3gs and ipod touch 4gen), just to add swift plugins.
> > >>
> > >> I'm ok with dropping support to old versions when there are real
> > >> advantages
> > >> or security reasons.
> > >>
> > >> I'm limited on resources too, but I volunteer to test on my ipod touch
> > >>
> > >>
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
> >
>

Re: [iOS 8] WKWebView moving forward

[Michal Mocny]

Success!  I did indeed have to add the framework manually.

Thanks for instructions.

On Thu, Nov 6, 2014 at 7:49 PM, Shazron  wrote:

> There have been major changes to the `wkwebview` branch of `cordova-ios`.
> The `WKWebView` functionality has been moved to a plugin in the
> `cordova-plugins` repo.
>
> So, for now you can do:
>
> cordova create wkwvtest test.project wkwvtest
> cd wkwvtest
> cordova platform add ios@wkwebview --usegit
> cordova plugin add
> https://github.com/apache/cordova-plugins.git#master:wkwebview-engine
>
> Modify the root `config.xml` and edit this value to:
>
> http://localhost:0"; />
>
> Then:
>
> cordova emulate
>
> You might get a build error, this is a `plugman` bug that doesn't install
> `WebKit.framework` properly even though it is defined in plugin.xml. You
> might have to do a:
>
> open -a Xcode platforms/ios
>
> ...and add the framework manually.
>
> On Thu, Nov 6, 2014 at 11:15 AM, Shazron  wrote:
>
> > Thanks Tony - I'll look at that PR when I have some time.
> >
> > Yesterday I did some major work to isolate the webviews into plugins
> > (CDVWKWebViewEngine, CDVUIWebViewEngine). This way we can reduce the risk
> > by extracting the WKWebView items into a plugin, and the core has no
> > dependency on WebKit.framework anymore, plus speedy (well, speedier)
> > updates if it needs updating. The CDVUIWebViewEngine will remain in the
> > core as the default engine. I'm still working on this, but it already
> works
> > currently. I'm abstracting things out more, and removing code from the
> > CDVViewController which has become unwieldy.
> >
> > Swapping out engines would use the preference:
> > 
> >
> > Any new web engine needs to implement the new CDVWebViewEngineProtocol
> > protocol, and installed as a plugin.
> >
> > On Mon, Nov 3, 2014 at 6:55 PM, Homer, Tony 
> wrote:
> >
> >> I have already forked it and made the changes in a topic branch.
> >> I was originally thinking that I would make 2 topic branches: 1 for
> >> localhost-only and 1 for auth tokens.
> >> However, after I finished the first set of changes I realized that the
> >> second set would be dependent on the first.
> >> I’ll submit a pull request tomorrow for you to look at - I’ll be happy
> to
> >> redo it as multiple branches if that makes sense.
> >>
> >> I got a little sidetracked with local web server plugin, but I’ve also
> >> forked cordova-ios and made a topic branch from wkwebview.
> >> I'll start working on some of the changes I proposed earlier in this
> >> thread tomorrow (for plugins like camera that return file:// urls,
> etc.).
> >>
> >> Tony
> >>
> >> On 11/3/14, 7:23 PM, "Shazron"  wrote:
> >>
> >> >Thanks Tony for all the investigation. Please do fork the local web
> >> server
> >> >plugin and put all your work in topic branches for eventual pull
> requests
> >> >to the main repo.
> >> >
> >> >This is precisely why the local web server is a plugin, and not in the
> >> >core. I don't profess to be a security expert, and we can update this
> >> >plugin to cover most of the security cases or someone else can provide
> >> >their better plugin. I don't think this needs to be bulletproof, not
> that
> >> >we can entirely be (has there ever been a Security Update by Apple that
> >> >*didn't* include a WebKit vulnerability?)
> >> >
> >> >I'd like to get the cordova-ios/wkwebview branch back into the mainline
> >> as
> >> >soon as possible, but under an experimental flag (--experimental ?)
> for
> >> >bin/create. This will choose a new template that has WebKit.framework
> in
> >> >it, which will also define a macro to conditionally compile the new
> bits
> >> >in
> >> >(I haven't added the macros yet in the topic branch).
> >> >
> >> >
> >> >
> >> >
> >> >On Mon, Nov 3, 2014 at 7:27 AM, Homer, Tony 
> >> wrote:
> >> >
> >> >> I spent a lot of time thinking about ways to avoid replay attacks for
> >> >>the
> >> >> local web server plugin this weekend.
> >> >>
> >> >> Specifically, I felt like there should be a way to take advantage of
> >> the
> >> >> fact that the client and the server are running in the same process.
> >> >> I thought this might enable some kind of sideband (non-http)
> >> >> authentication possibility.
> >> >> The 2 possibilities I was most interested in, but eventually
> concluded
> >> >>are
> >> >> not practical were:
> >> >> 1. unique token per http request - not practical because there is no
> >> per
> >> >> http request event available
> >> >> 2. a whitelist of “remote” ports - not practical because there is no
> >> >> simple way to get a list of ports in use by WKWebView
> >> >>
> >> >> After going down this rathole and coming up empty, I reconsidered the
> >> >> original problem and came to the following conclusions.
> >> >> 1. restricting requests to localhost-only limits “attacks” to
> >> >>backgrounded
> >> >> apps
> >> >> 2. including a token in the requests will prevent backgrounded apps
> >> from
> >> >> being able to successfully make

Re: Review: Tools Release blog post

[Marcel Kinard]

You mention near the top that the iOS, Windows, and WP8 platforms are updated, 
but there isn't mention of what that is. One could infer that this release has 
those updates, but I realize it's just changing the default versions of those 
platforms on an "add". How about linking to those posts:

http://cordova.apache.org/announcements/2014/11/06/cordova-ios-3.7.0.html
http://cordova.apache.org/announcements/2014/11/06/cordova-wp-windows-3.7.0.html

On Nov 7, 2014, at 5:22 PM, Mark Koudritsky  wrote:

> Please review and send PRs!
> https://github.com/kamrik/apache-blog-posts/blob/master/2014-11-10-tools-release.md

Re: Review: Tools Release blog post

[Mark Koudritsky]

It's for the lib, other changes are mostly fixes in help text.
Should I add some trivial line about plugman to release notes?

On Mon, Nov 10, 2014 at 9:17 AM, Ian Clelland 
wrote:

> Are there any changes at all to plugman that necessitate its release, or is
> it just being released so that there's a version that uses the new
> cordova-lib? It seems odd that it's in the announcement, but missing from
> the releasenotes.
>
> On Fri Nov 07 2014 at 5:22:51 PM Mark Koudritsky 
> wrote:
>
> > Please review and send PRs!
> > https://github.com/kamrik/apache-blog-posts/blob/master/
> > 2014-11-10-tools-release.md
> >
>

Re: cordova 64-bit support

[Michal Mocny]

Our policy has historically been to drop support if usage is under 5%.
There some amount of leeway in judgement here as well: is it trivial to
continue support or causing us pain?

For iOS, 5% of usage comes from iOS6 or below as reported by
https://developer.apple.com/support/appstore/.  I'd venture and say thats
almost all iOS 6, which puts us right on the border.

That said, the support story for cordova is: all existing apps continue to
work, if you want to target the older platform you can continue to use an
older cordova-ios, so I think we can be bold here.  1 more month of iphone
sales and itll be <5% usage for iOS6 ;)

-Michal

On Sun, Nov 9, 2014 at 6:20 PM, julio cesar sanchez 
wrote:

> Apple just says "earlier" 5%. That should be iOS 5 and iOS 6
>
> El domingo, 9 de noviembre de 2014, Terence M. Bandoian  >
> escribió:
>
> > It might make sense to consider dropping support for an iOS version when
> > usage, as reported by Apple, drops below a certain level.
> >
> > -Terence Bandoian
> >
> >
> > On 11/8/2014 5:13 PM, julio cesar sanchez wrote:
> >
> >> iOS 5 support was removed on cordova 3.5, released on may 2014, I think
> >> it's too soon to remove iOS 6 support with all the devices left behind
> >> (iphone 3gs and ipod touch 4gen), just to add swift plugins.
> >>
> >> I'm ok with dropping support to old versions when there are real
> >> advantages
> >> or security reasons.
> >>
> >> I'm limited on resources too, but I volunteer to test on my ipod touch
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

Re: Running browser platform in Linux

[Michal Mocny]

On Thu, Nov 6, 2014 at 8:53 PM, Parashuram Narasimhan (MS OPEN TECH) <
panar...@microsoft.com> wrote:

> Sorry for not being clear. I was saying that we should not open the
> file:// URL in a specific browser. We should ideally spin up a webserver
> and open the default browser on the system
>
> Why a server ? Because
> - file:// and http:// have differences in quota and permissions for many
> APIs like IndexedDB or WebSQL
>
Usually use python -m SimpleHTTPServer for this when working locally.  Node
alternative is https://github.com/nodeapps/http-server.  This will also
make it easier to integrate livereload most likely.


> - Cordova apps on mobile can make cross-domain AJAX requests. You cannot
> do that in the browser due to same-origin restriction. However, CORS can
> help, but is restricted due to file://
> - Cookies and protocol relative paths may get messed up.
>
> Why default browser? Default browser would just mean opening the HTML file.
> - I may not have Chrome installed

- Chrome may not be installed at that location
> - Issues like Linux that you described.
> - Integration of cordova-browsers in IDEs and Ripple-as-a-platform may be
> hard.
>
- Biggest reason: Safari will be a better testbed for iOS.  IE for WP.  FF
for FFOS.

I know Steven had no specific reasons for making chrome-only, it was just
the first implementation.

Looks like Victor filed https://issues.apache.org/jira/browse/CB-7978 and
has already submitted a PR for the linux fix (thanks Victor! I'll take a
look).

I've file https://issues.apache.org/jira/browse/CB-7999 to investigate a
web-server version.


>
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Thursday, November 6, 2014 1:55 PM
> To: dev@cordova.apache.org
> Subject: Re: Running browser platform in Linux
>
> Victor, feel free to send a PR so is uses config.xml content src instead
> of www/index.html.
>
> Also send the PR for your patches to run script.
>
>
> On Thu, Nov 6, 2014 at 1:17 PM, Victor Sosa 
> wrote:
>
> > Not sure I'm following you, Parashuram, can you explain a little more,
> > please?
> >
> > One more I noticed is that in the run script of the browser platform,
> > it is directly pointing to "www/*index.html*", why is index.html
> > hardcoded there instead of reading config.xml?
> >
> > I patched my run script to use this google-chrome command and I'm
> > happy to share it. Also will try to patch the index.html reference in
> > the script to open the browser.
> >
> > 2014-11-06 14:50 GMT-06:00 Parashuram Narasimhan (MS OPEN TECH) <
> > panar...@microsoft.com>:
> >
> > > I don't this we should launch Chrome this way. How about using
> > > something like browser-launcher, or even karma-chrome-launcher
> > > instead? Also, why
> > not
> > > just "open" the HTML page?
> >
>
> Chrome needs to be launched with flags for some of the plugins to work
> (camera I believe). That is why you can't just open it.
>
>
> > >
> > > -Original Message-
> > > From: Victor Sosa [mailto:sosah.vic...@gmail.com]
> > > Sent: Thursday, November 6, 2014 12:45 PM
> > > To: dev@cordova.apache.org
> > > Subject: Running browser platform in Linux
> > >
> > > Hello all.
> > >
> > > I've been playing a little bit with the Browse platform and the
> > > first thing I notice is that when running the application using
> > > "cordova run browser"
> > > it handles the cases of when using Windows and Darwin (MacOS) but no
> > Linux
> > > (I'm on Ubuntu 14.04). Is there any particular reason of why it is
> > > not handled?
> > >
> > >
> > >
> > https://github.com/apache/cordova-browser/blob/master/bin/templates/pr
> > oject/cordova/run
> > >
> > > Moreover, I have Chrome installed in my machine, but it doesn't
> > > respond
> > to
> > > the typical "chrome" command because I get an error in the standard
> > > output[1], so I have to use "google-chrome" command to launch it.
> > > Does anyone something about this? I downloaded the DEB package
> > > directly from Google Chrome.
> > >
> > > Appreciate your help
> > >
> > > [1]
> > > * Error*chrome: error while loading shared libraries: libudev.so.0:
> > cannot
> > > open shared object file: No such file or directory
> > >
> > >
> > > --
> > > Victor Adrian Sosa Herrera
> > > IBM Software Engineer
> > > Guadalajara, Jalisco
> > >
> >
> >
> >
> > --
> > Victor Adrian Sosa Herrera
> > IBM Software Engineer
> > Guadalajara, Jalisco
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: Summarizing thoughts on cordova-browser vs Ripple

[Michal Mocny]

On Thu, Nov 6, 2014 at 6:52 PM, Horn, Julian C 
wrote:

> I'd like to introduce myself and put in my two cents here. My name is
> Julian Horn.  I work for Intel on the XDK, an integrated development
> environment for cross-platform HTML5 applications.  I am the team lead for
> the Device Emulator component, which is our Ripple derivative.  My
> background is mostly in software development tools: compilers, debuggers,
> simulators and analysis tools. I have been working with the Ripple code
> base for a couple of years now.
>
> If I'm understanding the cordova-browser concept, the implementation of a
> Cordova API for the browser platform should consist of code that bridges
> between the platform-independent Cordova API and whatever equivalent is
> available in the current browser session.  For example, the camera API
> getPicture function would invoke the getUserMedia API, which is the closest
> thing we have to a W3C standard way to take a picture.  If the browser
> doesn't implement this API or the host system doesn't have a camera, then
> the getPicture call fails with "camera unavailable".
>
> This seems like a fine way to gradually migrate from packaged apps that
> rely on native code plugins to pure web apps that rely on the browser to
> access mobile device resources.  This should work great when you have a
> browser-portable implementation.  It may be a challenge with some plugins,
> since of course Cordova/PhoneGap was designed to cover gaps in browser
> support.  But at least we don't have to wait for a real W3C standard to be
> agreed.
>
> The goal of our XDK product is to facilitate development of cross-platform
> mobile HTML5 applications.  We see the Device Emulator (our Ripple) as
> enabling developers to test an HTML5 mobile application on the host
> system.  While this is no substitute for testing on real hardware, the
> Device Emulator does offers some advantages that can accelerate the
> development process.  To summarize quickly:
>  * It’s really fast.
>  * You don't need an array of mobile devices.
>  * You can put off dealing with weird target system quirks until after you
> get your basic application logic debugged.
>  * You get full native JavaScript debugging, which is faster, simpler, and
> more available than remote debug.
>  * You can create testing situations that are difficult or impossible to
> create in real life, such as GPS timeout.
>  * It's a great teaching tool.
>  * It allows you to prototype quickly.
>
> Assuming the functionality delivered by Ripple has value (and we find it
> does), one needs a way to reconcile this with the cordova-browser effort.
> Here's how I see that working out.
>
> One idea is to rely on the browser developer tools to supply emulation
> support and just drop Ripple.  I don't like this much.  Today the developer
> tools emulation UI is fairly primitive, but of course, there is nothing
> stopping the browser vendors from building all the functionality in the
> Ripple Geolocation panel (or indeed all of Ripple) into the developer
> tools.  The bigger problem from my point of view is that this is a closed
> system.  There's no way for a non-browser-vendor to extend the browser to
> provide emulation support for new plugin APIs.
>
> The alternative is to do a "cordova prepare browser" and load the results
> into Ripple.


This would be my preference if at all possible.  Specifically, I think
ripple would move much faster and be better architected if it didn't have
to depend on making changes directly to cordova.  Though it should be
acceptable to create a ripple platform (cordova run ripple) if really need
be.


>   Assuming the browser platform code follows the usual pattern, that is,
> that it goes through an exec/execProxy layer, it should be possible for
> Ripple to intercept at that level.  Ripple can delegate to the execProxy
> implementation if it has no emulation-time implementation of its own.  This
> means that unrecognized APIs run unaltered, in which case you get whatever
> behavior you get on the browser platform.  This is a really exciting
> prospect.  It's way better than that "we don't know what to do" dialog that
> Ripple puts up when an exec layer function it doesn't recognize is called.
>

Thats interesting.  I hadn't considered doing it this way, but it actually
sounds like a great solution.


>
> In fact there are some Cordova APIs that Ripple implements by mostly
> delegating to a Chrome-specific API.  For example, the simulation of the
> Cordova File API is based on webkitRequestFileSystem.  (Unfortunately no
> other browser vendors have seen fit to support this API.)  In those cases I
> think the Ripple implementation of the API is likely to coincide nicely
> with the browser platform implementation.
>
> Unlike ripple-as-a-platform, this model doesn't allow plugin authors to
> provide their own emulation-time solutions.  I was always skeptical that
> many plugin authors would really do this (others disagree).  But if they a

[GitHub] cordova-plugin-battery-status pull request: CB-7971 Add cordova-pl...

[daserge]

GitHub user daserge opened a pull request:

https://github.com/apache/cordova-plugin-battery-status/pull/19

CB-7971 Add cordova-plugin-battery-status support for Windows Phone 8.1

Added Windows Phone 8.1 support
Updated the documentation

[Jira issue](https://issues.apache.org/jira/browse/CB-7971)

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

$ git pull https://github.com/MSOpenTech/cordova-plugin-battery-status 
CB-7971

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

https://github.com/apache/cordova-plugin-battery-status/pull/19.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 #19


commit 0703999de8160773fe51067d8f589ed862b9a11b
Author: daserge 
Date:   2014-11-10T07:06:02Z

CB-7971 Add cordova-plugin-battery-status support for Windows Phone 8.1

Added Windows Phone 8.1 support
Updated the documentation




---
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: Review: Tools Release blog post

[Ian Clelland]

Are there any changes at all to plugman that necessitate its release, or is
it just being released so that there's a version that uses the new
cordova-lib? It seems odd that it's in the announcement, but missing from
the releasenotes.

On Fri Nov 07 2014 at 5:22:51 PM Mark Koudritsky  wrote:

> Please review and send PRs!
> https://github.com/kamrik/apache-blog-posts/blob/master/
> 2014-11-10-tools-release.md
>

[GitHub] cordova-plugin-battery-status pull request: CB-7971 Add cordova-pl...

[daserge]

Github user daserge closed the pull request at:

https://github.com/apache/cordova-plugin-battery-status/pull/18


---
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