Re: meet up in SF next week (June 9-14)?

[John M. Wargo]

I'll be there too, but not for the WWDC, i'll be attending the MIT Technology 
Review Mobile Summit.

On 6/6/2013 10:58 AM, Brian LeRoux wrote:

Yup I'm around too (tho not at WWDC). Maybe an informal cordova dinner
is in order?


On Thu, Jun 6, 2013 at 1:30 AM, Shazron  wrote:

Hi James, I will be at WWDC next week, let's meet up. Feel free to drop by
the Adobe SF office as well :)
(although its not exactly near Moscone West)


On Wed, Jun 5, 2013 at 8:42 AM, James Jong  wrote:


I was able to get a late ticket to go to WWDC so I'll be in SF next week.
  Anyone else here going and want to meet up?  Perhaps we can get together
one evening?  All those around welcome, not limited to those going to WWDC.

-James Jong

console.log

[John M. Wargo]

I remember seeing something on the dev lists a while back about console.log and 
I can't remember the resolution. It doesn't seem to be working in Cordova on 
iOS (my Android config stopped working with the latest ADT, so I can't test it 
there right now).  Did it make it into a plugin or something?
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: console.log

[John M. Wargo]

Nevermind, I found it.

On 7/28/2013 9:32 AM, John M. Wargo wrote:

I remember seeing something on the dev lists a while back about console.log and 
I can't remember the resolution. It doesn't seem to be working in Cordova on 
iOS (my Android config stopped working with the latest ADT, so I can't test it 
there right now).  Did it make it into a plugin or something?
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Serve vs. opening an HTML file in the browser

[John M. Wargo]

Can someone help me understand why I would want to use cordova serve rather 
than just loading the web content in the browser directly (through File - Open 
for example)?

Is there something special that serve does that makes this approach better?

Re: core APIs and the CLI

[John M. Wargo]

OK, I just whacked everything and started over. I opened a terminal window on 
Macintosh and issued the following commands:

jmw-mini:~ jwargo$ cd dev
jmw-mini:dev jwargo$ cordova create test
jmw-mini:dev jwargo$ cd test
jmw-mini:test jwargo$ cordova platform add android ios
jmw-mini:test jwargo$ cordova plugin add 
https://git-wip-us.apache.org/repos/asf/cordova-plugin-camera.git
jmw-mini:test jwargo$ cordova prepare android
jmw-mini:test jwargo$ cordova prepare ios

At the end of the process, I looked at the config.xml in the iOS project's www 
folder and found the following:


http://www.w3.org/ns/widgets"; 
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
HelloCordova

A sample Apache Cordova application that responds to the deviceready 
event.

http://cordova.io";>
Apache Cordova Team







I even went in and forced an update to the config.xml in the cordova project's 
config.xml file and did another cordova prepare.

My changes came over to the config.xml, but no camera entry.

I'm running CLI 3.0.6.

On 8/22/2013 1:46 PM, Ian Clelland wrote:

On Thu, Aug 22, 2013 at 11:11 AM, Braden Shepherdson wrote:


Are you sure you ran a "cordova prepare" in both cases? There should be a
 tag for Camera on both platforms, as far as I know.



That was my thinking as well. I checked earlier, and there definitely is a
feature tag for iOS. (It's the only tag specified in plugin.xml, and it's
the only required change, according to the docs). I don't think plugin add
/ plugin remove should be manipulating config.xml in the platforms
directories -- that should be the job of `cordova prepare`.

Ian

On Thu, Aug 22, 2013 at 7:46 AM, John Wargo  wrote:

I'm working on the part of my book that deals with the core APIs and I
need some guidance on how things are supposed to work.

I noticed that if I added the Camera API plugin to a project, that the

CLI

manages adding the camera feature to the android project's config.xml

file

in res/xml/config.xml. If I remove the plugin, the settings are removed
from the config.xml.

The documentation says that a setting is also required for the iOS
config.xml, but in my testing, the CLI doesn't make that change for me.

The

Xcode project's config.xml doesn't change as I add and remove the Camera
plugin.

So am I seeing an anomaly here or is this behavior as expected?  I

assumed

the CLI would take care of everything, but my testing here says

otherwise.

How's this supposed to work or what must the developer do? It doesn't

make

sense that the CLI would do this for Android and not iOS.

Re: Camera API

[John M. Wargo]

I could spend some time working through the permutations on a few platforms 
(Android, BB 10, iOS and Windows Phone), but will be a while before I can get 
to it - I've got a day job and I'm trying to finish writing a book with three 
chapters to go and a deadline approaching.

If nobody else can get to it before then, then I'll make that my first doc 
contribution.

On 8/28/2013 12:15 PM, Shazron wrote:

IMO first step would be that we find out what the existing implementations
actually do, and doc them
do our standard deprecation dance and implement the new shiny and correct
functionality


On Thu, Aug 29, 2013 at 12:04 AM, James Jong  wrote:


Several ways we could go here.  One is to improve the documentation.  iOS
chooses the larger image size.  I'm not sure if all the platforms do it the
same way.  I'd be happy to update the doc if it's all the same.  Second is
to modify the implementation to only require either W or H.  Note that we
would break backwards compatibility there.

-James Jong

On Aug 28, 2013, at 10:16 AM, Ray Camden  wrote:


As a user though, that doesn't necessarily make sense. You are saying,
"You must give me a H and W, but I'm going to maintain the aspect ratio

no

matter what." Given that, which side is "corrected" if I pass a H and W
that do not maintain the aspect ratio? Do we document it? I've worked on
another platform that provides a way to pass a H and W that act as a
bounding box, so if I use 150x150, my final result will be no bigger than
150x150, but possibly smaller in order to maintain aspect ratio. If that
is what PG is doing, then the docs should clearly spell that out. Maybe

it

is assumed by "Aspect ratio remains constant", but I think it could be
clearer.

On 8/28/13 9:04 AM, "James Jong"  wrote:


You're right that it could be calculated based on one or the other.  The
code expects both today.  I think the point is to be clear that the
aspect ratio is maintained, so that the user does not expect to be able
to arbitrarily set both.

-James Jong

On Aug 28, 2013, at 7:15 AM, John Wargo  wrote:


I've got another silly question. In looking at the Camera API, I see
the following:

targetWidth: Width in pixels to scale image. Must be used with
targetHeight. Aspect ratio remains constant. (Number)

targetHeight: Height in pixels to scale image. Must be used with
targetWidth. Aspect ratio remains constant. (Number)

I'm not getting why targetWidth MUST be used with targetHeight (and
visa versa) when aspect ratio remains constant. If aspect ratio remains
constant, then setting one automatically forces the other - that's the
whole point of maintaining aspect ratio, right? If the API is
maintaining aspect ratio while sizing the image, then forcing the
developer to specify both parameters is simply wasted work.

What am I missing here?

Re: Camera API

[John M. Wargo]

I went back and looked at the manuscript for PhoneGap Essentials and back then 
(a year and a half ago) I had tested this and wrote the following:

"The targetHeight & targetWidth parameters are supposed to control the height and 
width of the image obtained using getPicture. In my testing though, the parameters did not 
affect the resulting picture. The documentation says as well that the parameters must be used 
in conjunction with each other and that aspect ratio is maintained. This further reinforces 
that these options cannot work as documented (which my testing has proven) since it doesn't 
make sense that you have to set both height and width while at the same time maintaining an 
aspect ratio for the picture. If it truly was maintaining aspect ratio, then I'd expect that 
only one of the values would be able to be set. To truly maintain aspect ratio, you'd only be 
able to set either targetHeight or targetWidth, not both."

Anyway, I'll do some testing again and post the results.

On 8/28/2013 12:15 PM, Shazron wrote:

IMO first step would be that we find out what the existing implementations
actually do, and doc them
do our standard deprecation dance and implement the new shiny and correct
functionality


On Thu, Aug 29, 2013 at 12:04 AM, James Jong  wrote:


Several ways we could go here.  One is to improve the documentation.  iOS
chooses the larger image size.  I'm not sure if all the platforms do it the
same way.  I'd be happy to update the doc if it's all the same.  Second is
to modify the implementation to only require either W or H.  Note that we
would break backwards compatibility there.

-James Jong

On Aug 28, 2013, at 10:16 AM, Ray Camden  wrote:


As a user though, that doesn't necessarily make sense. You are saying,
"You must give me a H and W, but I'm going to maintain the aspect ratio

no

matter what." Given that, which side is "corrected" if I pass a H and W
that do not maintain the aspect ratio? Do we document it? I've worked on
another platform that provides a way to pass a H and W that act as a
bounding box, so if I use 150x150, my final result will be no bigger than
150x150, but possibly smaller in order to maintain aspect ratio. If that
is what PG is doing, then the docs should clearly spell that out. Maybe

it

is assumed by "Aspect ratio remains constant", but I think it could be
clearer.

On 8/28/13 9:04 AM, "James Jong"  wrote:


You're right that it could be calculated based on one or the other.  The
code expects both today.  I think the point is to be clear that the
aspect ratio is maintained, so that the user does not expect to be able
to arbitrarily set both.

-James Jong

On Aug 28, 2013, at 7:15 AM, John Wargo  wrote:


I've got another silly question. In looking at the Camera API, I see
the following:

targetWidth: Width in pixels to scale image. Must be used with
targetHeight. Aspect ratio remains constant. (Number)

targetHeight: Height in pixels to scale image. Must be used with
targetWidth. Aspect ratio remains constant. (Number)

I'm not getting why targetWidth MUST be used with targetHeight (and
visa versa) when aspect ratio remains constant. If aspect ratio remains
constant, then setting one automatically forces the other - that's the
whole point of maintaining aspect ratio, right? If the API is
maintaining aspect ratio while sizing the image, then forcing the
developer to specify both parameters is simply wasted work.

What am I missing here?

Re: Publishing plugins to Git

[John M. Wargo]

Andrew,

Thank you, I'll try that.

On 9/8/2013 8:16 PM, Andrew Grieve wrote:

You didn't use the correct URL. Try:

https://github.com/johnwargo/cordova-programming-code.git#master:plugins/carrier



On Sun, Sep 8, 2013 at 1:33 PM, John Wargo  wrote:


Is there anything special about distributing your plugins on GitHub?  My
files are up there, but when I try to test adding the plugin from that
location I get the following error:

[Error: Error fetching plugin: Error: failed to get the plugin via git
from URL https://github.com/johnwargo/**cordova-programming-code/tree/**
master/plugins/carrier,
output: Cloning into 'plugman-tmp1378661193771'...
fatal: https://github.com/johnwargo/**cordova-programming-code/tree/**
master/plugins/carrier/info/**refs?service=git-upload-packnot
 found: did you run git update-server-info on the server?

Re: Publishing plugins to Git

[John M. Wargo]

Don,

Thanks, I'll try this as well.

On 9/8/2013 8:26 PM, Don Coleman wrote:

Plugman needs to clone the project, I'm not sure if you can clone a
directory.

I create a git project for each of my plugins e.g.
https://github.com/don/BluetoothSerial.git


On Sun, Sep 8, 2013 at 8:16 PM, Andrew Grieve  wrote:


You didn't use the correct URL. Try:


https://github.com/johnwargo/cordova-programming-code.git#master:plugins/carrier



On Sun, Sep 8, 2013 at 1:33 PM, John Wargo  wrote:


Is there anything special about distributing your plugins on GitHub?  My
files are up there, but when I try to test adding the plugin from that
location I get the following error:

[Error: Error fetching plugin: Error: failed to get the plugin via git
from URL https://github.com/johnwargo/**cordova-programming-code/tree/**
master/plugins/carrier<

https://github.com/johnwargo/cordova-programming-code/tree/master/plugins/carrier

,
output: Cloning into 'plugman-tmp1378661193771'...
fatal: https://github.com/johnwargo/**cordova-programming-code/tree/**
master/plugins/carrier/info/**refs?service=git-upload-pack<

https://github.com/johnwargo/cordova-programming-code/tree/master/plugins/carrier/info/refs?service=git-upload-pack>not
found: did you run git update-server-info on the server?

Cordova download link broken

[John M. Wargo]

The default download link on cordova.io points to 
https://www.apache.org/dist/cordova/cordova-3.1.0-src.zip

Which is currently generating an error:


 Not Found

The requested URL /dist/cordova/cordova-3.1.0-src.zip was not found on this 
server.

--
Apache/2.4.7 (Unix) mod_wsgi/3.4 Python/2.7.5 OpenSSL/1.0.1e Server at 
www.apache.org Port 80



--

Camera targetWidth & targetHeight

[John M. Wargo]

A while back I posted a question regarding Camera targetWidth & targetHeight 
properties and how they worked. After some discussion, the conclusion I reached was 
that the documentation couldn't be correct about how it worked since there was no 
way to determine the camera's resolution with the current API but the docs said I 
had to provide both parameters.  I said I'd do some testing and I have finally 
gotten around to completing it. Here's what I discovered:

I created an application that allowed me to pass in different values for 
targetWidth & targetHeight when taking a picture. I tested at the following 
image sizes: 640x480, 800x600, 1024x768 as well as setting only the targetWidth to 
1024 or only the targetHeight to 768.

Here's the results:

Android
PortraitLandscape
480x640 640x480
600x800 800x600
768x10241024x768
768x10241024x768
768x10241024x768



iOS
PortraitLandscape
360x480 640x480
450x600 800x600
576x768 1024x768
2448x3264   3264x2448
2448x3264   3264x2448



Windows Phone 8
PortraitLandscape
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836


As you can see, Android properly implements the targetWidth & targetHeight 
properties. On iOS, it supports setting both properties, but not instances where 
only one is specified. Windows Phone 8 ignores the parameters completely.  On iOS, 
when you turn the device on its side, the Camera API applies the target width or 
height to the wrong axis (Android does this well however).

I'm trying to test this on a BlackBerry device, but my development environment 
is giving me fits right now. I'll work on it in the morning and publish my 
results when I get them.

I would suggest that the android implementation is as expected and that the other 
platforms need their implementations of targetWidth & targetHeight adjusted so 
it works correctly. The documentation should be updated as well as it's incorrect 
today specifying that both properties must be provided.

If the group doesn't want to support only providing one of the properties, then 
I would expect that the onError callback is called when only one is provided 
rather than simply ignoring them as is the case with iOS and Windows Phone.

I posted my sample application and a spreadsheet with my results to 
https://github.com/johnwargo/camera_res_test

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Camera targetWidth & targetHeight

[John M. Wargo]

Yes, that's what I determined in my testing. IMHO the other platforms should do 
that as well. No need to force both if the developer simply wants to set one of 
them. The docs say both are required - either Android is wrong or the other 
platforms are wrong.

I say we remove that reference from the docs and update the other platforms so 
they work like Android does. Android is right on only requiring one of the 
parameters plus it properly deals with the device in portrait or landscape mode 
(which iOS does not).

On 12/2/2013 10:18 PM, Simon MacDonald wrote:

IIRC on Android if you only specify the width or height it will determine
what the other value should be by using the same aspect ration as the
original image.


Simon Mac Donald
http://hi.im/simonmacdonald


On Mon, Dec 2, 2013 at 10:15 PM, John M. Wargo  wrote:


A while back I posted a question regarding Camera targetWidth &
targetHeight properties and how they worked. After some discussion, the
conclusion I reached was that the documentation couldn't be correct about
how it worked since there was no way to determine the camera's resolution
with the current API but the docs said I had to provide both parameters.  I
said I'd do some testing and I have finally gotten around to completing it.
Here's what I discovered:

I created an application that allowed me to pass in different values for
targetWidth & targetHeight when taking a picture. I tested at the following
image sizes: 640x480, 800x600, 1024x768 as well as setting only the
targetWidth to 1024 or only the targetHeight to 768.

Here's the results:

Android
PortraitLandscape
480x640 640x480
600x800 800x600
768x10241024x768
768x10241024x768
768x10241024x768



iOS
PortraitLandscape
360x480 640x480
450x600 800x600
576x768 1024x768
2448x3264   3264x2448
2448x3264   3264x2448



Windows Phone 8
PortraitLandscape
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836


As you can see, Android properly implements the targetWidth & targetHeight
properties. On iOS, it supports setting both properties, but not instances
where only one is specified. Windows Phone 8 ignores the parameters
completely.  On iOS, when you turn the device on its side, the Camera API
applies the target width or height to the wrong axis (Android does this
well however).

I'm trying to test this on a BlackBerry device, but my development
environment is giving me fits right now. I'll work on it in the morning and
publish my results when I get them.

I would suggest that the android implementation is as expected and that
the other platforms need their implementations of targetWidth &
targetHeight adjusted so it works correctly. The documentation should be
updated as well as it's incorrect today specifying that both properties
must be provided.

If the group doesn't want to support only providing one of the properties,
then I would expect that the onError callback is called when only one is
provided rather than simply ignoring them as is the case with iOS and
Windows Phone.

I posted my sample application and a spreadsheet with my results to
https://github.com/johnwargo/camera_res_test

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

Re: Camera targetWidth & targetHeight

[John M. Wargo]

It occurred to me this morning that I didn't test a scenario where an application 
deliberately didn't maintain an appropriate aspect ratio with targetWidth & 
targetHeight.

I added a button to my app that set targetWidth to 2048 and targetHeight to 768.

On Android I got the following:

Portrait: 768x1024
Landscape: 1024x768

On iOS I got the following:

Portrait: 576x768
Landscape: 1024x768

Not what I expected. So apparently the API grabs the smaller property and 
applies a set aspect ratio to the resulting photo rather than try to do 
something weird. Notice again that on iOS the API applies the restriction 
weirdly in portrait.

On 12/2/2013 10:18 PM, Simon MacDonald wrote:

IIRC on Android if you only specify the width or height it will determine
what the other value should be by using the same aspect ration as the
original image.


Simon Mac Donald
http://hi.im/simonmacdonald


On Mon, Dec 2, 2013 at 10:15 PM, John M. Wargo  wrote:


A while back I posted a question regarding Camera targetWidth &
targetHeight properties and how they worked. After some discussion, the
conclusion I reached was that the documentation couldn't be correct about
how it worked since there was no way to determine the camera's resolution
with the current API but the docs said I had to provide both parameters.  I
said I'd do some testing and I have finally gotten around to completing it.
Here's what I discovered:

I created an application that allowed me to pass in different values for
targetWidth & targetHeight when taking a picture. I tested at the following
image sizes: 640x480, 800x600, 1024x768 as well as setting only the
targetWidth to 1024 or only the targetHeight to 768.

Here's the results:

Android
PortraitLandscape
480x640 640x480
600x800 800x600
768x10241024x768
768x10241024x768
768x10241024x768



iOS
PortraitLandscape
360x480 640x480
450x600 800x600
576x768 1024x768
2448x3264   3264x2448
2448x3264   3264x2448



Windows Phone 8
PortraitLandscape
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836


As you can see, Android properly implements the targetWidth & targetHeight
properties. On iOS, it supports setting both properties, but not instances
where only one is specified. Windows Phone 8 ignores the parameters
completely.  On iOS, when you turn the device on its side, the Camera API
applies the target width or height to the wrong axis (Android does this
well however).

I'm trying to test this on a BlackBerry device, but my development
environment is giving me fits right now. I'll work on it in the morning and
publish my results when I get them.

I would suggest that the android implementation is as expected and that
the other platforms need their implementations of targetWidth &
targetHeight adjusted so it works correctly. The documentation should be
updated as well as it's incorrect today specifying that both properties
must be provided.

If the group doesn't want to support only providing one of the properties,
then I would expect that the onError callback is called when only one is
provided rather than simply ignoring them as is the case with iOS and
Windows Phone.

I posted my sample application and a spreadsheet with my results to
https://github.com/johnwargo/camera_res_test

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

Camera API: correctOrientation

[John M. Wargo]

Can someone explain to me what correctOrientation is supposed to do?

I just spent the last hour or so trying everything I can think of to make this 
thing do its voodo on Android and iOS and I can't tell the difference between 
photos taken with correctOrientation : true and
correctOrientation : false. either I don't know what I'm looking for, I can't 
code or this option simply does nothing. :-)

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Camera API: correctOrientation

[John M. Wargo]

Josh,

That's the PhoneGap 1.7 docs you linked - when you look at the Cordova 3.2 docs 
(http://docs.phonegap.com/en/3.2.0/cordova_camera_camera.md.html#cameraOptions),
 it does not list _any_ issues with correctOrientation on Android or iOS. I 
expect it not to work on Windows Phone because it's listed in the docs as being 
a limitation, but not on Android or iOS.

I'm not a newb; I'm not asking because I'm too stupid to look in the documentation first. 
I've written a book on PhoneGap as well as a book on Cordova 3.0, so I know how most of 
this works and to look at the docs first. I'm hoping that I don't have to begin any 
question with "I've already looked in the docs, but..."

I started with the documentation and all it says is:

"Rotate the image to correct for the orientation of the device during capture"

Not a very clear description of what actually happens. You're right though, I'm not really asking 
what it's supopsed to do, but instead "does it work?" and if so, "Any idea why it 
isn't working for me?"

I've written an application that takes a picture without the option defined and 
with the option set to true as well as false and on Android or iOS devices; I 
can't see any difference in the photos for all three options.

So, am I missing something and this just not supposed to work? Or is something 
else biting me in the butt here?

On 12/4/2013 8:25 PM, Josh Soref wrote:

John wrote:

Can someone explain to me what correctOrientation is supposed to do?

http://docs.phonegap.com/en/1.7.0/cordova_camera_camera.md.html

Lists a bunch of platforms that don't implement it.

My guess is that some older platforms wouldn't automatically switch between 
portrait and landscape orientations for photos.
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

Re: Camera API: correctOrientation

[John M. Wargo]

I can't get it to do anything on iOS, so I think it's broken.

Any chance someone can do a quick test to confirm my suspicion? Probably need 
to remove it from the docs if it doesn't do anything.

On 12/4/2013 8:41 PM, Jesse wrote:

It appears to do nothing, except on iOS.
It is listed as supported on iOS and Android, and back in 1.7, it was iOS
only,

Android does this:
this.correctOrientation = args.getBoolean(8);

iOS uses it after the image is captured, and calls
imageCorrectedForCaptureOrientation
[1] which rotates it according to the orientation of the camera when the
picture was taken.


[1]
https://github.com/apache/cordova-plugin-camera/blob/master/src/ios/CDVCamera.m#L455


@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:25 PM, Josh Soref  wrote:


John wrote:

Can someone explain to me what correctOrientation is supposed to do?

http://docs.phonegap.com/en/1.7.0/cordova_camera_camera.md.html

Lists a bunch of platforms that don't implement it.

My guess is that some older platforms wouldn't automatically switch
between portrait and landscape orientations for photos.
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute non-public
information. Any use of this information by anyone other than the intended
recipient is prohibited. If you have received this transmission in error,
please immediately reply to the sender and delete this information from
your system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Re: Camera API: correctOrientation

[John M. Wargo]

Jesse,

Thanks for providing that information.

I downloaded an EXIF property viewer and notice that with correctOrientation 
missing or set to false, there are 18 EXIF properties in the file. When I 
enable correctOrientation, another 30 EXIF properties are added to the file 
(for a total of 48).

Do you know what part of this actually affects orientation? There's an 
orientation EXIF property, but it's set to 0 for all three of my test files.

Enabling this option adds GPS information to image files on iOS as well. I 
wonder if this particular option is not named correctly. Should it be called 
something like enableEXIF with the documentation explaining what features it 
adds to a file.


On 12/4/2013 9:04 PM, Jesse wrote:

It definitely does something, you just may not notice it.
If you try to display an image you took in your app on iOS in any image
viewer that does not correctly interpret exif, then the picture will still
display correctly.
If you remove the code, it will not.

@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:59 PM, John M. Wargo  wrote:


I can't get it to do anything on iOS, so I think it's broken.

Any chance someone can do a quick test to confirm my suspicion? Probably
need to remove it from the docs if it doesn't do anything.


On 12/4/2013 8:41 PM, Jesse wrote:


It appears to do nothing, except on iOS.
It is listed as supported on iOS and Android, and back in 1.7, it was iOS
only,

Android does this:
this.correctOrientation = args.getBoolean(8);

iOS uses it after the image is captured, and calls
imageCorrectedForCaptureOrientation
[1] which rotates it according to the orientation of the camera when the
picture was taken.


[1]
https://github.com/apache/cordova-plugin-camera/blob/
master/src/ios/CDVCamera.m#L455


@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:25 PM, Josh Soref  wrote:

  John wrote:

Can someone explain to me what correctOrientation is supposed to do?


http://docs.phonegap.com/en/1.7.0/cordova_camera_camera.md.html

Lists a bunch of platforms that don't implement it.

My guess is that some older platforms wouldn't automatically switch
between portrait and landscape orientations for photos.
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public
information. Any use of this information by anyone other than the
intended
recipient is prohibited. If you have received this transmission in error,
please immediately reply to the sender and delete this information from
your system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be
unlawful.

Re: Camera API: correctOrientation

[John M. Wargo]

Jesse,

I've been thinking about what you said and I'm not getting it. I created an app 
that has three buttons, one takes a picture without correctOrientation even 
defined, another sets correctOrientation to true while the last one sets 
correctOrientation to false.

When I look at the photos on my Mac or in Windows Explorer, all three photos 
have the same orientation.

When I look at the EXIF properties in an EXIF editor, all three photos have 
orientation set the same value. The editor says its 0, but the field seems to 
be a two byte value which contains 00 01.

Since I'm comparing three photos at the same time, one of them should be turned 
on its side (the one where correctOrientation is true) while the other two are 
displayed in portrait orientation. That's expected behavior based on what you 
say below, but that's not what's happening for me.

I'm still leaning toward this particular option being broken.

On 12/4/2013 9:04 PM, Jesse wrote:

It definitely does something, you just may not notice it.
If you try to display an image you took in your app on iOS in any image
viewer that does not correctly interpret exif, then the picture will still
display correctly.
If you remove the code, it will not.

@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:59 PM, John M. Wargo  wrote:


I can't get it to do anything on iOS, so I think it's broken.

Any chance someone can do a quick test to confirm my suspicion? Probably
need to remove it from the docs if it doesn't do anything.


On 12/4/2013 8:41 PM, Jesse wrote:


It appears to do nothing, except on iOS.
It is listed as supported on iOS and Android, and back in 1.7, it was iOS
only,

Android does this:
this.correctOrientation = args.getBoolean(8);

iOS uses it after the image is captured, and calls
imageCorrectedForCaptureOrientation
[1] which rotates it according to the orientation of the camera when the
picture was taken.


[1]
https://github.com/apache/cordova-plugin-camera/blob/
master/src/ios/CDVCamera.m#L455


@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:25 PM, Josh Soref  wrote:

  John wrote:

Can someone explain to me what correctOrientation is supposed to do?


http://docs.phonegap.com/en/1.7.0/cordova_camera_camera.md.html

Lists a bunch of platforms that don't implement it.

My guess is that some older platforms wouldn't automatically switch
between portrait and landscape orientations for photos.
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public
information. Any use of this information by anyone other than the
intended
recipient is prohibited. If you have received this transmission in error,
please immediately reply to the sender and delete this information from
your system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be
unlawful.

Re: Camera API: correctOrientation

[John M. Wargo]

That makes sense. As I only have this iOS 7 device, can someone do a quick test 
on an older version of the OS?

On 12/5/2013 9:51 AM, Andrew Grieve wrote:

One explanation is that the iOS camera now always rotates the image for you?


On Thu, Dec 5, 2013 at 9:11 AM, John M. Wargo  wrote:


Jesse,

I've been thinking about what you said and I'm not getting it. I created
an app that has three buttons, one takes a picture without
correctOrientation even defined, another sets correctOrientation to true
while the last one sets correctOrientation to false.

When I look at the photos on my Mac or in Windows Explorer, all three
photos have the same orientation.

When I look at the EXIF properties in an EXIF editor, all three photos
have orientation set the same value. The editor says its 0, but the field
seems to be a two byte value which contains 00 01.

Since I'm comparing three photos at the same time, one of them should be
turned on its side (the one where correctOrientation is true) while the
other two are displayed in portrait orientation. That's expected behavior
based on what you say below, but that's not what's happening for me.

I'm still leaning toward this particular option being broken.


On 12/4/2013 9:04 PM, Jesse wrote:


It definitely does something, you just may not notice it.
If you try to display an image you took in your app on iOS in any image
viewer that does not correctly interpret exif, then the picture will still
display correctly.
If you remove the code, it will not.

@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:59 PM, John M. Wargo  wrote:

  I can't get it to do anything on iOS, so I think it's broken.

Any chance someone can do a quick test to confirm my suspicion? Probably
need to remove it from the docs if it doesn't do anything.


On 12/4/2013 8:41 PM, Jesse wrote:

  It appears to do nothing, except on iOS.

It is listed as supported on iOS and Android, and back in 1.7, it was
iOS
only,

Android does this:
this.correctOrientation = args.getBoolean(8);

iOS uses it after the image is captured, and calls
imageCorrectedForCaptureOrientation
[1] which rotates it according to the orientation of the camera when the
picture was taken.


[1]
https://github.com/apache/cordova-plugin-camera/blob/
master/src/ios/CDVCamera.m#L455


@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:25 PM, Josh Soref 
wrote:

   John wrote:


Can someone explain to me what correctOrientation is supposed to do?

  http://docs.phonegap.com/en/1.7.0/cordova_camera_camera.md.html

Lists a bunch of platforms that don't implement it.

My guess is that some older platforms wouldn't automatically switch
between portrait and landscape orientations for photos.
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public
information. Any use of this information by anyone other than the
intended
recipient is prohibited. If you have received this transmission in
error,
please immediately reply to the sender and delete this information from
your system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be
unlawful.

Re: Camera API: correctOrientation

[John M. Wargo]

Here's the test app: https://github.com/johnwargo/camera_correctOrientation

I ran some tests on Android and orientation is 1 (instead of 0 on iOS) I put 
some screen shots in the repository to show what I'm seeing.

On 12/5/2013 2:16 PM, purplecabbage wrote:

Looking at the code for ios, correctOrientation doesn't modify exif, it rotates 
image bits.

Can you share your test app John?

Sent from my iPhone


On Dec 5, 2013, at 7:42 AM, "John M. Wargo"  wrote:

That makes sense. As I only have this iOS 7 device, can someone do a quick test 
on an older version of the OS?


On 12/5/2013 9:51 AM, Andrew Grieve wrote:
One explanation is that the iOS camera now always rotates the image for you?



On Thu, Dec 5, 2013 at 9:11 AM, John M. Wargo  wrote:

Jesse,

I've been thinking about what you said and I'm not getting it. I created
an app that has three buttons, one takes a picture without
correctOrientation even defined, another sets correctOrientation to true
while the last one sets correctOrientation to false.

When I look at the photos on my Mac or in Windows Explorer, all three
photos have the same orientation.

When I look at the EXIF properties in an EXIF editor, all three photos
have orientation set the same value. The editor says its 0, but the field
seems to be a two byte value which contains 00 01.

Since I'm comparing three photos at the same time, one of them should be
turned on its side (the one where correctOrientation is true) while the
other two are displayed in portrait orientation. That's expected behavior
based on what you say below, but that's not what's happening for me.

I'm still leaning toward this particular option being broken.



On 12/4/2013 9:04 PM, Jesse wrote:

It definitely does something, you just may not notice it.
If you try to display an image you took in your app on iOS in any image
viewer that does not correctly interpret exif, then the picture will still
display correctly.
If you remove the code, it will not.

@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:59 PM, John M. Wargo  wrote:

I can't get it to do anything on iOS, so I think it's broken.

Any chance someone can do a quick test to confirm my suspicion? Probably
need to remove it from the docs if it doesn't do anything.


On 12/4/2013 8:41 PM, Jesse wrote:

It appears to do nothing, except on iOS.

It is listed as supported on iOS and Android, and back in 1.7, it was
iOS
only,

Android does this:
this.correctOrientation = args.getBoolean(8);

iOS uses it after the image is captured, and calls
imageCorrectedForCaptureOrientation
[1] which rotates it according to the orientation of the camera when the
picture was taken.


[1]
https://github.com/apache/cordova-plugin-camera/blob/
master/src/ios/CDVCamera.m#L455


@purplecabbage
risingj.com


On Wed, Dec 4, 2013 at 5:25 PM, Josh Soref 
wrote:

  John wrote:


Can someone explain to me what correctOrientation is supposed to do?

http://docs.phonegap.com/en/1.7.0/cordova_camera_camera.md.html

Lists a bunch of platforms that don't implement it.

My guess is that some older platforms wouldn't automatically switch
between portrait and landscape orientations for photos.
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public
information. Any use of this information by anyone other than the
intended
recipient is prohibited. If you have received this transmission in
error,
please immediately reply to the sender and delete this information from
your system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be
unlawful.

Re: Help required on moving files

[John M. Wargo]

Prasad,

This is a list for developers working on the Cordova Framework. If you want help 
using Cordova, you should post your questions to: 
https://groups.google.com/forum/#!forum/phonegap 


The Camera API has an option for saving photos to the photo album. 
http://cordova.apache.org/docs/en/3.1.0/cordova_camera_camera.md.html#Camera. 


On 12/6/2013 3:27 AM, Prasad Ravindra Sangodkar wrote:

Hi,

I have an requirement, where I need to move some photos from my app folder(Eg: 
"www/img/gallery/photo1.png") to the phone gallery for both android & ios.

I am using cordova with angularJS.

Can you please guide me in getting this done.

Thanks,
Prasad S.

Fwd: Camera targetWidth & targetHeight

[John M. Wargo]

So, does anyone have an opinion on how this discrepancy should be addressed? 
The methods work differently on different platforms and I think they should 
work the same.

To me Android works as I expect it should - setting the properties along the 
right axis. Do I need to file JIRA tickets about bringing iOS into alignment?

Also, what about when only one parameter is provided? Should we decide how this 
is supposed to work and implement it across the different platforms?  I'm for 
supporting only one parameter, allows me to set the one side and let the camera 
aspect ratio determine the other.

 Original Message 
Subject:Camera targetWidth & targetHeight
Date:   Mon, 02 Dec 2013 22:15:06 -0500
From:   John M. Wargo 
To: Cordova Dev 



A while back I posted a question regarding Camera targetWidth & targetHeight 
properties and how they worked. After some discussion, the conclusion I reached was 
that the documentation couldn't be correct about how it worked since there was no 
way to determine the camera's resolution with the current API but the docs said I 
had to provide both parameters.  I said I'd do some testing and I have finally 
gotten around to completing it. Here's what I discovered:

I created an application that allowed me to pass in different values for 
targetWidth & targetHeight when taking a picture. I tested at the following 
image sizes: 640x480, 800x600, 1024x768 as well as setting only the targetWidth to 
1024 or only the targetHeight to 768.

Here's the results:

Android
PortraitLandscape
480x640 640x480
600x800 800x600
768x10241024x768
768x10241024x768
768x10241024x768



iOS
PortraitLandscape
360x480 640x480
450x600 800x600
576x768 1024x768
2448x3264   3264x2448
2448x3264   3264x2448



Windows Phone 8
PortraitLandscape
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836
1836x3264   3264x1836


As you can see, Android properly implements the targetWidth & targetHeight 
properties. On iOS, it supports setting both properties, but not instances where 
only one is specified. Windows Phone 8 ignores the parameters completely.  On iOS, 
when you turn the device on its side, the Camera API applies the target width or 
height to the wrong axis (Android does this well however).

I'm trying to test this on a BlackBerry device, but my development environment 
is giving me fits right now. I'll work on it in the morning and publish my 
results when I get them.

I would suggest that the android implementation is as expected and that the other 
platforms need their implementations of targetWidth & targetHeight adjusted so 
it works correctly. The documentation should be updated as well as it's incorrect 
today specifying that both properties must be provided.

If the group doesn't want to support only providing one of the properties, then 
I would expect that the onError callback is called when only one is provided 
rather than simply ignoring them as is the case with iOS and Windows Phone.

I posted my sample application and a spreadsheet with my results to 
https://github.com/johnwargo/camera_res_test

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
------

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: CLI version to install

[John M. Wargo]

I did not know that, thanks!

On 12/24/2013 2:41 PM, Dan Moore wrote:

Hi John,

I believe

npm view cordova

shows all the versions available in npm.

Dan

Re: CLI version to install

[John M. Wargo]

I didn't know that either, thanks. Learn something new every day.

Merry Christmas all and to all a good night.

On 12/24/2013 3:40 PM, Brian LeRoux wrote:

Or

`npm info cordova`
On Dec 25, 2013 5:49 AM, "Dan Moore"  wrote:


Hi John,

I believe

npm view cordova

shows all the versions available in npm.

Dan

Re: template?

[John M. Wargo]

sorry, not JSON file, but JSON string.

On 1/3/2014 11:16 AM, John Wargo wrote:

I thought I saw a thread a while back that said you'd be able to pass the CLI 
create command a path to a project folder that contains the web application 
template to use for the new project. I just installed 3.3 and according to the 
help, the 4th parameter points to a JSON file that contains key/value pairs 
that will be added to the project's config.json file.  Did I miss something?  I 
thought the team had added a way for developers to specify the web application 
project that would be used.

Re: Hangout?

[John M. Wargo]

Me too. I dropped off because I didn't' want to eat up a slot.

On 1/29/2014 12:30 PM, Lisa Seacat DeLuca wrote:

What's the URL for the non-live people.  The listeners?  I dont' want to take 
up a spot for larger groups but I'd like to listen in.



*Lisa Seacat DeLuca*
Emerging Mobile Software Engineer - IBM Master Inventor
SWG Emerging Internet Standards
--
*Phone:*1-410-332-2128| *Mobile:*1-415-787-4589*
E-mail:*_ldel...@us.ibm.com_ <mailto:ldel...@us.ibm.com>*
personal website: *_lisaseacat.com_ <http://lisaseacat.com/>*
Chat:*Sametime: ldel...@us.ibm.com *
Find me on:*LinkedIn: http://www.linkedin.com/in/lisaseacat 
<http://www.linkedin.com/in/lisaseacat>Twitter: https://twitter.com/LisaSeacat 
<https://twitter.com/LisaSeacat>*and within IBM on:*IBM Connections: 
https://w3-connections.ibm.com/profiles/html/profileView.do?key=2e1afd56-daa9-428e-8f4a-2fa7516940c0
 
<https://w3-connections.ibm.com/profiles/html/profileView.do?key=2e1afd56-daa9-428e-8f4a-2fa7516940c0>
   
IBM

100 East Pratt St 21-2212
Baltimore, MD 21202-1009
United States






From: Andrew Grieve 
To: dev 
Date: 01/29/2014 12:28 PM
Subject: Re: Hangout?
Sent by: agri...@google.com
--



Come on in!
https://plus.google.com/hangouts/_/hoaevent/AP36tYf6UPXu7iH0JI5udIQwnbLx1JBdZw7XFq7Mdb3-BkZ3gvKh8A?authuser=0&hl=en-GB


On Wed, Jan 29, 2014 at 12:25 PM, Ken Wallis  wrote:

> Yup, Steve is just getting setup
>
> Sent from my BlackBerry 10 smartphone.
>   Original Message
> From: Wargo, John
> Sent: Wednesday, January 29, 2014 9:21 AM
> To: dev@cordova.apache.org
> Reply To: dev@cordova.apache.org
> Subject: Hangout?
>
>
> The hangout is in a few minutes, right?
>
> John M. Wargo
> Twitter: @johnwargo<https://twitter.com/johnwargo>
>
>

Hooks?

[John M. Wargo]

So, what exactly are hooks?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Hooks?

[John M. Wargo]

See, even though I'm not contributing code to the project, I still add value 
from pointing out where things aren't explained very well. :=)

On 1/29/2014 5:19 PM, Brian LeRoux wrote:

Added an issue to, you know, document hooks. ;)

Great first bug!

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




On Wed, Jan 29, 2014 at 10:32 AM, Dick Van den Brink <
d_vandenbr...@outlook.com> wrote:


I created 2 simple ones here:
https://github.com/DickvdBrink/cordova-hooks

The only docs for it are here I guess:
https://github.com/apache/cordova-cli/blob/master/templates/hooks-README.md





From: shaz...@gmail.com
Date: Wed, 29 Jan 2014 10:22:58 -0800
Subject: Re: Hooks?
To: dev@cordova.apache.org

When you create a project using the CLI, there is a hidden folder called
".cordova", in it is a folder called "hooks" which contain hook folders
that you can add scripts to. See example:


https://github.com/SpiderOak/SpiderOakMobileClient/tree/master/.cordova/hooks


On Wed, Jan 29, 2014 at 10:02 AM, Ian Clelland 
Hooks are scripts that can be run at various times in the cordova build
process. There is a directory for them, with subdirectories for each

time:

pre-prepare, post-prepare, pre-build, post-build, etc.

They're part of cordova-cli, which runs them automatically. I don't

know if

they're properly documented anywhere.




On Wed, Jan 29, 2014 at 12:59 PM, John M. Wargo 
wrote:


So, what exactly are hooks?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

targetWidth and targetHeight are not being interpreted consistently across platforms

[John M. Wargo]

Finally got around to submitting the JIRA ticket on the camera api targetWidth 
and targetHeight issues I documented last year. Sorry for the delay - had yet 
another book to finish...

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

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Looking forward to contribute | Introducing myself

[John M. Wargo]

Have you looked here: 
http://cordova.apache.org/docs/en/3.3.0/guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide.

On 2/5/2014 11:08 PM, Asanka Nissanka wrote:

I would love to share my experience on plugin development.

I had a look at the wiki and I need to whether there are any existing docs
on plugin development, in case I have missed. And if I am writing one,
where I should be adding that ?

On Tue, Feb 4, 2014 at 5:27 AM, Marcel Kinard  wrote:


Welcome! A great starting point is
http://wiki.apache.org/cordova/ContributorWorkflow

One of the things I've been interested in is a "Plugin Development Guide"
being added to the docs. Would you have interest in sharing your experience
with other potential plugin developers?

Re: cordova-lib versioning proposal

[John M. Wargo]

Rush album titles.

On 4/17/2014 5:08 PM, Brian LeRoux wrote:

Since cordova-lib is going to be a sort of container for a whole bunch of
node modules with their own versioning in package.json we need to come up
with our convention for tagging releases of the aggregate cordova-lib
itself.

Ubuntu probably has the most fun names. We probably want at least one
integer to make it obvious what is new/old.

We could do street names. Race horse names. Famous robots. Something! Ideas.

Re: Hooks

[John M. Wargo]

But a complete project template could include hooks and even merges.

John M. Wargo

> On Apr 22, 2014, at 12:11 PM, "Brian LeRoux"  wrote:
> 
> working only for www makes sense to me. if I'm creating a wholesale copy
> why not just cp -r? changing the namespace?
> 
> 
>> On Tue, Apr 22, 2014 at 8:53 AM, Andrew Grieve  wrote:
>> 
>> There's an outstanding bug that --copy-from and --link-to work only for
>> www/. https://issues.apache.org/jira/browse/CB-5833. Would be great if
>> anyone wanted to take it on :)
>> 
>> 
>>> On Tue, Apr 22, 2014 at 9:38 AM, Wargo, John  wrote:
>>> 
>>> I was relying upon the docs. The CLI help is pretty unreadable in a
>>> terminal window on Windows as it's written for a 120 character wide
>> screen
>>> for some reason and Windows terminal by default is 80 characters wide.  I
>>> guess we need to get the docs updated to reflect these parameters. I'll
>>> submit a ticket and perhaps fix this.
>>> 
>>> What about hooks though? It seems that the copyfrom option is for the www
>>> folder contents, but what about merges and hooks? Shouldn't a 'complete'
>>> project template include both as well?  It seems to me that the copyto
>>> option should copy to the root project level which would then allow
>>> developers to include stuff in hooks and merges as well as www when
>> copying
>>> over a project template.
>>> 
>>> What do you think?
>>> 
>>> John M. Wargo
>>> SCN Blog: http://scn.sap.com/blogs/johnwargo
>>> Twitter: @johnwargo
>>> 
>>> -Original Message-
>>> From: Shazron [mailto:shaz...@gmail.com]
>>> Sent: Monday, April 21, 2014 1:29 PM
>>> To: dev@cordova.apache.org
>>> Subject: Re: Hooks
>>> 
>>> In the help for cordova create in 3.4, there is the --copy-from and
>>> --link-to options.
>>> 
>>> 
>>> 
>>>> On Mon, Apr 21, 2014 at 10:22 AM, John Wargo  wrote:
>>>> 
>>>> Regarding hooks, is there an easy way to deploy them to your project?
>> For
>>>> example, with the ability to specify a project template to use with the
>>> CLI
>>>> create command, can that include hooks?
>>>> 
>>>> I thought the template option was added to the CLI, but the 3.4 CLI
>> docs
>>>> don't mention it:
>>> http://cordova.apache.org/docs/en/3.4.0/guide_cli_index.
>>>> md.html#The%20Command-Line%20Interface. Is it in there?
>> 

Re: HTML5DevConf Intro talk slides & interview

[John M. Wargo]

UI is way beyond the scope of Cordova. If one were included, most would yank it 
out and use something else. Use whatever you want, it's HTML, CSS and 
JavaScript.

John M. Wargo

> On Jun 27, 2014, at 3:34 PM, "Ajai Khattri"  wrote:
> 
>> On Wed, May 28, 2014 at 04:27:24PM -0400, Lisa Seacat DeLuca wrote:
>> 
>> I received a wide range of questions following my session including basic 
>> getting started Apache Cordova questions. the future direction of the 
>> Apache Cordova project, or confusion in recognizing that Cordova is merely 
>> the Native-web bridge and there is no user experience component.  I 
>> explained that developers are free to leverage any framework or UX 
>> techniques they wish, to create a seamless native look and feel.  For some 
>> reason many of the developers had a hard time wrapping their head around 
>> that.  It's almost like they expected the UI styling to be part of 
>> Cordova.
> 
> Speaking as a developer who recently started using Cordova, I would say
> not having a UI library merely adds to the load and increases the
> learning curve. I initially had looked at Titanium for that very reason.
> 
> I eventually came back to Cordova but ONLY because I found Ionic
> (ionicframework.com) which also integrates AngularJS quite nicely.
> 
> Having a resource that lists possible frameworks and/or combinations
> that work with/on top of Cordova would go a long way.
> 
> 
> -- 
> Aj.
> FaceBook: facebook.com/ajaikhattri
> EnoLand: http://flip.it/Gig0n

Re: Need help to develop a plugin to call a native IOS Libraries from the Phone gap

[John M. Wargo]

Ram,

This is the list used by the developers of Apache Cordova. If you want to know 
how to do anything with Apache Cordova, the best place to start is the 
documentation at http://cordova.apache.org/docs/en/3.5.0/.

Support questions are best answered on Stack Overflow: 
http://stackoverflow.com/search?q=cordova.

There is an excellent book that can show everything you need to know about 
Apache Cordova, including how to write plugins: Apache Cordova 3 Programming 
(www.cordovaprogramming.com).

On 9/14/2014 4:20 AM, RAM Mohan Adduri wrote:


Dear Team –

I am just started developing Phonegap plugin to call a native service libraries 
in IPad so can you please help me on this. It would be great if you can provide 
some resources to understand how to develop this.

Regards,

Ram


RAM Mohan Adduri

Consultant
Temporary Users

PO Box 217, Doha, Qatar

T: 28746M:
Follow us on Twitter  and Facebook 






--

The information in this email and any attachments thereto may contain 
information that is confidential, protected by intellectual property rights, 
and may be legally privileged. It is intended solely for the addressee(s). 
Access to this email by anyone else is unauthorized. Any use, disclosure, 
copying, or distribution of the information contained herein by persons other 
than the designated addressee is unauthorized and may be unlawful. If you are 
not the intended recipient, you should delete the message immediately from your 
system. If you believe that you have received this email in error, please 
contact the sender. Any views expressed in this email and its attachments are 
those of the individual sender except where the sender expressly states them to 
be the views of Ooredoo.

Cordova-Create Module

[John M. Wargo]

I recently created a node module called Cordova-create that takes care of the 
typical developer new project workflow.

It makes calls to create, then adds a set of platforms and a set of plugins to 
the project.  I did this because I found myself performing the same steps over 
and over again and wanted a simpler way to do it. I made it configurable, so 
you can edit a cordova-create.json file in the home folder to specify the 
platforms and plugins to add.

I published it to npm so others can use it, you can find it here: 
https://www.npmjs.org/package/cordova-create.

Did I make a mistake by calling it cordova-create?  I don't want to confuse 
this module with the other cordova stuff, but I named it the way that made the 
most sense for me. Does anyone care that I named it that way?

targetWidth and targetHeight are not being interpreted consistently across platforms

[John M. Wargo]

Back in January I did a bunch of research on the issue I identified regarding 
how with the Camera API, targetwidth and target height are not implemented 
consistently across platforms. I just noticed that nobody is assigned to this 
ticket: https://issues.apache.org/jira/browse/CB-5942.

Is this something someone can take a look at? It's an inconsistency in the API.

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Cordova-Create Module

[John M. Wargo]

Well...with that in mind. If this is something you think would be useful in 
Cordova - you can go ahead and use it.

I've signed a CLA and I'm already contributing (not code, but stuff with the 
APIs and so on, hopefully docs in the near future), so if the project thinks 
it's useful, I can contribute it. I'd have to change the license, I simply 
grabbed the MIT license because it was easy, but that's not a problem.

On 9/14/2014 9:38 PM, Michal Mocny wrote:

A different name might be better, since we may publish a cordova-create
module in the future that literally just creates an empty shell (aka what
`cordova create` does).

I think this is more like a boilerplate app (akin to what yeoman does,
perhaps).  No suggestions beyond that.

Anyway, thanks for sharing!

-Michal

On Sun, Sep 14, 2014 at 10:00 AM, John M. Wargo  wrote:


I recently created a node module called Cordova-create that takes care of
the typical developer new project workflow.

It makes calls to create, then adds a set of platforms and a set of
plugins to the project.  I did this because I found myself performing the
same steps over and over again and wanted a simpler way to do it. I made it
configurable, so you can edit a cordova-create.json file in the home folder
to specify the platforms and plugins to add.

I published it to npm so others can use it, you can find it here:
https://www.npmjs.org/package/cordova-create.

Did I make a mistake by calling it cordova-create?  I don't want to
confuse this module with the other cordova stuff, but I named it the way
that made the most sense for me. Does anyone care that I named it that way?

Node Hook?

[John M. Wargo]

Is there anything special I have to do to run a node app as a hook on Windows?

I was experimenting with this yesterday on Cordova 3.5, and when I have the 
following hook as a before prepare:

#! /usr/bin/env node
console.log('this is a node module');

I get the following error:

The system cannot find the path specified.
Hook failed with error code 1: 
C:\Users\jwargo\dev\lunchmenu\hooks\before_prepare\test.js

So it's seeing the hook and not 'finding' it?

On Stack Overflow, the suggestion was to remove the first line and just have 
the console line:

console.log('this is a node module');

When I do that, I get a different error:

Hook failed with error code Unknown system errno 193: 
C:\Users\jwargo\dev\lunchmenu\hooks\before_prepare\test.js

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Node Hook?

[John M. Wargo]

Node is absolutely on the path - the cordova command works and I can run node 
test.js without error.

I'll check the line endings. Thanks.

On 9/22/2014 1:01 PM, Dick Van den Brink wrote:

I'm still on 3.4 so not sure about 3.5 but I know it doesnt work when you use 
windows newlines. Can you change it to unix newlines and check if that works? 
(+ is node in your path?)

Would expect a different error though...

Sent from my Windows Phone
____
From: John M. Wargo<mailto:jwarg...@gmail.com>
Sent: ‎22/‎09/‎2014 18:47
To: Cordova Dev<mailto:dev@cordova.apache.org>
Subject: Node Hook?

Is there anything special I have to do to run a node app as a hook on Windows?

I was experimenting with this yesterday on Cordova 3.5, and when I have the 
following hook as a before prepare:

  #! /usr/bin/env node
  console.log('this is a node module');

I get the following error:

  The system cannot find the path specified.
  Hook failed with error code 1: 
C:\Users\jwargo\dev\lunchmenu\hooks\before_prepare\test.js

So it's seeing the hook and not 'finding' it?

On Stack Overflow, the suggestion was to remove the first line and just have 
the console line:

  console.log('this is a node module');

When I do that, I get a different error:

  Hook failed with error code Unknown system errno 193: 
C:\Users\jwargo\dev\lunchmenu\hooks\before_prepare\test.js

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Node Hook?

[John M. Wargo]

That was it - the space in the shebang.

Thanks so much!!!

On 9/22/2014 1:02 PM, Mark Koudritsky wrote:

Looks like cordova couldn't find where node is on your system. On Windows
cordova is doing some hackish magic to deal with shebang lines. The code
for this magic is in extractSheBangInterpreter
<https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/hooker.js#L87>.
Not
sure, but it looks like you have a space after #! in your shebang line and
the regexp in extractSheBangInterpreter is not expecting it.

On Mon, Sep 22, 2014 at 12:46 PM, John M. Wargo  wrote:


Is there anything special I have to do to run a node app as a hook on
Windows?

I was experimenting with this yesterday on Cordova 3.5, and when I have
the following hook as a before prepare:

 #! /usr/bin/env node
 console.log('this is a node module');

I get the following error:

 The system cannot find the path specified.
 Hook failed with error code 1: C:\Users\jwargo\dev\lunchmenu\
hooks\before_prepare\test.js

So it's seeing the hook and not 'finding' it?

On Stack Overflow, the suggestion was to remove the first line and just
have the console line:

 console.log('this is a node module');

When I do that, I get a different error:

 Hook failed with error code Unknown system errno 193:
C:\Users\jwargo\dev\lunchmenu\hooks\before_prepare\test.js

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

Ubuntu requirements not met with CLI installation

[John M. Wargo]

I setup a clean ubuntu installation yesterday and get an error when creating a 
new project. Apparently during the CLI installation a required module isn't 
being installed. When you install QTCreator, the error goes away.

I've created a JIRA ticket for this: 
https://issues.apache.org/jira/browse/CB-7653 with complete details.

Plugman issues/questions

[John M. Wargo]

I'm playing around with plugman in Cordova 4.0 and have found some issues and 
have some questions.

First of all, the docs are incorrect and I've filed a ticket: 
https://issues.apache.org/jira/browse/CB-7894.  The example for adding a plugin 
is missing the install switch.:

$ plugman -platform  --project  --plugin  
[--plugins_dir ] [--www ] [-variable = [--variable 
= ...]]

It should be:

$ plugman install -platform  --project  --plugin 
[--plugins_dir ] [--www ] [-variable = [--variable 
= ...]]

The docs also say that the switch for uninstall is "--uninstall", but in my testing it's 
actually "uninstall"  - I've created a ticket for this: 
https://issues.apache.org/jira/browse/CB-7895.

The docs say to use the platform scripts to create a plugman project, but when 
I follow the links to the download, there's no download for Cordova 4.0. When 
will that be published?

When I unpublish my plugin, it says it's unpublished, but the entry is still 
there in the registry. Should I submit a ticket for this?

I can't find any information on what the plugman owner command does. When I 
execute it, I get an error:

C:\Users\jwargo\dev\myplugin>plugman owner ls
ENOENT, open 'C:\Users\jwargo\dev\myplugin\package.json'

I can't find anything in the docs that tells me I should be creating a 
package.json. Should I be?

I created one using npm init. Then, when I issue a plugman owner ls I get the 
following error:

404 Not Found: myplugin

Can someone explain to me how this is supposed to work? I can't seem to find 
any documentation on this command.

Regarding the registry, it doesn't explain anywhere how to set the description 
for the plugin - I'm assuming it's through a readme.md file. I also don't see 
anywhere I can login to the registry site and edit my entry. I'm assuming also 
that keywords are set through the package.json file?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Plugman issues/questions

[John M. Wargo]

Steve,

I'd love to make the changes, but I can't right now. With my day job and trying 
to finish up Apache Cordova 4 Programming at night, I won't be able to 
contribute any doc changes until after that is done.

Yeah, I figured as much, but the download link on the home page says "Download 
4.0" and there isn't one. So someone following the plugman and platform docs will be 
confused.

[1] doesn't have information about owner, all it says is:

$ plugman owner ls org.apache.cordova.core.file
$ plugman owner add username org.apache.cordova.core.file
$ plugman owner rm username org.apache.cordova.core.file

Which doesn't tell anything about what it means, what it's supposed to do and 
how it's supposed to work (sorry). when I execute an ls, I get an error. For 
the other ones, what am I adding and removing? a Plugin Repository user name? 
Npm user name? Just a name? There's no details, no examples, nothing. so I 
don't understand how I'm supposed to understand how to use this without any 
information except for the commands.  Where does owner write the information? 
The config.xml? somewhere else? Does this go to the registry? See what I mean?

Any chance you can provide me with a little background you have on owner?

I'll submit a ticket for unpublish.

On 10/29/2014 2:40 PM, Steven Gill wrote:

Hey John,

Thanks for filing the two issues. It would be great if you could send PRs
for them too! I believe the correct information is in this help file [1]

Platform scripts: the platforms were not bumped to version 4.0. What you
see at https://www.apache.org/dist/cordova/platforms/ is the latest
released platforms. 4.0.0 referes to the cordova cli version. You can read
more about our change in versioning at
http://cordova.apache.org/announcements/2014/10/16/cordova-4.html

[1] also has info on addUser and owner. This info needs to be copied over
to docs.cordova.io. Would love some help with that if you have time!

You should not be creating a package.json. plugman publish command will
create one based on values from your plugin.xml. It gets deleted after a
successful publish.

Plugman unpublish might be a bug. File it.

Checkout a existing plugins plugin.xml [2] to see how we set description,
repo, keywords, etc. If you have a README.md file, that will also get
uploaded on publish.

We don't have any login setup on the site. We have an existing issue at
[3]. Just no time to do it.

As you can see, our documentation around plugin publishing is severely
lacking. We could really use some help sprucing it up!

[1] https://github.com/apache/cordova-plugman/blob/master/doc/help.txt
[2] https://github.com/apache/cordova-plugin-file/blob/master/plugin.xml
[3] https://issues.apache.org/jira/browse/CB-7246



On Wed, Oct 29, 2014 at 10:43 AM, Brian LeRoux  wrote:


thats def a bug John / pls file!

On Wed, Oct 29, 2014 at 5:52 AM, John M. Wargo  wrote:


I'm playing around with plugman in Cordova 4.0 and have found some issues
and have some questions.

First of all, the docs are incorrect and I've filed a ticket:
https://issues.apache.org/jira/browse/CB-7894.  The example for adding a
plugin is missing the install switch.:

$ plugman -platform 
--project  --plugin  [--plugins_dir

]

[--www ] [-variable = [--variable =
...]]

It should be:

$ plugman install -platform 
--project  --plugin [--plugins_dir ]
[--www ] [-variable = [--variable =
...]]

The docs also say that the switch for uninstall is "--uninstall", but in
my testing it's actually "uninstall"  - I've created a ticket for this:
https://issues.apache.org/jira/browse/CB-7895.

The docs say to use the platform scripts to create a plugman project, but
when I follow the links to the download, there's no download for Cordova
4.0. When will that be published?

When I unpublish my plugin, it says it's unpublished, but the entry is
still there in the registry. Should I submit a ticket for this?

I can't find any information on what the plugman owner command does. When
I execute it, I get an error:

C:\Users\jwargo\dev\myplugin>plugman owner ls
ENOENT, open 'C:\Users\jwargo\dev\myplugin\package.json'

I can't find anything in the docs that tells me I should be creating a
package.json. Should I be?

I created one using npm init. Then, when I issue a plugman owner ls I get
the following error:

404 Not Found: myplugin

Can someone explain to me how this is supposed to work? I can't seem to
find any documentation on this command.

Regarding the registry, it doesn't explain anywhere how to set the
description for the plugin - I'm assuming it's through a readme.md file.
I also don't see anywhere I can login to the registry site and edit my
entry. I'm assuming also that keywords are set through the package.json
file?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

Re: Plugman issues/questions

[John M. Wargo]

Shaz,

Thanks. I just tried it against my registry entry and was able to get it to 
work.  There's a bug in plugman - if I don't provide a plugin ID, I get weird 
errors.

For example, if I issue "plugman owner ls" and don't provide a plugin ID, I get a 404 
error rather than something like "You did't provide a plugin name" I'll create a ticket.

On 10/29/2014 5:04 PM, Shazron wrote:

```
$ plugman owner ls org.apache.cordova.core.file
$ plugman owner add username org.apache.cordova.core.file
$ plugman owner rm username org.apache.cordova.core.file
```

plugins.cordova.io basically uses npm code on the backend, so it's similar
(substitute package for plugin). Each plugin on plugins.cordova.io has
owners -- i.e. people that have permissions to publish updates to the
plugin, "ls" here lists all owners (and their emails). Similarly "add" and
"rm" removes owners for each plugin.

On Wed, Oct 29, 2014 at 1:41 PM, John M. Wargo  wrote:


Steve,

I'd love to make the changes, but I can't right now. With my day job and
trying to finish up Apache Cordova 4 Programming at night, I won't be able
to contribute any doc changes until after that is done.

Yeah, I figured as much, but the download link on the home page says
"Download 4.0" and there isn't one. So someone following the plugman and
platform docs will be confused.

[1] doesn't have information about owner, all it says is:

$ plugman owner ls org.apache.cordova.core.file
$ plugman owner add username org.apache.cordova.core.file
$ plugman owner rm username org.apache.cordova.core.file

Which doesn't tell anything about what it means, what it's supposed to do
and how it's supposed to work (sorry). when I execute an ls, I get an
error. For the other ones, what am I adding and removing? a Plugin
Repository user name? Npm user name? Just a name? There's no details, no
examples, nothing. so I don't understand how I'm supposed to understand how
to use this without any information except for the commands.  Where does
owner write the information? The config.xml? somewhere else? Does this go
to the registry? See what I mean?

Any chance you can provide me with a little background you have on owner?

I'll submit a ticket for unpublish.


On 10/29/2014 2:40 PM, Steven Gill wrote:


Hey John,

Thanks for filing the two issues. It would be great if you could send PRs
for them too! I believe the correct information is in this help file [1]

Platform scripts: the platforms were not bumped to version 4.0. What you
see at https://www.apache.org/dist/cordova/platforms/ is the latest
released platforms. 4.0.0 referes to the cordova cli version. You can read
more about our change in versioning at
http://cordova.apache.org/announcements/2014/10/16/cordova-4.html

[1] also has info on addUser and owner. This info needs to be copied over
to docs.cordova.io. Would love some help with that if you have time!

You should not be creating a package.json. plugman publish command will
create one based on values from your plugin.xml. It gets deleted after a
successful publish.

Plugman unpublish might be a bug. File it.

Checkout a existing plugins plugin.xml [2] to see how we set description,
repo, keywords, etc. If you have a README.md file, that will also get
uploaded on publish.

We don't have any login setup on the site. We have an existing issue at
[3]. Just no time to do it.

As you can see, our documentation around plugin publishing is severely
lacking. We could really use some help sprucing it up!

[1] https://github.com/apache/cordova-plugman/blob/master/doc/help.txt
[2] https://github.com/apache/cordova-plugin-file/blob/master/plugin.xml
[3] https://issues.apache.org/jira/browse/CB-7246



On Wed, Oct 29, 2014 at 10:43 AM, Brian LeRoux  wrote:

  thats def a bug John / pls file!

On Wed, Oct 29, 2014 at 5:52 AM, John M. Wargo 
wrote:

  I'm playing around with plugman in Cordova 4.0 and have found some

issues
and have some questions.

First of all, the docs are incorrect and I've filed a ticket:
https://issues.apache.org/jira/browse/CB-7894.  The example for adding
a
plugin is missing the install switch.:

$ plugman -platform 
--project  --plugin  [--plugins_dir


]


[--www ] [-variable = [--variable =
...]]

It should be:

$ plugman install -platform 
--project  --plugin [--plugins_dir
]
[--www ] [-variable = [--variable =
...]]

The docs also say that the switch for uninstall is "--uninstall", but in
my testing it's actually "uninstall"  - I've created a ticket for this:
https://issues.apache.org/jira/browse/CB-7895.

The docs say to use the platform scripts to create a plugman project,
but
when I follow the links to the download, there's no download for Cordova
4.0. When will that be published?

When I unpublish my plugin, it says it's unpublished, but the entry is
still t

Re: Plugman issues/questions

[John M. Wargo]

Filed: https://issues.apache.org/jira/browse/CB-7900.

On 10/29/2014 1:43 PM, Brian LeRoux wrote:

thats def a bug John / pls file!

On Wed, Oct 29, 2014 at 5:52 AM, John M. Wargo  wrote:


I'm playing around with plugman in Cordova 4.0 and have found some issues
and have some questions.

First of all, the docs are incorrect and I've filed a ticket:
https://issues.apache.org/jira/browse/CB-7894.  The example for adding a
plugin is missing the install switch.:

$ plugman -platform 
--project  --plugin  [--plugins_dir ]
[--www ] [-variable = [--variable =
...]]

It should be:

$ plugman install -platform 
--project  --plugin [--plugins_dir ]
[--www ] [-variable = [--variable =
...]]

The docs also say that the switch for uninstall is "--uninstall", but in
my testing it's actually "uninstall"  - I've created a ticket for this:
https://issues.apache.org/jira/browse/CB-7895.

The docs say to use the platform scripts to create a plugman project, but
when I follow the links to the download, there's no download for Cordova
4.0. When will that be published?

When I unpublish my plugin, it says it's unpublished, but the entry is
still there in the registry. Should I submit a ticket for this?

I can't find any information on what the plugman owner command does. When
I execute it, I get an error:

C:\Users\jwargo\dev\myplugin>plugman owner ls
ENOENT, open 'C:\Users\jwargo\dev\myplugin\package.json'

I can't find anything in the docs that tells me I should be creating a
package.json. Should I be?

I created one using npm init. Then, when I issue a plugman owner ls I get
the following error:

404 Not Found: myplugin

Can someone explain to me how this is supposed to work? I can't seem to
find any documentation on this command.

Regarding the registry, it doesn't explain anywhere how to set the
description for the plugin - I'm assuming it's through a readme.md file.
I also don't see anywhere I can login to the registry site and edit my
entry. I'm assuming also that keywords are set through the package.json
file?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

Re: Plugman issues/questions

[John M. Wargo]

Steve,

You're right, I'm being an idiot. I'll make the changes today and submit the 
PR.  I'm just the tiniest bit intimidated by the process since I've not done it 
before.

On 10/29/2014 2:40 PM, Steven Gill wrote:

Hey John,

Thanks for filing the two issues. It would be great if you could send PRs
for them too! I believe the correct information is in this help file [1]

Platform scripts: the platforms were not bumped to version 4.0. What you
see at https://www.apache.org/dist/cordova/platforms/ is the latest
released platforms. 4.0.0 referes to the cordova cli version. You can read
more about our change in versioning at
http://cordova.apache.org/announcements/2014/10/16/cordova-4.html

[1] also has info on addUser and owner. This info needs to be copied over
to docs.cordova.io. Would love some help with that if you have time!

You should not be creating a package.json. plugman publish command will
create one based on values from your plugin.xml. It gets deleted after a
successful publish.

Plugman unpublish might be a bug. File it.

Checkout a existing plugins plugin.xml [2] to see how we set description,
repo, keywords, etc. If you have a README.md file, that will also get
uploaded on publish.

We don't have any login setup on the site. We have an existing issue at
[3]. Just no time to do it.

As you can see, our documentation around plugin publishing is severely
lacking. We could really use some help sprucing it up!

[1] https://github.com/apache/cordova-plugman/blob/master/doc/help.txt
[2] https://github.com/apache/cordova-plugin-file/blob/master/plugin.xml
[3] https://issues.apache.org/jira/browse/CB-7246



On Wed, Oct 29, 2014 at 10:43 AM, Brian LeRoux  wrote:


thats def a bug John / pls file!

On Wed, Oct 29, 2014 at 5:52 AM, John M. Wargo  wrote:


I'm playing around with plugman in Cordova 4.0 and have found some issues
and have some questions.

First of all, the docs are incorrect and I've filed a ticket:
https://issues.apache.org/jira/browse/CB-7894.  The example for adding a
plugin is missing the install switch.:

$ plugman -platform 
--project  --plugin  [--plugins_dir

]

[--www ] [-variable = [--variable =
...]]

It should be:

$ plugman install -platform 
--project  --plugin [--plugins_dir ]
[--www ] [-variable = [--variable =
...]]

The docs also say that the switch for uninstall is "--uninstall", but in
my testing it's actually "uninstall"  - I've created a ticket for this:
https://issues.apache.org/jira/browse/CB-7895.

The docs say to use the platform scripts to create a plugman project, but
when I follow the links to the download, there's no download for Cordova
4.0. When will that be published?

When I unpublish my plugin, it says it's unpublished, but the entry is
still there in the registry. Should I submit a ticket for this?

I can't find any information on what the plugman owner command does. When
I execute it, I get an error:

C:\Users\jwargo\dev\myplugin>plugman owner ls
ENOENT, open 'C:\Users\jwargo\dev\myplugin\package.json'

I can't find anything in the docs that tells me I should be creating a
package.json. Should I be?

I created one using npm init. Then, when I issue a plugman owner ls I get
the following error:

404 Not Found: myplugin

Can someone explain to me how this is supposed to work? I can't seem to
find any documentation on this command.

Regarding the registry, it doesn't explain anywhere how to set the
description for the plugin - I'm assuming it's through a readme.md file.
I also don't see anywhere I can login to the registry site and edit my
entry. I'm assuming also that keywords are set through the package.json
file?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

Plugman Platform for iOS incorrectly configures the plugin.xml file.

[John M. Wargo]

I noticed something with Plugman this morning. When you add iOS as a platform, 
the plugin.xml file points to src/ios/CDVpluginname.m, but the file created by 
Plugman is actually src/ios/pluginname.m.



Submitted a ticket: https://issues.apache.org/jira/browse/CB-7909.
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Plugman issues/questions

[John M. Wargo]

Steve,

I'm trying to get setup to make the changes and submit them, but I'm not a big 
Git guy, so I'm running into some issues. Can you, or someone else, help me?

I'm working through the guide here: 
http://wiki.apache.org/cordova/IssueWorkflow.

It says I need to setup my environment using:

$ git clone https://git-wip-us.apache.org/repos/asf/cordova-docs.git
$ git remote add github https://github.com/you/cordova-docs.git


There seems to be a missing step there. Should it be?

$ git clone https://git-wip-us.apache.org/repos/asf/cordova-docs.git
$ cd cordova-docs
$ git remote add github https://github.com/you/cordova-docs.git


Later it says:

Before sending the pull request, you should ensure that your changes merge 
cleanly with the main documentation repository, and that the granularity of 
your commits make sense.

$ git checkout master
$ git pull apache master
$ git checkout CB-1234
$ git rebase master -i

There seems to be a step missing, when did I define a remote target of 'apache' to do the 
pull against?  The docs say: "The following commands will give you two remotes: 
origin (apache) and github (your repository). Replaceyouwith your github.com account name 
in the following commands:"

How does that first remote get set to 'apache'?

On 10/29/2014 2:40 PM, Steven Gill wrote:

Hey John,

Thanks for filing the two issues. It would be great if you could send PRs
for them too! I believe the correct information is in this help file [1]

Platform scripts: the platforms were not bumped to version 4.0. What you
see at https://www.apache.org/dist/cordova/platforms/ is the latest
released platforms. 4.0.0 referes to the cordova cli version. You can read
more about our change in versioning at
http://cordova.apache.org/announcements/2014/10/16/cordova-4.html

[1] also has info on addUser and owner. This info needs to be copied over
to docs.cordova.io. Would love some help with that if you have time!

You should not be creating a package.json. plugman publish command will
create one based on values from your plugin.xml. It gets deleted after a
successful publish.

Plugman unpublish might be a bug. File it.

Checkout a existing plugins plugin.xml [2] to see how we set description,
repo, keywords, etc. If you have a README.md file, that will also get
uploaded on publish.

We don't have any login setup on the site. We have an existing issue at
[3]. Just no time to do it.

As you can see, our documentation around plugin publishing is severely
lacking. We could really use some help sprucing it up!

[1] https://github.com/apache/cordova-plugman/blob/master/doc/help.txt
[2] https://github.com/apache/cordova-plugin-file/blob/master/plugin.xml
[3] https://issues.apache.org/jira/browse/CB-7246



On Wed, Oct 29, 2014 at 10:43 AM, Brian LeRoux  wrote:


thats def a bug John / pls file!

On Wed, Oct 29, 2014 at 5:52 AM, John M. Wargo  wrote:


I'm playing around with plugman in Cordova 4.0 and have found some issues
and have some questions.

First of all, the docs are incorrect and I've filed a ticket:
https://issues.apache.org/jira/browse/CB-7894.  The example for adding a
plugin is missing the install switch.:

$ plugman -platform 
--project  --plugin  [--plugins_dir

]

[--www ] [-variable = [--variable =
...]]

It should be:

$ plugman install -platform 
--project  --plugin [--plugins_dir ]
[--www ] [-variable = [--variable =
...]]

The docs also say that the switch for uninstall is "--uninstall", but in
my testing it's actually "uninstall"  - I've created a ticket for this:
https://issues.apache.org/jira/browse/CB-7895.

The docs say to use the platform scripts to create a plugman project, but
when I follow the links to the download, there's no download for Cordova
4.0. When will that be published?

When I unpublish my plugin, it says it's unpublished, but the entry is
still there in the registry. Should I submit a ticket for this?

I can't find any information on what the plugman owner command does. When
I execute it, I get an error:

C:\Users\jwargo\dev\myplugin>plugman owner ls
ENOENT, open 'C:\Users\jwargo\dev\myplugin\package.json'

I can't find anything in the docs that tells me I should be creating a
package.json. Should I be?

I created one using npm init. Then, when I issue a plugman owner ls I get
the following error:

404 Not Found: myplugin

Can someone explain to me how this is supposed to work? I can't seem to
find any documentation on this command.

Regarding the registry, it doesn't explain anywhere how to set the
description for the plugin - I'm assuming it's through a readme.md file.
I also don't see anywhere I can login to the registry site and edit my
entry. I'm assuming also that keywords are set through the package.json
file?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
















--

Firefox OS problem

[John M. Wargo]

Guys,

There seems to be a problem with the Firefox OS platform:

C:\Users\jwargo\dev\ac4p\compass>cordova platform add firefoxos
npm http GET https://registry.npmjs.org/cordova-firefoxos/3.6.3
npm http 401 https://registry.npmjs.org/cordova-firefoxos/3.6.3
Unable to fetch platform firefoxos: Error: unauthorized Name or password is 
incorrect.: cordova-firefoxos/3.6.3

C:\Users\jwargo\dev\ac4p\compass>


Some sort of password problem with npm?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Fwd: Firefox OS problem

[John M. Wargo]

Nevermind. Stupid User Problem.


 Original Message 
Subject:Firefox OS problem
Date:   Fri, 21 Nov 2014 21:27:40 -0500
From:   John M. Wargo 
To: Cordova Dev 



Guys,

There seems to be a problem with the Firefox OS platform:

C:\Users\jwargo\dev\ac4p\compass>cordova platform add firefoxos
npm http GET https://registry.npmjs.org/cordova-firefoxos/3.6.3
npm http 401 https://registry.npmjs.org/cordova-firefoxos/3.6.3
Unable to fetch platform firefoxos: Error: unauthorized Name or password is 
incorrect.: cordova-firefoxos/3.6.3

C:\Users\jwargo\dev\ac4p\compass>


Some sort of password problem with npm?

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
------

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Self Introduction Letter

[John M. Wargo]

Welcome!

You'll want to follow the process documented here: 
http://cordova.apache.org/#contribute.

On 12/28/2014 5:44 AM, koldv...@gmail.com wrote:

Dear Sir/Madam,


I would like to offer my services as contributor, especially as a developer, to 
your community.


I am a final year engineering student with major in computer science. I have 
high level fluency in programming in C++ and JAVA (J2SE) . I have developed 
mobile applications on various platforms such as Android( ADT-SDK) and 
Windows(Visual C#) as well as web applications with PHP, JavaScript and MySQL. 
I have also used Cordova as alternative.


Now I want to work on open source project and contribute to the community which 
will help boost my knowledge and experience.


Thanking You,




Yours sincerely,


-Siddharth Singh

Re: Created a plugin to help with local plugin development

[John M. Wargo]

You're probably right, but it seems to make sense to include it for consistency 
sake.

On 1/14/2015 7:40 PM, Shazron wrote:

I noticed that sometime ago - my thinking is, there is no more context
(.opts.plugin object) really after the plugin is uninstalled, that's why
the hook is not there.

On Wed, Jan 14, 2015 at 4:27 PM, Wargo, John  wrote:


Looking at the Hooks read me at
https://github.com/apache/cordova-lib/blob/master/cordova-lib/templates/hooks-README.md.
Looks like after_plugin_uninstall is missing from the list.   I'm assuming
it's supposed to be there? Let me know and I'll make the change.

John M. Wargo

-Original Message-
From: Michal Mocny [mailto:mmo...@google.com]
Sent: Monday, December 1, 2014 2:14 PM
To: dev
Subject: FYI: Created a plugin to help with local plugin development

Took the opportunity to use our new plugin hooks and created a plugin to
automate a tedious task I've been doing a lot of recently: plugin
re-installation.

https://github.com/mmocny/cordova-plugin-plugin-auto-upgrade

As per the README:


This plugin with automatically upgrade (re-install) a set of plugins
(specified by you) before every cordova prepare. This is useful if you are
doing plugin development and would like to automatically synchronize your
app with any changes made to your plugin.

Install the plugin: cordova plugin add
org.apache.cordova.labs.pluginAutoUpgrade

At root of your app, create a pluginAutoUpgrade.json file, which looks
like:

{
   "PLUGIN_ID": "PLUGIN_INSTALL_PATH",
   "PLUGIN_ID2": "PLUGIN_INSTALL_PATH"
}



This is useful if you are making changes to a plugin inside the plugin's
directory structure.

For more meaty plugin work, you are possibly better off making native
changes inside platforms/ and js changes inside plugins/, and being very
careful to not clobber your work (or use the build/run scripts directly to
skip prepare entirely).  I'm considering improving that workflow as well.

For now, I've found this plugin useful for minor plugin work.  Sharing in
case you do, too.

-Michal

Cordova plugin namespace

[John M. Wargo]

Looking at the plugin guide at 
http://cordova.apache.org/docs/en/4.0.0/plugin_ref_spec.md.html the first 
sentence on the page refers to a Cordova Plugin Namespace page that no longer 
exists: http://apache.org/cordova/ns/plugins/1.0.

Anyone know what happened to it?
--

*John M. Wargo*
www.johnwargo.com

Re: Plugin management ?

[John M. Wargo]

I published a node module a while back that does it. I originally published it 
as cordova-create, but changed it to cdva-create so I wouldn't disturb anything 
the Cordova team did in the future.

https://www.npmjs.com/package/cdva-create


On 1/22/2015 5:36 AM, Stéphane Wirtel wrote:

Hi all,

In my project, I use a lot of plugins.

So, is there a small tool or a config file where I can specify my dependencies 
(plugins) and just with a command line, install all my plugins ?

I think to grunt (Gruntfile.js), bower (bower.json) and npm (package.json)

Thank you,

Stephane
--
Stéphane Wirtel - http://wirtel.be - @matrixise

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

.

Re: Cordova plugin namespace

[John M. Wargo]

You're right (embarrassed giggle), I was thinking about another page.  Yep, 
that's a namespace URL.

On 1/28/2015 9:46 AM, Andrew Grieve wrote:

I don't think the URL ever existed. XML namespace URLs don't need to
actually exist IIRC. They are just identifiers.

On Tue, Jan 27, 2015 at 6:07 PM, John M. Wargo  wrote:


Looking at the plugin guide at http://cordova.apache.org/
docs/en/4.0.0/plugin_ref_spec.md.html the first sentence on the page
refers to a Cordova Plugin Namespace page that no longer exists:
http://apache.org/cordova/ns/plugins/1.0.

Anyone know what happened to it?
--

*John M. Wargo*
www.johnwargo.com

Re: Some thoughts/questions on the new --save feature

[John M. Wargo]

You used to be able to pass settings for the project's config.json file on the 
command line to create:

cordova create test com.johnwargo.test Test {\"autosave\":\"true\"}

That worked pre-4.0 but didn't seem to work in my moments ago test of this with 
the latest version. It would make the .cordova folder and populate the .json 
file with any parameters that were passed on the command line. At SAP we use 
this to help developers set the plugin search path so the CLI can find locally 
installed dependent plugins.

Was this (admittedly ugly) feature removed?

On 3/6/2015 9:30 PM, Mefire O. wrote:

- autosave IS a released feature. The 4.3.0 release includes it.
- I don't think the feature may go away, I think it just feels dirty to 
instruct users to directly edit the .cordova/config.json file. It doesn't seem 
to me like it contributes a good user experience.
- I like the idea of having a command to hide this from the user as suggested 
by Jesse : 'cordova config [--global] autosave true|false'.

If we decide to go the 'cordova config' route, I think it might make sense to 
wait on documenting it until it's in.
Otherwise, we should just go ahead and document it.

Thanks,
Mefire


-Original Message-
From: Raymond Camden [mailto:raymondcam...@gmail.com]
Sent: Friday, March 6, 2015 6:09 PM
To: dev@cordova.apache.org
Subject: Re: Some thoughts/questions on the new --save feature

Well to be clear, I thought at first this was a *released* feature, just not 
one documented well. (Or maybe documented and I missed it - I miss crap all the 
time.)

If I understand right, this is a feature, but one that may go away, so there 
may not be a need to document it.

Or maybe not - this thread has gone back and forth a bit. ;)

In my opinion, the ability to modify the CLI at the global or project level 
seems interesting. Maybe not terribly useful to most, but it seems like a good 
feature, so I'd be in favor of this being documented. (I don't actually see me 
adding this to my book - it feels too out there.)

But what I really want is to hear a firm decision. :)

On Fri, Mar 6, 2015 at 6:59 PM, Jesse  wrote:

We are not expecting users to modify this file, afaik.
Raymond is living on the cutting edge because he is writing a book, so
he wants details before they are available.

Personally, I would expect that we would mimic git with something like :
cordova config [--global] autosave true|false

But all of this is currently sausage ingredients ...




@purplecabbage
risingj.com

On Fri, Mar 6, 2015 at 4:43 PM, Nikhil Khandelwal

wrote:


If we are expecting users of the CLI to modify this config.json file,
not only should we document it but also make it easy for them to edit
it. The analogy of git's config management comes to mind - with both
support for local & global preferences. However, looks like
'autosave' is the only user preference that we might have for now.

Thanks,
Nikhil

-Original Message-
From: Mefire O. [mailto:ommen...@microsoft.com]
Sent: Thursday, March 5, 2015 12:37 PM
To: dev@cordova.apache.org
Subject: RE: Some thoughts/questions on the new --save feature

Yep, I think both options should be documented.

Thanks,
Mefire

-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
Andrew Grieve
Sent: Thursday, March 5, 2015 11:28 AM
To: dev
Subject: Re: Some thoughts/questions on the new --save feature

I don't have strong feelings about this.

When designing this, some wanted to have --save be default, some
wanted to match npm for the sake of matching npm. In the end both
ways were implemented.

I don't think we need to spend a lot of time on strategizing this. If
some one wants to doc it, go for it.

On Thu, Mar 5, 2015 at 12:34 PM, Victor Sosa 
wrote:


So, to me this file is a good way to automate the autosave feature
just as Gorkem is pointing (configure the JSON file, add plugins in
the usual way with cordova plugin add and share your project, no
flags needed to simply allow a good, or best,  SCM practice), but
it has been mentioned that the consensus is to not promote it, does
this mean at some point the support will be dropped? Is it considered 
experimental?

2015-03-05 11:17 GMT-06:00 Gorkem Ercan :



On 5 Mar 2015, at 12:01, Raymond Camden wrote:

  "just one way of doing things"

This confuses me though. It seemed as if this new config (I mean
new to me) was a way to configure the CLI. Is there another way
to configure the CLI? With the example that was given (default
to auto
save) being a preference for the tooling - can we accomplish
that another way?



That is the only way to enable auto save.
That preference is originally added for IDEs, build servers etc.
that use CLI.
However I think it does provide a more natural flow at least for me.
If

we

think we do not like config.json
then we should think about a more acceptable way to enable that
functionality.


  On Thu, Mar 5, 2015 at 10:50 AM, Andrew Grieve


wrote:


I don't think they a

Setting config.json values

[John M. Wargo]

Earlier this month, there was a conversation on this thread about enabling auto 
saving of plugin information to the project's config.json file 
(.cordova/config.json, right?) by setting auto_save_plugins to true in the file.

I responded on that thread suggesting that users would be able to set this 
value by passing the configuration value on the command line to the cordova 
create command like so:

cordova create test com.johnwargo.test Test {\"auto_save_plugins\":\"true\"}

Shouldn't this be a viable way to enable users to automagically set this value?

The problem is that this CLI feature no longer seems to work. Last fall, I was 
able to set the plugin search path using the following:

cordova create test2 com.johnwargo.test2 Test2 
"{\"plugin_search_path\":\"d:/dev\"}"

But I just tested it (for a second time on a different system) and that 
capability, passing config.json values on the command line to create, no longer 
seems to be working. Did I miss something? Was this feature removed?  Or should 
I submit a ticket on this issue?

Currently the SAP Mobile Platform Hybrid SDK ships as a local installer, the 
plugins aren't in the plugin registry or even github. The plugins have local 
dependencies (the AppUpdate plugin relies upon capabilities exposed by the 
Logon plugin) and the Cordova CLI isn't able to resolve them locally without 
the plugin_search_path being set. We've instructed users to use this feature, 
but now it seems it's not working. Can someone confirm?

Since plugin_search_path is valuable for SAP customers and auto_save_plugins is 
important for this new save/restore capability, is it time to design a simpler 
approach to allow developers to easily set these properties as needed for their 
projects?  It seems that having a create command parameter that points to a 
configuration file containing default settings for the project would be a 
useful thing to have.

What says the group?
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Setting config.json values

[John M. Wargo]

Any chance we can start a conversation about simplifying this too? Passing 
escaped JSON on the command line is, sorry, not a clean way to do this. As more 
config options are added, this becomes less manageable.

On 3/26/2015 2:42 PM, Shazron wrote:

Whoever ends up fixing this, please add a test for the functionality

On Thu, Mar 26, 2015 at 11:35 AM, Josh Soref  wrote:

It's possible i broke it:

https://github.com/apache/cordova-cli/commit/106d8801a70a9b97cd606e27f80c6c7988f368cc#diff-ef7004c4000a2616f36c594dc5db207a

try something from before this?

i'd suggest a bisect

specifically, find the last version where the command worked;
then try only upgrading lib, to the version+1 and see if it worked, if so, it's 
probably in cli.

i'd be really embarrassed if it's my fault.

i've been under the weather this week, so i'm catching up on mail/offering spot 
advice and giving up.


From: Shazron [shaz...@gmail.com]
Sent: Thursday, March 26, 2015 1:19 PM
To: dev@cordova.apache.org
Subject: Re: Setting config.json values

The help still says CONFIG is an option:
cordova create  [ID [NAME [CONFIG]]] [options] [PLATFORM...]

and config handling seems to still be there..
https://github.com/apache/cordova-lib/blob/cc596a37d77a92665292a5370d660a898217e0cb/cordova-lib/src/cordova/create.js#L41

.. so I think it's a bug. Two things here:
1. this bug
2. PLATFORM is not defined in the create help (I know it should be
obvious, but...)





On Thu, Mar 26, 2015 at 6:57 AM, John M. Wargo  wrote:

Earlier this month, there was a conversation on this thread about enabling
auto saving of plugin information to the project's config.json file
(.cordova/config.json, right?) by setting auto_save_plugins to true in the
file.

I responded on that thread suggesting that users would be able to set this
value by passing the configuration value on the command line to the cordova
create command like so:

 cordova create test com.johnwargo.test Test
{\"auto_save_plugins\":\"true\"}

Shouldn't this be a viable way to enable users to automagically set this
value?

The problem is that this CLI feature no longer seems to work. Last fall, I
was able to set the plugin search path using the following:

 cordova create test2 com.johnwargo.test2 Test2
"{\"plugin_search_path\":\"d:/dev\"}"

But I just tested it (for a second time on a different system) and that
capability, passing config.json values on the command line to create, no
longer seems to be working. Did I miss something? Was this feature removed?
Or should I submit a ticket on this issue?

Currently the SAP Mobile Platform Hybrid SDK ships as a local installer, the
plugins aren't in the plugin registry or even github. The plugins have local
dependencies (the AppUpdate plugin relies upon capabilities exposed by the
Logon plugin) and the Cordova CLI isn't able to resolve them locally without
the plugin_search_path being set. We've instructed users to use this
feature, but now it seems it's not working. Can someone confirm?

Since plugin_search_path is valuable for SAP customers and auto_save_plugins
is important for this new save/restore capability, is it time to design a
simpler approach to allow developers to easily set these properties as
needed for their projects?  It seems that having a create command parameter
that points to a configuration file containing default settings for the
project would be a useful thing to have.

What says the group?
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

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


-

Doc issues

[John M. Wargo]

I want to start tackling some of the open doc issues in JIRA, can someone set 
me up so I can assign tasks to myself?

JIRA user name is jwargo.

--

*John M. Wargo*
www.johnwargo.com

News Feed Broken

[John M. Wargo]

I noticed that the Cordova news feed at http://cordova.apache.org/rss.xml is 
broken.

I've filed a ticket. https://issues.apache.org/jira/browse/CB-8800


--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Apache Cordova 4 Programming book

[John M. Wargo]

Cordova Devs,

I wanted to let everyone know that Apache Cordova 4 Programming has been 
released and is available online: 
http://www.informit.com/store/apache-cordova-4-programming-9780134048192.

--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Stepping aside

[John M. Wargo]

All,

SAP eliminated my position back in March, so I'm no longer involved with SAP's 
Cordova-based products. I recently started a new job at Forrester Research; I 
accepted a position as a Principal Analyst in Forrester's Application 
Development and Delivery area. In this role, I'll be focusing on mobile and 
open-source development. Because of my new role, I'll likely not be able to 
participate in the Cordova project any longer.  I'll keep trolling the list and 
help out where I can, but I'm not sure at this time what I'll be able to do.

I will however see you guys at open source conferences and at PhoneGap day this 
year if possible.
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
--

Re: Stepping aside

[John M. Wargo]

Well, the latest two books are out there, together providing 800 solid pages of 
Cordova coverage. Right now it's pretty hard to publish books on Cordova as  
you guys are making big changes too quickly :-).  Just published a book on 
Cordova 4 and within a week of it coming out you guys release cordova 5. Too 
hard to keep up.

Kidding aside, the books are selling quite well, so when the publisher's ready 
to do an update, perhaps I'll be able to do it.

On 5/16/2015 9:26 AM, Brian LeRoux wrote:

what does this mean for the future of your book John? (def the best
resource out there for our community and we really appreciate the years of
work you've dedicated to the project.)

also: would love to see you at PGD!

On Sat, May 16, 2015 at 3:33 AM, John M. Wargo  wrote:


All,

SAP eliminated my position back in March, so I'm no longer involved with
SAP's Cordova-based products. I recently started a new job at Forrester
Research; I accepted a position as a Principal Analyst in Forrester's
Application Development and Delivery area. In this role, I'll be focusing
on mobile and open-source development. Because of my new role, I'll likely
not be able to participate in the Cordova project any longer.  I'll keep
trolling the list and help out where I can, but I'm not sure at this time
what I'll be able to do.

I will however see you guys at open source conferences and at PhoneGap day
this year if possible.
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>

--





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

I'm baaaaaack!

[John M. Wargo]

Greetings Cordova Dev Team!

Its been a while, so I thought I'd pop on the list and re-introduce myself.

Hello, my name is John M. Wargo and I've been a Cordova developer since 
PhoneGap version 2 (more or less). I was a contributor for many years and wrote 
4 books on Apache Cordova/PhoneGap, but dropped off the map about two years due 
to a job change. I recently joined Microsoft as a Program Manager working on 
our Mobile Center product (working for Ryan J. Salva, and working with 
Parashuram N - whom I think you all know). In my new position, I'm not sure how 
much I'll be working directly with the project team, but I will do what I can.

I will be attending PhoneGap day in NY next month (I'll actually be Microsoft's 
onsite host for the event), and joining in on the dev conversation whenever I 
can.  Any get togethers planned for NY before/during/after the conference?  
Please let me know if you need anything in or around the event.

John M. Wargo
Web: www.johnwargo.com <http://www.johnwargo.com>
Twitter: @johnwargo <https://twitter.com/johnwargo>