cordova 5.0.0 and gradle

[Axel Nennker]

Hi,

I update to cordova 5 and now my project build fail.

I am behind a corporate proxy
  ignisvulpis@namenlos:~/development/nur_der_hsv$ echo $JAVA_OPTS
  -Dhttp.proxyHost=http://xxx.yyy.109.5:8080/
and have gradle 2.3 installed
  ignisvulpis@namenlos:~/development/nur_der_hsv$ which gradle
  /usr/local/gradle-2.3/bin/gradle

But it seems cordova forces gradle to download gradle version 2.2.1 which
fails.

I don't want network access at build-time. We made local copies of all
plugins we need and do a cordova plugin add plugindirectory to add them.
Platforms are downloaded sometimes.

How do I prevent cordova to try to download an older version of gradle?

cheers
Axel


exerpt from our ant file output:
run-app:
 [echo] Build and run BasicWallet for: android
 [exec] Running command:
/home/ignisvulpis/development/nur_der_hsv/app/platforms/android/cordova/run
 [exec] ANDROID_HOME=/home/ignisvulpis/Android/Sdk
 [exec] JAVA_HOME=/usr/lib/jvm/java-8-oracle
 [exec] WARNING : No target specified, deploying to device '7ece97a7'.
 [exec] Running:
/home/ignisvulpis/development/nur_der_hsv/app/platforms/android/gradlew
cdvBuildDebug -b
/home/ignisvulpis/development/nur_der_hsv/app/platforms/android/build.gradle
-PcdvBuildArch=arm -Dorg.gradle.daemon=true
 [exec] Downloading
http://services.gradle.org/distributions/gradle-2.2.1-all.zip
 [exec]
 [exec] ERROR running one or more of the platforms: Error:
/home/ignisvulpis/development/nur_der_hsv/app/platforms/android/cordova/run:
Command failed with exit code 8
 [exec] You may not have the required environment or OS to run this
project
 [exec] Exception in thread "main" java.lang.RuntimeException:
java.net.ConnectException: Connection refused
 [exec] at
org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:78)
 [exec] at org.gradle.wrapper.Install.createDist(Install.java:47)
 [exec] at
org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
 [exec] at
org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:48)
 [exec] Caused by: java.net.ConnectException: Connection refused
 [exec] at java.net.PlainSocketImpl.socketConnect(Native Method)

[GitHub] cordova-plugin-media pull request: CB-8888 Makes media status repo...

[vladimir-kotikov]

GitHub user vladimir-kotikov opened a pull request:

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

CB- Makes media status reporting on windows more precise

Fix for https://issues.apache.org/jira/browse/CB-

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

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

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

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


commit 5cf73f56d571e0e71762aeaeddaa05e9bbc78d06
Author: Vladimir Kotikov 
Date:   2015-04-22T09:50:19Z

CB- Makes media status reporting on windows more precise




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

Cookie support in docs.

[Andrey Kurdumov]

Hi,

I come across the following SO question.
http://stackoverflow.com/questions/24374397/cookie-support-in-cordova-official-documentation

The guy could not find any mentions about cookie support in the Phonegap. I
do google search and find that the only mention about cookie support is
issue CB-8026 where stated that Android support third-party cookies. I
personally was having problems with that, but resolve it using custom HTTP
header.

Question is: Does it make sense add the section in the docs regarding
cookies, and their limitations in Cordova apps, due to fact that files
server over file:/// protocol?

Re: cordova 5.0.0 and gradle

[Axel Nennker]

Ignoring the no-network-while-building requirement for a moment and setting
the JAVA_OPTS proxy variable correctly leads to this:
 [exec] Downloading
http://services.gradle.org/distributions/gradle-2.2.1-all.zip
 [exec]
..
 [exec] Unzipping
/home/ignisvulpis/.gradle/wrapper/dists/gradle-2.2.1-all/2m8005s69iu8v0oiejfej094b/gradle-2.2.1-all.zip
to
/home/ignisvulpis/.gradle/wrapper/dists/gradle-2.2.1-all/2m8005s69iu8v0oiejfej094b
 [exec] Set executable permissions for:
/home/ignisvulpis/.gradle/wrapper/dists/gradle-2.2.1-all/2m8005s69iu8v0oiejfej094b/gradle-2.2.1/bin/gradle
 [exec]
 [exec] FAILURE: Build failed with an exception.
 [exec]
 [exec] * What went wrong:
 [exec] A problem occurred configuring root project 'android'.
 [exec] > Could not resolve all dependencies for configuration
':classpath'.
 [exec]> Could not resolve com.android.tools.build:gradle:1.0.0+.
 [exec]  Required by:
 [exec]  :android:unspecified
 [exec]   > Failed to list versions for
com.android.tools.build:gradle.
 [exec]  > Unable to load Maven meta-data from
https://repo1.maven.org/maven2/com/android/tools/build/gradle/maven-metadata.xml
.
 [exec] > Could not GET '
https://repo1.maven.org/maven2/com/android/tools/build/gradle/maven-metadata.xml
'.
 [exec]> Connection to https://repo1.maven.org refused
 [exec]
 [exec] * Try:
 [exec] Run with --stacktrace option to get the stack trace. Run with
--info or --debug option to get more log output.

It seems that cordova detects that my gradle version is 2.3 and sets the
dependency to com.android.tools.build:gradle:1.0.0+ but later something
decides that gradle 2.2.1 should be used.

-Axel

2015-04-22 11:42 GMT+02:00 Axel Nennker :

> Hi,
>
> I update to cordova 5 and now my project build fail.
>
> I am behind a corporate proxy
>   ignisvulpis@namenlos:~/development/nur_der_hsv$ echo $JAVA_OPTS
>   -Dhttp.proxyHost=http://xxx.yyy.109.5:8080/
> and have gradle 2.3 installed
>   ignisvulpi

[GitHub] cordova-plugin-whitelist pull request: Fixed error in Content-Secu...

[krebernisak]

Github user krebernisak commented on the pull request:


https://github.com/apache/cordova-plugin-whitelist/pull/3#issuecomment-95151565
  
+1


---
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: Question about bypassing the run-loop wait/entire bridge for plugins on iOS

[Carlos Santana]

Hi Tim, thanks for offering help.
There are was a recent discussion in the mailing list about keyboard plugin
for iOS [1]
And Shaz posted a Blog post on the maintenance of the keyboard plugin as a
Cordova core plugin. [2]

As some of the committers have express we think that the kyeboard plugin is
better to be a 3rd party plugin.
So I think improving the ionic keyboard plugin will be the preferred
solution, and since it's open source the better
Oh by the way Attention*** we moved plugins to npm [3], so grab the npm
name space for your plugin (i.e. cordova-plugin-keyboard) before some troll
does :-)

Kerri created some examples to provide a good UX using the ionic keyboard
plugin [4], I encourage to take a look and see how the plugin can be
enhanced, and maybe some of the examples incorporated into the ionic ui
framework (i.e. directive)

Take care and looking forward on more discussions and contributions from
ionic team !

[1]: http://markmail.org/thread/7vcswxfkqr67amee
[2]:
https://shazronatadobe.wordpress.com/2014/07/09/cordova-keyboard-plugin-maintenance-update/
[3]:
http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
[4]: https://github.com/kerrishotts/cordova-keyboard-example


On Tue, Apr 21, 2015 at 4:19 PM, Tim Lancina  wrote:

> Awesome, thanks guys! Yeah honestly one way to solve this particular
> problem I think is to just shrink the native view like the original Cordova
> keyboard plugin.  Speaking of which, is the Cordova keyboard plugin still
> kind of in limbo? Michal suggested to us last year that the Ionic keyboard
> plugin use it as a dependency, but we were a lot smaller as a team and had
> other priorities in building the framework.  Now that we're a little bigger
> and would like to invest more in the ecosystem as a whole, is there still
> any interest in having us contribute back to the official Cordova plugin?
> Or is it maybe too little too late.
>
> On Mon, Apr 20, 2015 at 7:46 PM, Andrew Grieve 
> wrote:
>
> > I think Jesse pretty much covered it.
> >
> > I would be surprised if you could get web animations to be in sync with
> > native animations like the keyboard. If you are to try, I think you'd get
> > closest by attaching a timestamp to the event you're sending to JS, and
> use
> > requestAnimationFrame to animate. CSS animations don't guarantee that
> they
> > will start right away I don't think.
> >
> > That said - yes, you should just experiment with whether using
> > stringByEvaluatingJavaScriptFromString helps at all. If it doesn't help
> > anyways though, there's no point in using it.
> > What can go wrong?
> > - possibility of deadlock, esp when JS callback tries to do an alert()
> > - does not optimized calls to exec() made from within the callback
> > - will not work out-of-the-box with WKWebView.
> >
> > On Mon, Apr 20, 2015 at 5:40 PM, Jesse  wrote:
> >
> > > I think you are best off to experiment and see what you can get working
> > > consistently.  The focus lately has been on the wkwebview bridge, which
> > is
> > > entirely new, while the current webview implementation is a collection
> of
> > > workarounds for various issues.
> > >
> > > If you can distill this down to a simple project that demonstrates the
> > > issue, I would be happy to have a look.
> > >
> > >
> > >
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Mon, Apr 20, 2015 at 3:25 PM, Tim Lancina  wrote:
> > >
> > > > Whoops should probably have subscribed to the mailing list! Apologies
> > if
> > > > this screws up the thread.
> > > >
> > > > Thanks for your response Jesse. The problem is knowing when to start
> > the
> > > > css animation, hence why it would be best to be able to fire an event
> > > > indicating the keyboard is about to show as quickly as possible.  If
> > you
> > > > wait for the run-loop, the animation will be behind by an arbitrary
> > > amount
> > > > by the time it receives the event.  This isn't the end of the world,
> it
> > > > just isn't as smooth and simultaneous as native.
> > > >
> > > > In the case of the keyboard plugin, all it does is trigger an event
> on
> > > the
> > > > document indicating the keyboard will show/hide.  So if I'm
> > understanding
> > > > correctly, it would be better to leave the default evalJS
> > > > scheduledOnRunLoop:YES call because the handlers for those events
> fired
> > > by
> > > > the plugin could in theory result in more calls to native, correct?
> > > >
> > > > I suppose we could fire one event immediately, with the stipulation
> > that
> > > > handlers for the event shouldn't trigger any native calls, and
> another
> > > > marginally slower, 'safe' event that could be used in most
> > circumstances.
> > > >
> > > > If I'm making any false assumptions or overlooking something, please
> > let
> > > me
> > > > know!
> > > >
> > > > Best,
> > > > Tim
> > > >
> > > > On Mon, Apr 20, 2015 at 4:45 PM, Josh Bavari 
> > wrote:
> > > >
> > > > >
> > > > > -- Forwarded message 

Re: Discussions on vote threads

[Frederico Galvão]

As a developer (cordova customer) who follows pretty much everything
related to cordova development closely, I always look for a blog post or
some form of changelog in the [VOTE]/[DISCUSS] thread, but rarely do I find
one. That'll be a nice inclusion in the process for me, to say the least.

2015-04-19 21:48 GMT-03:00 Parashuram N (MS OPEN TECH) <
panar...@microsoft.com>:

> I think it is a great idea to have the blog post ready before we start the
> DISCUSS. Should we try this out for a couple of releases in the future to
> see if everyone gets and idea of what is being discussed, without having to
> dig deep into the mailing lists.
>
> -Original Message-
> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
> Grieve
> Sent: Thursday, April 9, 2015 5:04 PM
> To: dev
> Subject: Re: Discussions on vote threads
>
> Both good feedback Jesse & Leo!
>
> I'll update the email templates to state discussion should happen on the
> DISCUSS thread.
>
> Leo - Maybe one baby step towards what you describe is having the blog
> post ready in the DISCUSS before the VOTE happens? Might be able to do more
> what you describe, but I think you (or someone else who fully groks it)
> would need to try it out for a release and see how it goes.
>
> On Thu, Apr 9, 2015 at 5:05 PM, Treggiari, Leo 
> wrote:
>
> > I'll tell you why I didn't raise my question until now.  Sorry it was
> > on the vote thread, but it was the first time that I was able to see
> > the information that I needed to understand exactly (at least better)
> > what was going to happen with whitelisting.  Actually, the title of
> > the message (that is was a vote thread) never made it to my forefront
> consciousness.
> >
> > This is a process suggestion and I hope you take it in the spirit of
> > trying to make the process better and the project releases better.
> > Maybe
> > *my* problem is exactly just that and no one else is having the same
> > problem.  I have a hard time figuring out to any level of detail what
> > is being changed/added in any release.  Sometimes there are written
> > proposals that go into some level of detail.  Then there are e-mail
> > discussions and/or comments made to a document.  But not often do I
> > see the original proposal updated with final decisions before a
> > release occurs.  So how many people know what is actually happening in
> > a release at more than the level that, e.g., whitelisting is changing
> > and there are some new plugins.  If I wrote the code I'd know.  If I
> > reviewed the code, I’d probably know.  If I tried to piece together
> > the likely changes by following all discussions and comments, I might
> > know.  I did not write or review the code and I try at keeping up with
> the discussions but it still leaves me with questions.
> >
> > Even after a release, I often find it difficult to find a description
> > (spec or documentation) about exactly how something is supposed to work.
> > So here is a rough suggestion about how I think things could improve.
> > I'm just a downstream consumer and so I don't expect my opinions to
> > carry much weight compared to you who have created and maintained
> Cordova over years.
> >
> > Imagine there was a complete spec to the visible functionality in
> > Cordova, including plugins, CLI commands, configuration files, etc.
> > Certainly a lot exists but I have found myself in the situation where
> > I can find no documentation about some option or some 'corner case'.
> > If you think the project already has this, great - step 1 is done.
> >
> > When a proposal is made to change the visible functionality, the
> > differences to the existing spec are documented in a proposal spec and
> > then reviewed by this mailing list.  Discussions take place like they
> > do today, but at some point the proposer decides the discussions have
> > died down and then updates the proposal spec.  Maybe there is some
> > further discussion based upon the update or not.  However, with the
> > update(s) to the proposal spec everyone should be able to understand
> > what is expected when the proposed functionality is released and
> > should raise any issues or questions before vote time comes.  With the
> > release, the information in the proposal spec can be merged into the
> complete public spec.
> >
> > So that's my excuse regarding why my questions and issues are often
> > "last minute".  Other than of course, "my cat ate my e-mail!"
> >
> > Leo
> >
> > -Original Message-
> > From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
> > Andrew Grieve
> > Sent: Thursday, April 09, 2015 1:01 PM
> > To: dev
> > Subject: Re: Discussions on vote threads
> >
> > That's a good point. Perhaps we should update our template to say
> > "minium or 48 hours, and at least 24 hours after the last non-vote
> comment"
> >
> > On Thu, Apr 9, 2015 at 3:58 PM, Joe Bowser  wrote:
> >
> > > There's nothing wrong with the practice except that a vote thread
> > > with comm

Re: How to get plugin lists for cordova-android 3.7.x

[Carlos Santana]

Hi Fu
  If you want to test what was release at the time frame that Android 3.7.1
was released then one way if too look at the release notes.

You can use Cordova CLI 4.2.0 [1] "npm install -g cordova@4.2.0", it pinned
cordova-android@3.7.1
To get the plugin list that was tested at that time frame you can take a
look at the release notes for Plugins [2] when for Android 3.7.1 was the
latest pinned.

use latest cordova-mobile-spec and latest cordova-plugin-test-framework

Don't know why you will want to test old plugins, I will stick with latest
plugins released this week. and latest cordova-cli and add android platform
3.7.1 "cordova platform add android@3.7.1"

I guess I didn't answer you questions :-), but I gave you enough rope


[1]: http://cordova.apache.org/news/2015/03/02/tools-release.html
[2]: http://cordova.apache.org/news/2015/02/10/plugins-release.html



On Tue, Apr 21, 2015 at 8:20 PM, Fu, Junwei  wrote:

> Hi All,
>
> Mobile-spec has no 3.7.x branch, how can I  get the plugin lists for
> cordova-android 3.7.x, and how to build mobile-spec to test cordova-android
> 3.7.x, do we use the latest cordova-plugin-test-framework, cordova-cli,
> cordova-mobile-spec and so on.
>
> Thanks,
> Junwei.
>



-- 
Carlos Santana

Re: Does Cordova have a problem making developers happy?

[Frederico Galvão]

As someone who has given a couple of local speechs and presentations about
Cordova, I could say with some certainty that most of the time what makes
Cordova a not-so-well known tool is the misconception about what it's aimed
at doing, and incoherent expectations towards what it CAN do for the
developer.

Other than that, and all the small things that have been already mentioned
previously by everyone, I'd say that web development (the one out there,
not the one defined by ES{6,7,8} or future dream
tools/standards/frameworks) in general is still not ready to what is needed
for mobile development to be taken seriously and be able to build complex
applications successfully. Very few development teams have enough awareness
of how much more is needed on a well built application other than jQuery
and 256 plugins.

