RE: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Dick Van den Brink 
This is awesome! Still need to support the older versions though but in the 
long run it makes things a lot easier!

Sent from my Windows Phone

From: Michal Mocny
Sent: ‎11/‎1/‎2013 4:12
To: dev; 
bows...@apache.org
Cc: Ian Clelland
Subject: Re: Chromeview has arrived in Android 4.4

On Thu, Oct 31, 2013 at 10:37 PM, Joe Bowser  wrote:

> On Thu, Oct 31, 2013 at 10:24 PM, Ian Clelland 
> wrote:
> > Joe -- I'm not sure what you mean -- it's definitely mentioned on
> > http://developer.android.com/about/versions/kitkat.html -- was there a
> more
> > definitive docs location you were hoping for?
> >
>
> That's a relief.  I am pulling the KitKat source now.  (TIP: Don't do
> Android Source Dev and Chromium Dev on the same box, both use repo,
> but different versions)
>
> My main fear was that only Google devices would get KitKat WebView and
> that AOSP would get nothing, similar to how AOSP apparently doesn't
> have a Gallery or a default SMS client anymore.  There are rumours
> that AOSP no longer has a dialer, but that would be batshit insane,
> since that would mean that it'd be next to impossible to make phone
> calls on AOSP. :(
>
> Also, I heard that the Galaxy Nexus wasn't getting KitKat, which makes
> no sense since the story was about supporting older hardware.  No idea
> what older hardware means, to be honest.  Technically my HTC One is
> "Older" than the Nexus 5.
>

It is about supporting 512m of ram, specifically, so that less expensive
new devices can still target new versions of Android instead of requiring
gingerbread.

I'm not sure about the specific story for galaxy nexus, but have also heard
rumour that i wont be supported.  I imagine they tried and couldn't for
some good technical reason.


>
> Here's an Ars Technica article bashing Google that touches on it.  I
> don't know how true this is, I'm still fetching 4.4 from the
> repository onto my laptop now, but I do know that there's the GApps
> bundle that's only allows on Open Handset Alliance devices (GMail,
> Hangouts, G+, Play Store, etc)
>
> http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/
>
> Even if you disagree with this, it's still worth the read.
>
> Joe
>
> >
> > On Thu, Oct 31, 2013 at 4:23 PM, Joe Bowser  wrote:
> >>
> >> I'm cautiously optimistic. Disappointed this is documented on Google's
> >> site
> >> and not Android's site. That piece of minutiae matters.
> >> On Oct 31, 2013 12:14 PM, "Carlos Santana" 
> wrote:
> >>
> >> > I'm going to the store to buy a Bag of KitKat to celebrate "Happy
> >> > Halloween" !
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Thu, Oct 31, 2013 at 2:55 PM, Brian LeRoux  wrote:
> >> >
> >> > > omfg thank you google!
> >> > >
> >> > >
> >> > > On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill <
> stevengil...@gmail.com
> >> > > >wrote:
> >> > >
> >> > > > Celebrate!
> >> > > > https://developers.google.com/chrome/mobile/docs/webview/overview
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Carlos Santana
> >> > 
> >> >
> >
> >
>

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Michal Mocny 
On Thu, Oct 31, 2013 at 10:37 PM, Joe Bowser  wrote:

> On Thu, Oct 31, 2013 at 10:24 PM, Ian Clelland 
> wrote:
> > Joe -- I'm not sure what you mean -- it's definitely mentioned on
> > http://developer.android.com/about/versions/kitkat.html -- was there a
> more
> > definitive docs location you were hoping for?
> >
>
> That's a relief.  I am pulling the KitKat source now.  (TIP: Don't do
> Android Source Dev and Chromium Dev on the same box, both use repo,
> but different versions)
>
> My main fear was that only Google devices would get KitKat WebView and
> that AOSP would get nothing, similar to how AOSP apparently doesn't
> have a Gallery or a default SMS client anymore.  There are rumours
> that AOSP no longer has a dialer, but that would be batshit insane,
> since that would mean that it'd be next to impossible to make phone
> calls on AOSP. :(
>
> Also, I heard that the Galaxy Nexus wasn't getting KitKat, which makes
> no sense since the story was about supporting older hardware.  No idea
> what older hardware means, to be honest.  Technically my HTC One is
> "Older" than the Nexus 5.
>

It is about supporting 512m of ram, specifically, so that less expensive
new devices can still target new versions of Android instead of requiring
gingerbread.

I'm not sure about the specific story for galaxy nexus, but have also heard
rumour that i wont be supported.  I imagine they tried and couldn't for
some good technical reason.


>
> Here's an Ars Technica article bashing Google that touches on it.  I
> don't know how true this is, I'm still fetching 4.4 from the
> repository onto my laptop now, but I do know that there's the GApps
> bundle that's only allows on Open Handset Alliance devices (GMail,
> Hangouts, G+, Play Store, etc)
>
> http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/
>
> Even if you disagree with this, it's still worth the read.
>
> Joe
>
> >
> > On Thu, Oct 31, 2013 at 4:23 PM, Joe Bowser  wrote:
> >>
> >> I'm cautiously optimistic. Disappointed this is documented on Google's
> >> site
> >> and not Android's site. That piece of minutiae matters.
> >> On Oct 31, 2013 12:14 PM, "Carlos Santana" 
> wrote:
> >>
> >> > I'm going to the store to buy a Bag of KitKat to celebrate "Happy
> >> > Halloween" !
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Thu, Oct 31, 2013 at 2:55 PM, Brian LeRoux  wrote:
> >> >
> >> > > omfg thank you google!
> >> > >
> >> > >
> >> > > On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill <
> stevengil...@gmail.com
> >> > > >wrote:
> >> > >
> >> > > > Celebrate!
> >> > > > https://developers.google.com/chrome/mobile/docs/webview/overview
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Carlos Santana
> >> > 
> >> >
> >
> >
>

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Joe Bowser 
On Thu, Oct 31, 2013 at 10:24 PM, Ian Clelland  wrote:
> Joe -- I'm not sure what you mean -- it's definitely mentioned on
> http://developer.android.com/about/versions/kitkat.html -- was there a more
> definitive docs location you were hoping for?
>

That's a relief.  I am pulling the KitKat source now.  (TIP: Don't do
Android Source Dev and Chromium Dev on the same box, both use repo,
but different versions)

My main fear was that only Google devices would get KitKat WebView and
that AOSP would get nothing, similar to how AOSP apparently doesn't
have a Gallery or a default SMS client anymore.  There are rumours
that AOSP no longer has a dialer, but that would be batshit insane,
since that would mean that it'd be next to impossible to make phone
calls on AOSP. :(

Also, I heard that the Galaxy Nexus wasn't getting KitKat, which makes
no sense since the story was about supporting older hardware.  No idea
what older hardware means, to be honest.  Technically my HTC One is
"Older" than the Nexus 5.

Here's an Ars Technica article bashing Google that touches on it.  I
don't know how true this is, I'm still fetching 4.4 from the
repository onto my laptop now, but I do know that there's the GApps
bundle that's only allows on Open Handset Alliance devices (GMail,
Hangouts, G+, Play Store, etc)
http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/

Even if you disagree with this, it's still worth the read.

Joe

>
> On Thu, Oct 31, 2013 at 4:23 PM, Joe Bowser  wrote:
>>
>> I'm cautiously optimistic. Disappointed this is documented on Google's
>> site
>> and not Android's site. That piece of minutiae matters.
>> On Oct 31, 2013 12:14 PM, "Carlos Santana"  wrote:
>>
>> > I'm going to the store to buy a Bag of KitKat to celebrate "Happy
>> > Halloween" !
>> >
>> >
>> >
>> >
>> >
>> > On Thu, Oct 31, 2013 at 2:55 PM, Brian LeRoux  wrote:
>> >
>> > > omfg thank you google!
>> > >
>> > >
>> > > On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill > > > >wrote:
>> > >
>> > > > Celebrate!
>> > > > https://developers.google.com/chrome/mobile/docs/webview/overview
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Carlos Santana
>> > 
>> >
>
>

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Ian Clelland 
Joe -- I'm not sure what you mean -- it's definitely mentioned on
http://developer.android.com/about/versions/kitkat.html -- was there a more
definitive docs location you were hoping for?


On Thu, Oct 31, 2013 at 4:23 PM, Joe Bowser  wrote:

> I'm cautiously optimistic. Disappointed this is documented on Google's site
> and not Android's site. That piece of minutiae matters.
> On Oct 31, 2013 12:14 PM, "Carlos Santana"  wrote:
>
> > I'm going to the store to buy a Bag of KitKat to celebrate "Happy
> > Halloween" !
> >
> >
> >
> >
> >
> > On Thu, Oct 31, 2013 at 2:55 PM, Brian LeRoux  wrote:
> >
> > > omfg thank you google!
> > >
> > >
> > > On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill  > > >wrote:
> > >
> > > > Celebrate!
> > > > https://developers.google.com/chrome/mobile/docs/webview/overview
> > > >
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > 
> >
>

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Tommy Williams 
Is -webkit-overflow-scrolling: touch; in this chrome webview?

I wanted chromeview as much as anyone, but I am scared of all the
fragmentation it might cause being in one version, not globally available.
On 01/11/2013 7:24 AM, "Joe Bowser"  wrote:

> I'm cautiously optimistic. Disappointed this is documented on Google's site
> and not Android's site. That piece of minutiae matters.
> On Oct 31, 2013 12:14 PM, "Carlos Santana"  wrote:
>
> > I'm going to the store to buy a Bag of KitKat to celebrate "Happy
> > Halloween" !
> >
> >
> >
> >
> >
> > On Thu, Oct 31, 2013 at 2:55 PM, Brian LeRoux  wrote:
> >
> > > omfg thank you google!
> > >
> > >
> > > On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill  > > >wrote:
> > >
> > > > Celebrate!
> > > > https://developers.google.com/chrome/mobile/docs/webview/overview
> > > >
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > 
> >
>

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread James Jong 
Awesome news!!
-James Jong

On Oct 31, 2013, at 2:34 PM, Steven Gill  wrote:

> Celebrate! https://developers.google.com/chrome/mobile/docs/webview/overview

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Joe Bowser 
I'm cautiously optimistic. Disappointed this is documented on Google's site
and not Android's site. That piece of minutiae matters.
On Oct 31, 2013 12:14 PM, "Carlos Santana"  wrote:

> I'm going to the store to buy a Bag of KitKat to celebrate "Happy
> Halloween" !
>
>
>
>
>
> On Thu, Oct 31, 2013 at 2:55 PM, Brian LeRoux  wrote:
>
> > omfg thank you google!
> >
> >
> > On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill  > >wrote:
> >
> > > Celebrate!
> > > https://developers.google.com/chrome/mobile/docs/webview/overview
> > >
> >
>
>
>
> --
> Carlos Santana
> 
>

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Carlos Santana 
I'm going to the store to buy a Bag of KitKat to celebrate "Happy
Halloween" !





On Thu, Oct 31, 2013 at 2:55 PM, Brian LeRoux  wrote:

> omfg thank you google!
>
>
> On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill  >wrote:
>
> > Celebrate!
> > https://developers.google.com/chrome/mobile/docs/webview/overview
> >
>



-- 
Carlos Santana

Re: Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Brian LeRoux 
omfg thank you google!


On Thu, Oct 31, 2013 at 11:34 AM, Steven Gill wrote:

> Celebrate!
> https://developers.google.com/chrome/mobile/docs/webview/overview
>

Re: Cordova for Ubuntu

2013-10-31 Thread Steven Gill 
Hey Maxim,

I will help you guys out on our end to integrate into cordova. I am
thinking we hold off merging in until after 3.2 gets released.

We should look into moving your guys cordova-ubuntu code into
https://git-wip-us.apache.org/repos/asf?p=cordova-ubuntu.git




On Wed, Oct 30, 2013 at 3:51 PM, Maxim Ermilov
wrote:

> > First step is to get a CLA signed w/ Apache.
> CLA&ICLA is finally signed.
>
> > In the meantime, you can create pull requests to Plugman, CLI and Plugin*
> https://github.com/apache/cordova-plugman/pull/24
> https://github.com/apache/cordova-cli/pull/47
> https://github.com/apache/cordova-plugin-console/pull/3
>
> _
> Best regards,
> Maxim Ermilov
>
>

Rejoice! "Android 4.4 (KitKat) includes a new WebView component based on the Chromium open source project"

2013-10-31 Thread Michal Mocny 
https://developers.google.com/chrome/mobile/docs/webview/overview

Also, Remote Debugging on Android:

https://developers.google.com/chrome-developer-tools/docs/remote-debugging

Chromeview has arrived in Android 4.4!!!!

2013-10-31 Thread Steven Gill 
Celebrate! https://developers.google.com/chrome/mobile/docs/webview/overview

