Re: Plugin and CordovaPlugin
Sounds good, as long as we set it to deprecate after 3.0. I can get it done tomorrow. On Mon, Jun 10, 2013 at 10:45 PM, Filip Maj f...@adobe.com wrote: Might not be a bad idea, I'm sure users would appreciate it. Is it acceptable for us to do an android-only 2.8.1 ? On 6/10/13 10:41 PM, Steven Gill stevengil...@gmail.com wrote: 2.8.1? On Mon, Jun 10, 2013 at 9:13 PM, Joe Bowser bows...@gmail.com wrote: This just affects Android. On Mon, Jun 10, 2013 at 8:56 PM, Jesse MacFadyen purplecabb...@gmail.com wrote: Can someone post a link to a commit, or a ticket for this? I am having trouble understanding the scope, as is. Does this just affect Android? Cheers, Jesse Sent from my iPhone5 On Jun 10, 2013, at 8:26 PM, Joe Bowser bows...@gmail.com wrote: OK, if we bring it back, how long should we bring it back for? We can't keep it around forever. The only reason that I want to bring it back is because I feel that it was unfair to the users to have this deprecated without it even being listed on the Deprecation article on our wiki, let alone announced. Unlike something like WebSQL vs WebStorage, where we're forced to make a crap choice, this is something that we have full control over. On Mon, Jun 10, 2013 at 8:09 PM, Tommy-Carlos Williams to...@devgeeks.org wrote: The plugin ecosystem is in a bit of an uproar about it :( If it's not a massive pain, it could really help. On 11/06/2013, at 12:57 PM, Simon MacDonald simon.macdon...@gmail.com wrote: I think the right thing to do is to put it back in for now. I'm answering tons of questions on this and people are begging me to update plugins I didn't even write. So the empirical evidence is the users are not ready for this change. Simon Mac Donald http://hi.im/simonmacdonald On Mon, Jun 10, 2013 at 7:19 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that we have recently deprecated Plugin in favour for CordovaPlugin, but it seems that we really screwed up the deprecation and now one of the flagship apps that use PhoneGap no longer has a valid upgrade path. I think that this is a major problem that is biting us in the ass, so I would like to see us put the Plugin shim back into Cordova. I know this is a bad thing to add, but we basically gave our users the giant middle finger by deprecating this without notifying them at all. I'm not sure what we should do in this case. Joe
CRC32 checksum failed with Cordova 2.2.0
Hi, due to the fact that Cordova 2.2.0 is the last iOS 4 supporting release, I need to get Cordova 2.2.0 worked for my iOS project. I've installed Cordova via npm without any problems. When I try to add iOS as a platform via cordova platform add ios, I get a checksum-failed error: Downloading ios library, this may take a while...CRC32 checksum failed apache-cordova-ios-e5b4aaf Can somebody help me with that? Greets, Andreas
Hi group
Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr
RE: CRC32 checksum failed with Cordova 2.2.0
As I found out the npm installation doesn't include the necessary lib folder. Where can I find it? Is there still existing download link for Cordova 2.2.0? On http://archive.apache.org/dist/cordova/ the list stops on Cordova 2.3.0, the first version of cordova without any iOS 4 support. Hmpf... Can somebody help me with that? From: andreas.san...@hotmail.de To: dev@cordova.apache.org Subject: CRC32 checksum failed with Cordova 2.2.0 Date: Tue, 11 Jun 2013 09:39:38 +0200 Hi, due to the fact that Cordova 2.2.0 is the last iOS 4 supporting release, I need to get Cordova 2.2.0 worked for my iOS project. I've installed Cordova via npm without any problems. When I try to add iOS as a platform via cordova platform add ios, I get a checksum-failed error: Downloading ios library, this may take a while...CRC32 checksum failed apache-cordova-ios-e5b4aaf Can somebody help me with that? Greets, Andreas
an update on Tizen port
Hi folks, I entered issues for Tizen updates in JIRA: CB-3396 Update Tizen For Tizen SDK 2.0 (done 05/17/2013) CB-3739 Tizen SDK 2.1 port Extending APIs (done 06/07/2013) CB-3739 Tizen SDK 2.1 port Extending APIs CB-3740 Tizen SDK 2.1 fulfilling APIs CB 3396 and CB3739 were about adapting the existing port to respectively Tizen SDK 2.0 and 2.1 I am currently working on CB-3739 adding missing API (SplashScreen, Globalization, inAppBrowser is working) @Paul ~~~ Paul Plaquette, Senior Software Engineer Intel Corporation SAS SSG/OTC: Open Source Technology Center France, Montpellier
Fixing Issue
Hi everyone, I have done some research on two way SSL (mutual SSL) in blackberry native java. (BB OS 7 and earlier) I saw this issue on JIRA https://issues.apache.org/jira/browse/CB-3351 I would like to try this out. In native it's not much. Just HTTPSConection.open(url); Before that client and CA certificate must be installed in the device via Desktop studio or through email. As I'm noob to this cordova/apache contribution, could anyone please tell me what to do next? How I can solve this issue? Cheers! -- Regards!* - **Lolitha Ratnayake, *
Re: Hi group
Hi Piotr, I have a Firefox OS device so feel free to ping me if you need some test or whatever you may need. :) Giorgio On Tue, Jun 11, 2013 at 9:44 AM, Piotr Zalewa pzal...@mozilla.com wrote: Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr
Re: Plugin and CordovaPlugin
This is sort of a tough one i think, how long has this deprecation notice been in the code? if we change android to work, and then remove it again, will we still have the same issue with the users. i'm just trying to play devil's advocate here. As a user, it would be nice to have this come back for a release, but as a developer, i can see the other hand On Jun 11, 2013, at 2:26 AM, Joe Bowser bows...@gmail.com wrote: Sounds good, as long as we set it to deprecate after 3.0. I can get it done tomorrow. On Mon, Jun 10, 2013 at 10:45 PM, Filip Maj f...@adobe.com wrote: Might not be a bad idea, I'm sure users would appreciate it. Is it acceptable for us to do an android-only 2.8.1 ? On 6/10/13 10:41 PM, Steven Gill stevengil...@gmail.com wrote: 2.8.1? On Mon, Jun 10, 2013 at 9:13 PM, Joe Bowser bows...@gmail.com wrote: This just affects Android. On Mon, Jun 10, 2013 at 8:56 PM, Jesse MacFadyen purplecabb...@gmail.com wrote: Can someone post a link to a commit, or a ticket for this? I am having trouble understanding the scope, as is. Does this just affect Android? Cheers, Jesse Sent from my iPhone5 On Jun 10, 2013, at 8:26 PM, Joe Bowser bows...@gmail.com wrote: OK, if we bring it back, how long should we bring it back for? We can't keep it around forever. The only reason that I want to bring it back is because I feel that it was unfair to the users to have this deprecated without it even being listed on the Deprecation article on our wiki, let alone announced. Unlike something like WebSQL vs WebStorage, where we're forced to make a crap choice, this is something that we have full control over. On Mon, Jun 10, 2013 at 8:09 PM, Tommy-Carlos Williams to...@devgeeks.org wrote: The plugin ecosystem is in a bit of an uproar about it :( If it's not a massive pain, it could really help. On 11/06/2013, at 12:57 PM, Simon MacDonald simon.macdon...@gmail.com wrote: I think the right thing to do is to put it back in for now. I'm answering tons of questions on this and people are begging me to update plugins I didn't even write. So the empirical evidence is the users are not ready for this change. Simon Mac Donald http://hi.im/simonmacdonald On Mon, Jun 10, 2013 at 7:19 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that we have recently deprecated Plugin in favour for CordovaPlugin, but it seems that we really screwed up the deprecation and now one of the flagship apps that use PhoneGap no longer has a valid upgrade path. I think that this is a major problem that is biting us in the ass, so I would like to see us put the Plugin shim back into Cordova. I know this is a bad thing to add, but we basically gave our users the giant middle finger by deprecating this without notifying them at all. I'm not sure what we should do in this case. Joe
RE: Hi group
Welcome Piotr! -- Ken Wallis Product Manager – WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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: Fixing Issue
Hi Lolitha, I am not sure exactly what issue you are having? Thanks. -- Ken Wallis Product Manager – WebWorks BlackBerry 289-261-4369 From: Lolitha Ratnayake [lolith...@gmail.com] Sent: Tuesday, June 11, 2013 2:16 AM To: dev@cordova.apache.org Subject: Fixing Issue Hi everyone, I have done some research on two way SSL (mutual SSL) in blackberry native java. (BB OS 7 and earlier) I saw this issue on JIRA https://issues.apache.org/jira/browse/CB-3351 I would like to try this out. In native it's not much. Just HTTPSConection.open(url); Before that client and CA certificate must be installed in the device via Desktop studio or through email. As I'm noob to this cordova/apache contribution, could anyone please tell me what to do next? How I can solve this issue? Cheers! -- Regards!* - **Lolitha Ratnayake, * - 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: Fixing Issue
Hi Ken, It's not me having issue. But someone has put it as a issue on JIRA. https://issues.apache.org/jira/browse/CB-3351 on here. I have done native java two way SSL so I was wondering weather I can help to solve this issue. On Tue, Jun 11, 2013 at 6:14 PM, Ken Wallis kwal...@blackberry.com wrote: Hi Lolitha, I am not sure exactly what issue you are having? Thanks. -- Ken Wallis Product Manager – WebWorks BlackBerry 289-261-4369 From: Lolitha Ratnayake [lolith...@gmail.com] Sent: Tuesday, June 11, 2013 2:16 AM To: dev@cordova.apache.org Subject: Fixing Issue Hi everyone, I have done some research on two way SSL (mutual SSL) in blackberry native java. (BB OS 7 and earlier) I saw this issue on JIRA https://issues.apache.org/jira/browse/CB-3351 I would like to try this out. In native it's not much. Just HTTPSConection.open(url); Before that client and CA certificate must be installed in the device via Desktop studio or through email. As I'm noob to this cordova/apache contribution, could anyone please tell me what to do next? How I can solve this issue? Cheers! -- Regards!* - **Lolitha Ratnayake, * - 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. -- Regards!* - **Lolitha Ratnayake, *
Re: Hi group
Great to have you aboard Piotr. Welcome! -James Jong On Jun 11, 2013, at 5:40 AM, Ken Wallis kwal...@blackberry.com wrote: Welcome Piotr! -- Ken Wallis Product Manager – WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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: Plugin and CordovaPlugin
I'm indifferent about adding this back. What I do want to comment on is that this seems like a good precursor of the furor that 3.0 is likely to create. Lots of things are going to change, and all of these old plugins are going to be in a questionable state. In principle there's no reason why you can't manually install them in a 3.0-era project, I suppose. But it's going to be very confusing, and I suspect people are going to be trying to use the CLI tools to install old plugins, and manually installing new plugins. Or just not updating, because it would require more than a small bit of work to migrate their apps. How firm are we going to be when our users cry out for a 2.10, for long-term support for 2.x? It might be to our advantage to promise a couple of bugfix releases on 2.x up front when announcing 3.0. That sets the expectations: you have plenty of warning, and time to make the change, but it's not going to last forever; the decision for when to drop support is already made. We don't want to find ourselves juggling both branches six months from now, let alone a year from now. Braden On Tue, Jun 11, 2013 at 8:18 AM, Lucas Holmquist lholm...@redhat.comwrote: This is sort of a tough one i think, how long has this deprecation notice been in the code? if we change android to work, and then remove it again, will we still have the same issue with the users. i'm just trying to play devil's advocate here. As a user, it would be nice to have this come back for a release, but as a developer, i can see the other hand On Jun 11, 2013, at 2:26 AM, Joe Bowser bows...@gmail.com wrote: Sounds good, as long as we set it to deprecate after 3.0. I can get it done tomorrow. On Mon, Jun 10, 2013 at 10:45 PM, Filip Maj f...@adobe.com wrote: Might not be a bad idea, I'm sure users would appreciate it. Is it acceptable for us to do an android-only 2.8.1 ? On 6/10/13 10:41 PM, Steven Gill stevengil...@gmail.com wrote: 2.8.1? On Mon, Jun 10, 2013 at 9:13 PM, Joe Bowser bows...@gmail.com wrote: This just affects Android. On Mon, Jun 10, 2013 at 8:56 PM, Jesse MacFadyen purplecabb...@gmail.com wrote: Can someone post a link to a commit, or a ticket for this? I am having trouble understanding the scope, as is. Does this just affect Android? Cheers, Jesse Sent from my iPhone5 On Jun 10, 2013, at 8:26 PM, Joe Bowser bows...@gmail.com wrote: OK, if we bring it back, how long should we bring it back for? We can't keep it around forever. The only reason that I want to bring it back is because I feel that it was unfair to the users to have this deprecated without it even being listed on the Deprecation article on our wiki, let alone announced. Unlike something like WebSQL vs WebStorage, where we're forced to make a crap choice, this is something that we have full control over. On Mon, Jun 10, 2013 at 8:09 PM, Tommy-Carlos Williams to...@devgeeks.org wrote: The plugin ecosystem is in a bit of an uproar about it :( If it's not a massive pain, it could really help. On 11/06/2013, at 12:57 PM, Simon MacDonald simon.macdon...@gmail.com wrote: I think the right thing to do is to put it back in for now. I'm answering tons of questions on this and people are begging me to update plugins I didn't even write. So the empirical evidence is the users are not ready for this change. Simon Mac Donald http://hi.im/simonmacdonald On Mon, Jun 10, 2013 at 7:19 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that we have recently deprecated Plugin in favour for CordovaPlugin, but it seems that we really screwed up the deprecation and now one of the flagship apps that use PhoneGap no longer has a valid upgrade path. I think that this is a major problem that is biting us in the ass, so I would like to see us put the Plugin shim back into Cordova. I know this is a bad thing to add, but we basically gave our users the giant middle finger by deprecating this without notifying them at all. I'm not sure what we should do in this case. Joe
Re: Plugin and CordovaPlugin
On Tue, Jun 11, 2013 at 5:18 AM, Lucas Holmquist lholm...@redhat.com wrote: This is sort of a tough one i think, how long has this deprecation notice been in the code? Does it matter if the deprecation is in code? Our users don't read code, which is painfully obvious. The fact is that this was deprecated in code for six months, but we didn't announce the change, and very few people have updated their plugins. if we change android to work, and then remove it again, will we still have the same issue with the users. I hope not, but if we do I don't care at that point. We gave them notice. If they get upset about this change at that point, it's their own fault. i'm just trying to play devil's advocate here. As a user, it would be nice to have this come back for a release, but as a developer, i can see the other hand Fair enough. I'm not known as the champion of the users, actually quite to the contrary. I'm the developer that all our Android users despise because I close bugs that I feel are out of scope, or that we just can't fix. Therefore, when I say that we should probably fix things, it's probably an actual real issue and doesn't come from any warm fuzzy feeling I have for these people.
Re: Plugin and CordovaPlugin
On Tue, Jun 11, 2013 at 6:56 AM, Braden Shepherdson bra...@chromium.org wrote: I'm indifferent about adding this back. What I do want to comment on is that this seems like a good precursor of the furor that 3.0 is likely to create. Lots of things are going to change, and all of these old plugins are going to be in a questionable state. In principle there's no reason why you can't manually install them in a 3.0-era project, I suppose. The old plugins are already in a questionable state. We don't maintain these plugins. The problem that we have now is that there are projects that depend on these plugins, and people haven't been updating the plugins. I know for a fact that not even PhoneGap Build has updated their Facebook Connect plugin. Also, I do have concerns about the publicity that 3.0 isn't getting so far. We need to actually announce to our users that we're making a massive change to Cordova. But it's going to be very confusing, and I suspect people are going to be trying to use the CLI tools to install old plugins, and manually installing new plugins. Or just not updating, because it would require more than a small bit of work to migrate their apps. How firm are we going to be when our users cry out for a 2.10, for long-term support for 2.x? It might be to our advantage to promise a couple of bugfix releases on 2.x up front when announcing 3.0. That sets the expectations: you have plenty of warning, and time to make the change, but it's not going to last forever; the decision for when to drop support is already made. I think we should do a three release deprecation of 2.x, as in by the time that 3.2 rolls out, we stop supporting 2.x altogether. People will continue to use 2.x, but we won't support it. We don't want to find ourselves juggling both branches six months from now, let alone a year from now. Fair enough! Based on what happened last year, I think 3.2.0 will come out in the fall, therefore we're not going to be stuck with the old version for very long. What do other people think? Should we just not maintain 2.x at all? Who can we blame for this, because I'm getting tired of being the Batman of this project.
Re: Plugin and CordovaPlugin
I think three releases sounds fine. My main point here is that we should make that decision now, and announce the deprecation plan alongside 3.0, so users know the situation. Announcing both soon also sounds like a good idea, but we want to make sure any announcement of 3.0 is accompanied by our deprecation plan for 2.x. Braden On Tue, Jun 11, 2013 at 10:12 AM, Joe Bowser bows...@gmail.com wrote: On Tue, Jun 11, 2013 at 6:56 AM, Braden Shepherdson bra...@chromium.org wrote: I'm indifferent about adding this back. What I do want to comment on is that this seems like a good precursor of the furor that 3.0 is likely to create. Lots of things are going to change, and all of these old plugins are going to be in a questionable state. In principle there's no reason why you can't manually install them in a 3.0-era project, I suppose. The old plugins are already in a questionable state. We don't maintain these plugins. The problem that we have now is that there are projects that depend on these plugins, and people haven't been updating the plugins. I know for a fact that not even PhoneGap Build has updated their Facebook Connect plugin. Also, I do have concerns about the publicity that 3.0 isn't getting so far. We need to actually announce to our users that we're making a massive change to Cordova. But it's going to be very confusing, and I suspect people are going to be trying to use the CLI tools to install old plugins, and manually installing new plugins. Or just not updating, because it would require more than a small bit of work to migrate their apps. How firm are we going to be when our users cry out for a 2.10, for long-term support for 2.x? It might be to our advantage to promise a couple of bugfix releases on 2.x up front when announcing 3.0. That sets the expectations: you have plenty of warning, and time to make the change, but it's not going to last forever; the decision for when to drop support is already made. I think we should do a three release deprecation of 2.x, as in by the time that 3.2 rolls out, we stop supporting 2.x altogether. People will continue to use 2.x, but we won't support it. We don't want to find ourselves juggling both branches six months from now, let alone a year from now. Fair enough! Based on what happened last year, I think 3.2.0 will come out in the fall, therefore we're not going to be stuck with the old version for very long. What do other people think? Should we just not maintain 2.x at all? Who can we blame for this, because I'm getting tired of being the Batman of this project.
issues.apache.org is down
The subject says it all. --Mike S
Re: issues.apache.org is down
yeah, getting that too. you can ping issues.apache.org, it looks like just the jira tracker is down. Waiting patiently On Tue, Jun 11, 2013 at 8:00 AM, Michael Sierra msie...@adobe.com wrote: The subject says it all. --Mike S
Re: issues.apache.org is down
Looks like: https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=summary Is down for me too. Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jun 11, 2013 at 11:02 AM, Lorin Beer lorin.beer@gmail.com wrote: yeah, getting that too. you can ping issues.apache.org, it looks like just the jira tracker is down. Waiting patiently On Tue, Jun 11, 2013 at 8:00 AM, Michael Sierra msie...@adobe.com wrote: The subject says it all. --Mike S
Re: issues.apache.org is down
http://monitoring.apache.org/status/ Git-wip is down but JIRA is up for me. On 6/11/13 8:05 AM, Simon MacDonald simon.macdon...@gmail.com wrote: Looks like: https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=summary Is down for me too. Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jun 11, 2013 at 11:02 AM, Lorin Beer lorin.beer@gmail.com wrote: yeah, getting that too. you can ping issues.apache.org, it looks like just the jira tracker is down. Waiting patiently On Tue, Jun 11, 2013 at 8:00 AM, Michael Sierra msie...@adobe.com wrote: The subject says it all. --Mike S
Re: issues.apache.org is down
jira is back up, as of a few minutes ago. git-wip still down On Tue, Jun 11, 2013 at 8:10 AM, Filip Maj f...@adobe.com wrote: http://monitoring.apache.org/status/ Git-wip is down but JIRA is up for me. On 6/11/13 8:05 AM, Simon MacDonald simon.macdon...@gmail.com wrote: Looks like: https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=summary Is down for me too. Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jun 11, 2013 at 11:02 AM, Lorin Beer lorin.beer@gmail.com wrote: yeah, getting that too. you can ping issues.apache.org, it looks like just the jira tracker is down. Waiting patiently On Tue, Jun 11, 2013 at 8:00 AM, Michael Sierra msie...@adobe.com wrote: The subject says it all. --Mike S
Re: Hi group
Welcome man! I would totally link you to all the repos and which ones are important and how to get started, but the apache git servers we rely on are currently down :( On 6/11/13 6:47 AM, James Jong wjamesj...@gmail.com wrote: Great to have you aboard Piotr. Welcome! -James Jong On Jun 11, 2013, at 5:40 AM, Ken Wallis kwal...@blackberry.com wrote: Welcome Piotr! -- Ken Wallis Product Manager WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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: CRC32 checksum failed with Cordova 2.2.0
Hey Andreas, You can download the 2.2.0 tag for cordova-ios here: https://github.com/apache/cordova-ios/tags On 6/11/13 1:15 AM, Andreas Sander andreas.san...@hotmail.de wrote: As I found out the npm installation doesn't include the necessary lib folder. Where can I find it? Is there still existing download link for Cordova 2.2.0? On http://archive.apache.org/dist/cordova/ the list stops on Cordova 2.3.0, the first version of cordova without any iOS 4 support. Hmpf... Can somebody help me with that? From: andreas.san...@hotmail.de To: dev@cordova.apache.org Subject: CRC32 checksum failed with Cordova 2.2.0 Date: Tue, 11 Jun 2013 09:39:38 +0200 Hi, due to the fact that Cordova 2.2.0 is the last iOS 4 supporting release, I need to get Cordova 2.2.0 worked for my iOS project. I've installed Cordova via npm without any problems. When I try to add iOS as a platform via cordova platform add ios, I get a checksum-failed error: Downloading ios library, this may take a while...CRC32 checksum failed apache-cordova-ios-e5b4aaf Can somebody help me with that? Greets, Andreas
Re: git commit: [CB-3755] Update platform version from config.xml
Hey Tommy can you file issues for BB10 + WP7/8 support for this feature?
So we keep track of what needs to be covered for other platforms.
Cheers,
Fil
On 6/11/13 1:42 AM, devge...@apache.org devge...@apache.org wrote:
Updated Branches:
refs/heads/master2 5011b0caf - 04648ad00
[CB-3755] Update platform version from config.xml
- Updates AndroidManifest.xml android:versionName with version from
config.xml
- Updates AppName-Info.plist CFBundleVersion with version from config.xml
NOTE: So far this is only handling Android and iOS. WP7/8 and Blackberry
need to be updated as well
Project: http://git-wip-us.apache.org/repos/asf/cordova-cli/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-cli/commit/04648ad0
Tree: http://git-wip-us.apache.org/repos/asf/cordova-cli/tree/04648ad0
Diff: http://git-wip-us.apache.org/repos/asf/cordova-cli/diff/04648ad0
Branch: refs/heads/master2
Commit: 04648ad00a2e2601f4052ca9da90377f54f9dbcd
Parents: 5011b0c
Author: Tommy-Carlos Williams to...@devgeeks.org
Authored: Tue Jun 11 18:33:24 2013 +1000
Committer: Tommy-Carlos Williams to...@devgeeks.org
Committed: Tue Jun 11 18:33:24 2013 +1000
--
spec/cordova-cli/config_parser.spec.js | 20
.../android/android_parser.spec.js | 7 +++
spec/platform-script/ios/ios_parser.spec.js | 8
src/config_parser.js| 6 ++
src/metadata/android_parser.js | 6 ++
src/metadata/ios_parser.js | 4
6 files changed, 51 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cordova-cli/blob/04648ad0/spec/cord
ova-cli/config_parser.spec.js
--
diff --git a/spec/cordova-cli/config_parser.spec.js
b/spec/cordova-cli/config_parser.spec.js
index 77658fb..303b3d6 100644
--- a/spec/cordova-cli/config_parser.spec.js
+++ b/spec/cordova-cli/config_parser.spec.js
@@ -63,6 +63,26 @@ describe('config.xml parser', function () {
});
});
+describe('version', function() {
+var cfg;
+
+beforeEach(function() {
+cfg = new config_parser(xml);
+});
+
+it('should get the version', function() {
+expect(cfg.version()).toEqual('2.0.0');
+});
+it('should allow setting the version', function() {
+cfg.version('2.0.1');
+expect(cfg.version()).toEqual('2.0.1');
+});
+it('should write to disk after setting the version', function() {
+cfg.version('2.0.1');
+expect(fs.readFileSync(xml,
'utf-8')).toMatch(/version=2.0.1/);
+});
+});
+
describe('app name', function() {
var cfg;
http://git-wip-us.apache.org/repos/asf/cordova-cli/blob/04648ad0/spec/plat
form-script/android/android_parser.spec.js
--
diff --git a/spec/platform-script/android/android_parser.spec.js
b/spec/platform-script/android/android_parser.spec.js
index c0f77c1..4759a2c 100644
--- a/spec/platform-script/android/android_parser.spec.js
+++ b/spec/platform-script/android/android_parser.spec.js
@@ -98,6 +98,13 @@ describe('android project parser', function() {
expect(fs.existsSync(javs)).toBe(true);
expect(fs.readFileSync(javs, 'utf-8')).toMatch(/package
ca.filmaj.dewd/i);
});
+it('should update the application version properly', function() {
+config.version('2.0.1');
+project.update_from_config(config);
+
+var manifest = new
et.ElementTree(et.XML(fs.readFileSync(android_manifest, 'utf-8')));
+
expect(manifest.getroot().attrib[android:versionName]).toEqual('2.0.1');
+});
it('should handle unsupported - in the application package
name', function() {
var javs = path.join(android_path, 'src', 'ca', 'filmaj',
'the_dewd', 'cordovaExample.java');
var orig_javs = path.join(android_path, 'src', 'org',
'apache', 'cordova', 'cordovaExample', 'cordovaExample.java');
http://git-wip-us.apache.org/repos/asf/cordova-cli/blob/04648ad0/spec/plat
form-script/ios/ios_parser.spec.js
--
diff --git a/spec/platform-script/ios/ios_parser.spec.js
b/spec/platform-script/ios/ios_parser.spec.js
index 8598c3f..25f7833 100644
--- a/spec/platform-script/ios/ios_parser.spec.js
+++ b/spec/platform-script/ios/ios_parser.spec.js
@@ -90,6 +90,14 @@ describe('ios project parser', function () {
done();
});
});
+it('should update the application version (CFBundleVersion)
properly', function (done) {
+config.version('2.0.1');
+project.update_from_config(config, function () {
+
RE: CRC32 checksum failed with Cordova 2.2.0
Okay. Now I can create/update projects via scripts in the bin directory of cordova-ios. Is there a way to combine it with cordova cli tools? So that I can remove and add iOS platform again? From: f...@adobe.com To: dev@cordova.apache.org Date: Tue, 11 Jun 2013 08:18:59 -0700 Subject: Re: CRC32 checksum failed with Cordova 2.2.0 Hey Andreas, You can download the 2.2.0 tag for cordova-ios here: https://github.com/apache/cordova-ios/tags On 6/11/13 1:15 AM, Andreas Sander andreas.san...@hotmail.de wrote: As I found out the npm installation doesn't include the necessary lib folder. Where can I find it? Is there still existing download link for Cordova 2.2.0? On http://archive.apache.org/dist/cordova/ the list stops on Cordova 2.3.0, the first version of cordova without any iOS 4 support. Hmpf... Can somebody help me with that? From: andreas.san...@hotmail.de To: dev@cordova.apache.org Subject: CRC32 checksum failed with Cordova 2.2.0 Date: Tue, 11 Jun 2013 09:39:38 +0200 Hi, due to the fact that Cordova 2.2.0 is the last iOS 4 supporting release, I need to get Cordova 2.2.0 worked for my iOS project. I've installed Cordova via npm without any problems. When I try to add iOS as a platform via cordova platform add ios, I get a checksum-failed error: Downloading ios library, this may take a while...CRC32 checksum failed apache-cordova-ios-e5b4aaf Can somebody help me with that? Greets, Andreas
Re: CRC32 checksum failed with Cordova 2.2.0
There is a way but I'm not sure how much I should support you in this endeavor.. You are futzing with the code at this point so, consider this your warning! If you replace the contents of cordova-cli/lib/cordova-ios with the contents of your cordova-ios package, it *should* work. Depends on which version of cordova-cli you are running as the cli code has expectations about which bits inside the cordova-ios lib exist. If you installed it via npm install -g then it should exist somewhere like /usr/local/lib/node_modules/cordova On 6/11/13 8:36 AM, Andreas Sander andreas.san...@hotmail.de wrote: Okay. Now I can create/update projects via scripts in the bin directory of cordova-ios. Is there a way to combine it with cordova cli tools? So that I can remove and add iOS platform again? From: f...@adobe.com To: dev@cordova.apache.org Date: Tue, 11 Jun 2013 08:18:59 -0700 Subject: Re: CRC32 checksum failed with Cordova 2.2.0 Hey Andreas, You can download the 2.2.0 tag for cordova-ios here: https://github.com/apache/cordova-ios/tags On 6/11/13 1:15 AM, Andreas Sander andreas.san...@hotmail.de wrote: As I found out the npm installation doesn't include the necessary lib folder. Where can I find it? Is there still existing download link for Cordova 2.2.0? On http://archive.apache.org/dist/cordova/ the list stops on Cordova 2.3.0, the first version of cordova without any iOS 4 support. Hmpf... Can somebody help me with that? From: andreas.san...@hotmail.de To: dev@cordova.apache.org Subject: CRC32 checksum failed with Cordova 2.2.0 Date: Tue, 11 Jun 2013 09:39:38 +0200 Hi, due to the fact that Cordova 2.2.0 is the last iOS 4 supporting release, I need to get Cordova 2.2.0 worked for my iOS project. I've installed Cordova via npm without any problems. When I try to add iOS as a platform via cordova platform add ios, I get a checksum-failed error: Downloading ios library, this may take a while...CRC32 checksum failed apache-cordova-ios-e5b4aaf Can somebody help me with that? Greets, Andreas
Re: Plugin and CordovaPlugin
OK, We actually did deprecate this properly. I don't know how I missed this edit Simon did on the Wiki: https://wiki.apache.org/cordova/DeprecationPolicy I think we should put it back for 2.x and remove it from 3.x. We also shouldn't support any bugs that appear with old plugins adding this. On Tue, Jun 11, 2013 at 7:15 AM, Braden Shepherdson bra...@chromium.org wrote: I think three releases sounds fine. My main point here is that we should make that decision now, and announce the deprecation plan alongside 3.0, so users know the situation. Announcing both soon also sounds like a good idea, but we want to make sure any announcement of 3.0 is accompanied by our deprecation plan for 2.x. Braden On Tue, Jun 11, 2013 at 10:12 AM, Joe Bowser bows...@gmail.com wrote: On Tue, Jun 11, 2013 at 6:56 AM, Braden Shepherdson bra...@chromium.org wrote: I'm indifferent about adding this back. What I do want to comment on is that this seems like a good precursor of the furor that 3.0 is likely to create. Lots of things are going to change, and all of these old plugins are going to be in a questionable state. In principle there's no reason why you can't manually install them in a 3.0-era project, I suppose. The old plugins are already in a questionable state. We don't maintain these plugins. The problem that we have now is that there are projects that depend on these plugins, and people haven't been updating the plugins. I know for a fact that not even PhoneGap Build has updated their Facebook Connect plugin. Also, I do have concerns about the publicity that 3.0 isn't getting so far. We need to actually announce to our users that we're making a massive change to Cordova. But it's going to be very confusing, and I suspect people are going to be trying to use the CLI tools to install old plugins, and manually installing new plugins. Or just not updating, because it would require more than a small bit of work to migrate their apps. How firm are we going to be when our users cry out for a 2.10, for long-term support for 2.x? It might be to our advantage to promise a couple of bugfix releases on 2.x up front when announcing 3.0. That sets the expectations: you have plenty of warning, and time to make the change, but it's not going to last forever; the decision for when to drop support is already made. I think we should do a three release deprecation of 2.x, as in by the time that 3.2 rolls out, we stop supporting 2.x altogether. People will continue to use 2.x, but we won't support it. We don't want to find ourselves juggling both branches six months from now, let alone a year from now. Fair enough! Based on what happened last year, I think 3.2.0 will come out in the fall, therefore we're not going to be stuck with the old version for very long. What do other people think? Should we just not maintain 2.x at all? Who can we blame for this, because I'm getting tired of being the Batman of this project.
Re: CRC32 checksum failed with Cordova 2.2.0
Andreas, I'm curious if you could describe a bit why your project needs to run on iOS 4? According to a couple stats I found [1, 2], usage of iOS 4 appears to be around 1.4% of all iOS versions. Does that fall under the don't care or not worth it threshold for you? 1: http://stats.unity3d.com/mobile/os-ios.html 2: http://david-smith.org/iosversionstats/ Thanks! -- Marcel Kinard On Jun 11, 2013, at 3:39 AM, Andreas Sander andreas.san...@hotmail.de wrote: Hi, due to the fact that Cordova 2.2.0 is the last iOS 4 supporting release, I need to get Cordova 2.2.0 worked for my iOS project. I've installed Cordova via npm without any problems. When I try to add iOS as a platform via cordova platform add ios, I get a checksum-failed error: Downloading ios library, this may take a while...CRC32 checksum failed apache-cordova-ios-e5b4aaf Can somebody help me with that? Greets, Andreas
Re: Plugin and CordovaPlugin
Whatever we decide can we be extra loud about it? Blog posts, tweets, google groups. On Tuesday, June 11, 2013, Joe Bowser wrote: OK, We actually did deprecate this properly. I don't know how I missed this edit Simon did on the Wiki: https://wiki.apache.org/cordova/DeprecationPolicy I think we should put it back for 2.x and remove it from 3.x. We also shouldn't support any bugs that appear with old plugins adding this. On Tue, Jun 11, 2013 at 7:15 AM, Braden Shepherdson bra...@chromium.orgjavascript:; wrote: I think three releases sounds fine. My main point here is that we should make that decision now, and announce the deprecation plan alongside 3.0, so users know the situation. Announcing both soon also sounds like a good idea, but we want to make sure any announcement of 3.0 is accompanied by our deprecation plan for 2.x. Braden On Tue, Jun 11, 2013 at 10:12 AM, Joe Bowser bows...@gmail.comjavascript:; wrote: On Tue, Jun 11, 2013 at 6:56 AM, Braden Shepherdson bra...@chromium.org javascript:; wrote: I'm indifferent about adding this back. What I do want to comment on is that this seems like a good precursor of the furor that 3.0 is likely to create. Lots of things are going to change, and all of these old plugins are going to be in a questionable state. In principle there's no reason why you can't manually install them in a 3.0-era project, I suppose. The old plugins are already in a questionable state. We don't maintain these plugins. The problem that we have now is that there are projects that depend on these plugins, and people haven't been updating the plugins. I know for a fact that not even PhoneGap Build has updated their Facebook Connect plugin. Also, I do have concerns about the publicity that 3.0 isn't getting so far. We need to actually announce to our users that we're making a massive change to Cordova. But it's going to be very confusing, and I suspect people are going to be trying to use the CLI tools to install old plugins, and manually installing new plugins. Or just not updating, because it would require more than a small bit of work to migrate their apps. How firm are we going to be when our users cry out for a 2.10, for long-term support for 2.x? It might be to our advantage to promise a couple of bugfix releases on 2.x up front when announcing 3.0. That sets the expectations: you have plenty of warning, and time to make the change, but it's not going to last forever; the decision for when to drop support is already made. I think we should do a three release deprecation of 2.x, as in by the time that 3.2 rolls out, we stop supporting 2.x altogether. People will continue to use 2.x, but we won't support it. We don't want to find ourselves juggling both branches six months from now, let alone a year from now. Fair enough! Based on what happened last year, I think 3.2.0 will come out in the fall, therefore we're not going to be stuck with the old version for very long. What do other people think? Should we just not maintain 2.x at all? Who can we blame for this, because I'm getting tired of being the Batman of this project.
Re: Hi group
Welcome Piotr! On Tuesday, June 11, 2013, Filip Maj wrote: Welcome man! I would totally link you to all the repos and which ones are important and how to get started, but the apache git servers we rely on are currently down :( On 6/11/13 6:47 AM, James Jong wjamesj...@gmail.com javascript:; wrote: Great to have you aboard Piotr. Welcome! -James Jong On Jun 11, 2013, at 5:40 AM, Ken Wallis kwal...@blackberry.comjavascript:; wrote: Welcome Piotr! -- Ken Wallis Product Manager WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com javascript:;] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org javascript:; Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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: Hi group
Witam, Piotr! On Tue, Jun 11, 2013 at 11:15 AM, Filip Maj f...@adobe.com wrote: Welcome man! I would totally link you to all the repos and which ones are important and how to get started, but the apache git servers we rely on are currently down :( On 6/11/13 6:47 AM, James Jong wjamesj...@gmail.com wrote: Great to have you aboard Piotr. Welcome! -James Jong On Jun 11, 2013, at 5:40 AM, Ken Wallis kwal...@blackberry.com wrote: Welcome Piotr! -- Ken Wallis Product Manager WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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: Plugin and CordovaPlugin
I agree with you here Joe. We should put it back in 2.x stream and then kill it with fire for 3.x. For people who want to keep using the old style plugins then they can stick with the 2.x stream. Speaking of, are we going to have a long lived 2.x stream where we only port critical bug fixes? Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jun 11, 2013 at 1:53 PM, Joe Bowser bows...@gmail.com wrote: OK, We actually did deprecate this properly. I don't know how I missed this edit Simon did on the Wiki: https://wiki.apache.org/cordova/DeprecationPolicy I think we should put it back for 2.x and remove it from 3.x. We also shouldn't support any bugs that appear with old plugins adding this. On Tue, Jun 11, 2013 at 7:15 AM, Braden Shepherdson bra...@chromium.org wrote: I think three releases sounds fine. My main point here is that we should make that decision now, and announce the deprecation plan alongside 3.0, so users know the situation. Announcing both soon also sounds like a good idea, but we want to make sure any announcement of 3.0 is accompanied by our deprecation plan for 2.x. Braden On Tue, Jun 11, 2013 at 10:12 AM, Joe Bowser bows...@gmail.com wrote: On Tue, Jun 11, 2013 at 6:56 AM, Braden Shepherdson bra...@chromium.org wrote: I'm indifferent about adding this back. What I do want to comment on is that this seems like a good precursor of the furor that 3.0 is likely to create. Lots of things are going to change, and all of these old plugins are going to be in a questionable state. In principle there's no reason why you can't manually install them in a 3.0-era project, I suppose. The old plugins are already in a questionable state. We don't maintain these plugins. The problem that we have now is that there are projects that depend on these plugins, and people haven't been updating the plugins. I know for a fact that not even PhoneGap Build has updated their Facebook Connect plugin. Also, I do have concerns about the publicity that 3.0 isn't getting so far. We need to actually announce to our users that we're making a massive change to Cordova. But it's going to be very confusing, and I suspect people are going to be trying to use the CLI tools to install old plugins, and manually installing new plugins. Or just not updating, because it would require more than a small bit of work to migrate their apps. How firm are we going to be when our users cry out for a 2.10, for long-term support for 2.x? It might be to our advantage to promise a couple of bugfix releases on 2.x up front when announcing 3.0. That sets the expectations: you have plenty of warning, and time to make the change, but it's not going to last forever; the decision for when to drop support is already made. I think we should do a three release deprecation of 2.x, as in by the time that 3.2 rolls out, we stop supporting 2.x altogether. People will continue to use 2.x, but we won't support it. We don't want to find ourselves juggling both branches six months from now, let alone a year from now. Fair enough! Based on what happened last year, I think 3.2.0 will come out in the fall, therefore we're not going to be stuck with the old version for very long. What do other people think? Should we just not maintain 2.x at all? Who can we blame for this, because I'm getting tired of being the Batman of this project.
Re: Plugin and CordovaPlugin
I think that 2.9.x is going to be our long-lived 2.x stream. So, whatever we dump in this release will be with us for as long as we want to support that release. BTW: I have a 2.8.1 tagged and ready to go, but the git servers are down. :( On Tue, Jun 11, 2013 at 11:34 AM, Simon MacDonald simon.macdon...@gmail.com wrote: I agree with you here Joe. We should put it back in 2.x stream and then kill it with fire for 3.x. For people who want to keep using the old style plugins then they can stick with the 2.x stream. Speaking of, are we going to have a long lived 2.x stream where we only port critical bug fixes? Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jun 11, 2013 at 1:53 PM, Joe Bowser bows...@gmail.com wrote: OK, We actually did deprecate this properly. I don't know how I missed this edit Simon did on the Wiki: https://wiki.apache.org/cordova/DeprecationPolicy I think we should put it back for 2.x and remove it from 3.x. We also shouldn't support any bugs that appear with old plugins adding this. On Tue, Jun 11, 2013 at 7:15 AM, Braden Shepherdson bra...@chromium.org wrote: I think three releases sounds fine. My main point here is that we should make that decision now, and announce the deprecation plan alongside 3.0, so users know the situation. Announcing both soon also sounds like a good idea, but we want to make sure any announcement of 3.0 is accompanied by our deprecation plan for 2.x. Braden On Tue, Jun 11, 2013 at 10:12 AM, Joe Bowser bows...@gmail.com wrote: On Tue, Jun 11, 2013 at 6:56 AM, Braden Shepherdson bra...@chromium.org wrote: I'm indifferent about adding this back. What I do want to comment on is that this seems like a good precursor of the furor that 3.0 is likely to create. Lots of things are going to change, and all of these old plugins are going to be in a questionable state. In principle there's no reason why you can't manually install them in a 3.0-era project, I suppose. The old plugins are already in a questionable state. We don't maintain these plugins. The problem that we have now is that there are projects that depend on these plugins, and people haven't been updating the plugins. I know for a fact that not even PhoneGap Build has updated their Facebook Connect plugin. Also, I do have concerns about the publicity that 3.0 isn't getting so far. We need to actually announce to our users that we're making a massive change to Cordova. But it's going to be very confusing, and I suspect people are going to be trying to use the CLI tools to install old plugins, and manually installing new plugins. Or just not updating, because it would require more than a small bit of work to migrate their apps. How firm are we going to be when our users cry out for a 2.10, for long-term support for 2.x? It might be to our advantage to promise a couple of bugfix releases on 2.x up front when announcing 3.0. That sets the expectations: you have plenty of warning, and time to make the change, but it's not going to last forever; the decision for when to drop support is already made. I think we should do a three release deprecation of 2.x, as in by the time that 3.2 rolls out, we stop supporting 2.x altogether. People will continue to use 2.x, but we won't support it. We don't want to find ourselves juggling both branches six months from now, let alone a year from now. Fair enough! Based on what happened last year, I think 3.2.0 will come out in the fall, therefore we're not going to be stuck with the old version for very long. What do other people think? Should we just not maintain 2.x at all? Who can we blame for this, because I'm getting tired of being the Batman of this project.
Re: Hi group
Welcome to Cordova Piotr (and thank you for JSFiddle!) On Tue, Jun 11, 2013 at 11:25 AM, Michal Mocny mmo...@chromium.org wrote: Witam, Piotr! On Tue, Jun 11, 2013 at 11:15 AM, Filip Maj f...@adobe.com wrote: Welcome man! I would totally link you to all the repos and which ones are important and how to get started, but the apache git servers we rely on are currently down :( On 6/11/13 6:47 AM, James Jong wjamesj...@gmail.com wrote: Great to have you aboard Piotr. Welcome! -James Jong On Jun 11, 2013, at 5:40 AM, Ken Wallis kwal...@blackberry.com wrote: Welcome Piotr! -- Ken Wallis Product Manager WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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: Hi group
Welcome Piotr! Hopefully I will be able to help you out post 3.0 on FFOS port On Tue, Jun 11, 2013 at 11:50 AM, Brian LeRoux b...@brian.io wrote: Welcome to Cordova Piotr (and thank you for JSFiddle!) On Tue, Jun 11, 2013 at 11:25 AM, Michal Mocny mmo...@chromium.org wrote: Witam, Piotr! On Tue, Jun 11, 2013 at 11:15 AM, Filip Maj f...@adobe.com wrote: Welcome man! I would totally link you to all the repos and which ones are important and how to get started, but the apache git servers we rely on are currently down :( On 6/11/13 6:47 AM, James Jong wjamesj...@gmail.com wrote: Great to have you aboard Piotr. Welcome! -James Jong On Jun 11, 2013, at 5:40 AM, Ken Wallis kwal...@blackberry.com wrote: Welcome Piotr! -- Ken Wallis Product Manager WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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: Plugin and CordovaPlugin
On Jun 11, 2013, at 2:23 PM, Shazron shaz...@gmail.com wrote: Whatever we decide can we be extra loud about it? Blog posts, tweets, google groups. On Tuesday, June 11, 2013, Joe Bowser wrote: OK, We actually did deprecate this properly. I don't know how I missed this edit Simon did on the Wiki: https://wiki.apache.org/cordova/DeprecationPolicy Yeah, something on this tack. So if it was deprecated properly, why is there noise in the plugin ecosystem? Joe/Simon did the right things, but for whatever reason it didn't connect with the consumers. If we think this is just a matter of consumer communication, here are some potential ways to improve that: - add to cordova-docs a top-level Upgrading Plugins Guide. I think Michael Billau had started one and might have a draft. And Simon has a blog post on this topic. - add to cordova-docs a top-level Deprecation Index that has: - pointers to other places in the docs (i.e., device.name, org.apache.cordova.api.Plugin) where there is detail on which things are going away. And the history of which things already have gone away. - in that detail, the version or date when they are going away, and link to the Upgrading Plugins Guide or Upgrading Cordova platformX Guide or some other reference that says what to do so you don't break when they do go away. - these would move it off the wiki into the docs, because perhaps consumers don't monitor the wiki. Perhaps all that should remain on the wiki is the policy definition. It does seem that the wiki is really geared to contributors/committers, not consumers. - add to cordova-docs a top-level summary of What's New in Cordova x.y. Shaz and Joe (and Simon) do a great job posting that on their blogs, but feels like there ought to be something in the docs. In lieu of making more work, just copy-paste their text into an md file for that in the docs (if they are OK with that). That can include reminders of deprecation hits. Is there an official news feed that could be monitored by plugin authors or other Cordova consumers for changes like this? I found the @apachecordova Twitter account. But perhaps there is something offered by apache-infra or elsewhere better suited to that kind of content. Whatever it is, including a top-level pointer to it in cordova-docs so consumers know they should be monitoring it. And so they can go back months later and look at the history easily (i.e., why did my plugin break in 2.2?). Comments? -- Marcel Kinard
RE: Hi group
Welcome Piotr! From: stevengil...@gmail.com Date: Tue, 11 Jun 2013 12:08:36 -0700 Subject: Re: Hi group To: dev@cordova.apache.org Welcome Piotr! Hopefully I will be able to help you out post 3.0 on FFOS port On Tue, Jun 11, 2013 at 11:50 AM, Brian LeRoux b...@brian.io wrote: Welcome to Cordova Piotr (and thank you for JSFiddle!) On Tue, Jun 11, 2013 at 11:25 AM, Michal Mocny mmo...@chromium.org wrote: Witam, Piotr! On Tue, Jun 11, 2013 at 11:15 AM, Filip Maj f...@adobe.com wrote: Welcome man! I would totally link you to all the repos and which ones are important and how to get started, but the apache git servers we rely on are currently down :( On 6/11/13 6:47 AM, James Jong wjamesj...@gmail.com wrote: Great to have you aboard Piotr. Welcome! -James Jong On Jun 11, 2013, at 5:40 AM, Ken Wallis kwal...@blackberry.com wrote: Welcome Piotr! -- Ken Wallis Product Manager WebWorks BlackBerry 289-261-4369 From: Piotr Zalewa [pzal...@mozilla.com] Sent: Tuesday, June 11, 2013 12:44 AM To: dev@cordova.apache.org Subject: Hi group Hi, I've been following the group for some time, however kept quiet. I'm working for Mozilla and I've been asked to help with porting Cordova to FirefoxOS. You may know me from few projects I've created (JSFiddle being probably most known to you). My latest and not finished project at Mozilla is Kitchensink - a webapp which tests APIs. I am a noob to Cordova and will hit probably quite a few trivial blockers. I am on the #cordova channel as zalun. Piotr - 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.
Any problem with making DirectoryManager.getTempDirectoryPath public
For Android. I need to make DirectoryManager.getTempDirectoryPath public so it can work with the camera plugin. -Steve
Re: Any problem with making DirectoryManager.getTempDirectoryPath public
It's a part of plugin breakout. The main question is whether DirectoryManager should be a public API by documenting it, since a plugin needs it to function, not should we make it public. But yeah, make it public Steve! On Tue, Jun 11, 2013 at 12:48 PM, Simon MacDonald simon.macdon...@gmail.com wrote: Huh, you shouldn't need to do that as the DirectoryManager and CameraLauncher are in the same package. I guess you are moving CameraLauncher into it's own package, in which case go for it. Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jun 11, 2013 at 3:43 PM, Steven Gill stevengil...@gmail.com wrote: For Android. I need to make DirectoryManager.getTempDirectoryPath public so it can work with the camera plugin. -Steve
June board report.
Am I missing anything? https://github.com/cordova/apache-board-reports/blob/master/2013-06.md
Re: June board report.
Mapes not Maps On 13-06-11 2:17 PM, Brian LeRoux b...@brian.io wrote: Am I missing anything? https://github.com/cordova/apache-board-reports/blob/master/2013-06.md
Re: CLI lazy loading of libraries
Hey guys another quick update
I have made progress on the hooks/events/middleware approach and opted for
a simpler, configuration approach. I think this approach satisfies
requirements for Adobe w.r.t. phonegap's CLI, as well as the wishes Michal
and Braden expressed for customizing the various libraries the cli
consumes.
Once the git servers are back up, I'll push the latest code, but in the
meantime, here's how the replace stock cordova libraries with your own
functionality is coded atm - it's hooked into the lazy load functionality:
1. customize project/.cordova/config.json's lib object to point to
specific locations of libraries (see examples below for detail)
- you can do so at a module-level as well by calling
`cordova.config({lib:{/* whatever */}});
2. Then every time you go to add a platform, it checks if the appropriate
fields exist in the config.json, and if so, will lazy load the necessary
library before shelling out the library executable.
3. This also works with the cordova hello world app. So if you call
cordova.config() with details about the location of your www assets and
whatnot before calling cordova.create(), it will use that info to lazy
load those assets first.
Example 1: I want to use latest (master) of cordova-android from my local
filesystem
You can do so via CLI or node-level module, here's the cli based example:
$ cordova create tmp
$ vim tmp/.cordova/config.json
* edit to add a path to the lib *
$ cat tmp/.cordova/config.json
{
id:'io.cordova.hello',
name:'HelloCordova',
lib:{
android:{
uri:/Users/fil/src/cordova-android,
version:master
id:cordova-master
}
}
}
$ cd tmp
$ cordova platform add android
^ that will shell out to /Users/fil/src/cordova-android/bin/create
You can do the same with a library that is stored on the web somewhere.
Currently, it must be a .tar.gz but nothing stopping us from adding more
support compression-wise. For example, imagine we have some fork of
cordova-android that uses ChromeView instead.
The above will also copy the local cordova-android directory into
~/.cordova/lib/android/cordova-master/master/.
Example 2: I want to use phonegap-start www app instead of the
cordova-app-hello-world
Can only do so via node module right now (because the the www assets get
copied over when you call create), but here's how you would do it:
$ node
cordova=require('cordova');
app_path = '/location/that/my/app/will/exist'
cordova.config(app_path, {
lib:{
www:{
uri:https://github.com/phonegap/phonegap-start/archive/2.5.0.tar.gz;,
version:2.5.0
id:phonegap
}
}});
cordova.create(app_path);
Downloading
https://github.com/phonegap/phonegap-start/archive/2.5.0.tar.gz...
Similarly to the my first example, this one will create a
~/.cordova/lib/www/phonegap/2.5.0 directory, with the contents of the tar
ball extracted into it.
I still have a bunch of work to do with this, like revamping our tests
completely and adding new coverage for these features, but inching closer.
On 6/7/13 2:46 PM, Michael Brooks mich...@michaelbrooks.ca wrote:
1. Awesome
2. Very similar logic exists in the phonegap-cli [1] [2]. Since this logic
is being used by phonegap-cli, node-phonegap-build, and cordova-cli, we
could extract it out to a new NPM module called cordova-config.
3. Additionally, PhoneGap will want to load its own Hello World app
instead
of the Cordova Hello World app. So, it would be nice to accomodate this
situation gracefully. Do Chrome Apps have any odd requirements?
[1]
https://github.com/mwbrooks/phonegap-cli/blob/master/lib/common/config.js
[2]
https://github.com/mwbrooks/phonegap-cli/tree/master/spec/common/config
On Fri, Jun 7, 2013 at 2:38 PM, Filip Maj f...@adobe.com wrote:
Cool, thanks Mike, I'll use the gitweb approach to download libraries.
And re #2: fair enough, I'll add that bit of logic to the find the root
of a cordova project utility function.
As for the hooks, I am still mulling over different approaches. One
scenario that us Adobe folk want to support for PhoneGap is redirecting
any adds/builds for particular platforms that are not supported on a
user's machine to PhoneGap Build. For example, if a user's machine was
not
setup for iOS development (say, a Windows machine), the PhoneGap CLI not
only needs to know when a particular event happens, but also needs to be
able to stop the Cordova CLI from proceeding with the event - something
akin to e.preventDefault() in DOM events.
I'm not sure of any npm libraries out there that have a similar eventing
system in place but I will do some research and see if there is any
prior
art out there.
If anyone on the list has any ideas, I'm all ears :)
On 13-06-07 10:07 AM, Michael Brooks mich...@michaelbrooks.ca wrote:
1. The Apache GitWeb implementation allows us to download a tar.gz of
any
hash or tag. Using this will allow us to
Re: CRC32 checksum failed with Cordova 2.2.0
Andreas, I'm curious if you could describe a bit why your project needs to run on iOS 4? According to a couple stats I found [1, 2], usage of iOS 4 appears to be around 1.4% of all iOS versions. Does that fall under the don't care or not worth it threshold for you? @Marcel My decision is based on my customer's wish to provide iOS 4 support for his app. I fully agree with you that all the effort needs to be taken into account doesn't really deserve the few percentages of people (let it be 4-5%) really using this app under iOS 4. I will discuss the problems with my customer again, but I simply tried to fulfill that iOS 4 support with cordova, but as I found out today that's not that simple as it seemed to me before. There is a way but I'm not sure how much I should support you in this endeavor.. You are futzing with the code at this point so, consider this your warning! If you replace the contents of cordova-cli/lib/cordova-ios with the contents of your cordova-ios package, it *should* work. Depends on which version of cordova-cli you are running as the cli code has expectations about which bits inside the cordova-ios lib exist. If you installed it via npm install -g then it should exist somewhere like /usr/local/lib/node_modules/cordova @Filip Maj Thanks for all of your help. I know that this isn't the intended workflow. ;-) The cordova in usr/local is there, yes. Thx for pointing out the cordova-ios directory inside lib folder. I thought it should be renamed to ios. Maybe that's solving my main problem. ;-) I know that I'm working on an edge case. I simply tried to get my project running under iOS 4. Now, without any usage of cordova cli, which is broken for me under cordova 2.2.0 due to this weird checksum problem, everything is running now. With best regards from Germany and really thank you for your time and help! Andreas
Re: June board report.
:`( On Tue, Jun 11, 2013 at 2:49 PM, Brian LeRoux b...@brian.io wrote: whatever he's a Bruins guy ;P On Tue, Jun 11, 2013 at 2:28 PM, Max Woghiren m...@chromium.org wrote: Benn, also. On Tue, Jun 11, 2013 at 5:27 PM, Joni Rustulka j...@adobe.com wrote: Mapes not Maps On 13-06-11 2:17 PM, Brian LeRoux b...@brian.io wrote: Am I missing anything? https://github.com/cordova/apache-board-reports/blob/master/2013-06.md
Re: June board report.
awww sorry mapes GO HAWKS! On Tue, Jun 11, 2013 at 4:55 PM, Benn Mapes benn.ma...@gmail.com wrote: :`( On Tue, Jun 11, 2013 at 2:49 PM, Brian LeRoux b...@brian.io wrote: whatever he's a Bruins guy ;P On Tue, Jun 11, 2013 at 2:28 PM, Max Woghiren m...@chromium.org wrote: Benn, also. On Tue, Jun 11, 2013 at 5:27 PM, Joni Rustulka j...@adobe.com wrote: Mapes not Maps On 13-06-11 2:17 PM, Brian LeRoux b...@brian.io wrote: Am I missing anything? https://github.com/cordova/apache-board-reports/blob/master/2013-06.md
Re: CLI lazy loading of libraries
That sounds awesome, sweet work Fil!
Question: your cordova-android lib example has the uri
/Users/fil/src/cordova-android, but you mention supporting only .tar.gz
-- does that mean that non-archived local directories are also supported?
(I should hope so).
Thanks!
-Michal
On Tue, Jun 11, 2013 at 6:10 PM, Filip Maj f...@adobe.com wrote:
Hey guys another quick update
I have made progress on the hooks/events/middleware approach and opted for
a simpler, configuration approach. I think this approach satisfies
requirements for Adobe w.r.t. phonegap's CLI, as well as the wishes Michal
and Braden expressed for customizing the various libraries the cli
consumes.
Once the git servers are back up, I'll push the latest code, but in the
meantime, here's how the replace stock cordova libraries with your own
functionality is coded atm - it's hooked into the lazy load functionality:
1. customize project/.cordova/config.json's lib object to point to
specific locations of libraries (see examples below for detail)
- you can do so at a module-level as well by calling
`cordova.config({lib:{/* whatever */}});
2. Then every time you go to add a platform, it checks if the appropriate
fields exist in the config.json, and if so, will lazy load the necessary
library before shelling out the library executable.
3. This also works with the cordova hello world app. So if you call
cordova.config() with details about the location of your www assets and
whatnot before calling cordova.create(), it will use that info to lazy
load those assets first.
Example 1: I want to use latest (master) of cordova-android from my local
filesystem
You can do so via CLI or node-level module, here's the cli based example:
$ cordova create tmp
$ vim tmp/.cordova/config.json
* edit to add a path to the lib *
$ cat tmp/.cordova/config.json
{
id:'io.cordova.hello',
name:'HelloCordova',
lib:{
android:{
uri:/Users/fil/src/cordova-android,
version:master
id:cordova-master
}
}
}
$ cd tmp
$ cordova platform add android
^ that will shell out to /Users/fil/src/cordova-android/bin/create
You can do the same with a library that is stored on the web somewhere.
Currently, it must be a .tar.gz but nothing stopping us from adding more
support compression-wise. For example, imagine we have some fork of
cordova-android that uses ChromeView instead.
The above will also copy the local cordova-android directory into
~/.cordova/lib/android/cordova-master/master/.
Example 2: I want to use phonegap-start www app instead of the
cordova-app-hello-world
Can only do so via node module right now (because the the www assets get
copied over when you call create), but here's how you would do it:
$ node
cordova=require('cordova');
app_path = '/location/that/my/app/will/exist'
cordova.config(app_path, {
lib:{
www:{
uri:https://github.com/phonegap/phonegap-start/archive/2.5.0.tar.gz;,
version:2.5.0
id:phonegap
}
}});
cordova.create(app_path);
Downloading
https://github.com/phonegap/phonegap-start/archive/2.5.0.tar.gz...
Similarly to the my first example, this one will create a
~/.cordova/lib/www/phonegap/2.5.0 directory, with the contents of the tar
ball extracted into it.
I still have a bunch of work to do with this, like revamping our tests
completely and adding new coverage for these features, but inching closer.
On 6/7/13 2:46 PM, Michael Brooks mich...@michaelbrooks.ca wrote:
1. Awesome
2. Very similar logic exists in the phonegap-cli [1] [2]. Since this logic
is being used by phonegap-cli, node-phonegap-build, and cordova-cli, we
could extract it out to a new NPM module called cordova-config.
3. Additionally, PhoneGap will want to load its own Hello World app
instead
of the Cordova Hello World app. So, it would be nice to accomodate this
situation gracefully. Do Chrome Apps have any odd requirements?
[1]
https://github.com/mwbrooks/phonegap-cli/blob/master/lib/common/config.js
[2]
https://github.com/mwbrooks/phonegap-cli/tree/master/spec/common/config
On Fri, Jun 7, 2013 at 2:38 PM, Filip Maj f...@adobe.com wrote:
Cool, thanks Mike, I'll use the gitweb approach to download libraries.
And re #2: fair enough, I'll add that bit of logic to the find the root
of a cordova project utility function.
As for the hooks, I am still mulling over different approaches. One
scenario that us Adobe folk want to support for PhoneGap is redirecting
any adds/builds for particular platforms that are not supported on a
user's machine to PhoneGap Build. For example, if a user's machine was
not
setup for iOS development (say, a Windows machine), the PhoneGap CLI not
only needs to know when a particular event happens, but also needs to be
able to stop the Cordova CLI from proceeding with the event - something
akin to
Re: June board report.
xD On Tue, Jun 11, 2013 at 5:04 PM, Brian LeRoux b...@brian.io wrote: awww sorry mapes GO HAWKS! On Tue, Jun 11, 2013 at 4:55 PM, Benn Mapes benn.ma...@gmail.com wrote: :`( On Tue, Jun 11, 2013 at 2:49 PM, Brian LeRoux b...@brian.io wrote: whatever he's a Bruins guy ;P On Tue, Jun 11, 2013 at 2:28 PM, Max Woghiren m...@chromium.org wrote: Benn, also. On Tue, Jun 11, 2013 at 5:27 PM, Joni Rustulka j...@adobe.com wrote: Mapes not Maps On 13-06-11 2:17 PM, Brian LeRoux b...@brian.io wrote: Am I missing anything? https://github.com/cordova/apache-board-reports/blob/master/2013-06.md
