[GitHub] cordova-android pull request: Update tests.java

[AppCanOpenSource]

Github user AppCanOpenSource commented on the pull request:

https://github.com/apache/cordova-android/pull/112#issuecomment-51561066
  
Just for test


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

[GitHub] cordova-android pull request: Update tests.java

[AppCanOpenSource]

GitHub user AppCanOpenSource opened a pull request:

https://github.com/apache/cordova-android/pull/112

Update tests.java



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

$ git pull https://github.com/AppCanOpenSource/cordova-android patch-1

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

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


commit 8826b428d25bf123006970e05f091c48d8cff67b
Author: AppCan 
Date:   2014-08-08T03:59:25Z

Update tests.java




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

[GitHub] cordova-lib pull request: Allow plugin modules to be .json files

[joseph-onsip]

GitHub user joseph-onsip opened a pull request:

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

Allow plugin modules to be .json files

This lets projects include JSON files as they would in Node.js

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

$ git pull https://github.com/joseph-onsip/cordova-lib exportJSON

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

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


commit 28b372e1952131e18dcfa679694bd523a3e46e20
Author: Joseph Frazier 
Date:   2014-08-07T14:06:39Z

Allow plugin modules to be .json files




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

Re: Plugins Release blog post draft

[Andrew Grieve]

LGTM


On Thu, Aug 7, 2014 at 7:17 PM, Steven Gill  wrote:

> Please review and send PRs for changes. I can also add you to the repo if
> you want to edit directly on github and not worry about the PR.
>
>
> https://github.com/cordova/apache-blog-posts/blob/master/2014-08-08-plugins-release.md
>

Plugins Release blog post draft

[Steven Gill]

Please review and send PRs for changes. I can also add you to the repo if
you want to edit directly on github and not worry about the PR.

https://github.com/cordova/apache-blog-posts/blob/master/2014-08-08-plugins-release.md

RE: platform switches for Windows Universal Apps

[Parashuram Narasimhan (MS OPEN TECH)]

It would be great if we have a unified format across all platforms. It would be 
great if these options can also be specified in config.xml - that would also 
help IDEs. 

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Thursday, August 7, 2014 3:32 PM
To: dev@cordova.apache.org
Subject: Re: platform switches for Windows Universal Apps

cordova run ios --retina --64bit --family ipad

cordova run android --target=X

We need to clean this up I think ...



@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 2:58 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> I think we should also ensure use reuse concepts that already exist in 
> other platforms. How are phone vs tablet options specified for Android 
> and iOS on the command line? How do we plan to do it in the future ?
>
> -Original Message-
> From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> Sent: Thursday, August 7, 2014 5:25 AM
> To: dev@cordova.apache.org
> Subject: platform switches for Windows Universal Apps
>
> New Windows platform template supports standard Windows apps as well 
> as Windows Phone 8.1 apps. As a developer I need an option to specify 
> which target I should run when doing 'cordova run/emulate' (run phone 
> version on the device/emulator or run windows store app).
>
> Current draft implementation uses '-store' and '-phone' switches but 
> we should discuss final names for them. Here are a few alternatives.  
> Thoughts?
>
> --tablet
> --handset or --phone
> or --targetDevice="tablet, handset" <- similar to how we define target 
> chip architecture
>
> Thx!
> Sergey
>

[GitHub] cordova-coho pull request: Removed references to -dev branch

[asfgit]

Github user asfgit closed the pull request at:

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


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

Re: platform switches for Windows Universal Apps

[Jesse]

cordova run ios --retina --64bit --family ipad

cordova run android --target=X

We need to clean this up I think ...



@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 2:58 PM, Parashuram Narasimhan (MS OPEN TECH) <
panar...@microsoft.com> wrote:

> I think we should also ensure use reuse concepts that already exist in
> other platforms. How are phone vs tablet options specified for Android and
> iOS on the command line? How do we plan to do it in the future ?
>
> -Original Message-
> From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> Sent: Thursday, August 7, 2014 5:25 AM
> To: dev@cordova.apache.org
> Subject: platform switches for Windows Universal Apps
>
> New Windows platform template supports standard Windows apps as well as
> Windows Phone 8.1 apps. As a developer I need an option to specify which
> target I should run when doing 'cordova run/emulate' (run phone version on
> the device/emulator or run windows store app).
>
> Current draft implementation uses '-store' and '-phone' switches but we
> should discuss final names for them. Here are a few alternatives.  Thoughts?
>
> --tablet
> --handset or --phone
> or --targetDevice="tablet, handset" <- similar to how we define target
> chip architecture
>
> Thx!
> Sergey
>

RE: platform switches for Windows Universal Apps

[Parashuram Narasimhan (MS OPEN TECH)]

I think we should also ensure use reuse concepts that already exist in other 
platforms. How are phone vs tablet options specified for Android and iOS on the 
command line? How do we plan to do it in the future ?

-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] 
Sent: Thursday, August 7, 2014 5:25 AM
To: dev@cordova.apache.org
Subject: platform switches for Windows Universal Apps

New Windows platform template supports standard Windows apps as well as Windows 
Phone 8.1 apps. As a developer I need an option to specify which target I 
should run when doing 'cordova run/emulate' (run phone version on the 
device/emulator or run windows store app).

Current draft implementation uses '-store' and '-phone' switches but we should 
discuss final names for them. Here are a few alternatives.  Thoughts?

--tablet
--handset or --phone
or --targetDevice="tablet, handset" <- similar to how we define target chip 
architecture

Thx!
Sergey

Re: Plugman poor documentation of adduser

[Steven Gill]

Hey Jan,

Issue: https://issues.apache.org/jira/browse/CB-7274

I will spend some time either tomorrow or early next week looking into this
issue. Can you add any additional details to the issue I created?




On Thu, Aug 7, 2014 at 11:57 AM, Jan Velecký  wrote:

> @Dick Van den Brink: I'm happy, that I'm not only man, who have this issue.
> :-)
>
> @Jesse:
> Tested in Git Bash. Result is a same:
> $ plugman adduser
> > Username: Velda
> > Username: Velda
> > Username: Velda
> > Username:
> and on and on
>
> When I type Velda and enter it for 20th, it will became dull.
>
> Well, for me, plugman have too deep untransparent dependencies, that I'm
> scared of. I spent nearly half an hour with unsuccessful finding
> corresponding code, but then I realized I haven't stomach for it. :-)
>
> Thanks for reply
>
>
> -- Původní zpráva --
> Od: Jesse 
> Komu: dev@cordova.apache.org 
> Datum: 7. 8. 2014 20:46:04
> Předmět: Re: Plugman poor documentation of adduser
>
> "Also, try running it from a git-bash and NOT a command prompt, that may be
> the issue you are having in windows.
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Aug 7, 2014 at 11:44 AM, Jesse  wrote:
>
> > You should see this:
> > $ plugman adduser
> > Username: purplecabbage
> > Password:
> > Email: purplecabb...@gmail.com
> > user added
> >
> > Notes:
> > - Be sure to remember your password, as there does not currently appear
> to
> > be a way to change it.
> > - There is no documentation
> > - Ideally this workflow should be doable from the plugin site, which
> > currently has no concept of people at all, other than listing
> 'maintainer'
> > in every plugin. ( issue for this [1] )
> > - Please help us to improve this, anyone!?
> >
> >
> > [1] https://issues.apache.org/jira/browse/CB-7246
> >
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Thu, Aug 7, 2014 at 11:26 AM, Dick Van den Brink <
> > d_vandenbr...@outlook.com> wrote:
> >
> >> Had the same issue last time I tried… so sorry I don't have a solution ☹
> >>
> >>
> >>
> >>
> >>
> >>
> >> Verzonden met Windows Mail
> >>
> >>
> >>
> >>
> >>
> >> Van: Jan Velecký
> >> Verzonden: ‎donderdag‎ ‎7‎ ‎augustus‎ ‎2014 ‎20‎:‎20
> >> Aan: dev@cordova.apache.org
> >>
> >>
> >>
> >>
> >>
> >> Anybody there, who use plugman...?
> >>
> >>
> >> -- Původní zpráva --
> >>
> >> Od: Jan Velecký 
> >>
> >> Komu: dev@cordova.apache.org
> >>
> >> Datum: 6. 8. 2014 17:34:01
> >>
> >> Předmět: Plugman poor documentation of adduser
> >>
> >>
> >> "Hello,
> >>
> >> how can I add user to Cordova plugin repository to be able to upload
> >> plugin?
> >>
> >> When I type plugman adduser into cmd (Windows 7 64 bit), it wanna
> Username
> >>
> >> from me...
> >>
> >> Probably new username (documentation of plugman is so poor), but I can
> >> type
> >>
> >> anything and it wanna username again, I can type username (Velda),
> e-mail
> >>
> >> and nothing.
> >>
> >>
> >>
> >> Thanks for help."
> >>
> >
> >"
>