In the end, everything sums up to how well defined expectations are. And
I'm sure Cordova, along with its website and documentation, can be a lot
better at guiding developers to better expectations towards everything that
can be expected from cordova, and what can't.

I'm interested in contributing to this in whatever small way I can.

2015-04-19 21:48 GMT-03:00 Parashuram N (MS OPEN TECH) <
panar...@microsoft.com>:

> I think FAQs, tutorials and blogs are great. I would also like to
> contribute to this. Maybe a good start would be to identify a the topics
> that require a blog post ?
> If we have a list of things to blog about, I am sure the community can
> come up with the actual articles and blog posts.
> I am sure my team would love to help with the content. Should we start
> putting together a list of topics that would need tutorials ?
>
>
>
> -Original Message-
> From: Kerri Shotts [mailto:kerrisho...@gmail.com]
> Sent: Monday, April 13, 2015 8:57 PM
> To: dev@cordova.apache.org
> Subject: Re: Does Cordova have a problem making developers happy?
>
> I had similar ideas about writing some FAQs or posts. Great minds clearly
> think alike, right? ;-) (I’m joking. I know my mind… so not great… Wait…
> that might actually be an insult to everyone else. The only way to win is
> not to play! Aah! Clearly I need to go to bed. I’ve been staring at
> my latest book’s chapter for way too long.)
>
> In fact, I’ve toyed with the idea of doing some screencasts using Cordova
> and the various tools I use with it (like gulp, browserify, and babeljs),
> and these could make some excellent topics as well. Especially debugging,
> because it’s not always enough just to say “here’s where you go to start
> debugging remotely”. Debugging is a skill (an art, really), so I could see
> a lot from that topic alone, but geared more directly at typical debugging
> issues one finds in Cordova dev. Hmm. Where to find the hours in the day?
> Or a clone… I could really use a clone…
>
>
>
>
> From: Raymond Camden 
> Reply: dev@cordova.apache.org >
> Date: April 13, 2015 at 8:18:39 PM
> To: dev@cordova.apache.org >
> Subject:  Re: Does Cordova have a problem making developers happy?
>
> Like Tommy, I may steal some of these for blog posts -
>
> "People is having troubles connecting with the server, some of them
> > because use localhost as the url, others because they don't configure
> > the whitelist properly, others for unknow reasons"
>
> As for the debug one, I ask, "Do you know how to remote debug?" about
> 5-10 times a week now. Sadly, now that it is so DARN easy to debug, folks
> just don't seem to know they CAN do it.
>
> On Mon, Apr 13, 2015 at 6:49 PM, tommy-carlos williams 
> wrote:
> > If no one else has time to do something with this list by the time I get
> free of my current stress-pile (say a couple weeks from now), I would love
> to take a crack at it. An FAQ with not just the list, but actual solutions
> and examples would be a great resource.
> >
> > Even if someone else does it, I might use it as the basis for a series
> > of blog posts or something. It’s such a good summary of people’s
> > frustrations. I would probably even have one or two to add from the
> > #phonegap IRC channel.. :/
> >
> > --
> > tommy-carlos williams
> >
> > On 14 April 2015 at 08:16:56, Josh Soref (jso...@blackberry.com) wrote:
> >
> > So, I want someone to make this into a FAQ, somehow.
> >
> > I don't have time today, but it's a really great list.
> >
> > Bonus points for getting it Stickied at the top of StackOverflow.
> >
> > (obviously, it should include some explanation of how to correct these
> > things, and thankfully most are pretty easy to address.)
> >
> > Some are probably asking for samples (e.g. a "how to do things
> > slowly/choppily w/ left: vs. how to use CSS transitions" -- Raymond?)
> >
> > Julio wrote an amazing summary of Cordova Stack Overflow posts:
> >> I read most of the questions with cordova tag on stackoverflow and
> >> the questions on the google group and I see this problems.
> >>
> >> - Some people don't read the docs
> >> - Some people read the wrong docs (they use cordova 2.9.1 because
>

Re: [ANNOUNCEMENT] Cordova Tools (CLI 5.0.0) + Plugins (renamed) have been released

[Carlos Santana]

Hi Ray
Home page http://cordova.apache.org shows the last 3 blog posts with
corresponding "Read More" that takes you directly to post.

21 Apr 2015 » Tools Release: April 21, 2015

21 Apr 2015 » Plugins Release and Moving plugins to npm: April 21, 2015

15 Apr 2015 » Apache Cordova Android 4.0.0


If you see this now, maybe it was a caching problem, and now is resolved.



On Wed, Apr 22, 2015 at 12:53 AM, Shazron  wrote:

> It should be, I see it?
>
> On Tue, Apr 21, 2015 at 8:12 PM, Raymond Camden 
> wrote:
> > Query - the blog listing on the home page isn't updated. Is that a known
> issue?
> >
> > On Tue, Apr 21, 2015 at 5:46 PM, Steven Gill 
> wrote:
> >> Tools and plugins have been released.
> >>
> >> Includes fetching from npm and renamed plugins.
> >>
> >> Plugins:
> >>
> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
> >>
> >> Tools: http://cordova.apache.org/news/2015/04/21/tools-release.html
> >>
> >> Tweets:
> >> https://twitter.com/apachecordova/status/590676867046383616
> >> https://twitter.com/apachecordova/status/590677169745068034
> >> https://twitter.com/apachecordova/status/590677437454929920
> >
> >
> >
> > --
> >
> ===
> > Raymond Camden, Developer Advocate for MobileFirst at IBM
> >
> > Email : raymondcam...@gmail.com
> > Blog : www.raymondcamden.com
> > Twitter: raymondcamden
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>


-- 
Carlos Santana

RE: Proposal: Expose check_reqs at the CLI level

[Vladimir Kotikov (Akvelon)]

Hey, guys. Have anyone looked at it?
I've made some refactoring to make changes more readable, and updated data 
contract between platform's check_reqs code and LIB API.

Josh, regarding command name. I thought that there is still no agreement about 
verb name.
Personally I agree that `cordova doctor` or `cordova requirements` sounds 
better, but this is just a command name ant it could be changed at any time. 

---
Best regards, Vladimir

-Original Message-
From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Sent: Monday, 20 April, 2015 22:04
To: dev@cordova.apache.org
Subject: RE: Proposal: Expose check_reqs at the CLI level

This was only an initial implementation - no pull request has been sent. I 
think this is just a way for folks to play with what Vlad has now. I am sure we 
will change the verb name before a PR comes in. 

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Monday, April 20, 2015 11:59 AM
To: dev@cordova.apache.org
Subject: RE: Proposal: Expose check_reqs at the CLI level

-1

Didn't everyone agree to call it `cordova doctor` or worst, `cordova 
requirements`?

> -Original Message-
> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> Sent: Monday, April 20, 2015 11:46 AM
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> Hi, list.
> 
> I would like to share a draft implementation for check_reqs command 
> and check_reqs API:
> Changes  could be found here:
> CLI: https://github.com/apache/cordova-
> cli/compare/master...MSOpenTech:requirements_check
> LIB: https://github.com/apache/cordova-
> lib/compare/master...MSOpenTech:requirements_check
> Cordova-android: https://github.com/apache/cordova-
> android/compare/master...MSOpenTech:requirements_check
> 
> The implementation consists of following:
> 1. 'cordova check-reqs' command for cordova CLI, which calls 
> corresponding cordova-lib API with options, specified from CLI
> 
> 2. 'check_reqs' module for cordova-lib, which works as a wrapper 
> around platforms' check_reqs scripts. It returns a promise, either 
> resolved if check_reqs platform script is found and ran successfully 
> or rejected in case if check_reqs script is failed due to some internal 
> errors or not found at all.
> 
> 3. check_reqs script for android platform, updated to return array of 
> requirements.
> 
> * Each requirements is an object with following fields:
> - id - some short id, could be useful for tools, that consume API 
> directly
> - name - readable name for this requirement, such as 'Jav JDK' 
> or 'Gradle build tools', etc.
> - installed - Boolean paremeter that indicates if requirement 
> is properly installed/satisfied
> - reason - error, reported by requirements check routines if 
> requirement is missing.
> 
> Please note that work is still in progress, and will be changed 
> according to review comments.
> TBD:
> * move presentation logic from LIB to CLI;
> * refine data format, returned by cordova-lib API
> * add other platforms
> * and more... :)
> 
> ---
> Best regards, Vladimir
> 
> -Original Message-
> From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
> Sent: Monday, 20 April, 2015 3:49
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> Looks like implementing a global level check_reqs without a project 
> seems harder, I would suggest we make it a part of a second phase of 
> this implementation. For now, we have a basic version that simply 
> abstracts out existing check_reqs into a separate, platform level 
> command. This could be a good first phase, and should also give us an 
> idea about how developers use this command.
> 
> As a part of Phase 2, anyone from the community should be able to 
> build on a cordova level check reqs, and possibly extend it to 
> checking reqs when no project is present.
> 
> 
> -Original Message-
> From: Josh Soref [mailto:jso...@blackberry.com]
> Sent: Wednesday, April 15, 2015 8:53 AM
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> We already support:
> 
> `cordova build android`
> 
> There's no need for the extra `platform` verb..
> 
> But,
> `cordova build android --nobuild` isn't any more intuitive than w/ the 
> extra "platform".
> 
> 
> And yes, as I noted, and others have noted, we used to run check_reqs 
> in add, we're not going back to doing that.
> 
> A `cordova doctor` or `cordova requirements` verb seems fine.
> 
> I'm also fine `cordova doctor PLATFORM` instead of `cordova platform 
> doctor PLATFORM`,
> 
> As for when someone is likely to want to ask "what requirements do I 
> need for a platform", it's fairly arbitrary.
> 
> Someone who is given a project might know that they don't have the 
> environment for a platform, they aren't likely to want to go down a 

Re: [ANNOUNCEMENT] Cordova Tools (CLI 5.0.0) + Plugins (renamed) have been released

[Raymond Camden]

Ah - a shift reload fixed it. Is the caching a bit high for the page?

On Wed, Apr 22, 2015 at 7:15 AM, Carlos Santana  wrote:
> Hi Ray
> Home page http://cordova.apache.org shows the last 3 blog posts with
> corresponding "Read More" that takes you directly to post.
>
> 21 Apr 2015 » Tools Release: April 21, 2015
> 
> 21 Apr 2015 » Plugins Release and Moving plugins to npm: April 21, 2015
> 
> 15 Apr 2015 » Apache Cordova Android 4.0.0
> 
>
> If you see this now, maybe it was a caching problem, and now is resolved.
>
>
>
> On Wed, Apr 22, 2015 at 12:53 AM, Shazron  wrote:
>
>> It should be, I see it?
>>
>> On Tue, Apr 21, 2015 at 8:12 PM, Raymond Camden 
>> wrote:
>> > Query - the blog listing on the home page isn't updated. Is that a known
>> issue?
>> >
>> > On Tue, Apr 21, 2015 at 5:46 PM, Steven Gill 
>> wrote:
>> >> Tools and plugins have been released.
>> >>
>> >> Includes fetching from npm and renamed plugins.
>> >>
>> >> Plugins:
>> >>
>> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
>> >>
>> >> Tools: http://cordova.apache.org/news/2015/04/21/tools-release.html
>> >>
>> >> Tweets:
>> >> https://twitter.com/apachecordova/status/590676867046383616
>> >> https://twitter.com/apachecordova/status/590677169745068034
>> >> https://twitter.com/apachecordova/status/590677437454929920
>> >
>> >
>> >
>> > --
>> >
>> ===
>> > Raymond Camden, Developer Advocate for MobileFirst at IBM
>> >
>> > Email : raymondcam...@gmail.com
>> > Blog : www.raymondcamden.com
>> > Twitter: raymondcamden
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> > For additional commands, e-mail: dev-h...@cordova.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>
>
>
> --
> Carlos Santana
> 



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

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

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

Re: Build signed archives using CLI

[Andrew Grieve]

PR LGTM, but I have one question (maybe mostly for Shaz):

Seems our build script pass -xcconfig "build-release.xcconfig", but our
project template doesn't use any .xcconfig:
http://pasteboard.co/2L2wg6r2.png

Would it be better to:
- use a different build-extras.xcconfig for debug / release (e.g.
build-extras-release.xcconfig)
- Set the xcconfigs in the project template so that they are used when
building from Xcode?


On Tue, Apr 21, 2015 at 4:47 PM, Nikhil Khandelwal 
wrote:

> Support for iOS is in this PR now:
> https://github.com/apache/cordova-ios/pull/138
>
> It allows you to specify a signing identity and a provisioning profile
> using command line arguments or build.json.
>
> Thanks,
> Nikhil
>
>
> -Original Message-
> From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
> Sent: Monday, April 6, 2015 9:37 AM
> To: dev@cordova.apache.org
> Subject: RE: Build signed archives using CLI
>
> Thanks, Andrew for doing a thorough review. This was merged in last week.
> I have created a new PR for the docs update:
> https://github.com/apache/cordova-docs/pull/277
>
> It's important to note, to make it simple to pass multiple signing
> parameters, I have created the concept of a build.json file (instead of
> cordova-keys.json suggested below) that can be used to specify build-time
> parameters. It supports specifying two sets of values - debug & release.
>
> This support is currently only for Android, I am working on another PR for
> iOS.
>
> Thanks,
> Nikhil
>
>
> -Original Message-
> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
> Grieve
> Sent: Wednesday, March 18, 2015 4:48 PM
> To: dev
> Subject: Re: Build signed archives using CLI
>
> Left some comments on the PR.
>
> On Tue, Mar 17, 2015 at 5:04 PM, Nikhil Khandelwal  >
> wrote:
>
> > I just submitted a PR for this for Android:
> > https://github.com/apache/cordova-android/pull/164
> >
> > Here's the rough design:
> >
> > - Build.json or command line args can be used to specify details
> > required for packaging:
> > - Keystore
> > - Alias
> > - Keystore password
> > - Password
> > - Keystore type.
> > - Debug-signing.properties or release-signing.properties is created at
> > prepare time to allow gradle or Ant build systems to pick up those
> > properties and generate a signed archive.
> > - ‘Clean’ will delete these autogenerated .properties files.
> > - If no password is specified for release signing, Ant & gradle will
> > prompt for passwords.
> >
> > I will shortly have a PR to update the docs.
> >
> > Thanks,
> > Nikhil
> >
> >
> > -Original Message-
> > From: Carlos Santana [mailto:csantan...@gmail.com]
> > Sent: Friday, February 13, 2015 2:28 PM
> > To: dev@cordova.apache.org
> > Subject: Re: Build signed archives using CLI
> >
> > Thanks Nikhil I see this as a very good and important feature to have
> > in our CLI stack
> >
> > On Fri, Feb 13, 2015 at 4:48 PM, Nikhil Khandelwal
> >  > >
> > wrote:
> >
> > > I'm taking this over from Dan. I like the idea of having the release
> > > signing information persisted in a json file.
> > >
> > > I have made some updates on the specific issue of how keys/passwords
> > > can be passed through CLI and JSON:
> > >
> > > https://docs.google.com/document/d/1tJQ9OoGrrMhZcLI3mg46rGzAfbiQu9Pu
> > > NB
> > > L1auAMGFM/edit#
> > >
> > > I'm still going through the details of packaging requirements of
> > > each platform. I expect to add some more details on how the
> > > packaging process will work with individual platform build systems
> > > in the coming days. I will update this thread when I do so.
> > >
> > > Here's the main JIRA with platform specific tasks here:
> > > https://issues.apache.org/jira/browse/CB-8483. I would love to
> > > collaborate with others who are interested in this area.
> > > Specifically, I plan to take up the task of implementing this for
> Android first.
> > >
> > > Thanks,
> > > Nikhil
> > >
> > >
> > > -Original Message-
> > > From: Victor Sosa [mailto:sosah.vic...@gmail.com]
> > > Sent: Tuesday, February 10, 2015 2:29 PM
> > > To: dev@cordova.apache.org
> > > Subject: Re: Build signed archives using CLI
> > >
> > > I'm leaning to Andrew and Omar's idea. I like the idea of having a
> > > file where all the platform-specific information will be stored,
> > > then each platform will take that information to sign the archive
> > > and produce a usable, I mean ready-to-distribute, binary.
> > >
> > > As for Omar's comment, I also concur there. If a user has the
> > > signing info in gradle or ant properties and that info is also
> > > provided in the new file discussed here, then it should take
> > > precedence and override the platform-specific one.
> > >
> > > Wondering if Dan is feeling OK now and ready to be back in the game
> > > :D
> > >
> > > 2015-02-02 14:58 GMT-06:00 Mefire O. :
> > >
> > > > +1 for having an additional file to abstract away all the platform
> > > > speci

[GitHub] cordova-plugin-camera pull request: solves CB-8804 https://github....

[agrieve]

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

https://github.com/apache/cordova-plugin-camera/pull/83#discussion_r28881787
  
--- Diff: src/android/CameraLauncher.java ---
@@ -163,7 +167,15 @@ else if ((srcType == PHOTOLIBRARY) || (srcType == 
SAVEDPHOTOALBUM)) {
 PluginResult r = new 
PluginResult(PluginResult.Status.NO_RESULT);
 r.setKeepCallback(true);
 callbackContext.sendPluginResult(r);
-
+
+return true;
+} else if (action.equals("checkForSavedResult")) {
+this.imageUri = Uri.fromFile(createCaptureFile(JPEG));
--- End diff --

should you do this only when savedRequestCode > 0?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-plugin-camera pull request: solves CB-8804 https://github....

[agrieve]

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

https://github.com/apache/cordova-plugin-camera/pull/83#discussion_r28881896
  
--- Diff: src/android/CameraLauncher.java ---
@@ -163,7 +167,15 @@ else if ((srcType == PHOTOLIBRARY) || (srcType == 
SAVEDPHOTOALBUM)) {
 PluginResult r = new 
PluginResult(PluginResult.Status.NO_RESULT);
 r.setKeepCallback(true);
 callbackContext.sendPluginResult(r);
-
+
+return true;
+} else if (action.equals("checkForSavedResult")) {
+this.imageUri = Uri.fromFile(createCaptureFile(JPEG));
+if (savedRequestCode > 0) {
+onActivityResult(savedRequestCode, savedResultCode, 
savedIntent);
+} else {
+callbackContext.success("no-result");
--- End diff --

Would be much nicer if returned result was false when coerced to a boolean 
(so that they can do if (result)). So maybe return empty string or null.


---
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: Proposal: Expose check_reqs at the CLI level

[Treggiari, Leo]

Hi Vladimir,

It's great to see this being worked on and discussed.  My comments below are 
mine and mine alone.

In addition to the code changes, I would have preferred to see a specification 
of the command, e.g.

cordova check-reqs platform [platform...]

I took a quick look at the CLI code changes and didn't see any option 
processing.  Are there any options?
Do the platform(s) specified on the command need to have been already added to 
the project?
Does the command require a project - i.e. be executed in a project directory?
Regarding the command name, I don't think being 'cute' is helpful to users - 
i.e. I recommend against 'doctor'.
I think 'check-requirements' would be OK.  It's long but how many times does a 
user need to type it?

Thanks,
Leo

-Original Message-
From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] 
Sent: Wednesday, April 22, 2015 7:18 AM
To: dev@cordova.apache.org
Subject: RE: Proposal: Expose check_reqs at the CLI level

Hey, guys. Have anyone looked at it?
I've made some refactoring to make changes more readable, and updated data 
contract between platform's check_reqs code and LIB API.

Josh, regarding command name. I thought that there is still no agreement about 
verb name.
Personally I agree that `cordova doctor` or `cordova requirements` sounds 
better, but this is just a command name ant it could be changed at any time. 

---
Best regards, Vladimir

-Original Message-
From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Sent: Monday, 20 April, 2015 22:04
To: dev@cordova.apache.org
Subject: RE: Proposal: Expose check_reqs at the CLI level

This was only an initial implementation - no pull request has been sent. I 
think this is just a way for folks to play with what Vlad has now. I am sure we 
will change the verb name before a PR comes in. 

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Monday, April 20, 2015 11:59 AM
To: dev@cordova.apache.org
Subject: RE: Proposal: Expose check_reqs at the CLI level

-1

Didn't everyone agree to call it `cordova doctor` or worst, `cordova 
requirements`?

> -Original Message-
> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> Sent: Monday, April 20, 2015 11:46 AM
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> Hi, list.
> 
> I would like to share a draft implementation for check_reqs command 
> and check_reqs API:
> Changes  could be found here:
> CLI: https://github.com/apache/cordova-
> cli/compare/master...MSOpenTech:requirements_check
> LIB: https://github.com/apache/cordova-
> lib/compare/master...MSOpenTech:requirements_check
> Cordova-android: https://github.com/apache/cordova-
> android/compare/master...MSOpenTech:requirements_check
> 
> The implementation consists of following:
> 1. 'cordova check-reqs' command for cordova CLI, which calls 
> corresponding cordova-lib API with options, specified from CLI
> 
> 2. 'check_reqs' module for cordova-lib, which works as a wrapper 
> around platforms' check_reqs scripts. It returns a promise, either 
> resolved if check_reqs platform script is found and ran successfully 
> or rejected in case if check_reqs script is failed due to some internal 
> errors or not found at all.
> 
> 3. check_reqs script for android platform, updated to return array of 
> requirements.
> 
> * Each requirements is an object with following fields:
> - id - some short id, could be useful for tools, that consume API 
> directly
> - name - readable name for this requirement, such as 'Jav JDK' 
> or 'Gradle build tools', etc.
> - installed - Boolean paremeter that indicates if requirement 
> is properly installed/satisfied
> - reason - error, reported by requirements check routines if 
> requirement is missing.
> 
> Please note that work is still in progress, and will be changed 
> according to review comments.
> TBD:
> * move presentation logic from LIB to CLI;
> * refine data format, returned by cordova-lib API
> * add other platforms
> * and more... :)
> 
> ---
> Best regards, Vladimir
> 
> -Original Message-
> From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
> Sent: Monday, 20 April, 2015 3:49
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> Looks like implementing a global level check_reqs without a project 
> seems harder, I would suggest we make it a part of a second phase of 
> this implementation. For now, we have a basic version that simply 
> abstracts out existing check_reqs into a separate, platform level 
> command. This could be a good first phase, and should also give us an 
> idea about how developers use this command.
> 
> As a part of Phase 2, anyone from the community should be able to 
> build on a cordova level check reqs, and possibly extend it to 
> checking reqs when no project

[GitHub] cordova-plugin-camera pull request: solves CB-8804 https://github....

[agrieve]

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

https://github.com/apache/cordova-plugin-camera/pull/83#discussion_r28882307
  
--- Diff: src/android/CameraLauncher.java ---
@@ -632,73 +645,79 @@ else if (destType == FILE_URI || destType == 
NATIVE_URI) {
  */
 public void onActivityResult(int requestCode, int resultCode, Intent 
intent) {
 
-// Get src and dest types from request code for a Camera Activity
-int srcType = (requestCode / 16) - 1;
-int destType = (requestCode % 16) - 1;
-
-// If Camera Crop
-if (requestCode >= CROP_CAMERA) {
-if (resultCode == Activity.RESULT_OK) {
+if (this.imageUri == null && this.getPictureFromGallery == false) {
--- End diff --

Would it be more appropriate to check if `callbackContext == null`? An app 
can be evicted even when getting a picture from the gallery.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-plugin-camera pull request: solves CB-8804 https://github....

[agrieve]

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

https://github.com/apache/cordova-plugin-camera/pull/83#discussion_r28882407
  
--- Diff: www/Camera.js ---
@@ -72,4 +72,8 @@ cameraExport.cleanup = function(successCallback, 
errorCallback) {
 exec(successCallback, errorCallback, "Camera", "cleanup", []);
 };
 
+cameraExport.checkForSavedResult = function(successCallback, 
errorCallback) {
--- End diff --

Please update the plugin README.md with docs on this new API


---
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 5.0.0 and gradle

[Andrew Grieve]

We do pin the gradle version since that's what we've tested with. Seems
reasonable to add an option to try setting your own version though (feel
free to file an issue / hack away at it).

The two spots the version is pinned:
- within build.gradle
- within cordova/lib/build.js's prepEnv function (just search for 2.2.1)

As for proxy configuration, I've never dealt with that :(. If you can
figure out how to make it work, please file an issue & PR and we'll be glad
to merge it in.

On Wed, Apr 22, 2015 at 7:03 AM, Axel Nennker  wrote:

> Ignoring the no-network-while-building requirement for a moment and setting
> the JAVA_OPTS proxy variable correctly leads to this:
>  [exec] Downloading
> http://services.gradle.org/distributions/gradle-2.2.1-all.zip
>  [exec]
>
> ..
>  [exec] Unzipping
>
> /home/ignisvulpis/.gradle/wrapper/dists/gradle-2.2.1-all/2m8005s69iu8v0oiejfej094b/gradle-2.2.1-all.zip
> to
>
> /home/ignisvulpis/.gradle/wrapper/dists/gradle-2.2.1-all/2m8005s69iu8v0oiejfej094b
>  [exec] Set executable permissions for:
>
> /home/ignisvulpis/.gradle/wrapper/dists/gradle-2.2.1-all/2m8005s69iu8v0oiejfej094b/gradle-2.2.1/bin/gradle
>  [exec]
>  [exec] FAILURE: Build failed with an exception.
>  [exec]
>  [exec] * What went wrong:
>  [exec] A problem occurred configuring root project 'android'.
>  [exec] > Could not resolve all dependencies for configuration
> ':classpath'.
>  [exec]> Could not resolve com.android.tools.build:gradle:1.0.0+.
>  [exec]  Required by:
>  [exec]  :android:unspecified
>  [exec]   > Failed to list versions for
> com.android.tools.build:gradle.
>  [exec]  > Unable to load Maven meta-data from
>
> https://repo1.maven.org/maven2/com/android/tools/build/gradle/maven-metadata.xml
> .
>  [exec] > Could not GET '
>
> https://repo1.maven.org/maven2/com/android/tools/build/gradle/maven-metadata.xml
> '.
>  [exec]> Connection to https://repo1.maven.org refused
>  [exec]
>  [exec] * Try:
>   

Re: [ANNOUNCEMENT] Cordova Tools (CLI 5.0.0) + Plugins (renamed) have been released

[Andrew Grieve]

WOOOHOOOHOHOOO!!

On Wed, Apr 22, 2015 at 11:04 AM, Raymond Camden 
wrote:

> Ah - a shift reload fixed it. Is the caching a bit high for the page?
>
> On Wed, Apr 22, 2015 at 7:15 AM, Carlos Santana 
> wrote:
> > Hi Ray
> > Home page http://cordova.apache.org shows the last 3 blog posts with
> > corresponding "Read More" that takes you directly to post.
> >
> > 21 Apr 2015 » Tools Release: April 21, 2015
> > 
> > 21 Apr 2015 » Plugins Release and Moving plugins to npm: April 21, 2015
> > <
> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
> >
> > 15 Apr 2015 » Apache Cordova Android 4.0.0
> > <
> http://cordova.apache.org/announcements/2015/04/15/cordova-android-4.0.0.html
> >
> >
> > If you see this now, maybe it was a caching problem, and now is resolved.
> >
> >
> >
> > On Wed, Apr 22, 2015 at 12:53 AM, Shazron  wrote:
> >
> >> It should be, I see it?
> >>
> >> On Tue, Apr 21, 2015 at 8:12 PM, Raymond Camden <
> raymondcam...@gmail.com>
> >> wrote:
> >> > Query - the blog listing on the home page isn't updated. Is that a
> known
> >> issue?
> >> >
> >> > On Tue, Apr 21, 2015 at 5:46 PM, Steven Gill 
> >> wrote:
> >> >> Tools and plugins have been released.
> >> >>
> >> >> Includes fetching from npm and renamed plugins.
> >> >>
> >> >> Plugins:
> >> >>
> >>
> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
> >> >>
> >> >> Tools: http://cordova.apache.org/news/2015/04/21/tools-release.html
> >> >>
> >> >> Tweets:
> >> >> https://twitter.com/apachecordova/status/590676867046383616
> >> >> https://twitter.com/apachecordova/status/590677169745068034
> >> >> https://twitter.com/apachecordova/status/590677437454929920
> >> >
> >> >
> >> >
> >> > --
> >> >
> >>
> ===
> >> > Raymond Camden, Developer Advocate for MobileFirst at IBM
> >> >
> >> > Email : raymondcam...@gmail.com
> >> > Blog : www.raymondcamden.com
> >> > Twitter: raymondcamden
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> >> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> >> For additional commands, e-mail: dev-h...@cordova.apache.org
> >>
> >>
> >
> >
> > --
> > Carlos Santana
> > 
>
>
>
> --
> ===
> Raymond Camden, Developer Advocate for MobileFirst at IBM
>
> Email : raymondcam...@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: [ANNOUNCEMENT] Cordova Tools (CLI 5.0.0) + Plugins (renamed) have been released

[Michal Mocny]

Happy Santa?

On Wed, Apr 22, 2015 at 11:25 AM, Andrew Grieve 
wrote:

> WOOOHOOOHOHOOO!!
>
> On Wed, Apr 22, 2015 at 11:04 AM, Raymond Camden 
> wrote:
>
> > Ah - a shift reload fixed it. Is the caching a bit high for the page?
> >
> > On Wed, Apr 22, 2015 at 7:15 AM, Carlos Santana 
> > wrote:
> > > Hi Ray
> > > Home page http://cordova.apache.org shows the last 3 blog posts with
> > > corresponding "Read More" that takes you directly to post.
> > >
> > > 21 Apr 2015 » Tools Release: April 21, 2015
> > > 
> > > 21 Apr 2015 » Plugins Release and Moving plugins to npm: April 21, 2015
> > > <
> >
> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
> > >
> > > 15 Apr 2015 » Apache Cordova Android 4.0.0
> > > <
> >
> http://cordova.apache.org/announcements/2015/04/15/cordova-android-4.0.0.html
> > >
> > >
> > > If you see this now, maybe it was a caching problem, and now is
> resolved.
> > >
> > >
> > >
> > > On Wed, Apr 22, 2015 at 12:53 AM, Shazron  wrote:
> > >
> > >> It should be, I see it?
> > >>
> > >> On Tue, Apr 21, 2015 at 8:12 PM, Raymond Camden <
> > raymondcam...@gmail.com>
> > >> wrote:
> > >> > Query - the blog listing on the home page isn't updated. Is that a
> > known
> > >> issue?
> > >> >
> > >> > On Tue, Apr 21, 2015 at 5:46 PM, Steven Gill <
> stevengil...@gmail.com>
> > >> wrote:
> > >> >> Tools and plugins have been released.
> > >> >>
> > >> >> Includes fetching from npm and renamed plugins.
> > >> >>
> > >> >> Plugins:
> > >> >>
> > >>
> >
> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
> > >> >>
> > >> >> Tools:
> http://cordova.apache.org/news/2015/04/21/tools-release.html
> > >> >>
> > >> >> Tweets:
> > >> >> https://twitter.com/apachecordova/status/590676867046383616
> > >> >> https://twitter.com/apachecordova/status/590677169745068034
> > >> >> https://twitter.com/apachecordova/status/590677437454929920
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> >
> > >>
> >
> ===
> > >> > Raymond Camden, Developer Advocate for MobileFirst at IBM
> > >> >
> > >> > Email : raymondcam...@gmail.com
> > >> > Blog : www.raymondcamden.com
> > >> > Twitter: raymondcamden
> > >> >
> > >> >
> -
> > >> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >> >
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Carlos Santana
> > > 
> >
> >
> >
> > --
> >
> ===
> > Raymond Camden, Developer Advocate for MobileFirst at IBM
> >
> > Email : raymondcam...@gmail.com
> > Blog : www.raymondcamden.com
> > Twitter: raymondcamden
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

Re: Question about bypassing the run-loop wait/entire bridge for plugins on iOS

[Connor Pearson]

Hey Tim,

I recently did some work on the shrink view behavior for iOS. Most of the
changes were pulled into the official plugin and the rest is here:
https://github.com/cjpearson/cordova-plugin-keyboard

I don't know how your css animation looks, but using shrink view may have
some of the same issues. I was trying to have the webview shrink as the
keyboard appears, but the animation wasn't quite right. From what I could
tell, the web view itself could be animated, but as soon as you start the
animation, its content shrinks completely. A few people suggested solutions
on Stack Overflow, but none of them worked for me.
http://stackoverflow.com/q/27923648/754604

I ended up settling for the jumpy behavior and cutting out the native
animation code. There may be a way to make it work using autolayout
constraints instead of resizing the frame, but I believe Cordova avoids
autolayout and I'm not sure what the repercussions of introducing it would
be.

Hope this helps

Connor

On Wed, Apr 22, 2015 at 9:56 AM, Carlos Santana 
wrote:

> Hi Tim, thanks for offering help.
> There are was a recent discussion in the mailing list about keyboard plugin
> for iOS [1]
> And Shaz posted a Blog post on the maintenance of the keyboard plugin as a
> Cordova core plugin. [2]
>
> As some of the committers have express we think that the kyeboard plugin is
> better to be a 3rd party plugin.
> So I think improving the ionic keyboard plugin will be the preferred
> solution, and since it's open source the better
> Oh by the way Attention*** we moved plugins to npm [3], so grab the npm
> name space for your plugin (i.e. cordova-plugin-keyboard) before some troll
> does :-)
>
> Kerri created some examples to provide a good UX using the ionic keyboard
> plugin [4], I encourage to take a look and see how the plugin can be
> enhanced, and maybe some of the examples incorporated into the ionic ui
> framework (i.e. directive)
>
> Take care and looking forward on more discussions and contributions from
> ionic team !
>
> [1]: http://markmail.org/thread/7vcswxfkqr67amee
> [2]:
>
> https://shazronatadobe.wordpress.com/2014/07/09/cordova-keyboard-plugin-maintenance-update/
> [3]:
>
> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
> [4]: https://github.com/kerrishotts/cordova-keyboard-example
>
>
> On Tue, Apr 21, 2015 at 4:19 PM, Tim Lancina  wrote:
>
> > Awesome, thanks guys! Yeah honestly one way to solve this particular
> > problem I think is to just shrink the native view like the original
> Cordova
> > keyboard plugin.  Speaking of which, is the Cordova keyboard plugin still
> > kind of in limbo? Michal suggested to us last year that the Ionic
> keyboard
> > plugin use it as a dependency, but we were a lot smaller as a team and
> had
> > other priorities in building the framework.  Now that we're a little
> bigger
> > and would like to invest more in the ecosystem as a whole, is there still
> > any interest in having us contribute back to the official Cordova plugin?
> > Or is it maybe too little too late.
> >
> > On Mon, Apr 20, 2015 at 7:46 PM, Andrew Grieve 
> > wrote:
> >
> > > I think Jesse pretty much covered it.
> > >
> > > I would be surprised if you could get web animations to be in sync with
> > > native animations like the keyboard. If you are to try, I think you'd
> get
> > > closest by attaching a timestamp to the event you're sending to JS, and
> > use
> > > requestAnimationFrame to animate. CSS animations don't guarantee that
> > they
> > > will start right away I don't think.
> > >
> > > That said - yes, you should just experiment with whether using
> > > stringByEvaluatingJavaScriptFromString helps at all. If it doesn't help
> > > anyways though, there's no point in using it.
> > > What can go wrong?
> > > - possibility of deadlock, esp when JS callback tries to do an alert()
> > > - does not optimized calls to exec() made from within the callback
> > > - will not work out-of-the-box with WKWebView.
> > >
> > > On Mon, Apr 20, 2015 at 5:40 PM, Jesse 
> wrote:
> > >
> > > > I think you are best off to experiment and see what you can get
> working
> > > > consistently.  The focus lately has been on the wkwebview bridge,
> which
> > > is
> > > > entirely new, while the current webview implementation is a
> collection
> > of
> > > > workarounds for various issues.
> > > >
> > > > If you can distill this down to a simple project that demonstrates
> the
> > > > issue, I would be happy to have a look.
> > > >
> > > >
> > > >
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > > On Mon, Apr 20, 2015 at 3:25 PM, Tim Lancina  wrote:
> > > >
> > > > > Whoops should probably have subscribed to the mailing list!
> Apologies
> > > if
> > > > > this screws up the thread.
> > > > >
> > > > > Thanks for your response Jesse. The problem is knowing when to
> start
> > > the
> > > > > css animation, hence why it would be best to be able to fire an
> event
> > > > > indicating the keybo

Re: Cookie support in docs.

[Andrew Grieve]

Cookies work the same as they do in a browser AFAIK. cookies for file:
don't make sense because you talk to a server at file:. If you make an XHR
to http:///, they it can set cookies.

On Wed, Apr 22, 2015 at 6:12 AM, Andrey Kurdumov 
wrote:

> Hi,
>
> I come across the following SO question.
>
> http://stackoverflow.com/questions/24374397/cookie-support-in-cordova-official-documentation
>
> The guy could not find any mentions about cookie support in the Phonegap. I
> do google search and find that the only mention about cookie support is
> issue CB-8026 where stated that Android support third-party cookies. I
> personally was having problems with that, but resolve it using custom HTTP
> header.
>
> Question is: Does it make sense add the section in the docs regarding
> cookies, and their limitations in Cordova apps, due to fact that files
> server over file:/// protocol?
>

RE: Proposal: Expose check_reqs at the CLI level

[Josh Soref]

We're going to type it often enough that I'd be upset at both check_reqs and 
check-requirements

"requirements" is good enough.

> -Original Message-
> From: Treggiari, Leo [mailto:leo.treggi...@intel.com]
> Sent: Wednesday, April 22, 2015 11:11 AM
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> Hi Vladimir,
> 
> It's great to see this being worked on and discussed.  My comments below
> are mine and mine alone.
> 
> In addition to the code changes, I would have preferred to see a specification
> of the command, e.g.
> 
>   cordova check-reqs platform [platform...]
> 
> I took a quick look at the CLI code changes and didn't see any option
> processing.  Are there any options?
> Do the platform(s) specified on the command need to have been already
> added to the project?
> Does the command require a project - i.e. be executed in a project directory?
> Regarding the command name, I don't think being 'cute' is helpful to users -
> i.e. I recommend against 'doctor'.
> I think 'check-requirements' would be OK.  It's long but how many times does
> a user need to type it?
> 
> Thanks,
> Leo
> 
> -Original Message-
> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> Sent: Wednesday, April 22, 2015 7:18 AM
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> Hey, guys. Have anyone looked at it?
> I've made some refactoring to make changes more readable, and updated
> data contract between platform's check_reqs code and LIB API.
> 
> Josh, regarding command name. I thought that there is still no agreement
> about verb name.
> Personally I agree that `cordova doctor` or `cordova requirements` sounds
> better, but this is just a command name ant it could be changed at any time.
> 
> ---
> Best regards, Vladimir
> 
> -Original Message-
> From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
> Sent: Monday, 20 April, 2015 22:04
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> This was only an initial implementation - no pull request has been sent. I
> think this is just a way for folks to play with what Vlad has now. I am sure 
> we
> will change the verb name before a PR comes in.
> 
> -Original Message-
> From: Josh Soref [mailto:jso...@blackberry.com]
> Sent: Monday, April 20, 2015 11:59 AM
> To: dev@cordova.apache.org
> Subject: RE: Proposal: Expose check_reqs at the CLI level
> 
> -1
> 
> Didn't everyone agree to call it `cordova doctor` or worst, `cordova
> requirements`?
> 
> > -Original Message-
> > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> > Sent: Monday, April 20, 2015 11:46 AM
> > To: dev@cordova.apache.org
> > Subject: RE: Proposal: Expose check_reqs at the CLI level
> >
> > Hi, list.
> >
> > I would like to share a draft implementation for check_reqs command
> > and check_reqs API:
> > Changes  could be found here:
> > CLI: https://github.com/apache/cordova-
> > cli/compare/master...MSOpenTech:requirements_check
> > LIB: https://github.com/apache/cordova-
> > lib/compare/master...MSOpenTech:requirements_check
> > Cordova-android: https://github.com/apache/cordova-
> > android/compare/master...MSOpenTech:requirements_check
> >
> > The implementation consists of following:
> > 1. 'cordova check-reqs' command for cordova CLI, which calls
> > corresponding cordova-lib API with options, specified from CLI
> >
> > 2. 'check_reqs' module for cordova-lib, which works as a wrapper
> > around platforms' check_reqs scripts. It returns a promise, either
> > resolved if check_reqs platform script is found and ran successfully
> > or rejected in case if check_reqs script is failed due to some internal 
> > errors
> or not found at all.
> >
> > 3. check_reqs script for android platform, updated to return array of
> > requirements.
> >
> > * Each requirements is an object with following fields:
> > - id - some short id, could be useful for tools, that consume API 
> > directly
> > - name - readable name for this requirement, such as 'Jav JDK'
> > or 'Gradle build tools', etc.
> > - installed - Boolean paremeter that indicates if requirement
> > is properly installed/satisfied
> > - reason - error, reported by requirements check routines if
> > requirement is missing.
> >
> > Please note that work is still in progress, and will be changed
> > according to review comments.
> > TBD:
> > * move presentation logic from LIB to CLI;
> > * refine data format, returned by cordova-lib API
> > * add other platforms
> > * and more... :)
> >
> > ---
> > Best regards, Vladimir
> >
> > -Original Message-
> > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
> > Sent: Monday, 20 April, 2015 3:49
> > To: dev@cordova.apache.org
> > Subject: RE: Proposal: Expose check_reqs at the CLI level
> >
> > Looks li

RE: Cookie support in docs.

[Josh Soref]

Andrey:
It makes sense for someone to write a simple document saying that cookies are 
supported for subresources requested from remote web servers, but that Cordova 
doesn't promise cookie support for the app itself, and it should suggest using 
localStorage or the file API for preferences.

Thanks for volunteering to work on this :)

> -Original Message-
> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
> Andrew Grieve
> Sent: Wednesday, April 22, 2015 11:18 AM
> To: dev
> Subject: Re: Cookie support in docs.
>
> Cookies work the same as they do in a browser AFAIK. cookies for file:
> don't make sense because you talk to a server at file:. If you make an XHR
> to http:///, they it can set cookies.
>
> On Wed, Apr 22, 2015 at 6:12 AM, Andrey Kurdumov
> 
> wrote:
>
> > Hi,
> >
> > I come across the following SO question.
> >
> > http://stackoverflow.com/questions/24374397/cookie-support-in-
> cordova-official-documentation
> >
> > The guy could not find any mentions about cookie support in the
> Phonegap. I
> > do google search and find that the only mention about cookie support is
> > issue CB-8026 where stated that Android support third-party cookies. I
> > personally was having problems with that, but resolve it using custom HTTP
> > header.
> >
> > Question is: Does it make sense add the section in the docs regarding
> > cookies, and their limitations in Cordova apps, due to fact that files
> > server over file:/// protocol?
> >


smime.p7s
Description: S/MIME cryptographic signature

Re: Question about bypassing the run-loop wait/entire bridge for plugins on iOS

[Tim Lancina]

Carlos - Thanks for bringing me up to speed and for the heads up on the npm
change.  That is an awesome guide by Kerri.

Connor - Thanks for the info! Honestly our frustrations with the native
resize were the main reason we decided on a different approach with the
Ionic plugin.  That being said, if it works in some situations maybe it's
worthwhile adding in, so I'll take a look at your repo and see if I can get
it working.

Cheers,
Tim

On Wed, Apr 22, 2015 at 10:44 AM Connor Pearson  wrote:

> Hey Tim,
>
> I recently did some work on the shrink view behavior for iOS. Most of the
> changes were pulled into the official plugin and the rest is here:
> https://github.com/cjpearson/cordova-plugin-keyboard
>
> I don't know how your css animation looks, but using shrink view may have
> some of the same issues. I was trying to have the webview shrink as the
> keyboard appears, but the animation wasn't quite right. From what I could
> tell, the web view itself could be animated, but as soon as you start the
> animation, its content shrinks completely. A few people suggested solutions
> on Stack Overflow, but none of them worked for me.
> http://stackoverflow.com/q/27923648/754604
>
> I ended up settling for the jumpy behavior and cutting out the native
> animation code. There may be a way to make it work using autolayout
> constraints instead of resizing the frame, but I believe Cordova avoids
> autolayout and I'm not sure what the repercussions of introducing it would
> be.
>
> Hope this helps
>
> Connor
>
> On Wed, Apr 22, 2015 at 9:56 AM, Carlos Santana 
> wrote:
>
> > Hi Tim, thanks for offering help.
> > There are was a recent discussion in the mailing list about keyboard
> plugin
> > for iOS [1]
> > And Shaz posted a Blog post on the maintenance of the keyboard plugin as
> a
> > Cordova core plugin. [2]
> >
> > As some of the committers have express we think that the kyeboard plugin
> is
> > better to be a 3rd party plugin.
> > So I think improving the ionic keyboard plugin will be the preferred
> > solution, and since it's open source the better
> > Oh by the way Attention*** we moved plugins to npm [3], so grab the
> npm
> > name space for your plugin (i.e. cordova-plugin-keyboard) before some
> troll
> > does :-)
> >
> > Kerri created some examples to provide a good UX using the ionic keyboard
> > plugin [4], I encourage to take a look and see how the plugin can be
> > enhanced, and maybe some of the examples incorporated into the ionic ui
> > framework (i.e. directive)
> >
> > Take care and looking forward on more discussions and contributions from
> > ionic team !
> >
> > [1]: http://markmail.org/thread/7vcswxfkqr67amee
> > [2]:
> >
> >
> https://shazronatadobe.wordpress.com/2014/07/09/cordova-keyboard-plugin-maintenance-update/
> > [3]:
> >
> >
> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
> > [4]: https://github.com/kerrishotts/cordova-keyboard-example
> >
> >
> > On Tue, Apr 21, 2015 at 4:19 PM, Tim Lancina  wrote:
> >
> > > Awesome, thanks guys! Yeah honestly one way to solve this particular
> > > problem I think is to just shrink the native view like the original
> > Cordova
> > > keyboard plugin.  Speaking of which, is the Cordova keyboard plugin
> still
> > > kind of in limbo? Michal suggested to us last year that the Ionic
> > keyboard
> > > plugin use it as a dependency, but we were a lot smaller as a team and
> > had
> > > other priorities in building the framework.  Now that we're a little
> > bigger
> > > and would like to invest more in the ecosystem as a whole, is there
> still
> > > any interest in having us contribute back to the official Cordova
> plugin?
> > > Or is it maybe too little too late.
> > >
> > > On Mon, Apr 20, 2015 at 7:46 PM, Andrew Grieve 
> > > wrote:
> > >
> > > > I think Jesse pretty much covered it.
> > > >
> > > > I would be surprised if you could get web animations to be in sync
> with
> > > > native animations like the keyboard. If you are to try, I think you'd
> > get
> > > > closest by attaching a timestamp to the event you're sending to JS,
> and
> > > use
> > > > requestAnimationFrame to animate. CSS animations don't guarantee that
> > > they
> > > > will start right away I don't think.
> > > >
> > > > That said - yes, you should just experiment with whether using
> > > > stringByEvaluatingJavaScriptFromString helps at all. If it doesn't
> help
> > > > anyways though, there's no point in using it.
> > > > What can go wrong?
> > > > - possibility of deadlock, esp when JS callback tries to do an
> alert()
> > > > - does not optimized calls to exec() made from within the callback
> > > > - will not work out-of-the-box with WKWebView.
> > > >
> > > > On Mon, Apr 20, 2015 at 5:40 PM, Jesse 
> > wrote:
> > > >
> > > > > I think you are best off to experiment and see what you can get
> > working
> > > > > consistently.  The focus lately has been on the wkwebview bridge,
> > which
> > > > is
> > > > > entirely new, while

Re: Cookie support in docs.

[Raymond Camden]

So we don't have a FAQ yet. Is it time to start it? Here is my stab:

Do cookies work in Cordova apps?

There are two ways in which you may want to use cookies. The first is
within XHR (Ajax) requests to remote resources. Unless you
specifically remove them, your Ajax library will automatically use
cookies in subsequent calls to remote APIs and resources you request.
So given that some API returns a cookie required for future calls, you
can assume it will be automatically sent when your app hits it again.

The other way your app may desire to use cookies is locally - ie
within the app itself. This does not make sense within a Cordova app
as it isn't running on a proper web server itself. If your intent is
simply to store data for the app then you should make use the various
existing methods (link to
http://cordova.apache.org/docs/en/4.0.0/cordova_storage_storage.md.html#Storage)
to store data locally.

On Wed, Apr 22, 2015 at 9:44 AM, Josh Soref  wrote:
> Andrey:
> It makes sense for someone to write a simple document saying that cookies are
> supported for subresources requested from remote web servers, but that Cordova
> doesn't promise cookie support for the app itself, and it should suggest using
> localStorage or the file API for preferences.
>
> Thanks for volunteering to work on this :)
>
>> -Original Message-
>> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
>> Andrew Grieve
>> Sent: Wednesday, April 22, 2015 11:18 AM
>> To: dev
>> Subject: Re: Cookie support in docs.
>>
>> Cookies work the same as they do in a browser AFAIK. cookies for file:
>> don't make sense because you talk to a server at file:. If you make an XHR
>> to http:///, they it can set cookies.
>>
>> On Wed, Apr 22, 2015 at 6:12 AM, Andrey Kurdumov
>> 
>> wrote:
>>
>> > Hi,
>> >
>> > I come across the following SO question.
>> >
>> > http://stackoverflow.com/questions/24374397/cookie-support-in-
>> cordova-official-documentation
>> >
>> > The guy could not find any mentions about cookie support in the
>> Phonegap. I
>> > do google search and find that the only mention about cookie support is
>> > issue CB-8026 where stated that Android support third-party cookies. I
>> > personally was having problems with that, but resolve it using custom HTTP
>> > header.
>> >
>> > Question is: Does it make sense add the section in the docs regarding
>> > cookies, and their limitations in Cordova apps, due to fact that files
>> > server over file:/// protocol?
>> >



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

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

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

[GitHub] cordova-ios pull request: CB-8485 Support for creating signed arch...

[nikhilkh]

Github user nikhilkh commented on the pull request:

https://github.com/apache/cordova-ios/pull/138#issuecomment-95274316
  
@shazron @agrieve Wonder if you can take a look?


---
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: Build signed archives using CLI

[Shazron]

I have rectified it in cordova-ios 4.0.x already, it picks up the
.xcconfig files.

On Wed, Apr 22, 2015 at 8:07 AM, Andrew Grieve  wrote:
> PR LGTM, but I have one question (maybe mostly for Shaz):
>
> Seems our build script pass -xcconfig "build-release.xcconfig", but our
> project template doesn't use any .xcconfig:
> http://pasteboard.co/2L2wg6r2.png
>
> Would it be better to:
> - use a different build-extras.xcconfig for debug / release (e.g.
> build-extras-release.xcconfig)
> - Set the xcconfigs in the project template so that they are used when
> building from Xcode?
>
>
> On Tue, Apr 21, 2015 at 4:47 PM, Nikhil Khandelwal 
> wrote:
>>
>> Support for iOS is in this PR now:
>> https://github.com/apache/cordova-ios/pull/138
>>
>> It allows you to specify a signing identity and a provisioning profile
>> using command line arguments or build.json.
>>
>> Thanks,
>> Nikhil
>>
>>
>> -Original Message-
>> From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
>> Sent: Monday, April 6, 2015 9:37 AM
>> To: dev@cordova.apache.org
>> Subject: RE: Build signed archives using CLI
>>
>> Thanks, Andrew for doing a thorough review. This was merged in last week.
>> I have created a new PR for the docs update:
>> https://github.com/apache/cordova-docs/pull/277
>>
>> It's important to note, to make it simple to pass multiple signing
>> parameters, I have created the concept of a build.json file (instead of
>> cordova-keys.json suggested below) that can be used to specify build-time
>> parameters. It supports specifying two sets of values - debug & release.
>>
>> This support is currently only for Android, I am working on another PR for
>> iOS.
>>
>> Thanks,
>> Nikhil
>>
>>
>> -Original Message-
>> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
>> Grieve
>> Sent: Wednesday, March 18, 2015 4:48 PM
>> To: dev
>> Subject: Re: Build signed archives using CLI
>>
>> Left some comments on the PR.
>>
>> On Tue, Mar 17, 2015 at 5:04 PM, Nikhil Khandelwal
>> 
>> wrote:
>>
>> > I just submitted a PR for this for Android:
>> > https://github.com/apache/cordova-android/pull/164
>> >
>> > Here's the rough design:
>> >
>> > - Build.json or command line args can be used to specify details
>> > required for packaging:
>> > - Keystore
>> > - Alias
>> > - Keystore password
>> > - Password
>> > - Keystore type.
>> > - Debug-signing.properties or release-signing.properties is created at
>> > prepare time to allow gradle or Ant build systems to pick up those
>> > properties and generate a signed archive.
>> > - ‘Clean’ will delete these autogenerated .properties files.
>> > - If no password is specified for release signing, Ant & gradle will
>> > prompt for passwords.
>> >
>> > I will shortly have a PR to update the docs.
>> >
>> > Thanks,
>> > Nikhil
>> >
>> >
>> > -Original Message-
>> > From: Carlos Santana [mailto:csantan...@gmail.com]
>> > Sent: Friday, February 13, 2015 2:28 PM
>> > To: dev@cordova.apache.org
>> > Subject: Re: Build signed archives using CLI
>> >
>> > Thanks Nikhil I see this as a very good and important feature to have
>> > in our CLI stack
>> >
>> > On Fri, Feb 13, 2015 at 4:48 PM, Nikhil Khandelwal
>> > > > >
>> > wrote:
>> >
>> > > I'm taking this over from Dan. I like the idea of having the release
>> > > signing information persisted in a json file.
>> > >
>> > > I have made some updates on the specific issue of how keys/passwords
>> > > can be passed through CLI and JSON:
>> > >
>> > > https://docs.google.com/document/d/1tJQ9OoGrrMhZcLI3mg46rGzAfbiQu9Pu
>> > > NB
>> > > L1auAMGFM/edit#
>> > >
>> > > I'm still going through the details of packaging requirements of
>> > > each platform. I expect to add some more details on how the
>> > > packaging process will work with individual platform build systems
>> > > in the coming days. I will update this thread when I do so.
>> > >
>> > > Here's the main JIRA with platform specific tasks here:
>> > > https://issues.apache.org/jira/browse/CB-8483. I would love to
>> > > collaborate with others who are interested in this area.
>> > > Specifically, I plan to take up the task of implementing this for
>> > > Android first.
>> > >
>> > > Thanks,
>> > > Nikhil
>> > >
>> > >
>> > > -Original Message-
>> > > From: Victor Sosa [mailto:sosah.vic...@gmail.com]
>> > > Sent: Tuesday, February 10, 2015 2:29 PM
>> > > To: dev@cordova.apache.org
>> > > Subject: Re: Build signed archives using CLI
>> > >
>> > > I'm leaning to Andrew and Omar's idea. I like the idea of having a
>> > > file where all the platform-specific information will be stored,
>> > > then each platform will take that information to sign the archive
>> > > and produce a usable, I mean ready-to-distribute, binary.
>> > >
>> > > As for Omar's comment, I also concur there. If a user has the
>> > > signing info in gradle or ant properties and that info is also
>> > > provided in the new file discussed here, then it should ta

Re: Proposal: Expose check_reqs at the CLI level

[Jesse]

I liked 'doctor', I don't think it is cute, it is in use elsewhere.
The words always seem to be the hard part, here are some alternatives :

doctor
requirements
examine
exam
diagnose
check
audit
inspect
eval



@purplecabbage
risingj.com

On Wed, Apr 22, 2015 at 9:43 AM, Josh Soref  wrote:

> We're going to type it often enough that I'd be upset at both check_reqs
> and check-requirements
>
> "requirements" is good enough.
>
> > -Original Message-
> > From: Treggiari, Leo [mailto:leo.treggi...@intel.com]
> > Sent: Wednesday, April 22, 2015 11:11 AM
> > To: dev@cordova.apache.org
> > Subject: RE: Proposal: Expose check_reqs at the CLI level
> >
> > Hi Vladimir,
> >
> > It's great to see this being worked on and discussed.  My comments below
> > are mine and mine alone.
> >
> > In addition to the code changes, I would have preferred to see a
> specification
> > of the command, e.g.
> >
> >   cordova check-reqs platform [platform...]
> >
> > I took a quick look at the CLI code changes and didn't see any option
> > processing.  Are there any options?
> > Do the platform(s) specified on the command need to have been already
> > added to the project?
> > Does the command require a project - i.e. be executed in a project
> directory?
> > Regarding the command name, I don't think being 'cute' is helpful to
> users -
> > i.e. I recommend against 'doctor'.
> > I think 'check-requirements' would be OK.  It's long but how many times
> does
> > a user need to type it?
> >
> > Thanks,
> > Leo
> >
> > -Original Message-
> > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> > Sent: Wednesday, April 22, 2015 7:18 AM
> > To: dev@cordova.apache.org
> > Subject: RE: Proposal: Expose check_reqs at the CLI level
> >
> > Hey, guys. Have anyone looked at it?
> > I've made some refactoring to make changes more readable, and updated
> > data contract between platform's check_reqs code and LIB API.
> >
> > Josh, regarding command name. I thought that there is still no agreement
> > about verb name.
> > Personally I agree that `cordova doctor` or `cordova requirements` sounds
> > better, but this is just a command name ant it could be changed at any
> time.
> >
> > ---
> > Best regards, Vladimir
> >
> > -Original Message-
> > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
> > Sent: Monday, 20 April, 2015 22:04
> > To: dev@cordova.apache.org
> > Subject: RE: Proposal: Expose check_reqs at the CLI level
> >
> > This was only an initial implementation - no pull request has been sent.
> I
> > think this is just a way for folks to play with what Vlad has now. I am
> sure we
> > will change the verb name before a PR comes in.
> >
> > -Original Message-
> > From: Josh Soref [mailto:jso...@blackberry.com]
> > Sent: Monday, April 20, 2015 11:59 AM
> > To: dev@cordova.apache.org
> > Subject: RE: Proposal: Expose check_reqs at the CLI level
> >
> > -1
> >
> > Didn't everyone agree to call it `cordova doctor` or worst, `cordova
> > requirements`?
> >
> > > -Original Message-
> > > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> > > Sent: Monday, April 20, 2015 11:46 AM
> > > To: dev@cordova.apache.org
> > > Subject: RE: Proposal: Expose check_reqs at the CLI level
> > >
> > > Hi, list.
> > >
> > > I would like to share a draft implementation for check_reqs command
> > > and check_reqs API:
> > > Changes  could be found here:
> > > CLI: https://github.com/apache/cordova-
> > > cli/compare/master...MSOpenTech:requirements_check
> > > LIB: https://github.com/apache/cordova-
> > > lib/compare/master...MSOpenTech:requirements_check
> > > Cordova-android: https://github.com/apache/cordova-
> > > android/compare/master...MSOpenTech:requirements_check
> > >
> > > The implementation consists of following:
> > > 1. 'cordova check-reqs' command for cordova CLI, which calls
> > > corresponding cordova-lib API with options, specified from CLI
> > >
> > > 2. 'check_reqs' module for cordova-lib, which works as a wrapper
> > > around platforms' check_reqs scripts. It returns a promise, either
> > > resolved if check_reqs platform script is found and ran successfully
> > > or rejected in case if check_reqs script is failed due to some
> internal errors
> > or not found at all.
> > >
> > > 3. check_reqs script for android platform, updated to return array of
> > > requirements.
> > >
> > > * Each requirements is an object with following fields:
> > > - id - some short id, could be useful for tools, that consume
> API directly
> > > - name - readable name for this requirement, such as 'Jav JDK'
> > > or 'Gradle build tools', etc.
> > > - installed - Boolean paremeter that indicates if requirement
> > > is properly installed/satisfied
> > > - reason - error, reported by requirements check routines if
> > > requirement is missing.
> > >
> > > Please note that work is still in progress, and will be changed
> > 

[GitHub] cordova-plugin-file-transfer pull request: CB-8761 [wp8]: Copy coo...

[nikhilkh]

Github user nikhilkh commented on the pull request:


https://github.com/apache/cordova-plugin-file-transfer/pull/74#issuecomment-95279535
  
@vladimir-kotikov Can you please take a look?


---
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-ios pull request: CB-8485 Support for creating signed arch...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-ios/pull/138#issuecomment-95280457
  
Looks sound to me. I'll give it a spin later today before I pull it in.


---
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: Cookie support in docs.

[Josh Soref]

Raymond wrote:
> So we don't have a FAQ yet.
> Is it time to start it?

It's long overdue.

> Here is my stab:
>
> Do cookies work in Cordova apps?
>
> There are two ways in which you may want to use cookies. The first is
> within XHR (Ajax) requests to remote resources.
> Unless you
> specifically remove them, your Ajax library will automatically use
> cookies in subsequent calls to remote APIs and resources you request.

Some handwaiving necessary to indicate that a cookie set for one domain won't 
be given to an unrelated domain -- yada yada.

> So given that some API returns a cookie required for future calls, you
> can assume it will be automatically sent when your app hits it again.

This overlooks normal cookies that you grow via the server setting them, or 
via a sub-resource using document.cookie.

> The other way your app may desire to use cookies is locally - ie
> within the app itself. This does not make sense within a Cordova app
> as it isn't running on a proper web server itself. If your intent is
> simply to store data for the app then you should make use the various
> existing methods (link to
> http://cordova.apache.org/docs/en/4.0.0/cordova_storage_storage.md.htm
> l#Storage)
> to store data locally.

Pretty good.

Note that /some/ platforms may have cookie support by accident if they in fact 
are hosted (or temporarily hosted) on a web server. I'm not sure if we want to 
say "you should not expect your app to be able to persist cookies for its own 
use, because generally speaking Cordova applications aren't backed by a web 
server and thus have no place to store cookies" or something like that.


smime.p7s
Description: S/MIME cryptographic signature

[GitHub] cordova-docs pull request: CB-8820 - Ensure platform guides are ac...

[stevengill]

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

https://github.com/apache/cordova-docs/pull/279#discussion_r28898337
  
--- Diff: docs/en/edge/guide/platforms/android/index.md ---
@@ -29,11 +29,12 @@ Overview.  For details on the CLI, see The Command-Line 
Interface.
 
 ## Requirements and Support
 
-Cordova for Android requires the Android SDK. See the Android SDK's
-[System Requirements](http://developer.android.com/sdk/index.html).
+Cordova for Android requires the Android SDK which could be installed
+on OS X, Linux or Windows operation system. See the Android SDK's
+[System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
 
 Cordova supports Android 2.3.x (Gingerbread, starting with Android API 
level 10)
--- End diff --

I saw on the list that cordova-android 4.0.0 dropped support for gingerbread


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-plugin-file-transfer pull request: Correct installation ur...

[rjatkinson2]

GitHub user rjatkinson2 opened a pull request:

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

Correct installation url to accurate location


![image](https://cloud.githubusercontent.com/assets/3825178/7282052/40c19674-e8e2-11e4-907b-0e570a03b9c1.png)

Original Configuration:


![image](https://cloud.githubusercontent.com/assets/3825178/7282070/52876302-e8e2-11e4-99d7-b678658608a8.png)

New Configuration:


![image](https://cloud.githubusercontent.com/assets/3825178/7282080/680425e4-e8e2-11e4-8e92-c26bf564285c.png)


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

$ git pull https://github.com/rjatkinson2/cordova-plugin-file-transfer 
patch-2

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

https://github.com/apache/cordova-plugin-file-transfer/pull/80.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 #80


commit f9343bb15281ee132a5ce883ad1ade2fbd7b6094
Author: Ryan Atkinson 
Date:   2015-04-22T18:25:12Z

Correct installation url to accurate location




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-docs pull request: CB-8820 - Ensure platform guides are ac...

[sgrebnov]

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

https://github.com/apache/cordova-docs/pull/279#discussion_r28904464
  
--- Diff: docs/en/edge/guide/platforms/android/index.md ---
@@ -29,11 +29,12 @@ Overview.  For details on the CLI, see The Command-Line 
Interface.
 
 ## Requirements and Support
 
-Cordova for Android requires the Android SDK. See the Android SDK's
-[System Requirements](http://developer.android.com/sdk/index.html).
+Cordova for Android requires the Android SDK which could be installed
+on OS X, Linux or Windows operation system. See the Android SDK's
+[System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
 
 Cordova supports Android 2.3.x (Gingerbread, starting with Android API 
level 10)
--- End diff --

Thx Steve, will double check, but I still see minSdkVersion is 10 in 
platform template
 < uses-sdk android:minSdkVersion="10" />


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-docs pull request: CB-8820 - Ensure platform guides are ac...

[stevengill]

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

https://github.com/apache/cordova-docs/pull/279#discussion_r28904679
  
--- Diff: docs/en/edge/guide/platforms/android/index.md ---
@@ -29,11 +29,12 @@ Overview.  For details on the CLI, see The Command-Line 
Interface.
 
 ## Requirements and Support
 
-Cordova for Android requires the Android SDK. See the Android SDK's
-[System Requirements](http://developer.android.com/sdk/index.html).
+Cordova for Android requires the Android SDK which could be installed
+on OS X, Linux or Windows operation system. See the Android SDK's
+[System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
 
 Cordova supports Android 2.3.x (Gingerbread, starting with Android API 
level 10)
--- End diff --

I decided to just merge it in. I can fix it on master myself. Can you
comment on the mailing list thread "Deprecation Wars. ICS vs Gingerbread"

On Wed, Apr 22, 2015 at 12:07 PM, Sergey Grebnov 
wrote:

> In docs/en/edge/guide/platforms/android/index.md
> :
>
> > @@ -29,11 +29,12 @@ Overview.  For details on the CLI, see The 
Command-Line Interface.
> >
> >  ## Requirements and Support
> >
> > -Cordova for Android requires the Android SDK. See the Android SDK's
> > -[System Requirements](http://developer.android.com/sdk/index.html).
> > +Cordova for Android requires the Android SDK which could be installed
> > +on OS X, Linux or Windows operation system. See the Android SDK's
> > +[System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
> >
> >  Cordova supports Android 2.3.x (Gingerbread, starting with Android API 
level 10)
>
> Thx Steve, will double check, but I still see minSdkVersion is 10 in
> platform template
> < uses-sdk android:minSdkVersion="10" />
>
> --
> Reply to this email directly or view it on GitHub
> .
>



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-docs pull request: Document iOS specific callback for orie...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-docs/pull/276


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-docs pull request: CB-8820 - Ensure platform guides are ac...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-docs/pull/279


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-docs pull request: typo fix tools.md

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-docs/pull/278


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] cordova-docs pull request: Fix plugin example to ubuntu platform

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-docs/pull/275


---
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: Deprecation Wars: ICS vs Gingerbread

[Sergey Grebnov (Akvelon)]

I still see minSdkVersion = 10 (GINGERBREAD) in platform template. Should it be 
replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also updated in platform 
docs? -  per docs we still support Gingerbread.

Steve is currently working on docs update so this is perfect time to change 
this.

-Sergey
-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, April 21, 2015 1:04 PM
To: dev@cordova.apache.org
Subject: Re: Deprecation Wars: ICS vs Gingerbread

Joe, perhaps that can be part of the Tools Release blog post? Steve put out a 
link to the draft in another thread.

On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser  wrote:
> Resurrecting this thread!
>
> I think we need to let our users know that Cordova 4.0 doesn't support 
> Gingerbread, or at least some of the features don't work on Gingerbread.
> I've been trying to clean up the JIRA a bit today, and it seems that 
> while we came to a consensus to drop 2.3, we didn't tell anyone. :/
>
>
> On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser  wrote:
>
>> Firefox works on 2.3, and Chrome does not. It also depends on the 
>> device
>>
>> On Tue, Jan 13, 2015, 12:20 PM Josh Soref  wrote:
>>
>>> Michal Mocny wrote:
>>> >... we aren't telling those individuals that they cannot use their 
>>> >phones, we are telling developers that want to create new 
>>> >applications for that target to either build mobile web, packaged 
>>> >native, or just stick to existing versions of cordova if really needed.
>>> >
>>> >I do not buy the argument that you are doing those individuals with 
>>> >those phones a favour by building them hybrid apps using the 
>>> >antiquated 2.3 webview on antiquated machine specs.
>>>
>>> I don't have an opinion on this. But I do have a question.
>>>
>>> Ignoring the fact that GeckoView is flaky today,
>>>
>>> 1. Does GeckoView / Firefox work (at all? well?) on a sample / 
>>> typical 2.3 device?
>>> 2. Can I run Chrome (or some relative) on that same device (at all? 
>>> well?)
>>>
>>

-
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: Cookie support in docs.

[Raymond Camden]

Do we need to say the domain/cookie thing when that is standard cookie
behavior? I think most folks know a cookie set by A.com won't be
usable via B.com. (Then again, repeating such things wouldn't hurt.)

On Wed, Apr 22, 2015 at 10:47 AM, Josh Soref  wrote:
> Raymond wrote:
>> So we don't have a FAQ yet.
>> Is it time to start it?
>
> It's long overdue.
>
>> Here is my stab:
>>
>> Do cookies work in Cordova apps?
>>
>> There are two ways in which you may want to use cookies. The first is
>> within XHR (Ajax) requests to remote resources.
>> Unless you
>> specifically remove them, your Ajax library will automatically use
>> cookies in subsequent calls to remote APIs and resources you request.
>
> Some handwaiving necessary to indicate that a cookie set for one domain won't
> be given to an unrelated domain -- yada yada.
>
>> So given that some API returns a cookie required for future calls, you
>> can assume it will be automatically sent when your app hits it again.
>
> This overlooks normal cookies that you grow via the server setting them, or
> via a sub-resource using document.cookie.
>
>> The other way your app may desire to use cookies is locally - ie
>> within the app itself. This does not make sense within a Cordova app
>> as it isn't running on a proper web server itself. If your intent is
>> simply to store data for the app then you should make use the various
>> existing methods (link to
>> http://cordova.apache.org/docs/en/4.0.0/cordova_storage_storage.md.htm
>> l#Storage)
>> to store data locally.
>
> Pretty good.
>
> Note that /some/ platforms may have cookie support by accident if they in fact
> are hosted (or temporarily hosted) on a web server. I'm not sure if we want to
> say "you should not expect your app to be able to persist cookies for its own
> use, because generally speaking Cordova applications aren't backed by a web
> server and thus have no place to store cookies" or something like that.



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

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

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

Re: Cookie support in docs.

[Shazron]

Created https://github.com/cordova/cordova-discuss/blob/master/FAQ.md
as a doc so we can stage edits.
If anyone needs direct access let me know.


On Wed, Apr 22, 2015 at 10:21 AM, Raymond Camden
 wrote:
> So we don't have a FAQ yet. Is it time to start it? Here is my stab:
>
> Do cookies work in Cordova apps?
>
> There are two ways in which you may want to use cookies. The first is
> within XHR (Ajax) requests to remote resources. Unless you
> specifically remove them, your Ajax library will automatically use
> cookies in subsequent calls to remote APIs and resources you request.
> So given that some API returns a cookie required for future calls, you
> can assume it will be automatically sent when your app hits it again.
>
> The other way your app may desire to use cookies is locally - ie
> within the app itself. This does not make sense within a Cordova app
> as it isn't running on a proper web server itself. If your intent is
> simply to store data for the app then you should make use the various
> existing methods (link to
> http://cordova.apache.org/docs/en/4.0.0/cordova_storage_storage.md.html#Storage)
> to store data locally.
>
> On Wed, Apr 22, 2015 at 9:44 AM, Josh Soref  wrote:
>> Andrey:
>> It makes sense for someone to write a simple document saying that cookies are
>> supported for subresources requested from remote web servers, but that 
>> Cordova
>> doesn't promise cookie support for the app itself, and it should suggest 
>> using
>> localStorage or the file API for preferences.
>>
>> Thanks for volunteering to work on this :)
>>
>>> -Original Message-
>>> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
>>> Andrew Grieve
>>> Sent: Wednesday, April 22, 2015 11:18 AM
>>> To: dev
>>> Subject: Re: Cookie support in docs.
>>>
>>> Cookies work the same as they do in a browser AFAIK. cookies for file:
>>> don't make sense because you talk to a server at file:. If you make an XHR
>>> to http:///, they it can set cookies.
>>>
>>> On Wed, Apr 22, 2015 at 6:12 AM, Andrey Kurdumov
>>> 
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > I come across the following SO question.
>>> >
>>> > http://stackoverflow.com/questions/24374397/cookie-support-in-
>>> cordova-official-documentation
>>> >
>>> > The guy could not find any mentions about cookie support in the
>>> Phonegap. I
>>> > do google search and find that the only mention about cookie support is
>>> > issue CB-8026 where stated that Android support third-party cookies. I
>>> > personally was having problems with that, but resolve it using custom HTTP
>>> > header.
>>> >
>>> > Question is: Does it make sense add the section in the docs regarding
>>> > cookies, and their limitations in Cordova apps, due to fact that files
>>> > server over file:/// protocol?
>>> >
>
>
>
> --
> ===
> Raymond Camden, Developer Advocate for MobileFirst at IBM
>
> Email : raymondcam...@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

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

Re: Cookie support in docs.

[Raymond Camden]

Sweet. Thanks Shazon!

On Wed, Apr 22, 2015 at 1:58 PM, Shazron  wrote:
> Created https://github.com/cordova/cordova-discuss/blob/master/FAQ.md
> as a doc so we can stage edits.
> If anyone needs direct access let me know.
>
>
> On Wed, Apr 22, 2015 at 10:21 AM, Raymond Camden
>  wrote:
>> So we don't have a FAQ yet. Is it time to start it? Here is my stab:
>>
>> Do cookies work in Cordova apps?
>>
>> There are two ways in which you may want to use cookies. The first is
>> within XHR (Ajax) requests to remote resources. Unless you
>> specifically remove them, your Ajax library will automatically use
>> cookies in subsequent calls to remote APIs and resources you request.
>> So given that some API returns a cookie required for future calls, you
>> can assume it will be automatically sent when your app hits it again.
>>
>> The other way your app may desire to use cookies is locally - ie
>> within the app itself. This does not make sense within a Cordova app
>> as it isn't running on a proper web server itself. If your intent is
>> simply to store data for the app then you should make use the various
>> existing methods (link to
>> http://cordova.apache.org/docs/en/4.0.0/cordova_storage_storage.md.html#Storage)
>> to store data locally.
>>
>> On Wed, Apr 22, 2015 at 9:44 AM, Josh Soref  wrote:
>>> Andrey:
>>> It makes sense for someone to write a simple document saying that cookies 
>>> are
>>> supported for subresources requested from remote web servers, but that 
>>> Cordova
>>> doesn't promise cookie support for the app itself, and it should suggest 
>>> using
>>> localStorage or the file API for preferences.
>>>
>>> Thanks for volunteering to work on this :)
>>>
 -Original Message-
 From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
 Andrew Grieve
 Sent: Wednesday, April 22, 2015 11:18 AM
 To: dev
 Subject: Re: Cookie support in docs.

 Cookies work the same as they do in a browser AFAIK. cookies for file:
 don't make sense because you talk to a server at file:. If you make an XHR
 to http:///, they it can set cookies.

 On Wed, Apr 22, 2015 at 6:12 AM, Andrey Kurdumov
 
 wrote:

 > Hi,
 >
 > I come across the following SO question.
 >
 > http://stackoverflow.com/questions/24374397/cookie-support-in-
 cordova-official-documentation
 >
 > The guy could not find any mentions about cookie support in the
 Phonegap. I
 > do google search and find that the only mention about cookie support is
 > issue CB-8026 where stated that Android support third-party cookies. I
 > personally was having problems with that, but resolve it using custom 
 > HTTP
 > header.
 >
 > Question is: Does it make sense add the section in the docs regarding
 > cookies, and their limitations in Cordova apps, due to fact that files
 > server over file:/// protocol?
 >
>>
>>
>>
>> --
>> ===
>> Raymond Camden, Developer Advocate for MobileFirst at IBM
>>
>> Email : raymondcam...@gmail.com
>> Blog : www.raymondcamden.com
>> Twitter: raymondcamden
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>



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

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

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

Re: Deprecation Wars: ICS vs Gingerbread

[Joe Bowser]

It should be replaced with 14.  This was definitely an oversight since we
all agreed in theory but never came to a proper decision.

On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
v-seg...@microsoft.com> wrote:

> I still see minSdkVersion = 10 (GINGERBREAD) in platform template. Should
> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also updated in
> platform docs? -  per docs we still support Gingerbread.
>
> Steve is currently working on docs update so this is perfect time to
> change this.
>
> -Sergey
> -Original Message-
> From: Shazron [mailto:shaz...@gmail.com]
> Sent: Tuesday, April 21, 2015 1:04 PM
> To: dev@cordova.apache.org
> Subject: Re: Deprecation Wars: ICS vs Gingerbread
>
> Joe, perhaps that can be part of the Tools Release blog post? Steve put
> out a link to the draft in another thread.
>
> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser  wrote:
> > Resurrecting this thread!
> >
> > I think we need to let our users know that Cordova 4.0 doesn't support
> > Gingerbread, or at least some of the features don't work on Gingerbread.
> > I've been trying to clean up the JIRA a bit today, and it seems that
> > while we came to a consensus to drop 2.3, we didn't tell anyone. :/
> >
> >
> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser  wrote:
> >
> >> Firefox works on 2.3, and Chrome does not. It also depends on the
> >> device
> >>
> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref 
> wrote:
> >>
> >>> Michal Mocny wrote:
> >>> >... we aren't telling those individuals that they cannot use their
> >>> >phones, we are telling developers that want to create new
> >>> >applications for that target to either build mobile web, packaged
> >>> >native, or just stick to existing versions of cordova if really
> needed.
> >>> >
> >>> >I do not buy the argument that you are doing those individuals with
> >>> >those phones a favour by building them hybrid apps using the
> >>> >antiquated 2.3 webview on antiquated machine specs.
> >>>
> >>> I don't have an opinion on this. But I do have a question.
> >>>
> >>> Ignoring the fact that GeckoView is flaky today,
> >>>
> >>> 1. Does GeckoView / Firefox work (at all? well?) on a sample /
> >>> typical 2.3 device?
> >>> 2. Can I run Chrome (or some relative) on that same device (at all?
> >>> well?)
> >>>
> >>
>
> -
> 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: Deprecation Wars: ICS vs Gingerbread

[Joe Bowser]

OK, because we screwed up, should we release a Cordova-Android 5.0?  This
is going to break people, even though I don't care about the breakage, I do
care about telling them about the breakage.

Thoughts?

On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser  wrote:

> It should be replaced with 14.  This was definitely an oversight since we
> all agreed in theory but never came to a proper decision.
>
> On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
> v-seg...@microsoft.com> wrote:
>
>> I still see minSdkVersion = 10 (GINGERBREAD) in platform template. Should
>> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also updated in
>> platform docs? -  per docs we still support Gingerbread.
>>
>> Steve is currently working on docs update so this is perfect time to
>> change this.
>>
>> -Sergey
>> -Original Message-
>> From: Shazron [mailto:shaz...@gmail.com]
>> Sent: Tuesday, April 21, 2015 1:04 PM
>> To: dev@cordova.apache.org
>> Subject: Re: Deprecation Wars: ICS vs Gingerbread
>>
>> Joe, perhaps that can be part of the Tools Release blog post? Steve put
>> out a link to the draft in another thread.
>>
>> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser  wrote:
>> > Resurrecting this thread!
>> >
>> > I think we need to let our users know that Cordova 4.0 doesn't support
>> > Gingerbread, or at least some of the features don't work on Gingerbread.
>> > I've been trying to clean up the JIRA a bit today, and it seems that
>> > while we came to a consensus to drop 2.3, we didn't tell anyone. :/
>> >
>> >
>> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser  wrote:
>> >
>> >> Firefox works on 2.3, and Chrome does not. It also depends on the
>> >> device
>> >>
>> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref 
>> wrote:
>> >>
>> >>> Michal Mocny wrote:
>> >>> >... we aren't telling those individuals that they cannot use their
>> >>> >phones, we are telling developers that want to create new
>> >>> >applications for that target to either build mobile web, packaged
>> >>> >native, or just stick to existing versions of cordova if really
>> needed.
>> >>> >
>> >>> >I do not buy the argument that you are doing those individuals with
>> >>> >those phones a favour by building them hybrid apps using the
>> >>> >antiquated 2.3 webview on antiquated machine specs.
>> >>>
>> >>> I don't have an opinion on this. But I do have a question.
>> >>>
>> >>> Ignoring the fact that GeckoView is flaky today,
>> >>>
>> >>> 1. Does GeckoView / Firefox work (at all? well?) on a sample /
>> >>> typical 2.3 device?
>> >>> 2. Can I run Chrome (or some relative) on that same device (at all?
>> >>> well?)
>> >>>
>> >>
>>
>> -
>> 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: Deprecation Wars: ICS vs Gingerbread

[Steven Gill]

4.1.0? Is the minsdk the only thing keeping gingerbread support around? Are
there other things about 4.0.0 that broke support for 2.3.0?



On Wed, Apr 22, 2015 at 2:13 PM, Joe Bowser  wrote:

> OK, because we screwed up, should we release a Cordova-Android 5.0?  This
> is going to break people, even though I don't care about the breakage, I do
> care about telling them about the breakage.
>
> Thoughts?
>
> On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser  wrote:
>
> > It should be replaced with 14.  This was definitely an oversight since we
> > all agreed in theory but never came to a proper decision.
> >
> > On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
> > v-seg...@microsoft.com> wrote:
> >
> >> I still see minSdkVersion = 10 (GINGERBREAD) in platform template.
> Should
> >> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also updated
> in
> >> platform docs? -  per docs we still support Gingerbread.
> >>
> >> Steve is currently working on docs update so this is perfect time to
> >> change this.
> >>
> >> -Sergey
> >> -Original Message-
> >> From: Shazron [mailto:shaz...@gmail.com]
> >> Sent: Tuesday, April 21, 2015 1:04 PM
> >> To: dev@cordova.apache.org
> >> Subject: Re: Deprecation Wars: ICS vs Gingerbread
> >>
> >> Joe, perhaps that can be part of the Tools Release blog post? Steve put
> >> out a link to the draft in another thread.
> >>
> >> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser  wrote:
> >> > Resurrecting this thread!
> >> >
> >> > I think we need to let our users know that Cordova 4.0 doesn't support
> >> > Gingerbread, or at least some of the features don't work on
> Gingerbread.
> >> > I've been trying to clean up the JIRA a bit today, and it seems that
> >> > while we came to a consensus to drop 2.3, we didn't tell anyone. :/
> >> >
> >> >
> >> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser 
> wrote:
> >> >
> >> >> Firefox works on 2.3, and Chrome does not. It also depends on the
> >> >> device
> >> >>
> >> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref 
> >> wrote:
> >> >>
> >> >>> Michal Mocny wrote:
> >> >>> >... we aren't telling those individuals that they cannot use their
> >> >>> >phones, we are telling developers that want to create new
> >> >>> >applications for that target to either build mobile web, packaged
> >> >>> >native, or just stick to existing versions of cordova if really
> >> needed.
> >> >>> >
> >> >>> >I do not buy the argument that you are doing those individuals with
> >> >>> >those phones a favour by building them hybrid apps using the
> >> >>> >antiquated 2.3 webview on antiquated machine specs.
> >> >>>
> >> >>> I don't have an opinion on this. But I do have a question.
> >> >>>
> >> >>> Ignoring the fact that GeckoView is flaky today,
> >> >>>
> >> >>> 1. Does GeckoView / Firefox work (at all? well?) on a sample /
> >> >>> typical 2.3 device?
> >> >>> 2. Can I run Chrome (or some relative) on that same device (at all?
> >> >>> well?)
> >> >>>
> >> >>
> >>
> >> -
> >> 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: Deprecation Wars: ICS vs Gingerbread

[Joe Bowser]

None of the Third Party WebViews work for 4.0.x

On Wed, Apr 22, 2015 at 2:19 PM Steven Gill  wrote:

> 4.1.0? Is the minsdk the only thing keeping gingerbread support around? Are
> there other things about 4.0.0 that broke support for 2.3.0?
>
>
>
> On Wed, Apr 22, 2015 at 2:13 PM, Joe Bowser  wrote:
>
> > OK, because we screwed up, should we release a Cordova-Android 5.0?  This
> > is going to break people, even though I don't care about the breakage, I
> do
> > care about telling them about the breakage.
> >
> > Thoughts?
> >
> > On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser  wrote:
> >
> > > It should be replaced with 14.  This was definitely an oversight since
> we
> > > all agreed in theory but never came to a proper decision.
> > >
> > > On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
> > > v-seg...@microsoft.com> wrote:
> > >
> > >> I still see minSdkVersion = 10 (GINGERBREAD) in platform template.
> > Should
> > >> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also
> updated
> > in
> > >> platform docs? -  per docs we still support Gingerbread.
> > >>
> > >> Steve is currently working on docs update so this is perfect time to
> > >> change this.
> > >>
> > >> -Sergey
> > >> -Original Message-
> > >> From: Shazron [mailto:shaz...@gmail.com]
> > >> Sent: Tuesday, April 21, 2015 1:04 PM
> > >> To: dev@cordova.apache.org
> > >> Subject: Re: Deprecation Wars: ICS vs Gingerbread
> > >>
> > >> Joe, perhaps that can be part of the Tools Release blog post? Steve
> put
> > >> out a link to the draft in another thread.
> > >>
> > >> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser 
> wrote:
> > >> > Resurrecting this thread!
> > >> >
> > >> > I think we need to let our users know that Cordova 4.0 doesn't
> support
> > >> > Gingerbread, or at least some of the features don't work on
> > Gingerbread.
> > >> > I've been trying to clean up the JIRA a bit today, and it seems that
> > >> > while we came to a consensus to drop 2.3, we didn't tell anyone. :/
> > >> >
> > >> >
> > >> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser 
> > wrote:
> > >> >
> > >> >> Firefox works on 2.3, and Chrome does not. It also depends on the
> > >> >> device
> > >> >>
> > >> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref 
> > >> wrote:
> > >> >>
> > >> >>> Michal Mocny wrote:
> > >> >>> >... we aren't telling those individuals that they cannot use
> their
> > >> >>> >phones, we are telling developers that want to create new
> > >> >>> >applications for that target to either build mobile web, packaged
> > >> >>> >native, or just stick to existing versions of cordova if really
> > >> needed.
> > >> >>> >
> > >> >>> >I do not buy the argument that you are doing those individuals
> with
> > >> >>> >those phones a favour by building them hybrid apps using the
> > >> >>> >antiquated 2.3 webview on antiquated machine specs.
> > >> >>>
> > >> >>> I don't have an opinion on this. But I do have a question.
> > >> >>>
> > >> >>> Ignoring the fact that GeckoView is flaky today,
> > >> >>>
> > >> >>> 1. Does GeckoView / Firefox work (at all? well?) on a sample /
> > >> >>> typical 2.3 device?
> > >> >>> 2. Can I run Chrome (or some relative) on that same device (at
> all?
> > >> >>> well?)
> > >> >>>
> > >> >>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
> > >>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
> > >>
> > >
> >
>

[GitHub] cordova-plugin-camera pull request: typo fix cameraproxy.js

[muratsu]

GitHub user muratsu opened a pull request:

https://github.com/apache/cordova-plugin-camera/pull/89

typo fix cameraproxy.js

There was a missing comma on cameraproxy

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

$ git pull https://github.com/muratsu/cordova-plugin-camera patch-1

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

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


commit 090ebd41932b0d21a06e795f42f3bc6eaf5c4a9c
Author: Murat Sutunc 
Date:   2015-04-22T21:23:47Z

typo fix cameraproxy.js

There was a missing comma on cameraproxy




---
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: Deprecation Wars: ICS vs Gingerbread

[Joe Bowser]

As in they don't work on Android 2.3.x, sorry hit send way too soon.  Also,
there's a lot of bad security issues on 2.3.x that we just can't fix, so
it's best that we draw the line here and not support 2.3.x

On Wed, Apr 22, 2015 at 2:23 PM Joe Bowser  wrote:

> None of the Third Party WebViews work for 4.0.x
>
> On Wed, Apr 22, 2015 at 2:19 PM Steven Gill 
> wrote:
>
>> 4.1.0? Is the minsdk the only thing keeping gingerbread support around?
>> Are
>> there other things about 4.0.0 that broke support for 2.3.0?
>>
>>
>>
>> On Wed, Apr 22, 2015 at 2:13 PM, Joe Bowser  wrote:
>>
>> > OK, because we screwed up, should we release a Cordova-Android 5.0?
>> This
>> > is going to break people, even though I don't care about the breakage,
>> I do
>> > care about telling them about the breakage.
>> >
>> > Thoughts?
>> >
>> > On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser  wrote:
>> >
>> > > It should be replaced with 14.  This was definitely an oversight
>> since we
>> > > all agreed in theory but never came to a proper decision.
>> > >
>> > > On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
>> > > v-seg...@microsoft.com> wrote:
>> > >
>> > >> I still see minSdkVersion = 10 (GINGERBREAD) in platform template.
>> > Should
>> > >> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also
>> updated
>> > in
>> > >> platform docs? -  per docs we still support Gingerbread.
>> > >>
>> > >> Steve is currently working on docs update so this is perfect time to
>> > >> change this.
>> > >>
>> > >> -Sergey
>> > >> -Original Message-
>> > >> From: Shazron [mailto:shaz...@gmail.com]
>> > >> Sent: Tuesday, April 21, 2015 1:04 PM
>> > >> To: dev@cordova.apache.org
>> > >> Subject: Re: Deprecation Wars: ICS vs Gingerbread
>> > >>
>> > >> Joe, perhaps that can be part of the Tools Release blog post? Steve
>> put
>> > >> out a link to the draft in another thread.
>> > >>
>> > >> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser 
>> wrote:
>> > >> > Resurrecting this thread!
>> > >> >
>> > >> > I think we need to let our users know that Cordova 4.0 doesn't
>> support
>> > >> > Gingerbread, or at least some of the features don't work on
>> > Gingerbread.
>> > >> > I've been trying to clean up the JIRA a bit today, and it seems
>> that
>> > >> > while we came to a consensus to drop 2.3, we didn't tell anyone. :/
>> > >> >
>> > >> >
>> > >> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser 
>> > wrote:
>> > >> >
>> > >> >> Firefox works on 2.3, and Chrome does not. It also depends on the
>> > >> >> device
>> > >> >>
>> > >> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref 
>> > >> wrote:
>> > >> >>
>> > >> >>> Michal Mocny wrote:
>> > >> >>> >... we aren't telling those individuals that they cannot use
>> their
>> > >> >>> >phones, we are telling developers that want to create new
>> > >> >>> >applications for that target to either build mobile web,
>> packaged
>> > >> >>> >native, or just stick to existing versions of cordova if really
>> > >> needed.
>> > >> >>> >
>> > >> >>> >I do not buy the argument that you are doing those individuals
>> with
>> > >> >>> >those phones a favour by building them hybrid apps using the
>> > >> >>> >antiquated 2.3 webview on antiquated machine specs.
>> > >> >>>
>> > >> >>> I don't have an opinion on this. But I do have a question.
>> > >> >>>
>> > >> >>> Ignoring the fact that GeckoView is flaky today,
>> > >> >>>
>> > >> >>> 1. Does GeckoView / Firefox work (at all? well?) on a sample /
>> > >> >>> typical 2.3 device?
>> > >> >>> 2. Can I run Chrome (or some relative) on that same device (at
>> all?
>> > >> >>> well?)
>> > >> >>>
>> > >> >>
>> > >>
>> > >> -
>> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
>> > >>
>> > >>
>> > >> -
>> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
>> > >>
>> > >
>> >
>>
>

[GitHub] cordova-ios pull request: CB-8485 Support for creating signed arch...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-ios/pull/138


---
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: Deprecation Wars: ICS vs Gingerbread

[Steven Gill]

Okay. Since pluggable webviews don't work with 2.3.x, I'd say we do a
cordova-android 4.1.0 release with minsdk 14.

I'll update the docs to say we only support android 4+

On Wed, Apr 22, 2015 at 2:24 PM, Joe Bowser  wrote:

> As in they don't work on Android 2.3.x, sorry hit send way too soon.  Also,
> there's a lot of bad security issues on 2.3.x that we just can't fix, so
> it's best that we draw the line here and not support 2.3.x
>
> On Wed, Apr 22, 2015 at 2:23 PM Joe Bowser  wrote:
>
> > None of the Third Party WebViews work for 4.0.x
> >
> > On Wed, Apr 22, 2015 at 2:19 PM Steven Gill 
> > wrote:
> >
> >> 4.1.0? Is the minsdk the only thing keeping gingerbread support around?
> >> Are
> >> there other things about 4.0.0 that broke support for 2.3.0?
> >>
> >>
> >>
> >> On Wed, Apr 22, 2015 at 2:13 PM, Joe Bowser  wrote:
> >>
> >> > OK, because we screwed up, should we release a Cordova-Android 5.0?
> >> This
> >> > is going to break people, even though I don't care about the breakage,
> >> I do
> >> > care about telling them about the breakage.
> >> >
> >> > Thoughts?
> >> >
> >> > On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser  wrote:
> >> >
> >> > > It should be replaced with 14.  This was definitely an oversight
> >> since we
> >> > > all agreed in theory but never came to a proper decision.
> >> > >
> >> > > On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
> >> > > v-seg...@microsoft.com> wrote:
> >> > >
> >> > >> I still see minSdkVersion = 10 (GINGERBREAD) in platform template.
> >> > Should
> >> > >> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also
> >> updated
> >> > in
> >> > >> platform docs? -  per docs we still support Gingerbread.
> >> > >>
> >> > >> Steve is currently working on docs update so this is perfect time
> to
> >> > >> change this.
> >> > >>
> >> > >> -Sergey
> >> > >> -Original Message-
> >> > >> From: Shazron [mailto:shaz...@gmail.com]
> >> > >> Sent: Tuesday, April 21, 2015 1:04 PM
> >> > >> To: dev@cordova.apache.org
> >> > >> Subject: Re: Deprecation Wars: ICS vs Gingerbread
> >> > >>
> >> > >> Joe, perhaps that can be part of the Tools Release blog post? Steve
> >> put
> >> > >> out a link to the draft in another thread.
> >> > >>
> >> > >> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser 
> >> wrote:
> >> > >> > Resurrecting this thread!
> >> > >> >
> >> > >> > I think we need to let our users know that Cordova 4.0 doesn't
> >> support
> >> > >> > Gingerbread, or at least some of the features don't work on
> >> > Gingerbread.
> >> > >> > I've been trying to clean up the JIRA a bit today, and it seems
> >> that
> >> > >> > while we came to a consensus to drop 2.3, we didn't tell anyone.
> :/
> >> > >> >
> >> > >> >
> >> > >> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser 
> >> > wrote:
> >> > >> >
> >> > >> >> Firefox works on 2.3, and Chrome does not. It also depends on
> the
> >> > >> >> device
> >> > >> >>
> >> > >> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref <
> jso...@blackberry.com>
> >> > >> wrote:
> >> > >> >>
> >> > >> >>> Michal Mocny wrote:
> >> > >> >>> >... we aren't telling those individuals that they cannot use
> >> their
> >> > >> >>> >phones, we are telling developers that want to create new
> >> > >> >>> >applications for that target to either build mobile web,
> >> packaged
> >> > >> >>> >native, or just stick to existing versions of cordova if
> really
> >> > >> needed.
> >> > >> >>> >
> >> > >> >>> >I do not buy the argument that you are doing those individuals
> >> with
> >> > >> >>> >those phones a favour by building them hybrid apps using the
> >> > >> >>> >antiquated 2.3 webview on antiquated machine specs.
> >> > >> >>>
> >> > >> >>> I don't have an opinion on this. But I do have a question.
> >> > >> >>>
> >> > >> >>> Ignoring the fact that GeckoView is flaky today,
> >> > >> >>>
> >> > >> >>> 1. Does GeckoView / Firefox work (at all? well?) on a sample /
> >> > >> >>> typical 2.3 device?
> >> > >> >>> 2. Can I run Chrome (or some relative) on that same device (at
> >> all?
> >> > >> >>> well?)
> >> > >> >>>
> >> > >> >>
> >> > >>
> >> > >>
> -
> >> > >> 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: Deprecation Wars: ICS vs Gingerbread

[Joe Bowser]

BTW: Sorry for rushing the commit and sticking the ugly merge commit to try
and fix it.

On Wed, Apr 22, 2015 at 2:28 PM Steven Gill  wrote:

> Okay. Since pluggable webviews don't work with 2.3.x, I'd say we do a
> cordova-android 4.1.0 release with minsdk 14.
>
> I'll update the docs to say we only support android 4+
>
> On Wed, Apr 22, 2015 at 2:24 PM, Joe Bowser  wrote:
>
> > As in they don't work on Android 2.3.x, sorry hit send way too soon.
> Also,
> > there's a lot of bad security issues on 2.3.x that we just can't fix, so
> > it's best that we draw the line here and not support 2.3.x
> >
> > On Wed, Apr 22, 2015 at 2:23 PM Joe Bowser  wrote:
> >
> > > None of the Third Party WebViews work for 4.0.x
> > >
> > > On Wed, Apr 22, 2015 at 2:19 PM Steven Gill 
> > > wrote:
> > >
> > >> 4.1.0? Is the minsdk the only thing keeping gingerbread support
> around?
> > >> Are
> > >> there other things about 4.0.0 that broke support for 2.3.0?
> > >>
> > >>
> > >>
> > >> On Wed, Apr 22, 2015 at 2:13 PM, Joe Bowser 
> wrote:
> > >>
> > >> > OK, because we screwed up, should we release a Cordova-Android 5.0?
> > >> This
> > >> > is going to break people, even though I don't care about the
> breakage,
> > >> I do
> > >> > care about telling them about the breakage.
> > >> >
> > >> > Thoughts?
> > >> >
> > >> > On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser 
> wrote:
> > >> >
> > >> > > It should be replaced with 14.  This was definitely an oversight
> > >> since we
> > >> > > all agreed in theory but never came to a proper decision.
> > >> > >
> > >> > > On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
> > >> > > v-seg...@microsoft.com> wrote:
> > >> > >
> > >> > >> I still see minSdkVersion = 10 (GINGERBREAD) in platform
> template.
> > >> > Should
> > >> > >> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also
> > >> updated
> > >> > in
> > >> > >> platform docs? -  per docs we still support Gingerbread.
> > >> > >>
> > >> > >> Steve is currently working on docs update so this is perfect time
> > to
> > >> > >> change this.
> > >> > >>
> > >> > >> -Sergey
> > >> > >> -Original Message-
> > >> > >> From: Shazron [mailto:shaz...@gmail.com]
> > >> > >> Sent: Tuesday, April 21, 2015 1:04 PM
> > >> > >> To: dev@cordova.apache.org
> > >> > >> Subject: Re: Deprecation Wars: ICS vs Gingerbread
> > >> > >>
> > >> > >> Joe, perhaps that can be part of the Tools Release blog post?
> Steve
> > >> put
> > >> > >> out a link to the draft in another thread.
> > >> > >>
> > >> > >> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser 
> > >> wrote:
> > >> > >> > Resurrecting this thread!
> > >> > >> >
> > >> > >> > I think we need to let our users know that Cordova 4.0 doesn't
> > >> support
> > >> > >> > Gingerbread, or at least some of the features don't work on
> > >> > Gingerbread.
> > >> > >> > I've been trying to clean up the JIRA a bit today, and it seems
> > >> that
> > >> > >> > while we came to a consensus to drop 2.3, we didn't tell
> anyone.
> > :/
> > >> > >> >
> > >> > >> >
> > >> > >> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser  >
> > >> > wrote:
> > >> > >> >
> > >> > >> >> Firefox works on 2.3, and Chrome does not. It also depends on
> > the
> > >> > >> >> device
> > >> > >> >>
> > >> > >> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref <
> > jso...@blackberry.com>
> > >> > >> wrote:
> > >> > >> >>
> > >> > >> >>> Michal Mocny wrote:
> > >> > >> >>> >... we aren't telling those individuals that they cannot use
> > >> their
> > >> > >> >>> >phones, we are telling developers that want to create new
> > >> > >> >>> >applications for that target to either build mobile web,
> > >> packaged
> > >> > >> >>> >native, or just stick to existing versions of cordova if
> > really
> > >> > >> needed.
> > >> > >> >>> >
> > >> > >> >>> >I do not buy the argument that you are doing those
> individuals
> > >> with
> > >> > >> >>> >those phones a favour by building them hybrid apps using the
> > >> > >> >>> >antiquated 2.3 webview on antiquated machine specs.
> > >> > >> >>>
> > >> > >> >>> I don't have an opinion on this. But I do have a question.
> > >> > >> >>>
> > >> > >> >>> Ignoring the fact that GeckoView is flaky today,
> > >> > >> >>>
> > >> > >> >>> 1. Does GeckoView / Firefox work (at all? well?) on a sample
> /
> > >> > >> >>> typical 2.3 device?
> > >> > >> >>> 2. Can I run Chrome (or some relative) on that same device
> (at
> > >> all?
> > >> > >> >>> well?)
> > >> > >> >>>
> > >> > >> >>
> > >> > >>
> > >> > >>
> > -
> > >> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
> > >> > >>
> > >> > >>
> > >> > >>
> > -
> > >> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
> > >> > >>
> > >> > >

[GitHub] cordova-plugin-camera pull request: typo fix cameraproxy.js

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-camera/pull/89


---
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-medic pull request: Syncing code from Apache Infra SVN.

[dblotsky]

GitHub user dblotsky opened a pull request:

https://github.com/apache/cordova-medic/pull/45

Syncing code from Apache Infra SVN.

Adding IRC bot code that was added separately on the Apache Infra SVN 
version of `cordova.conf`.

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

$ git pull https://github.com/MSOpenTech/cordova-medic apache-sync

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

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


commit 7640a905ef3764d1887119ee0c14878f64870e74
Author: Dmitry Blotsky 
Date:   2015-04-23T00:10:07Z

Syncing code from Apache Infra SVN.




---
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: Deprecation Wars: ICS vs Gingerbread

[Andrew Grieve]

Not sure it's worth doing another release just for this. Devs can already
set the minSdkVersion using a .

On Wed, Apr 22, 2015 at 5:33 PM, Joe Bowser  wrote:

> BTW: Sorry for rushing the commit and sticking the ugly merge commit to try
> and fix it.
>
> On Wed, Apr 22, 2015 at 2:28 PM Steven Gill 
> wrote:
>
> > Okay. Since pluggable webviews don't work with 2.3.x, I'd say we do a
> > cordova-android 4.1.0 release with minsdk 14.
> >
> > I'll update the docs to say we only support android 4+
> >
> > On Wed, Apr 22, 2015 at 2:24 PM, Joe Bowser  wrote:
> >
> > > As in they don't work on Android 2.3.x, sorry hit send way too soon.
> > Also,
> > > there's a lot of bad security issues on 2.3.x that we just can't fix,
> so
> > > it's best that we draw the line here and not support 2.3.x
> > >
> > > On Wed, Apr 22, 2015 at 2:23 PM Joe Bowser  wrote:
> > >
> > > > None of the Third Party WebViews work for 4.0.x
> > > >
> > > > On Wed, Apr 22, 2015 at 2:19 PM Steven Gill 
> > > > wrote:
> > > >
> > > >> 4.1.0? Is the minsdk the only thing keeping gingerbread support
> > around?
> > > >> Are
> > > >> there other things about 4.0.0 that broke support for 2.3.0?
> > > >>
> > > >>
> > > >>
> > > >> On Wed, Apr 22, 2015 at 2:13 PM, Joe Bowser 
> > wrote:
> > > >>
> > > >> > OK, because we screwed up, should we release a Cordova-Android
> 5.0?
> > > >> This
> > > >> > is going to break people, even though I don't care about the
> > breakage,
> > > >> I do
> > > >> > care about telling them about the breakage.
> > > >> >
> > > >> > Thoughts?
> > > >> >
> > > >> > On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser 
> > wrote:
> > > >> >
> > > >> > > It should be replaced with 14.  This was definitely an oversight
> > > >> since we
> > > >> > > all agreed in theory but never came to a proper decision.
> > > >> > >
> > > >> > > On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) <
> > > >> > > v-seg...@microsoft.com> wrote:
> > > >> > >
> > > >> > >> I still see minSdkVersion = 10 (GINGERBREAD) in platform
> > template.
> > > >> > Should
> > > >> > >> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and also
> > > >> updated
> > > >> > in
> > > >> > >> platform docs? -  per docs we still support Gingerbread.
> > > >> > >>
> > > >> > >> Steve is currently working on docs update so this is perfect
> time
> > > to
> > > >> > >> change this.
> > > >> > >>
> > > >> > >> -Sergey
> > > >> > >> -Original Message-
> > > >> > >> From: Shazron [mailto:shaz...@gmail.com]
> > > >> > >> Sent: Tuesday, April 21, 2015 1:04 PM
> > > >> > >> To: dev@cordova.apache.org
> > > >> > >> Subject: Re: Deprecation Wars: ICS vs Gingerbread
> > > >> > >>
> > > >> > >> Joe, perhaps that can be part of the Tools Release blog post?
> > Steve
> > > >> put
> > > >> > >> out a link to the draft in another thread.
> > > >> > >>
> > > >> > >> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser <
> bows...@gmail.com>
> > > >> wrote:
> > > >> > >> > Resurrecting this thread!
> > > >> > >> >
> > > >> > >> > I think we need to let our users know that Cordova 4.0
> doesn't
> > > >> support
> > > >> > >> > Gingerbread, or at least some of the features don't work on
> > > >> > Gingerbread.
> > > >> > >> > I've been trying to clean up the JIRA a bit today, and it
> seems
> > > >> that
> > > >> > >> > while we came to a consensus to drop 2.3, we didn't tell
> > anyone.
> > > :/
> > > >> > >> >
> > > >> > >> >
> > > >> > >> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser <
> bows...@gmail.com
> > >
> > > >> > wrote:
> > > >> > >> >
> > > >> > >> >> Firefox works on 2.3, and Chrome does not. It also depends
> on
> > > the
> > > >> > >> >> device
> > > >> > >> >>
> > > >> > >> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref <
> > > jso...@blackberry.com>
> > > >> > >> wrote:
> > > >> > >> >>
> > > >> > >> >>> Michal Mocny wrote:
> > > >> > >> >>> >... we aren't telling those individuals that they cannot
> use
> > > >> their
> > > >> > >> >>> >phones, we are telling developers that want to create new
> > > >> > >> >>> >applications for that target to either build mobile web,
> > > >> packaged
> > > >> > >> >>> >native, or just stick to existing versions of cordova if
> > > really
> > > >> > >> needed.
> > > >> > >> >>> >
> > > >> > >> >>> >I do not buy the argument that you are doing those
> > individuals
> > > >> with
> > > >> > >> >>> >those phones a favour by building them hybrid apps using
> the
> > > >> > >> >>> >antiquated 2.3 webview on antiquated machine specs.
> > > >> > >> >>>
> > > >> > >> >>> I don't have an opinion on this. But I do have a question.
> > > >> > >> >>>
> > > >> > >> >>> Ignoring the fact that GeckoView is flaky today,
> > > >> > >> >>>
> > > >> > >> >>> 1. Does GeckoView / Firefox work (at all? well?) on a
> sample
> > /
> > > >> > >> >>> typical 2.3 device?
> > > >> > >> >>> 2. Can I run Chrome (or some relative) on that same device
> > (at
> > > >> all?
> > > >> > >> >>> well?)
> > > >> > >> >>>
> > > >> > >> >>
> > > >> > >>
> > > >> > >>
>

RE: How to get plugin lists for cordova-android 3.7.x

[Fu, Junwei]

Thanks for your patient explain.

I want to rebase Cordova 3.7.x to crosswalk-cordova, need suitable plugin list 
and mobile-spec to verify the version.

Thanks,
Junwei.
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Wednesday, April 22, 2015 10:12 PM
To: dev@cordova.apache.org
Subject: Re: How to get plugin lists for cordova-android 3.7.x

Hi Fu
  If you want to test what was release at the time frame that Android 3.7.1 was 
released then one way if too look at the release notes.

You can use Cordova CLI 4.2.0 [1] "npm install -g cordova@4.2.0", it pinned
cordova-android@3.7.1
To get the plugin list that was tested at that time frame you can take a look 
at the release notes for Plugins [2] when for Android 3.7.1 was the latest 
pinned.

use latest cordova-mobile-spec and latest cordova-plugin-test-framework

Don't know why you will want to test old plugins, I will stick with latest 
plugins released this week. and latest cordova-cli and add android platform
3.7.1 "cordova platform add android@3.7.1"

I guess I didn't answer you questions :-), but I gave you enough rope


[1]: http://cordova.apache.org/news/2015/03/02/tools-release.html
[2]: http://cordova.apache.org/news/2015/02/10/plugins-release.html



On Tue, Apr 21, 2015 at 8:20 PM, Fu, Junwei  wrote:

> Hi All,
>
> Mobile-spec has no 3.7.x branch, how can I  get the plugin lists for 
> cordova-android 3.7.x, and how to build mobile-spec to test 
> cordova-android 3.7.x, do we use the latest 
> cordova-plugin-test-framework, cordova-cli, cordova-mobile-spec and so on.
>
> Thanks,
> Junwei.
>



--
Carlos Santana

Re: Cookie support in docs.

[Andrey Kurdumov]

I put section about CORS, since looks like not everybody unaware that CORS
applied to all remote communicatoins.

https://github.com/cordova/cordova-discuss/pull/1

Please take a look.

2015-04-23 3:01 GMT+06:00 Raymond Camden :

> Sweet. Thanks Shazon!
>
> On Wed, Apr 22, 2015 at 1:58 PM, Shazron  wrote:
> > Created https://github.com/cordova/cordova-discuss/blob/master/FAQ.md
> > as a doc so we can stage edits.
> > If anyone needs direct access let me know.
> >
> >
> > On Wed, Apr 22, 2015 at 10:21 AM, Raymond Camden
> >  wrote:
> >> So we don't have a FAQ yet. Is it time to start it? Here is my stab:
> >>
> >> Do cookies work in Cordova apps?
> >>
> >> There are two ways in which you may want to use cookies. The first is
> >> within XHR (Ajax) requests to remote resources. Unless you
> >> specifically remove them, your Ajax library will automatically use
> >> cookies in subsequent calls to remote APIs and resources you request.
> >> So given that some API returns a cookie required for future calls, you
> >> can assume it will be automatically sent when your app hits it again.
> >>
> >> The other way your app may desire to use cookies is locally - ie
> >> within the app itself. This does not make sense within a Cordova app
> >> as it isn't running on a proper web server itself. If your intent is
> >> simply to store data for the app then you should make use the various
> >> existing methods (link to
> >>
> http://cordova.apache.org/docs/en/4.0.0/cordova_storage_storage.md.html#Storage
> )
> >> to store data locally.
> >>
> >> On Wed, Apr 22, 2015 at 9:44 AM, Josh Soref 
> wrote:
> >>> Andrey:
> >>> It makes sense for someone to write a simple document saying that
> cookies are
> >>> supported for subresources requested from remote web servers, but that
> Cordova
> >>> doesn't promise cookie support for the app itself, and it should
> suggest using
> >>> localStorage or the file API for preferences.
> >>>
> >>> Thanks for volunteering to work on this :)
> >>>
>  -Original Message-
>  From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
>  Andrew Grieve
>  Sent: Wednesday, April 22, 2015 11:18 AM
>  To: dev
>  Subject: Re: Cookie support in docs.
> 
>  Cookies work the same as they do in a browser AFAIK. cookies for file:
>  don't make sense because you talk to a server at file:. If you make
> an XHR
>  to http:///, they it can set cookies.
> 
>  On Wed, Apr 22, 2015 at 6:12 AM, Andrey Kurdumov
>  
>  wrote:
> 
>  > Hi,
>  >
>  > I come across the following SO question.
>  >
>  > http://stackoverflow.com/questions/24374397/cookie-support-in-
>  cordova-official-documentation
>  >
>  > The guy could not find any mentions about cookie support in the
>  Phonegap. I
>  > do google search and find that the only mention about cookie
> support is
>  > issue CB-8026 where stated that Android support third-party
> cookies. I
>  > personally was having problems with that, but resolve it using
> custom HTTP
>  > header.
>  >
>  > Question is: Does it make sense add the section in the docs
> regarding
>  > cookies, and their limitations in Cordova apps, due to fact that
> files
>  > server over file:/// protocol?
>  >
> >>
> >>
> >>
> >> --
> >>
> ===
> >> Raymond Camden, Developer Advocate for MobileFirst at IBM
> >>
> >> Email : raymondcam...@gmail.com
> >> Blog : www.raymondcamden.com
> >> Twitter: raymondcamden
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> >> For additional commands, e-mail: dev-h...@cordova.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>
>
>
> --
> ===
> Raymond Camden, Developer Advocate for MobileFirst at IBM
>
> Email : raymondcam...@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: [DISCUSS] Docs release

[Andrey Kurdumov]

Could Viktor or Lisa update all untranslated Russian in CrowdIn.
If I understand correclty, they could just use Microsoft translator for
that and do that automatically.
I have to do that manually, and I don't have cycles to fully
translate/proofread language for this release.

2015-04-22 7:43 GMT+06:00 Sergey Grebnov (Akvelon) :

> I've sent a PR to update platform guides as per discussion in a separate
> thread; it will be great if we can review and include it to docs release
>
> https://github.com/apache/cordova-docs/pull/279
>
> Thx!
> Sergey
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Tuesday, April 21, 2015 5:49 PM
> To: dev@cordova.apache.org
> Subject: [DISCUSS] Docs release
>
> I'm going to look into doing this. Any blockers, let me know
>
> Don't believe we have to vote on this one.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: Adding Other Platform Slaves to Medic

[Willy Aguirre]

any update? Dmitry

2015-04-20 1:10 GMT-05:00 Willy Aguirre :

> https://github.com/apache/cordova-medic/pull/39 my last commit is about
> createMedicJson
> 
> it works, yes can help with debug the slave.
>
> Regards,
>
> Willy
>
> 2015-04-17 22:09 GMT-05:00 Parashuram N (MS OPEN TECH) <
> panar...@microsoft.com>:
>
> In an earlier mail, folks had said that they would also contribute slaves.
>> Is there a process to begin that now ?
>>
>> On 4/17/15, 4:47 PM, "Dmitry Blotsky"  wrote:
>>
>> >Hi list,
>> >
>> >Right now medic runs Android, iOS, Windows, and Windows Phone builds. The
>> >instructions for adding new slaves are here:
>> >
>> https://github.com/apache/cordova-medic/blob/master/SLAVES.md#connecting-t
>> >o-apaches-master
>> ><
>> https://github.com/apache/cordova-medic/blob/master/SLAVES.md#connecting-
>> >to-apaches-master>.
>> >
>> >Willy Aguirre has been working on adding FirefoxOS support. Willy, have
>> >you been able to successfully test your support locally with your
>> >changes? If so, you can follow the steps to add your slave to Apache. If
>> >you¹re running into issues, post them and we can debug.
>> >
>> >Kindly,
>> >Dmitry
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>
>
>
> --
> Willy Aguirre | @willrre
> Blog: http://osgux.tumblr.com/
> Mozilla Rep: https://reps.mozilla.org/u/Willy/
> Mozilla Hispano - Willyaguirre
> 
>



-- 
Willy Aguirre | @willrre
Blog: http://osgux.tumblr.com/
Mozilla Rep: https://reps.mozilla.org/u/Willy/
Mozilla Hispano - Willyaguirre

[GitHub] cordova-medic pull request: Syncing code from Apache Infra SVN.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-medic/pull/45


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