Re: Review Request 15046: "Prepare" should not depend on the ~/.cordova/libs directory

2013-10-31 Thread Braden Shepherdson 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15046/#review27917
---

Ship it!


Ship It!

- Braden Shepherdson


On Oct. 30, 2013, 4:12 p.m., Mark Koudritsky wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15046/
> ---
> 
> (Updated Oct. 30, 2013, 4:12 p.m.)
> 
> 
> Review request for cordova.
> 
> 
> Bugs: CB-5063
> https://issues.apache.org/jira/browse/CB-5063
> 
> 
> Repository: cordova-cli
> 
> 
> Description
> ---
> 
> Currently all platform parsers (src/metadata/*_parser.js) copy
> cordova.js from util.libDirectory for each run of prepare. This results
> in errors when changing machines since the ~/.cordova/lib directory is
> not populated.
> 
> With this change all the parsers construct the project www dir by first
> copying contents of a new dir named 
> /platforms//platform_www
> (which contains cordova.js) and then the www dir from the app.
> 
> Until individual platform create scripts will be updated to create the
> platform_www dir, prepare.js checks if the platform_www exists and if
> not, creates it using cordova.js from ~/.cordova/lib.
> 
> Even after the platform create scripts are updated the check will be
> required for projects that were created using older version and don't
> yet have a platform_www dir.
> 
> 
> Diffs
> -
> 
>   spec/metadata/android_parser.spec.js 4afb52d 
>   spec/metadata/blackberry_parser.spec.js 3353eb1 
>   spec/metadata/ios_parser.spec.js 17206c6 
>   spec/metadata/windows8_parser.spec.js 5639317 
>   spec/metadata/wp7_parser.spec.js 6b69d09 
>   spec/metadata/wp8_parser.spec.js 02372cc 
>   spec/prepare.spec.js 8012924 
>   src/metadata/android_parser.js df446e1 
>   src/metadata/blackberry10_parser.js d9f71f3 
>   src/metadata/firefoxos_parser.js c3edd7b 
>   src/metadata/ios_parser.js 20e985c 
>   src/metadata/windows8_parser.js 68520fc 
>   src/metadata/wp7_parser.js b19dc32 
>   src/metadata/wp8_parser.js 3bdef16 
>   src/prepare.js 4ea22c5 
> 
> Diff: https://reviews.apache.org/r/15046/diff/
> 
> 
> Testing
> ---
> 
> npm test
> corodva platform add android
> corodva platform add ios
> corodva platform add balckberry10
> cordova prepare
> verified platfrom_www dir exists and contains the right file.
> 
> Did not test for win platforms.
> 
> 
> Thanks,
> 
> Mark Koudritsky
> 
>

Re: Cordova Plugins and CocoaPods

2013-10-31 Thread Erik Jan de Wit 
The AeroGear-PushPlugin uses cocoa pods, what would be nice is to be able to 
include a pod install into the CLI.

On 31 Oct,2013, at 16:11 , Don Coleman  wrote:

> I have some iOS code that we are converting into a Cordova plugin.
> 
> The project uses CocoaPods to manage dependencies.
> 
> Have you see any Cordova plugins that use CocoaPods  or can you think of a
> way to make CLI and CocoaPods play nice together?

Re: mobile-spec and releases: How do we test?

2013-10-31 Thread Michal Mocny 
This is awesome progress, guys, thanks for the help.

I'm going to put all the bits together and compile a list of tasks left and
write-up instructions for those who have yet to take a look.  If everyone
on the lists is still happy with the direction, I'll move those to JIRA.


On Thu, Oct 31, 2013 at 11:08 AM, David Kemp  wrote:

> I converted the couchdb reporter to the 2.0 style and added it to the repo.
> It works(hard coded config), but still needs the configuration components
> completed and some final adjustments to the data.
>
>
>
>
> On Thu, Oct 31, 2013 at 11:05 AM, Anis KADRI  wrote:
>
> > I ported the contacts plugin [1] to the new style and I found the
> > process to be more or less straightforward. I also kept the eval in
> > there but there might be a better way ?
> >
> > [1] http://goo.gl/uhnwtz
> >
> > On Wed, Oct 30, 2013 at 3:42 PM, Michal Mocny 
> wrote:
> > > Sadly, we are approaching an in-between time of moving the mobile-spec
> > > tests out of the app and into plugins.  We are still investigating the
> > best
> > > way to do this without disruption.
> > >
> > > For what its worth: several plugins now have a 'cdvtest' branch which
> > > supplies new-style tests ripped out of mobile-spec.  If you are having
> > > issues cleaning up the old style tests, take a look at the new ones (or
> > try
> > > porting yourself).
> > >
> > > I'm going to write up a doc with the summary of the state of testing
> > within
> > > a day or so given the results of this week to make it easier for you
> (and
> > > others) to pick up.
> > >
> > > -Michal
> > >
> > >
> > > On Wed, Oct 30, 2013 at 1:54 PM, Naik, Archana 
> wrote:
> > >
> > >>  Thanks Michal. You answered my questions.
> > >>
> > >>  More to elaborate on my question: I am testing amazon-fireos
> > >> port(platform) with all plug-ins using mobile-spec. I am seeing some
> > >> failures in 3.1.0 version because of test cases timing out. I am
> pretty
> > new
> > >> to cordova and still in learning phase. :) I am trying to understand
> > these
> > >> failures. Interestingly they pass on 3.0.x version.
> > >>
> > >>  Archana
> > >>
> > >>
> > >>   From: Michal Mocny 
> > >> Date: Wednesday, October 30, 2013 10:27 AM
> > >> To: "Naik, Archana" 
> > >> Cc: "dev@cordova.apache.org" , Michal Mocny <
> > >> mmo...@chromium.org>
> > >>
> > >> Subject: Re: mobile-spec and releases: How do we test?
> > >>
> > >>   May you clarify?
> > >>
> > >>  Right now, there is no formal way to test plugins, we are trying to
> > >> invent that way now.  Check out cordova-labs repo's cdvtest branch
> for a
> > >> sample app & plugin to track progress.
> > >>
> > >>  Jasmine is hosted in that sample app, but plugins will not directly
> > >> know/care.  Any testing framework which is api-compatible should work.
> >  In
> > >> practice, I'm not sure how compatible they all are, so it may very
> well
> > be
> > >> limited to jasmine -- but it does mean you can make local
> modifications
> > >> such as our CI is doing to create a custom test reporter.
> > >>
> > >>  -Michal
> > >>
> > >>
> > >> On Wed, Oct 30, 2013 at 12:57 PM, Naik, Archana 
> > wrote:
> > >>
> > >>> Hi, Guys
> > >>>
> > >>> While on this topic, I have a question: how do I test individual
> > plug-in?
> > >>> Where is the this jasmine version specified?
> > >>>
> > >>> Thanks
> > >>> Archana
> > >>>
> > >>> On 10/30/13 7:26 AM, "Michal Mocny"  wrote:
> > >>>
> > >>> >Here are some links to jasmine-2 docs since its a hard time finding
> > them:
> > >>> >
> > >>> >http://jasmine.github.io/2.0/introduction.html
> > >>> >
> > >>> >
> https://github.com/pivotal/jasmine/blob/master/release_notes/20rc5.md
> > >>> >
> > >>> >
> > >>> >On Wed, Oct 30, 2013 at 10:16 AM, Michal Mocny  >
> > >>> >wrote:
> > >>> >
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> On Tue, Oct 29, 2013 at 5:29 PM, Bryan Higgins
> > >>> >>wrote:
> > >>> >>
> > >>> >>> I just converted geolocation to the new test style [1]
> > >>> >>>
> > >>> >>> I'm happy with the process overall, and I find the jasmine 2
> tests
> > are
> > >>> >>> more
> > >>> >>> succinct.
> > >>> >>>
> > >>> >>> There are a few things worth noting:
> > >>> >>> - I kept the eval code in. At google today, it was discussed that
> > this
> > >>> >>>may
> > >>> >>> not be the best approach.
> > >>> >>> - Jasmine 2: You must hit at least one expect statement or the
> test
> > >>> >>>will
> > >>> >>> timeout even though done was called.
> > >>> >>>
> > >>> >>
> > >>> >> We could file a bug (I ran into it during setup once too), but
> > really,
> > >>> >> what is the worth of a test if there are no expect clauses?
> > >>> >>
> > >>> >>
> > >>> >>> - I did not remove the manual test page [2]. It would be great if
> > we
> > >>> >>>had a
> > >>> >>> convention for importing these. (ie test harness looks for a page
> > at
> > >>> >>> www/test/plugin-id.html and adds a link to it if it exists)
> > >>> >>>
> > >>> >>
> > >>> >> I'm going to work on a solution for this today.  The though

Cordova Plugins and CocoaPods

2013-10-31 Thread Don Coleman 
I have some iOS code that we are converting into a Cordova plugin.

The project uses CocoaPods to manage dependencies.

Have you see any Cordova plugins that use CocoaPods  or can you think of a
way to make CLI and CocoaPods play nice together?

Re: mobile-spec and releases: How do we test?

2013-10-31 Thread David Kemp 
I converted the couchdb reporter to the 2.0 style and added it to the repo.
It works(hard coded config), but still needs the configuration components
completed and some final adjustments to the data.




On Thu, Oct 31, 2013 at 11:05 AM, Anis KADRI  wrote:

> I ported the contacts plugin [1] to the new style and I found the
> process to be more or less straightforward. I also kept the eval in
> there but there might be a better way ?
>
> [1] http://goo.gl/uhnwtz
>
> On Wed, Oct 30, 2013 at 3:42 PM, Michal Mocny  wrote:
> > Sadly, we are approaching an in-between time of moving the mobile-spec
> > tests out of the app and into plugins.  We are still investigating the
> best
> > way to do this without disruption.
> >
> > For what its worth: several plugins now have a 'cdvtest' branch which
> > supplies new-style tests ripped out of mobile-spec.  If you are having
> > issues cleaning up the old style tests, take a look at the new ones (or
> try
> > porting yourself).
> >
> > I'm going to write up a doc with the summary of the state of testing
> within
> > a day or so given the results of this week to make it easier for you (and
> > others) to pick up.
> >
> > -Michal
> >
> >
> > On Wed, Oct 30, 2013 at 1:54 PM, Naik, Archana  wrote:
> >
> >>  Thanks Michal. You answered my questions.
> >>
> >>  More to elaborate on my question: I am testing amazon-fireos
> >> port(platform) with all plug-ins using mobile-spec. I am seeing some
> >> failures in 3.1.0 version because of test cases timing out. I am pretty
> new
> >> to cordova and still in learning phase. :) I am trying to understand
> these
> >> failures. Interestingly they pass on 3.0.x version.
> >>
> >>  Archana
> >>
> >>
> >>   From: Michal Mocny 
> >> Date: Wednesday, October 30, 2013 10:27 AM
> >> To: "Naik, Archana" 
> >> Cc: "dev@cordova.apache.org" , Michal Mocny <
> >> mmo...@chromium.org>
> >>
> >> Subject: Re: mobile-spec and releases: How do we test?
> >>
> >>   May you clarify?
> >>
> >>  Right now, there is no formal way to test plugins, we are trying to
> >> invent that way now.  Check out cordova-labs repo's cdvtest branch for a
> >> sample app & plugin to track progress.
> >>
> >>  Jasmine is hosted in that sample app, but plugins will not directly
> >> know/care.  Any testing framework which is api-compatible should work.
>  In
> >> practice, I'm not sure how compatible they all are, so it may very well
> be
> >> limited to jasmine -- but it does mean you can make local modifications
> >> such as our CI is doing to create a custom test reporter.
> >>
> >>  -Michal
> >>
> >>
> >> On Wed, Oct 30, 2013 at 12:57 PM, Naik, Archana 
> wrote:
> >>
> >>> Hi, Guys
> >>>
> >>> While on this topic, I have a question: how do I test individual
> plug-in?
> >>> Where is the this jasmine version specified?
> >>>
> >>> Thanks
> >>> Archana
> >>>
> >>> On 10/30/13 7:26 AM, "Michal Mocny"  wrote:
> >>>
> >>> >Here are some links to jasmine-2 docs since its a hard time finding
> them:
> >>> >
> >>> >http://jasmine.github.io/2.0/introduction.html
> >>> >
> >>> >https://github.com/pivotal/jasmine/blob/master/release_notes/20rc5.md
> >>> >
> >>> >
> >>> >On Wed, Oct 30, 2013 at 10:16 AM, Michal Mocny 
> >>> >wrote:
> >>> >
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Tue, Oct 29, 2013 at 5:29 PM, Bryan Higgins
> >>> >>wrote:
> >>> >>
> >>> >>> I just converted geolocation to the new test style [1]
> >>> >>>
> >>> >>> I'm happy with the process overall, and I find the jasmine 2 tests
> are
> >>> >>> more
> >>> >>> succinct.
> >>> >>>
> >>> >>> There are a few things worth noting:
> >>> >>> - I kept the eval code in. At google today, it was discussed that
> this
> >>> >>>may
> >>> >>> not be the best approach.
> >>> >>> - Jasmine 2: You must hit at least one expect statement or the test
> >>> >>>will
> >>> >>> timeout even though done was called.
> >>> >>>
> >>> >>
> >>> >> We could file a bug (I ran into it during setup once too), but
> really,
> >>> >> what is the worth of a test if there are no expect clauses?
> >>> >>
> >>> >>
> >>> >>> - I did not remove the manual test page [2]. It would be great if
> we
> >>> >>>had a
> >>> >>> convention for importing these. (ie test harness looks for a page
> at
> >>> >>> www/test/plugin-id.html and adds a link to it if it exists)
> >>> >>>
> >>> >>
> >>> >> I'm going to work on a solution for this today.  The thought is that
> >>> the
> >>> >> plugin has a single module that can define all auto/manual tests,
> and
> >>> >>the
> >>> >> test-harness choses which to display where.
> >>> >>
> >>> >>
> >>> >>>
> >>> >>> [1]
> >>> >>>
> >>> >>>
> >>> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git
> >>> >>>;a=commit;h=075850a460d8171a04809cf6317fb4c4ef998603
> >>> >>> [2]
> >>> >>>
> >>> >>>
> >>> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git
> >>>
> >>>
> >>>;a=blob;f=test/manual.html;h=6ec2eed03e18c2efaa8710094d60930bb32227ba;hb
> >>> >>>=459a01c01e8dfa2

Re: mobile-spec and releases: How do we test?

2013-10-31 Thread Anis KADRI 
I ported the contacts plugin [1] to the new style and I found the
process to be more or less straightforward. I also kept the eval in
there but there might be a better way ?

[1] http://goo.gl/uhnwtz

On Wed, Oct 30, 2013 at 3:42 PM, Michal Mocny  wrote:
> Sadly, we are approaching an in-between time of moving the mobile-spec
> tests out of the app and into plugins.  We are still investigating the best
> way to do this without disruption.
>
> For what its worth: several plugins now have a 'cdvtest' branch which
> supplies new-style tests ripped out of mobile-spec.  If you are having
> issues cleaning up the old style tests, take a look at the new ones (or try
> porting yourself).
>
> I'm going to write up a doc with the summary of the state of testing within
> a day or so given the results of this week to make it easier for you (and
> others) to pick up.
>
> -Michal
>
>
> On Wed, Oct 30, 2013 at 1:54 PM, Naik, Archana  wrote:
>
>>  Thanks Michal. You answered my questions.
>>
>>  More to elaborate on my question: I am testing amazon-fireos
>> port(platform) with all plug-ins using mobile-spec. I am seeing some
>> failures in 3.1.0 version because of test cases timing out. I am pretty new
>> to cordova and still in learning phase. :) I am trying to understand these
>> failures. Interestingly they pass on 3.0.x version.
>>
>>  Archana
>>
>>
>>   From: Michal Mocny 
>> Date: Wednesday, October 30, 2013 10:27 AM
>> To: "Naik, Archana" 
>> Cc: "dev@cordova.apache.org" , Michal Mocny <
>> mmo...@chromium.org>
>>
>> Subject: Re: mobile-spec and releases: How do we test?
>>
>>   May you clarify?
>>
>>  Right now, there is no formal way to test plugins, we are trying to
>> invent that way now.  Check out cordova-labs repo's cdvtest branch for a
>> sample app & plugin to track progress.
>>
>>  Jasmine is hosted in that sample app, but plugins will not directly
>> know/care.  Any testing framework which is api-compatible should work.  In
>> practice, I'm not sure how compatible they all are, so it may very well be
>> limited to jasmine -- but it does mean you can make local modifications
>> such as our CI is doing to create a custom test reporter.
>>
>>  -Michal
>>
>>
>> On Wed, Oct 30, 2013 at 12:57 PM, Naik, Archana  wrote:
>>
>>> Hi, Guys
>>>
>>> While on this topic, I have a question: how do I test individual plug-in?
>>> Where is the this jasmine version specified?
>>>
>>> Thanks
>>> Archana
>>>
>>> On 10/30/13 7:26 AM, "Michal Mocny"  wrote:
>>>
>>> >Here are some links to jasmine-2 docs since its a hard time finding them:
>>> >
>>> >http://jasmine.github.io/2.0/introduction.html
>>> >
>>> >https://github.com/pivotal/jasmine/blob/master/release_notes/20rc5.md
>>> >
>>> >
>>> >On Wed, Oct 30, 2013 at 10:16 AM, Michal Mocny 
>>> >wrote:
>>> >
>>> >>
>>> >>
>>> >>
>>> >> On Tue, Oct 29, 2013 at 5:29 PM, Bryan Higgins
>>> >>wrote:
>>> >>
>>> >>> I just converted geolocation to the new test style [1]
>>> >>>
>>> >>> I'm happy with the process overall, and I find the jasmine 2 tests are
>>> >>> more
>>> >>> succinct.
>>> >>>
>>> >>> There are a few things worth noting:
>>> >>> - I kept the eval code in. At google today, it was discussed that this
>>> >>>may
>>> >>> not be the best approach.
>>> >>> - Jasmine 2: You must hit at least one expect statement or the test
>>> >>>will
>>> >>> timeout even though done was called.
>>> >>>
>>> >>
>>> >> We could file a bug (I ran into it during setup once too), but really,
>>> >> what is the worth of a test if there are no expect clauses?
>>> >>
>>> >>
>>> >>> - I did not remove the manual test page [2]. It would be great if we
>>> >>>had a
>>> >>> convention for importing these. (ie test harness looks for a page at
>>> >>> www/test/plugin-id.html and adds a link to it if it exists)
>>> >>>
>>> >>
>>> >> I'm going to work on a solution for this today.  The thought is that
>>> the
>>> >> plugin has a single module that can define all auto/manual tests, and
>>> >>the
>>> >> test-harness choses which to display where.
>>> >>
>>> >>
>>> >>>
>>> >>> [1]
>>> >>>
>>> >>>
>>> >>>
>>> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git
>>> >>>;a=commit;h=075850a460d8171a04809cf6317fb4c4ef998603
>>> >>> [2]
>>> >>>
>>> >>>
>>> >>>
>>> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git
>>>
>>> >>>;a=blob;f=test/manual.html;h=6ec2eed03e18c2efaa8710094d60930bb32227ba;hb
>>> >>>=459a01c01e8dfa2a688d25483bb48c46d8e2
>>> >>>
>>> >>>
>>> >>> On Tue, Oct 15, 2013 at 12:50 PM, David Kemp 
>>> >>>wrote:
>>> >>>
>>> >>> > In spite of that fact that it needs a tooling change, I like the
>>> >>>added
>>> >>> >  tag / prepare steps.
>>> >>> > The tooling change should be small and it means no runtime impact on
>>> >>> apps.
>>> >>> >
>>> >>> > I love the approach - a very positive step to cleaning up testing.
>>> >>> >
>>> >>> > David Kemp
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> > On Tue, Oct 15, 2013 at 12:18 PM, Michal Mocny >> >
>>> >>> > wrote:
>>> >>>

Re: So, what to do about storage issues?

2013-10-31 Thread Andrew Grieve 
Great! Thanks for following up!


On Wed, Oct 30, 2013 at 5:26 AM, Dick Van den Brink <
d_vandenbr...@outlook.com> wrote:

> A follow up on the issue, I had some time to check it today! Because we
> are still on cordova 3.0.0 I made a custom build with the fix and it works
> like a charm! Thanks :)
>
> To: dev@cordova.apache.org
> From: d_vandenbr...@outlook.com
> Subject: RE: So, what to do about storage issues?
> Date: Fri, 25 Oct 2013 13:55:26 +0700
>
>
>
>
>
>
>
> Wow, that would be awesome! Thanks! Hope I have time to check it next
> week! Thanks!
>
>
>
> Sent from my Windows Phone
>
>
>
> From:
> Andrew Grieve
>
> Sent:
> 10/24/2013 22:12
>
> To:
> dev
>
> Subject:
> Re: So, what to do about storage issues?
>
>
>
>
>
> Made a discovery today that Cordova's Quota logic was wrong. Filed this as
>
> https://issues.apache.org/jira/browse/CB-5193 and fixed it :). Multiple
>
> databases should work fine starting in 3.2 / 2.9.1.
>
>
>
>
>
>
>