[GitHub] cordova-plugin-vibration pull request: Cb 7138

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-vibration/pull/17


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

[GitHub] cordova-plugin-vibration pull request: CB-6966 Ported Vibration au...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-statusbar pull request: CB-7195 ported statusbar te...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-splashscreen pull request: CB-7196 port splashscree...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-splashscreen/pull/22


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

[GitHub] cordova-plugin-network-information pull request: CB-6964 port netw...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-network-information/pull/14


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

[GitHub] cordova-plugin-network-information pull request: [CB-7166] Fix nav...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-network-information/pull/13


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

[GitHub] cordova-plugin-media-capture pull request: CB-6959 ported capture ...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-globalization pull request: Port globalization test...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-globalization/pull/16


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

[GitHub] cordova-plugin-geolocation pull request: CB- 5114 Windows 8.1 - Us...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-geolocation pull request: Removing incorrectly adde...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-geolocation/pull/5


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

[GitHub] cordova-plugin-file pull request: CB-7094 Ported File manual tests

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-file-transfer pull request: CB-6961 port file-trans...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-dialogs pull request: CB-6965 ported notification t...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-dialogs/pull/23


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

[GitHub] cordova-plugin-device pull request: CB-7262 Adds support for unive...

[asfgit]

Github user asfgit closed the pull request at:

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


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

Re: [VOTE] Plugins Release

[Andrew Grieve]

+1

* Confirmed sigs & hashes with `coho verify-archive`
* Verified sha1s match tags with `coho verify-tags`



On Thu, Aug 7, 2014 at 10:38 AM, Ian Clelland 
wrote:

> +1
>
> * Verified all archives
> * Verified that the tags are correct, and point to the hashes listed
> * Verified contents of archives against public repositories at the listed
> hashes
> * Ran mobile-spec on iOS (3.5.0 and master)
> * Ran mobile-spec on Android (3.5.1, 4.0.x and master)
>
>
> Note: Three plugins did not work for me initially with cordova-ios
> 3.6.0-dev: Camera, Device-Orientation and Geolocation, since the
> CoreLocation framework has been removed from cordova-ios, and, for some
> reason, plugman didn't add it on prepare.
>
> However, they still work correctly with the released version of
> cordova-ios, and with master if you add the framework yourself. I suspect
> that this is an issue with plugman, though (and possibly just my install),
> and not the plugins themselves, as they seem to declare the dependency
> correctly.
>
>
> On Wed, Aug 6, 2014 at 10:39 PM, Steven Gill 
> wrote:
>
> > Please review and vote on the release of this plugins release.
> >
> > Release issue: https://issues.apache.org/jira/browse/CB-7244
> >
> > The plugins have been published to
> > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7244/
> >
> > The packages were published from their corresponding git tags:
> > cordova-plugin-battery-status: 0.2.10 (490888663e)
> > cordova-plugin-camera: 0.3.1 (823eb5d27a)
> > cordova-plugin-console: 0.2.10 (361a73573b)
> > cordova-plugin-contacts: 0.2.12 (5148d5ccd8)
> > cordova-plugin-device: 0.2.11 (efd903fe88)
> >
> >
> > cordova-plugin-device-motion: 0.2.9 (52c3348b18)
> > cordova-plugin-device-orientation: 0.3.8 (fc8b28414f)
> > cordova-plugin-dialogs: 0.2.9 (99e8f4c530)
> > cordova-plugin-file: 1.3.0 (149044114f)
> > cordova-plugin-file-transfer: 0.4.5 (a071c5bf9a)
> >
> >
> > cordova-plugin-geolocation: 0.3.9 (438f50f8c4)
> > cordova-plugin-globalization: 0.3.0 (bc3a4053ef)
> > cordova-plugin-inappbrowser: 0.5.1 (c37b08e038)
> > cordova-plugin-media: 0.2.12 (52ca8690db)
> > cordova-plugin-media-capture: 0.3.2 (373d161668)
> >
> >
> > cordova-plugin-network-information: 0.2.11 (00b71a7cd9)
> > cordova-plugin-splashscreen: 0.3.2 (3b58cd69b3)
> > cordova-plugin-statusbar: 0.1.7 (2ba62cb92c)
> > cordova-plugin-vibration: 0.3.10 (4a4dc85a35)
> >
> >
> > The blog post will be up tomorrow for review.
> >
> > Upon a successful vote I will upload the archives to dist/, upload
> > them to the Plugins Registry, and post the corresponding blog post.
> >
> > Voting guidelines:
> >
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Used `license-checker` to ensure all dependencies have
> > Apache-compatible licenses
> > * Ensured continuous build was green when repos were tagged
> >
>

[GitHub] cordova-plugin-device-orientation pull request: CB-6960

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-device-orientation/pull/11


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

[GitHub] cordova-plugin-device-motion pull request: CB-7160 port tests for ...

[purplecabbage]

Github user purplecabbage commented on the pull request:


https://github.com/apache/cordova-plugin-device-motion/pull/16#issuecomment-51522122
  
This is fully merged, not sure why it did not close.


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

[GitHub] cordova-lib pull request: CB-7255 Fixed writing plist unescaped

[asfgit]

Github user asfgit closed the pull request at:

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


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

Re: W3C Battery Feedback request

[Ian Clelland]

That spec *is* the one under discussion, as far as I can tell -- it's the
in-progress update to the old, busted, synchronous version that Joe very
rightfully bashed. There may still be other issues with it, but this is the
one that we should be commenting on.


On Thu, Aug 7, 2014 at 3:01 PM, Brian LeRoux  wrote:

> Plot thickens. Chrome has an experimental promises based API:
>
> https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html
>
> This is implementable.
>
>
> On Thu, Aug 7, 2014 at 11:08 AM, Brian LeRoux  wrote:
>
> > ya, idk, even those I have problems with (meaningful strings)
> >
> > current spec has lots of listeners for various events though
> >
> >
> >
> > On Thu, Aug 7, 2014 at 11:00 AM, Jesse  wrote:
> >
> >> addEventListener or nothing
> >> anyone can wrap it in a promise if they want
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >>
> >> On Thu, Aug 7, 2014 at 10:57 AM, Brian LeRoux  wrote:
> >>
> >> > bonus: https://gist.github.com/brianleroux/cc8b4adc0f9f0b7df654
> >> >
> >> > (I have no idea if this is the best way…not being a fan promises but
> >> > willing to cede they have won this round.)
> >> >
> >> >
> >> > On Thu, Aug 7, 2014 at 10:50 AM, Brian LeRoux  wrote:
> >> >
> >> > > ah, sometimes you have read inbetween the lines w/ Joe's messaging
> >> > >
> >> > > he's right, it is broken, and he did state why: its a blocking API
> >> > >
> >> > > our feedback would be perhaps received better with a concrete
> >> proposal:
> >> > > throw out the current spec and rewrite it using DOM promises or
> >> whatever
> >> > > flavor of the month we have for async querying of data. the current
> >> > > blocking API is not implementable by our bridge (async) so we can't
> do
> >> > much
> >> > > with it. ideally all web apis are async anyhow. ideally spec writers
> >> know
> >> > > this about the web and browsers, but alas.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On Thu, Aug 7, 2014 at 8:06 AM, Lisa Seacat DeLuca <
> >> ldel...@us.ibm.com>
> >> > > wrote:
> >> > >
> >> > >> Joe~
> >> > >>
> >> > >> Thank you for responding.  I just finished up sharing our thoughts
> on
> >> > the
> >> > >> Device APIs Working Group status call.  They appreciate the overall
> >> "it
> >> > is
> >> > >> broken" feedback but could really benefit from a concrete proposal
> on
> >> > how
> >> > >> to improve the battery specification.  Do you, or anyone else from
> >> the
> >> > >> Cordova team, want to take a stab at putting together a formal
> >> > >> proposal/recommendation that I can bring back to the DAP team?
>  This
> >> is
> >> > an
> >> > >> opportunity for us to help shape the spec!
> >> > >>
> >> > >> Here's a link to the current specification:
> >> > >> http://www.w3.org/TR/battery-status/
> >> > >>
> >> > >>
> >> > >> Lisa
> >> > >>
> >> > >> Lisa Seacat DeLuca
> >> > >> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> >> > >>  | | *ldel...@us.ibm.com* 
> |
> >> > >> *lisaseacat.com*  | [image: follow
> >> > >> @LisaSeacat on twitter] |
> [image:
> >> > >> follow Lisa Seacat DeLuca on linkedin]
> >> > >> 
> >> > >>
> >> > >>
> >> > >>
> >> > >> From:Joe Bowser 
> >> > >> To:dev 
> >> > >> Date:08/06/2014 02:45 PM
> >> > >> Subject:Re: W3C Battery Feedback request
> >> > >> --
> >> > >>
> >> > >>
> >> > >>
> >> > >> The spec is flawed in that there's no way we could implement it as
> it
> >> > >> stands. The spec needs to be reworked to be more event driven and
> >> > >> asynchronous.   Right now it's too much like device with everything
> >> up
> >> > >> front.
> >> > >>
> >> > >> This is all based on memory, but the spec was seriously broken the
> >> last
> >> > >> time I looked.
> >> > >> On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca" 
> >> > wrote:
> >> > >>
> >> > >> > I sent a note back in June asking if anyone had any feedback for
> >> the
> >> > >> > Device API's Working Group for the battery concerns that we had
> >> > >> previously
> >> > >> > voiced related to the battery spec.
> >> > >> >
> >> > >> >
> >> > >>
> >> >
> >>
> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results
> >> > >> >
> >> > >> > I need to update the DAP team on Thursday with any thoughts
> Cordova
> >> > has
> >> > >> so
> >> > >> > if anyone has any feedback please reply asap.  The link to the
> >> first
> >> > >> email
> >> > >> > has the questions from the DAP team to Cordova.
> >> > >> >
> >> > >> > Thank you!
> >> > >> >
> >> > >> >
> >> > >> > Lisa
> >> > >> >
> >> > >> > Lisa Seacat DeLuca
> >> > >> > Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> >> > >> >  | | *

[GitHub] cordova-plugin-contacts pull request: CB-7148 Ported contacts test...

[asfgit]

Github user asfgit closed the pull request at:

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


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

Re: W3C Battery Feedback request

[Brian LeRoux]

Plot thickens. Chrome has an experimental promises based API:

https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html

This is implementable.


On Thu, Aug 7, 2014 at 11:08 AM, Brian LeRoux  wrote:

> ya, idk, even those I have problems with (meaningful strings)
>
> current spec has lots of listeners for various events though
>
>
>
> On Thu, Aug 7, 2014 at 11:00 AM, Jesse  wrote:
>
>> addEventListener or nothing
>> anyone can wrap it in a promise if they want
>>
>> @purplecabbage
>> risingj.com
>>
>>
>> On Thu, Aug 7, 2014 at 10:57 AM, Brian LeRoux  wrote:
>>
>> > bonus: https://gist.github.com/brianleroux/cc8b4adc0f9f0b7df654
>> >
>> > (I have no idea if this is the best way…not being a fan promises but
>> > willing to cede they have won this round.)
>> >
>> >
>> > On Thu, Aug 7, 2014 at 10:50 AM, Brian LeRoux  wrote:
>> >
>> > > ah, sometimes you have read inbetween the lines w/ Joe's messaging
>> > >
>> > > he's right, it is broken, and he did state why: its a blocking API
>> > >
>> > > our feedback would be perhaps received better with a concrete
>> proposal:
>> > > throw out the current spec and rewrite it using DOM promises or
>> whatever
>> > > flavor of the month we have for async querying of data. the current
>> > > blocking API is not implementable by our bridge (async) so we can't do
>> > much
>> > > with it. ideally all web apis are async anyhow. ideally spec writers
>> know
>> > > this about the web and browsers, but alas.
>> > >
>> > >
>> > >
>> > >
>> > > On Thu, Aug 7, 2014 at 8:06 AM, Lisa Seacat DeLuca <
>> ldel...@us.ibm.com>
>> > > wrote:
>> > >
>> > >> Joe~
>> > >>
>> > >> Thank you for responding.  I just finished up sharing our thoughts on
>> > the
>> > >> Device APIs Working Group status call.  They appreciate the overall
>> "it
>> > is
>> > >> broken" feedback but could really benefit from a concrete proposal on
>> > how
>> > >> to improve the battery specification.  Do you, or anyone else from
>> the
>> > >> Cordova team, want to take a stab at putting together a formal
>> > >> proposal/recommendation that I can bring back to the DAP team?  This
>> is
>> > an
>> > >> opportunity for us to help shape the spec!
>> > >>
>> > >> Here's a link to the current specification:
>> > >> http://www.w3.org/TR/battery-status/
>> > >>
>> > >>
>> > >> Lisa
>> > >>
>> > >> Lisa Seacat DeLuca
>> > >> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
>> > >>  | | *ldel...@us.ibm.com*  |
>> > >> *lisaseacat.com*  | [image: follow
>> > >> @LisaSeacat on twitter] | [image:
>> > >> follow Lisa Seacat DeLuca on linkedin]
>> > >> 
>> > >>
>> > >>
>> > >>
>> > >> From:Joe Bowser 
>> > >> To:dev 
>> > >> Date:08/06/2014 02:45 PM
>> > >> Subject:Re: W3C Battery Feedback request
>> > >> --
>> > >>
>> > >>
>> > >>
>> > >> The spec is flawed in that there's no way we could implement it as it
>> > >> stands. The spec needs to be reworked to be more event driven and
>> > >> asynchronous.   Right now it's too much like device with everything
>> up
>> > >> front.
>> > >>
>> > >> This is all based on memory, but the spec was seriously broken the
>> last
>> > >> time I looked.
>> > >> On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca" 
>> > wrote:
>> > >>
>> > >> > I sent a note back in June asking if anyone had any feedback for
>> the
>> > >> > Device API's Working Group for the battery concerns that we had
>> > >> previously
>> > >> > voiced related to the battery spec.
>> > >> >
>> > >> >
>> > >>
>> >
>> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results
>> > >> >
>> > >> > I need to update the DAP team on Thursday with any thoughts Cordova
>> > has
>> > >> so
>> > >> > if anyone has any feedback please reply asap.  The link to the
>> first
>> > >> email
>> > >> > has the questions from the DAP team to Cordova.
>> > >> >
>> > >> > Thank you!
>> > >> >
>> > >> >
>> > >> > Lisa
>> > >> >
>> > >> > Lisa Seacat DeLuca
>> > >> > Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
>> > >> >  | | *ldel...@us.ibm.com* 
>> |
>> > >> > *lisaseacat.com*  | [image: follow
>> > >> > @LisaSeacat on twitter] |
>> [image:
>> > >> > follow Lisa Seacat DeLuca on linkedin]
>> > >> > 
>> > >> >
>> > >> >
>> > >>
>> > >>
>> > >
>> >
>>
>
>

[GitHub] cordova-plugin-camera pull request: CB-6958 ported camera tests to...

[asfgit]

Github user asfgit closed the pull request at:

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


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

Re: Plugman poor documentation of adduser

[Jan Velecký]

@Dick Van den Brink: I'm happy, that I'm not only man, who have this issue. 
:-)

@Jesse:
Tested in Git Bash. Result is a same: 
$ plugman adduser
> Username: Velda
> Username: Velda
> Username: Velda
> Username:
and on and on

When I type Velda and enter it for 20th, it will became dull.

Well, for me, plugman have too deep untransparent dependencies, that I'm 
scared of. I spent nearly half an hour with unsuccessful finding 
corresponding code, but then I realized I haven't stomach for it. :-)

Thanks for reply


-- Původní zpráva --
Od: Jesse 
Komu: dev@cordova.apache.org 
Datum: 7. 8. 2014 20:46:04
Předmět: Re: Plugman poor documentation of adduser

"Also, try running it from a git-bash and NOT a command prompt, that may be
the issue you are having in windows.

@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 11:44 AM, Jesse  wrote:

> You should see this:
> $ plugman adduser
> Username: purplecabbage
> Password:
> Email: purplecabb...@gmail.com
> user added
>
> Notes:
> - Be sure to remember your password, as there does not currently appear to
> be a way to change it.
> - There is no documentation
> - Ideally this workflow should be doable from the plugin site, which
> currently has no concept of people at all, other than listing 'maintainer'
> in every plugin. ( issue for this [1] )
> - Please help us to improve this, anyone!?
>
>
> [1] https://issues.apache.org/jira/browse/CB-7246
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Aug 7, 2014 at 11:26 AM, Dick Van den Brink <
> d_vandenbr...@outlook.com> wrote:
>
>> Had the same issue last time I tried… so sorry I don't have a solution ☹
>>
>>
>>
>>
>>
>>
>> Verzonden met Windows Mail
>>
>>
>>
>>
>>
>> Van: Jan Velecký
>> Verzonden: ‎donderdag‎ ‎7‎ ‎augustus‎ ‎2014 ‎20‎:‎20
>> Aan: dev@cordova.apache.org
>>
>>
>>
>>
>>
>> Anybody there, who use plugman...?
>>
>>
>> -- Původní zpráva --
>>
>> Od: Jan Velecký 
>>
>> Komu: dev@cordova.apache.org
>>
>> Datum: 6. 8. 2014 17:34:01
>>
>> Předmět: Plugman poor documentation of adduser
>>
>>
>> "Hello,
>>
>> how can I add user to Cordova plugin repository to be able to upload
>> plugin?
>>
>> When I type plugman adduser into cmd (Windows 7 64 bit), it wanna 
Username
>>
>> from me...
>>
>> Probably new username (documentation of plugman is so poor), but I can
>> type
>>
>> anything and it wanna username again, I can type username (Velda), e-mail
>>
>> and nothing.
>>
>>
>>
>> Thanks for help."
>>
>
>"

Re: Plugman poor documentation of adduser

[Jesse]

Also, try running it from a git-bash and NOT a command prompt, that may be
the issue you are having in windows.

@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 11:44 AM, Jesse  wrote:

> You should see this:
> $ plugman adduser
> Username: purplecabbage
> Password:
> Email: purplecabb...@gmail.com
> user added
>
> Notes:
> - Be sure to remember your password, as there does not currently appear to
> be a way to change it.
> - There is no documentation
> - Ideally this workflow should be doable from the plugin site, which
> currently has no concept of people at all, other than listing 'maintainer'
> in every plugin. ( issue for this [1] )
> - Please help us to improve this, anyone!?
>
>
> [1] https://issues.apache.org/jira/browse/CB-7246
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Aug 7, 2014 at 11:26 AM, Dick Van den Brink <
> d_vandenbr...@outlook.com> wrote:
>
>> Had the same issue last time I tried… so sorry I don't have a solution ☹
>>
>>
>>
>>
>>
>>
>> Verzonden met Windows Mail
>>
>>
>>
>>
>>
>> Van: Jan Velecký
>> Verzonden: ‎donderdag‎ ‎7‎ ‎augustus‎ ‎2014 ‎20‎:‎20
>> Aan: dev@cordova.apache.org
>>
>>
>>
>>
>>
>> Anybody there, who use plugman...?
>>
>>
>> -- Původní zpráva --
>>
>> Od: Jan Velecký 
>>
>> Komu: dev@cordova.apache.org
>>
>> Datum: 6. 8. 2014 17:34:01
>>
>> Předmět: Plugman poor documentation of adduser
>>
>>
>> "Hello,
>>
>> how can I add user to Cordova plugin repository to be able to upload
>> plugin?
>>
>> When I type plugman adduser into cmd (Windows 7 64 bit), it wanna Username
>>
>> from me...
>>
>> Probably new username (documentation of plugman is so poor), but I can
>> type
>>
>> anything and it wanna username again, I can type username (Velda), e-mail
>>
>> and nothing.
>>
>>
>>
>> Thanks for help."
>>
>
>

Re: Plugman poor documentation of adduser

[Jesse]

You should see this:
$ plugman adduser
Username: purplecabbage
Password:
Email: purplecabb...@gmail.com
user added

Notes:
- Be sure to remember your password, as there does not currently appear to
be a way to change it.
- There is no documentation
- Ideally this workflow should be doable from the plugin site, which
currently has no concept of people at all, other than listing 'maintainer'
in every plugin. ( issue for this [1] )
- Please help us to improve this, anyone!?


[1] https://issues.apache.org/jira/browse/CB-7246



@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 11:26 AM, Dick Van den Brink <
d_vandenbr...@outlook.com> wrote:

> Had the same issue last time I tried… so sorry I don't have a solution ☹
>
>
>
>
>
>
> Verzonden met Windows Mail
>
>
>
>
>
> Van: Jan Velecký
> Verzonden: ‎donderdag‎ ‎7‎ ‎augustus‎ ‎2014 ‎20‎:‎20
> Aan: dev@cordova.apache.org
>
>
>
>
>
> Anybody there, who use plugman...?
>
>
> -- Původní zpráva --
>
> Od: Jan Velecký 
>
> Komu: dev@cordova.apache.org
>
> Datum: 6. 8. 2014 17:34:01
>
> Předmět: Plugman poor documentation of adduser
>
>
> "Hello,
>
> how can I add user to Cordova plugin repository to be able to upload
> plugin?
>
> When I type plugman adduser into cmd (Windows 7 64 bit), it wanna Username
>
> from me...
>
> Probably new username (documentation of plugman is so poor), but I can type
>
> anything and it wanna username again, I can type username (Velda), e-mail
>
> and nothing.
>
>
>
> Thanks for help."
>

Re: Plugman poor documentation of adduser

[Dick Van den Brink]

Had the same issue last time I tried… so sorry I don't have a solution ☹






Verzonden met Windows Mail





Van: Jan Velecký
Verzonden: ‎donderdag‎ ‎7‎ ‎augustus‎ ‎2014 ‎20‎:‎20
Aan: dev@cordova.apache.org





Anybody there, who use plugman...?


-- Původní zpráva --

Od: Jan Velecký 

Komu: dev@cordova.apache.org

Datum: 6. 8. 2014 17:34:01

Předmět: Plugman poor documentation of adduser


"Hello,

how can I add user to Cordova plugin repository to be able to upload plugin?

When I type plugman adduser into cmd (Windows 7 64 bit), it wanna Username 

from me...

Probably new username (documentation of plugman is so poor), but I can type 

anything and it wanna username again, I can type username (Velda), e-mail 

and nothing.



Thanks for help."

Re: Plugman poor documentation of adduser

[Jan Velecký]

Anybody there, who use plugman...?


-- Původní zpráva --

Od: Jan Velecký 

Komu: dev@cordova.apache.org

Datum: 6. 8. 2014 17:34:01

Předmět: Plugman poor documentation of adduser


"Hello,

how can I add user to Cordova plugin repository to be able to upload plugin?

When I type plugman adduser into cmd (Windows 7 64 bit), it wanna Username 

from me...

Probably new username (documentation of plugman is so poor), but I can type 

anything and it wanna username again, I can type username (Velda), e-mail 

and nothing.



Thanks for help."

Re: W3C Battery Feedback request

[Brian LeRoux]

ya, idk, even those I have problems with (meaningful strings)

current spec has lots of listeners for various events though



On Thu, Aug 7, 2014 at 11:00 AM, Jesse  wrote:

> addEventListener or nothing
> anyone can wrap it in a promise if they want
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Aug 7, 2014 at 10:57 AM, Brian LeRoux  wrote:
>
> > bonus: https://gist.github.com/brianleroux/cc8b4adc0f9f0b7df654
> >
> > (I have no idea if this is the best way…not being a fan promises but
> > willing to cede they have won this round.)
> >
> >
> > On Thu, Aug 7, 2014 at 10:50 AM, Brian LeRoux  wrote:
> >
> > > ah, sometimes you have read inbetween the lines w/ Joe's messaging
> > >
> > > he's right, it is broken, and he did state why: its a blocking API
> > >
> > > our feedback would be perhaps received better with a concrete proposal:
> > > throw out the current spec and rewrite it using DOM promises or
> whatever
> > > flavor of the month we have for async querying of data. the current
> > > blocking API is not implementable by our bridge (async) so we can't do
> > much
> > > with it. ideally all web apis are async anyhow. ideally spec writers
> know
> > > this about the web and browsers, but alas.
> > >
> > >
> > >
> > >
> > > On Thu, Aug 7, 2014 at 8:06 AM, Lisa Seacat DeLuca  >
> > > wrote:
> > >
> > >> Joe~
> > >>
> > >> Thank you for responding.  I just finished up sharing our thoughts on
> > the
> > >> Device APIs Working Group status call.  They appreciate the overall
> "it
> > is
> > >> broken" feedback but could really benefit from a concrete proposal on
> > how
> > >> to improve the battery specification.  Do you, or anyone else from the
> > >> Cordova team, want to take a stab at putting together a formal
> > >> proposal/recommendation that I can bring back to the DAP team?  This
> is
> > an
> > >> opportunity for us to help shape the spec!
> > >>
> > >> Here's a link to the current specification:
> > >> http://www.w3.org/TR/battery-status/
> > >>
> > >>
> > >> Lisa
> > >>
> > >> Lisa Seacat DeLuca
> > >> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> > >>  | | *ldel...@us.ibm.com*  |
> > >> *lisaseacat.com*  | [image: follow
> > >> @LisaSeacat on twitter] | [image:
> > >> follow Lisa Seacat DeLuca on linkedin]
> > >> 
> > >>
> > >>
> > >>
> > >> From:Joe Bowser 
> > >> To:dev 
> > >> Date:08/06/2014 02:45 PM
> > >> Subject:Re: W3C Battery Feedback request
> > >> --
> > >>
> > >>
> > >>
> > >> The spec is flawed in that there's no way we could implement it as it
> > >> stands. The spec needs to be reworked to be more event driven and
> > >> asynchronous.   Right now it's too much like device with everything up
> > >> front.
> > >>
> > >> This is all based on memory, but the spec was seriously broken the
> last
> > >> time I looked.
> > >> On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca" 
> > wrote:
> > >>
> > >> > I sent a note back in June asking if anyone had any feedback for the
> > >> > Device API's Working Group for the battery concerns that we had
> > >> previously
> > >> > voiced related to the battery spec.
> > >> >
> > >> >
> > >>
> >
> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results
> > >> >
> > >> > I need to update the DAP team on Thursday with any thoughts Cordova
> > has
> > >> so
> > >> > if anyone has any feedback please reply asap.  The link to the first
> > >> email
> > >> > has the questions from the DAP team to Cordova.
> > >> >
> > >> > Thank you!
> > >> >
> > >> >
> > >> > Lisa
> > >> >
> > >> > Lisa Seacat DeLuca
> > >> > Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> > >> >  | | *ldel...@us.ibm.com* 
> |
> > >> > *lisaseacat.com*  | [image: follow
> > >> > @LisaSeacat on twitter] |
> [image:
> > >> > follow Lisa Seacat DeLuca on linkedin]
> > >> > 
> > >> >
> > >> >
> > >>
> > >>
> > >
> >
>

Re: W3C Battery Feedback request

[Jesse]

addEventListener or nothing
anyone can wrap it in a promise if they want

@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 10:57 AM, Brian LeRoux  wrote:

> bonus: https://gist.github.com/brianleroux/cc8b4adc0f9f0b7df654
>
> (I have no idea if this is the best way…not being a fan promises but
> willing to cede they have won this round.)
>
>
> On Thu, Aug 7, 2014 at 10:50 AM, Brian LeRoux  wrote:
>
> > ah, sometimes you have read inbetween the lines w/ Joe's messaging
> >
> > he's right, it is broken, and he did state why: its a blocking API
> >
> > our feedback would be perhaps received better with a concrete proposal:
> > throw out the current spec and rewrite it using DOM promises or whatever
> > flavor of the month we have for async querying of data. the current
> > blocking API is not implementable by our bridge (async) so we can't do
> much
> > with it. ideally all web apis are async anyhow. ideally spec writers know
> > this about the web and browsers, but alas.
> >
> >
> >
> >
> > On Thu, Aug 7, 2014 at 8:06 AM, Lisa Seacat DeLuca 
> > wrote:
> >
> >> Joe~
> >>
> >> Thank you for responding.  I just finished up sharing our thoughts on
> the
> >> Device APIs Working Group status call.  They appreciate the overall "it
> is
> >> broken" feedback but could really benefit from a concrete proposal on
> how
> >> to improve the battery specification.  Do you, or anyone else from the
> >> Cordova team, want to take a stab at putting together a formal
> >> proposal/recommendation that I can bring back to the DAP team?  This is
> an
> >> opportunity for us to help shape the spec!
> >>
> >> Here's a link to the current specification:
> >> http://www.w3.org/TR/battery-status/
> >>
> >>
> >> Lisa
> >>
> >> Lisa Seacat DeLuca
> >> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> >>  | | *ldel...@us.ibm.com*  |
> >> *lisaseacat.com*  | [image: follow
> >> @LisaSeacat on twitter] | [image:
> >> follow Lisa Seacat DeLuca on linkedin]
> >> 
> >>
> >>
> >>
> >> From:Joe Bowser 
> >> To:dev 
> >> Date:08/06/2014 02:45 PM
> >> Subject:Re: W3C Battery Feedback request
> >> --
> >>
> >>
> >>
> >> The spec is flawed in that there's no way we could implement it as it
> >> stands. The spec needs to be reworked to be more event driven and
> >> asynchronous.   Right now it's too much like device with everything up
> >> front.
> >>
> >> This is all based on memory, but the spec was seriously broken the last
> >> time I looked.
> >> On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca" 
> wrote:
> >>
> >> > I sent a note back in June asking if anyone had any feedback for the
> >> > Device API's Working Group for the battery concerns that we had
> >> previously
> >> > voiced related to the battery spec.
> >> >
> >> >
> >>
> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results
> >> >
> >> > I need to update the DAP team on Thursday with any thoughts Cordova
> has
> >> so
> >> > if anyone has any feedback please reply asap.  The link to the first
> >> email
> >> > has the questions from the DAP team to Cordova.
> >> >
> >> > Thank you!
> >> >
> >> >
> >> > Lisa
> >> >
> >> > Lisa Seacat DeLuca
> >> > Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> >> >  | | *ldel...@us.ibm.com*  |
> >> > *lisaseacat.com*  | [image: follow
> >> > @LisaSeacat on twitter] | [image:
> >> > follow Lisa Seacat DeLuca on linkedin]
> >> > 
> >> >
> >> >
> >>
> >>
> >
>

Re: W3C Battery Feedback request

[Brian LeRoux]

bonus: https://gist.github.com/brianleroux/cc8b4adc0f9f0b7df654

(I have no idea if this is the best way…not being a fan promises but
willing to cede they have won this round.)


On Thu, Aug 7, 2014 at 10:50 AM, Brian LeRoux  wrote:

> ah, sometimes you have read inbetween the lines w/ Joe's messaging
>
> he's right, it is broken, and he did state why: its a blocking API
>
> our feedback would be perhaps received better with a concrete proposal:
> throw out the current spec and rewrite it using DOM promises or whatever
> flavor of the month we have for async querying of data. the current
> blocking API is not implementable by our bridge (async) so we can't do much
> with it. ideally all web apis are async anyhow. ideally spec writers know
> this about the web and browsers, but alas.
>
>
>
>
> On Thu, Aug 7, 2014 at 8:06 AM, Lisa Seacat DeLuca 
> wrote:
>
>> Joe~
>>
>> Thank you for responding.  I just finished up sharing our thoughts on the
>> Device APIs Working Group status call.  They appreciate the overall "it is
>> broken" feedback but could really benefit from a concrete proposal on how
>> to improve the battery specification.  Do you, or anyone else from the
>> Cordova team, want to take a stab at putting together a formal
>> proposal/recommendation that I can bring back to the DAP team?  This is an
>> opportunity for us to help shape the spec!
>>
>> Here's a link to the current specification:
>> http://www.w3.org/TR/battery-status/
>>
>>
>> Lisa
>>
>> Lisa Seacat DeLuca
>> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
>>  | | *ldel...@us.ibm.com*  |
>> *lisaseacat.com*  | [image: follow
>> @LisaSeacat on twitter] | [image:
>> follow Lisa Seacat DeLuca on linkedin]
>> 
>>
>>
>>
>> From:Joe Bowser 
>> To:dev 
>> Date:08/06/2014 02:45 PM
>> Subject:Re: W3C Battery Feedback request
>> --
>>
>>
>>
>> The spec is flawed in that there's no way we could implement it as it
>> stands. The spec needs to be reworked to be more event driven and
>> asynchronous.   Right now it's too much like device with everything up
>> front.
>>
>> This is all based on memory, but the spec was seriously broken the last
>> time I looked.
>> On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca"  wrote:
>>
>> > I sent a note back in June asking if anyone had any feedback for the
>> > Device API's Working Group for the battery concerns that we had
>> previously
>> > voiced related to the battery spec.
>> >
>> >
>> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results
>> >
>> > I need to update the DAP team on Thursday with any thoughts Cordova has
>> so
>> > if anyone has any feedback please reply asap.  The link to the first
>> email
>> > has the questions from the DAP team to Cordova.
>> >
>> > Thank you!
>> >
>> >
>> > Lisa
>> >
>> > Lisa Seacat DeLuca
>> > Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
>> >  | | *ldel...@us.ibm.com*  |
>> > *lisaseacat.com*  | [image: follow
>> > @LisaSeacat on twitter] | [image:
>> > follow Lisa Seacat DeLuca on linkedin]
>> > 
>> >
>> >
>>
>>
>

Re: W3C Battery Feedback request

[Brian LeRoux]

ah, sometimes you have read inbetween the lines w/ Joe's messaging

he's right, it is broken, and he did state why: its a blocking API

our feedback would be perhaps received better with a concrete proposal:
throw out the current spec and rewrite it using DOM promises or whatever
flavor of the month we have for async querying of data. the current
blocking API is not implementable by our bridge (async) so we can't do much
with it. ideally all web apis are async anyhow. ideally spec writers know
this about the web and browsers, but alas.




On Thu, Aug 7, 2014 at 8:06 AM, Lisa Seacat DeLuca 
wrote:

> Joe~
>
> Thank you for responding.  I just finished up sharing our thoughts on the
> Device APIs Working Group status call.  They appreciate the overall "it is
> broken" feedback but could really benefit from a concrete proposal on how
> to improve the battery specification.  Do you, or anyone else from the
> Cordova team, want to take a stab at putting together a formal
> proposal/recommendation that I can bring back to the DAP team?  This is an
> opportunity for us to help shape the spec!
>
> Here's a link to the current specification:
> http://www.w3.org/TR/battery-status/
>
>
> Lisa
>
> Lisa Seacat DeLuca
> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
>  | | *ldel...@us.ibm.com*  |
> *lisaseacat.com*  | [image: follow
> @LisaSeacat on twitter] | [image:
> follow Lisa Seacat DeLuca on linkedin]
> 
>
>
>
> From:Joe Bowser 
> To:dev 
> Date:08/06/2014 02:45 PM
> Subject:Re: W3C Battery Feedback request
> --
>
>
>
> The spec is flawed in that there's no way we could implement it as it
> stands. The spec needs to be reworked to be more event driven and
> asynchronous.   Right now it's too much like device with everything up
> front.
>
> This is all based on memory, but the spec was seriously broken the last
> time I looked.
> On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca"  wrote:
>
> > I sent a note back in June asking if anyone had any feedback for the
> > Device API's Working Group for the battery concerns that we had
> previously
> > voiced related to the battery spec.
> >
> >
> http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results
> >
> > I need to update the DAP team on Thursday with any thoughts Cordova has
> so
> > if anyone has any feedback please reply asap.  The link to the first
> email
> > has the questions from the DAP team to Cordova.
> >
> > Thank you!
> >
> >
> > Lisa
> >
> > Lisa Seacat DeLuca
> > Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
> >  | | *ldel...@us.ibm.com*  |
> > *lisaseacat.com*  | [image: follow
> > @LisaSeacat on twitter] | [image:
> > follow Lisa Seacat DeLuca on linkedin]
> > 
> >
> >
>
>

[GitHub] cordova-plugin-vibration pull request: Cb 5459

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-vibration/pull/16


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

Re: Hello

[Brian LeRoux]

Welcome Jason! Lots to do and see here. Please document your journey of
getting up to speed. Lots of rough edges that we can smooth out with a
fresh perspective.

I'm sure your colleagues have already given you a boat load of stuff to
look at but our  wiki [1] * is a great place to start.

[1] http://wiki.cordova.io/

* Usually the wiki is available but not right now apparently =/



On Thu, Aug 7, 2014 at 7:19 AM, Jason Chase  wrote:

> Hi all,
>
> I'm Jason Chase, and I just joined the Google team working on Cordova.
>
> I've spent the last while working on enterprise SaaS solution, so I'm
> looking forward to the challenge of getting up to speed on Cordova.  Looks
> like there's a lot going on with Cordova, so I can't wait to contribute!
>
> Thanks,
> Jason
>

Re: Hello

[Lorin Beer]

Welcome Jason!


On Thu, Aug 7, 2014 at 9:55 AM, Sebastian Mil 
wrote:

> Hi Jason!
>
>
> On Thu, Aug 7, 2014 at 9:50 AM, Carlos Santana 
> wrote:
>
> > Welcome Jason !
> >
> >
> > On Thu, Aug 7, 2014 at 10:19 AM, Jason Chase 
> wrote:
> >
> > > Hi all,
> > >
> > > I'm Jason Chase, and I just joined the Google team working on Cordova.
> > >
> > > I've spent the last while working on enterprise SaaS solution, so I'm
> > > looking forward to the challenge of getting up to speed on Cordova.
> >  Looks
> > > like there's a lot going on with Cordova, so I can't wait to
> contribute!
> > >
> > > Thanks,
> > > Jason
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > 
> >
>

Re: Hello

[Sebastian Mil]

Hi Jason!


On Thu, Aug 7, 2014 at 9:50 AM, Carlos Santana  wrote:

> Welcome Jason !
>
>
> On Thu, Aug 7, 2014 at 10:19 AM, Jason Chase  wrote:
>
> > Hi all,
> >
> > I'm Jason Chase, and I just joined the Google team working on Cordova.
> >
> > I've spent the last while working on enterprise SaaS solution, so I'm
> > looking forward to the challenge of getting up to speed on Cordova.
>  Looks
> > like there's a lot going on with Cordova, so I can't wait to contribute!
> >
> > Thanks,
> > Jason
> >
>
>
>
> --
> Carlos Santana
> 
>

Re: Hello

[Carlos Santana]

Welcome Jason !


On Thu, Aug 7, 2014 at 10:19 AM, Jason Chase  wrote:

> Hi all,
>
> I'm Jason Chase, and I just joined the Google team working on Cordova.
>
> I've spent the last while working on enterprise SaaS solution, so I'm
> looking forward to the challenge of getting up to speed on Cordova.  Looks
> like there's a lot going on with Cordova, so I can't wait to contribute!
>
> Thanks,
> Jason
>



-- 
Carlos Santana

[GitHub] cordova-plugin-inappbrowser pull request: Hide status bar in iOS 7...

[Barryrowe]

GitHub user Barryrowe opened a pull request:

https://github.com/apache/cordova-plugin-inappbrowser/pull/59

Hide status bar in iOS 7 with option

This minor change allows you to use an option "hidestatusbar=yes" to hide 
the status bar in IOS 7. It implements the perferStatusBarHidden method. It 
defaults to NO, so that functionality does not change.

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

$ git pull https://github.com/Barryrowe/cordova-plugin-inappbrowser 
hide-status-bar

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

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


commit bd925e0366b70970c02b00fbfe13574448180329
Author: Barryrowe 
Date:   2014-08-07T14:40:42Z

Adding prefersStatusBarHidden method to view

Adding this method to see if it will work for our purposes.

commit 4715f28390cde890d137a91feb3f22020b12178b
Author: Barryrowe 
Date:   2014-08-07T16:10:55Z

Support property hidestatusbar to hide status bar

This adds support for hiding the status bar as an option passed to
the view. This is the iOS 7 way of hiding the status bar.




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

Re: [Vote] Tools Release for Android 3.5.1

[Ian Clelland]

Cordova-lib works for me, but I can't find that tag (or commit) in
cordova-cli. Did it get pushed to the Apache repo?


On Wed, Aug 6, 2014 at 6:14 PM, Marcel Kinard  wrote:

> [Strange that there was no feedback on the discuss thread, perhaps a vote
> thread will draw out some thumbs up or down.]
>
> Please review and vote on this Tools Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7267
>
> The scope of this tools release is a minimal change to 3.5.0 so that when
> adding the Android platform, it will add Android 3.5.1 as the default
> instead of Android 3.5.0. Nothing else is changed. Only cordova-lib and
> cordova-cli are affected.
>
> Both items have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-7267/
>
> The packages were published from their corresponding git tags:
> cordova-lib: 47043fa28beae7f8699af16b00678ab015f76e58 refs/tags/0.21.7-rc1
> cordova-cli: 1916516f145041ecbef60e1b3922b9b57ea08ef4
> refs/tags/3.5.0-0.2.7-rc1
>
> Upon a successful vote I will upload the archives to dist/, publish them
> to NPM, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 72 hours.
>
> I vote +1:
> * Ran coho audit-license-headers
> * Ran functional tests
> * Ran coho verify-archive

Re: W3C Battery Feedback request

[Lisa Seacat DeLuca]

Joe~

Thank you for responding.  I just finished up sharing our thoughts on the 
Device APIs Working Group status call.  They appreciate the overall "it is 
broken" feedback but could really benefit from a concrete proposal on how 
to improve the battery specification.  Do you, or anyone else from the 
Cordova team, want to take a stab at putting together a formal 
proposal/recommendation that I can bring back to the DAP team?  This is an 
opportunity for us to help shape the spec! 

Here's a link to the current specification: 
http://www.w3.org/TR/battery-status/


Lisa

Lisa Seacat DeLuca
Mobile Engineer | t: +415.787.4589 | ldel...@apache.org | | 
ldel...@us.ibm.com | lisaseacat.com | | 



From:   Joe Bowser 
To: dev 
Date:   08/06/2014 02:45 PM
Subject:Re: W3C Battery Feedback request



The spec is flawed in that there's no way we could implement it as it
stands. The spec needs to be reworked to be more event driven and
asynchronous.   Right now it's too much like device with everything up
front.

This is all based on memory, but the spec was seriously broken the last
time I looked.
On Aug 5, 2014 10:12 AM, "Lisa Seacat DeLuca"  wrote:

> I sent a note back in June asking if anyone had any feedback for the
> Device API's Working Group for the battery concerns that we had 
previously
> voiced related to the battery spec.
>
> 
http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+w3c+battery#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20w3c%20battery+page:1+mid:ezvvipwdcvhlt5h6+state:results

>
> I need to update the DAP team on Thursday with any thoughts Cordova has 
so
> if anyone has any feedback please reply asap.  The link to the first 
email
> has the questions from the DAP team to Cordova.
>
> Thank you!
>
>
> Lisa
>
> Lisa Seacat DeLuca
> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org*
>  | | *ldel...@us.ibm.com*  |
> *lisaseacat.com*  | [image: follow
> @LisaSeacat on twitter] | [image:
> follow Lisa Seacat DeLuca on linkedin]
> 
>
>

Re: [VOTE] Plugins Release

[Ian Clelland]

+1

* Verified all archives
* Verified that the tags are correct, and point to the hashes listed
* Verified contents of archives against public repositories at the listed
hashes
* Ran mobile-spec on iOS (3.5.0 and master)
* Ran mobile-spec on Android (3.5.1, 4.0.x and master)


Note: Three plugins did not work for me initially with cordova-ios
3.6.0-dev: Camera, Device-Orientation and Geolocation, since the
CoreLocation framework has been removed from cordova-ios, and, for some
reason, plugman didn't add it on prepare.

However, they still work correctly with the released version of
cordova-ios, and with master if you add the framework yourself. I suspect
that this is an issue with plugman, though (and possibly just my install),
and not the plugins themselves, as they seem to declare the dependency
correctly.


On Wed, Aug 6, 2014 at 10:39 PM, Steven Gill  wrote:

> Please review and vote on the release of this plugins release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7244
>
> The plugins have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7244/
>
> The packages were published from their corresponding git tags:
> cordova-plugin-battery-status: 0.2.10 (490888663e)
> cordova-plugin-camera: 0.3.1 (823eb5d27a)
> cordova-plugin-console: 0.2.10 (361a73573b)
> cordova-plugin-contacts: 0.2.12 (5148d5ccd8)
> cordova-plugin-device: 0.2.11 (efd903fe88)
>
>
> cordova-plugin-device-motion: 0.2.9 (52c3348b18)
> cordova-plugin-device-orientation: 0.3.8 (fc8b28414f)
> cordova-plugin-dialogs: 0.2.9 (99e8f4c530)
> cordova-plugin-file: 1.3.0 (149044114f)
> cordova-plugin-file-transfer: 0.4.5 (a071c5bf9a)
>
>
> cordova-plugin-geolocation: 0.3.9 (438f50f8c4)
> cordova-plugin-globalization: 0.3.0 (bc3a4053ef)
> cordova-plugin-inappbrowser: 0.5.1 (c37b08e038)
> cordova-plugin-media: 0.2.12 (52ca8690db)
> cordova-plugin-media-capture: 0.3.2 (373d161668)
>
>
> cordova-plugin-network-information: 0.2.11 (00b71a7cd9)
> cordova-plugin-splashscreen: 0.3.2 (3b58cd69b3)
> cordova-plugin-statusbar: 0.1.7 (2ba62cb92c)
> cordova-plugin-vibration: 0.3.10 (4a4dc85a35)
>
>
> The blog post will be up tomorrow for review.
>
> Upon a successful vote I will upload the archives to dist/, upload
> them to the Plugins Registry, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Used `license-checker` to ensure all dependencies have
> Apache-compatible licenses
> * Ensured continuous build was green when repos were tagged
>

Hello

[Jason Chase]

Hi all,

I'm Jason Chase, and I just joined the Google team working on Cordova.

I've spent the last while working on enterprise SaaS solution, so I'm
looking forward to the challenge of getting up to speed on Cordova.  Looks
like there's a lot going on with Cordova, so I can't wait to contribute!

Thanks,
Jason

Re: cordova.js and cordova.platformVersion

[Andrew Grieve]

That all sounds good to me Steve!


On Wed, Aug 6, 2014 at 6:48 PM, Steven Gill  wrote:

> I have started to look into adding cordova.platformVersion to cordova.js.
> Issue [1].
>
> Trying to figure out the best way to implement this.
>
> One potential method.
>
> 1) Pass in platformVersion to cordova.js during build step. Make coho
> handle it during release process:
> First off, cordovajs doesn't get branched and tagged on its own anymore
>
> Non-Browserify use case
> A) coho prepare-release-branch --version 3.5.0 -r android
>- This step would build cordova-js, inject cordova.platformVersion based
> on the --version being passed in.
>- Updating version in package.json files
> - Updating version numbers
>- Creating release branches
>
> B) coho tag-release --version 3.5.0 -r android
> - Tag cordova-android "3.5.0"
> - Tag cordova-js "android-3.5.0"
>
> Browserify use case
> Currently, cordova.version is set to 'N/A' in browserify builds of
> cordova.js.
>
> We would probably have to create a utility function that grabs the
> cordova.platformVersion property from "platform_www/cordova.js" files.
> These are the cordova.js files that get bundled at release with the
> platforms from the non-browserify use case.
>
> Use the version when building cordova.js in prepare-browserify.js.
>
>
> Thoughts? Other suggestions?
>
>
> [1] https://issues.apache.org/jira/browse/CB-7219
>

[GitHub] cordova-android pull request: CB-7265: Fix crash in shouldOverride...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-android/pull/111


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

[GitHub] cordova-android pull request: CB-7265: Fix crash in shouldOverride...

[mbektchiev]

GitHub user mbektchiev opened a pull request:

https://github.com/apache/cordova-android/pull/111

CB-7265: Fix crash in shouldOverrideUrlLoading on Android < 4.0.3

Application built with Cordova 3.5.1 running on a device with Android < 
4.0.3 crashes when the webview is redirected to a custom url scheme. See 
https://issues.apache.org/jira/browse/CB-7265
More easily reproducible by adding the following line in JS: 
`window.location="custom://";`

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

$ git pull https://github.com/Icenium/cordova-android 
bektchiev/CB-7265-custom-url-scheme-crash

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

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


commit 28111dafa2b3e44d07f947c784c932b6e4ee2159
Author: Martin Bektchiev 
Date:   2014-08-06T12:24:51Z

CB-7265: Fix crash on Android < 4.0.3




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

platform switches for Windows Universal Apps

[Sergey Grebnov (Akvelon)]

New Windows platform template supports standard Windows apps as well as Windows 
Phone 8.1 apps. As a developer I need an option to specify which target I 
should run when doing 'cordova run/emulate' (run phone version on the 
device/emulator or run windows store app).

Current draft implementation uses '-store' and '-phone' switches but we should 
discuss final names for them. Here are a few alternatives.  Thoughts?

--tablet
--handset or --phone
or --targetDevice="tablet, handset" <- similar to how we define target chip 
architecture

Thx!
Sergey

Re: Cordova things

[Mike Billau]

Thanks David for all of the help! Good luck to you sir!


On Wed, Aug 6, 2014 at 5:44 PM, Brian LeRoux  wrote:

> thanks again David and have fun in the new gig / stop by and say hi
> whenever!
>
>
> On Wed, Aug 6, 2014 at 2:26 PM, Jesse  wrote:
>
> > Thanks David, don't be a stranger. Best of luck.
> > Cheers,
> >   Jesse
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Wed, Aug 6, 2014 at 2:22 PM, Shazron  wrote:
> >
> > > Thanks David!
> > >
> > > On Wed, Aug 6, 2014 at 2:11 PM, Carlos Santana 
> > > wrote:
> > > > Thanks Kemp !! and good luck
> > > >
> > > >
> > > > On Wed, Aug 6, 2014 at 4:54 PM, Marcel Kinard 
> > > wrote:
> > > >
> > > >> David, thanks for rocking on Medic/CI, and best of luck to you!
> > > >>
> > > >> On Aug 6, 2014, at 4:27 PM, David Kemp  wrote:
> > > >>
> > > >> > Hi all,
> > > >> > I will be moving on to a different team and will likely not
> > contribute
> > > >> much
> > > >> > to Cordova. Its been a slice, but other exciting things await.
> > > >> >
> > > >> > Max will be handling Medic/CI stuff and helping to keep
> > ci.cordova.io
> > > >> green.
> > > >> >
> > > >> > Maybe I can get my next team to build apps with Cordova...
> > > >> >
> > > >> > Happy bug hunting,
> > > >> > David Kemp
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Carlos Santana
> > > > 
> > >
> >
>

[GitHub] cordova-plugin-battery-status pull request: CB-6957 Style improvem...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-battery-status pull request: CB-6957 Style improvem...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cordova-plugin-device pull request: CB-7262 Adds support for unive...

[vladimir-kotikov]

GitHub user vladimir-kotikov opened a pull request:

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

CB-7262 Adds support for universal windows apps.

Fix for [CB-7262](https://issues.apache.org/jira/browse/CB-7262)
This will prevent critical error (app won't start properly) when running 
Universal app on Windows Phone 8.1

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

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

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

https://github.com/apache/cordova-plugin-device/pull/19.patch

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

This closes #19


commit ae3f2ed888519b9657e91a2caafbaf490f9c2bc0
Author: Vladimir Kotikov 
Date:   2014-08-05T12:31:03Z

CB-7262 Adds support for universal windows apps.




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

[GitHub] cordova-mobile-spec pull request: CB-7269 Fixes loading cordova.js...

[vladimir-kotikov]

GitHub user vladimir-kotikov opened a pull request:

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

CB-7269 Fixes loading cordova.js on windows phone 8.1

Fix for [CB-7269](https://issues.apache.org/jira/browse/CB-7269) + minor 
JSHint fixes at lines 76, 79

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

$ git pull https://github.com/MSOpenTech/cordova-mobile-spec CB-7269

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

https://github.com/apache/cordova-mobile-spec/pull/102.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 #102


commit d340273f1f4fb2e9a1dbf5d2e57105c17ad478f2
Author: Vladimir Kotikov 
Date:   2014-07-04T09:52:54Z

CB-7269 Fixes loading cordova.js on windows phone 8.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.
---

[GitHub] cordova-mobile-spec pull request: CB-7268 Adds option for creating...

[vladimir-kotikov]

GitHub user vladimir-kotikov opened a pull request:

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

CB-7268 Adds option for creating mobilespec application with windows 
platform

Fix for [CB-7268](https://issues.apache.org/jira/browse/CB-7268)

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

$ git pull https://github.com/MSOpenTech/cordova-mobile-spec CB-7268

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

https://github.com/apache/cordova-mobile-spec/pull/101.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 #101


commit 10634a9118d1249578e08d2f758c4225aba99244
Author: Vladimir Kotikov 
Date:   2014-08-07T05:29:51Z

CB-7268 Adds option for creating mobilespec application with windows 
platform




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