Re: blackberry10 build
Matt - thanks for the detailed feedback! I'll be entering in JIRAs for the tasks needed to tighten up the bb10 CLI experience today. On Mon, Jul 22, 2013 at 11:20 AM, Lucas Holmquist lholm...@redhat.comwrote: Nice write up, On Jul 22, 2013, at 11:14 AM, Matt Lantz mattla...@gmail.com wrote: Developing a BlackBerry10 App with Cordova 3.0.0 So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any information about the blackberry10.json file I had to modify. After performing: sudo npm update -g cordova It stated I now had 3.0.0 I attempted the cordova -d run blackberry10 again and this time I saw the %home%/.cordova/blackberry10.json statement. I went to the file immediately and added the keystorepass that I had used in my debug token. Called the run command and bam the app uploaded to the device. I was elated. I can honestly say I am stupefied as to how awesome the CLI is for Cordova everyone! I was amazed at how fast I could get something put together. However, documentation is still lacking, in particular with blackberry10. It was quite confusing for a relative outsider. I'm happy to fork the documentation and work on any inconsistencies/ issues I can help with. On 20 July, 2013 at 9:17:46 PM, Filip Maj (f...@adobe.com) wrote: Yeh Matt if you would be so kind as to summarize your experience then certainly we can formalize as issues and make sure to fix in the coming weeks so it's not as difficult. Appreciate you working through it! On 7/20/13 9:31 AM, M. Lantz mattla...@gmail.com wrote: Thanks Jeff, I finally caught on to that after upgrading my Cordova. I was on 3.0.0rc not 3.0.0 and noticed the the comments that indicated that. Thanks though. M. Lantz On 2013-07-20, at 2:17 AM, Jeffrey Heifetz
cli docs - spaces in main activity name
The CLI docs for creating an app, use a main activity name containing a space $ cordova create HelloWorld com.example.hello Hello World This works for iOS but fails on Android. Should we adjust the docs, or attempt to make the Android scripts remove spaces? http://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface_create_the_app
Cordova + Yeoman
Would be neat to have first-class support for Cordova by Yeoman, but looks like their default template works decently already: http://www.gauntface.co.uk/blog/2013/07/18/cordova-web-best-practices/
Re: cli docs - spaces in main activity name
At some point we just stripped spaces. I imagine this created a bug and my guess is we removed the functionality rather than addressing the issue. We def do not want titles with no spaces! Maybe we add a fourth param. On Mon, Jul 22, 2013 at 12:10 PM, Andrew Grieve agri...@chromium.org wrote: The third parameter is the app's title, so I think it should be made to work with spaces. On Mon, Jul 22, 2013 at 12:07 PM, Don Coleman don.cole...@gmail.com wrote: The CLI docs for creating an app, use a main activity name containing a space $ cordova create HelloWorld com.example.hello Hello World This works for iOS but fails on Android. Should we adjust the docs, or attempt to make the Android scripts remove spaces? http://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface_create_the_app
Re: cli docs - spaces in main activity name
The third parameter is the app's title, so I think it should be made to work with spaces. On Mon, Jul 22, 2013 at 12:07 PM, Don Coleman don.cole...@gmail.com wrote: The CLI docs for creating an app, use a main activity name containing a space $ cordova create HelloWorld com.example.hello Hello World This works for iOS but fails on Android. Should we adjust the docs, or attempt to make the Android scripts remove spaces? http://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface_create_the_app
Re: blackberry10 build
Developing a BlackBerry10 App with Cordova 3.0.0So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one.After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience.On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command.cordova -d run blackberry10I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json.Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to:cordova -vI had cordova 3.0.0rc1 which was not giving me any information about the blackberry10.json file I had to modify. After performing:sudo npm update -g cordovaIt stated I now had 3.0.0I attempted the cordova -d run blackberry10 again and this time I saw the %home%/.cordova/blackberry10.json statement. I went to the file immediately and added the "keystorepass" that I had used in my debug token. Called the run command and bam the app uploaded to the device. I was elated.I can honestly say I am stupefied as to how awesome the CLI is for Cordova everyone! I was amazed at how fast I could get something put together. However, documentation is still lacking, in particular with blackberry10. It was quite confusing for a relative outsider. I'm happy to fork the documentation and work on any inconsistencies/ issues I can help with. On 20 July, 2013 at 9:17:46 PM, Filip Maj (f...@adobe.com) wrote: Yeh Matt if you would be so kind as to summarize your experience then certainly we can formalize as issues and make sure to fix in the coming weeks so it's not as difficult. Appreciate you working through it! On 7/20/13 9:31 AM, "M. Lantz" mattla...@gmail.com wrote: Thanks Jeff, I finally caught on to that after upgrading my Cordova. I was on 3.0.0rc not 3.0.0 and noticed the the comments that indicated that. Thanks though. M. Lantz On 2013-07-20, at 2:17 AM, Jeffrey Heifetz jheif...@blackberry.com wrote: You haw no signing key provided so it's skipping debug token generation. You need to either add a key store pass value to your %home%/.cordova/blackberry10.json or use the platform level cordova/run script with -k and your key store pass. Sent from my BlackBerry 10 smartphone on the Rogers network. From: Matt Lantz Sent: Friday, July 19, 2013 9:02 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org
Re: blackberry10 build
Thanks for this feedback Matt Contributions to documentation or anything are always welcome. On Mon, Jul 22, 2013 at 8:14 AM, Matt Lantz mattla...@gmail.com wrote: ** *Developing a BlackBerry10 App with Cordova 3.0.0* ** * So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any information about the blackberry10.json file I had to modify. After performing: sudo npm update -g cordova It stated I now had 3.0.0 I attempted the cordova -d run blackberry10 again and this time I saw the %home%/.cordova/blackberry10.json statement. I went to the file immediately and added the keystorepass that I had used in my debug token. Called the run command and bam the app uploaded to the device. I was elated. I can honestly say I am stupefied as to how awesome the CLI is for Cordova everyone! I was amazed at how fast I could get something put together. However, documentation is still lacking, in particular with blackberry10. It was quite confusing for a relative outsider. I'm happy to fork the documentation and work on any inconsistencies/ issues I can help with. * On 20 July, 2013 at 9:17:46 PM, Filip Maj (f...@adobe.com) wrote: Yeh Matt if you would be so kind as to summarize your experience then certainly we can formalize as issues and make sure to fix in the coming weeks so it's not as difficult. Appreciate you working through it! On 7/20/13 9:31 AM, M. Lantz mattla...@gmail.com wrote: Thanks Jeff, I finally caught on to that after upgrading my Cordova. I was on 3.0.0rc not 3.0.0 and noticed the the comments that indicated that. Thanks though. M. Lantz On 2013-07-20, at 2:17 AM, Jeffrey Heifetz jheif...@blackberry.com wrote: You haw no signing key provided so it's skipping debug token generation. You need to either add a key store pass value to your
Re: blackberry10 build
Nice write up, On Jul 22, 2013, at 11:14 AM, Matt Lantz mattla...@gmail.com wrote: Developing a BlackBerry10 App with Cordova 3.0.0 So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any information about the blackberry10.json file I had to modify. After performing: sudo npm update -g cordova It stated I now had 3.0.0 I attempted the cordova -d run blackberry10 again and this time I saw the %home%/.cordova/blackberry10.json statement. I went to the file immediately and added the keystorepass that I had used in my debug token. Called the run command and bam the app uploaded to the device. I was elated. I can honestly say I am stupefied as to how awesome the CLI is for Cordova everyone! I was amazed at how fast I could get something put together. However, documentation is still lacking, in particular with blackberry10. It was quite confusing for a relative outsider. I'm happy to fork the documentation and work on any inconsistencies/ issues I can help with. On 20 July, 2013 at 9:17:46 PM, Filip Maj (f...@adobe.com) wrote: Yeh Matt if you would be so kind as to summarize your experience then certainly we can formalize as issues and make sure to fix in the coming weeks so it's not as difficult. Appreciate you working through it! On 7/20/13 9:31 AM, M. Lantz mattla...@gmail.com wrote: Thanks Jeff, I finally caught on to that after upgrading my Cordova. I was on 3.0.0rc not 3.0.0 and noticed the the comments that indicated that. Thanks though. M. Lantz On 2013-07-20, at 2:17 AM, Jeffrey Heifetz jheif...@blackberry.com wrote: You haw no signing key provided so it's skipping debug token generation. You need to either add a key store pass value to your
RE: cli docs - spaces in main activity name
I just added a JIRA CB-4343 for bb10 modified it to include android. This appears new to 3.0; had no problem with Hello World prior. --Mike S From: brian.ler...@gmail.com [brian.ler...@gmail.com] On Behalf Of Brian LeRoux [b...@brian.io] Sent: Monday, July 22, 2013 12:21 PM To: dev@cordova.apache.org Subject: Re: cli docs - spaces in main activity name At some point we just stripped spaces. I imagine this created a bug and my guess is we removed the functionality rather than addressing the issue. We def do not want titles with no spaces! Maybe we add a fourth param. On Mon, Jul 22, 2013 at 12:10 PM, Andrew Grieve agri...@chromium.org wrote: The third parameter is the app's title, so I think it should be made to work with spaces. On Mon, Jul 22, 2013 at 12:07 PM, Don Coleman don.cole...@gmail.com wrote: The CLI docs for creating an app, use a main activity name containing a space $ cordova create HelloWorld com.example.hello Hello World This works for iOS but fails on Android. Should we adjust the docs, or attempt to make the Android scripts remove spaces? http://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface_create_the_app
Re: cli docs - spaces in main activity name
Stripping spaces and other invalid chars seems preferable to adding another parameter. There is an issue https://issues.apache.org/jira/browse/CB-4074, which appears to be *incorrectly* marked as a dup of CB-4198. On Mon, Jul 22, 2013 at 1:10 PM, Michael Sierra msie...@adobe.com wrote: I just added a JIRA CB-4343 for bb10 modified it to include android. This appears new to 3.0; had no problem with Hello World prior. --Mike S From: brian.ler...@gmail.com [brian.ler...@gmail.com] On Behalf Of Brian LeRoux [b...@brian.io] Sent: Monday, July 22, 2013 12:21 PM To: dev@cordova.apache.org Subject: Re: cli docs - spaces in main activity name At some point we just stripped spaces. I imagine this created a bug and my guess is we removed the functionality rather than addressing the issue. We def do not want titles with no spaces! Maybe we add a fourth param. On Mon, Jul 22, 2013 at 12:10 PM, Andrew Grieve agri...@chromium.org wrote: The third parameter is the app's title, so I think it should be made to work with spaces. On Mon, Jul 22, 2013 at 12:07 PM, Don Coleman don.cole...@gmail.com wrote: The CLI docs for creating an app, use a main activity name containing a space $ cordova create HelloWorld com.example.hello Hello World This works for iOS but fails on Android. Should we adjust the docs, or attempt to make the Android scripts remove spaces? http://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface_create_the_app
Re: cli docs - spaces in main activity name
Had those backwards https://issues.apache.org/jira/browse/CB-4198 is the issue. On Mon, Jul 22, 2013 at 1:41 PM, Don Coleman don.cole...@gmail.com wrote: Stripping spaces and other invalid chars seems preferable to adding another parameter. There is an issue https://issues.apache.org/jira/browse/CB-4074, which appears to be *incorrectly* marked as a dup of CB-4198. On Mon, Jul 22, 2013 at 1:10 PM, Michael Sierra msie...@adobe.com wrote: I just added a JIRA CB-4343 for bb10 modified it to include android. This appears new to 3.0; had no problem with Hello World prior. --Mike S From: brian.ler...@gmail.com [brian.ler...@gmail.com] On Behalf Of Brian LeRoux [b...@brian.io] Sent: Monday, July 22, 2013 12:21 PM To: dev@cordova.apache.org Subject: Re: cli docs - spaces in main activity name At some point we just stripped spaces. I imagine this created a bug and my guess is we removed the functionality rather than addressing the issue. We def do not want titles with no spaces! Maybe we add a fourth param. On Mon, Jul 22, 2013 at 12:10 PM, Andrew Grieve agri...@chromium.org wrote: The third parameter is the app's title, so I think it should be made to work with spaces. On Mon, Jul 22, 2013 at 12:07 PM, Don Coleman don.cole...@gmail.com wrote: The CLI docs for creating an app, use a main activity name containing a space $ cordova create HelloWorld com.example.hello Hello World This works for iOS but fails on Android. Should we adjust the docs, or attempt to make the Android scripts remove spaces? http://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface_create_the_app
Re: cli docs - spaces in main activity name
I think it's an issue with Android's underlying create script. It should be smart enough to know to munge the title-with-spaces for its code purposes (Java package name, Activity, etc), but leave it as-is for the labeling. Thx for filing I will look into it when I can. On 7/22/13 10:44 AM, Don Coleman don.cole...@gmail.com wrote: Had those backwards https://issues.apache.org/jira/browse/CB-4198 is the issue. On Mon, Jul 22, 2013 at 1:41 PM, Don Coleman don.cole...@gmail.com wrote: Stripping spaces and other invalid chars seems preferable to adding another parameter. There is an issue https://issues.apache.org/jira/browse/CB-4074, which appears to be *incorrectly* marked as a dup of CB-4198. On Mon, Jul 22, 2013 at 1:10 PM, Michael Sierra msie...@adobe.com wrote: I just added a JIRA CB-4343 for bb10 modified it to include android. This appears new to 3.0; had no problem with Hello World prior. --Mike S From: brian.ler...@gmail.com [brian.ler...@gmail.com] On Behalf Of Brian LeRoux [b...@brian.io] Sent: Monday, July 22, 2013 12:21 PM To: dev@cordova.apache.org Subject: Re: cli docs - spaces in main activity name At some point we just stripped spaces. I imagine this created a bug and my guess is we removed the functionality rather than addressing the issue. We def do not want titles with no spaces! Maybe we add a fourth param. On Mon, Jul 22, 2013 at 12:10 PM, Andrew Grieve agri...@chromium.org wrote: The third parameter is the app's title, so I think it should be made to work with spaces. On Mon, Jul 22, 2013 at 12:07 PM, Don Coleman don.cole...@gmail.com wrote: The CLI docs for creating an app, use a main activity name containing a space $ cordova create HelloWorld com.example.hello Hello World This works for iOS but fails on Android. Should we adjust the docs, or attempt to make the Android scripts remove spaces? http://docs.phonegap.com/en/edge/guide_cli_index.md.html#The%20Command-l ine%20Interface_create_the_app
Re: Cordova + Yeoman
Theres a yeoman generator on npm already: https://npmjs.org/package/generator-cordova also: holy cow the downloads shot up like crazy over the weekend: 1600 downloads / day of cordova-cli. http://npm-stat.vorb.de/charts.html?package=cordova On 7/22/13 9:00 AM, Andrew Grieve agri...@chromium.org wrote: Would be neat to have first-class support for Cordova by Yeoman, but looks like their default template works decently already: http://www.gauntface.co.uk/blog/2013/07/18/cordova-web-best-practices/
NPM stats on ripple
Just thought I would let everyone know we have had 7600 downloads of Ripple via npm this month. http://npm-stat.vorb.de/charts.html?package=ripple-emulator #OMFG
Re: blackberry10 build
I've entered the following issues into JIRA and we will be working to get them resolved over the next two weeks. Code: - [CB-4273] CLI pass through of command line args - [CB-4340] Query device to get PIN (no longer required in blackberry10.json) - [CB-4342] Auto-detect connected USB device - [CB-4344] Auto-detect started simulator - [CB-4345] Improve error output for common failure scenarios - [CB-4346] Change DEFAULT_BAR_NAME, remove from create script Docs: - [CB-4347] Restore improvements with screen shots / BBNDK path instructions - [CB-4349] Add debug token section - [CB-4351] Add project settings section (config.xml) On Mon, Jul 22, 2013 at 11:49 AM, Bryan Higgins br...@bryanhiggins.netwrote: Matt - thanks for the detailed feedback! I'll be entering in JIRAs for the tasks needed to tighten up the bb10 CLI experience today. On Mon, Jul 22, 2013 at 11:20 AM, Lucas Holmquist lholm...@redhat.comwrote: Nice write up, On Jul 22, 2013, at 11:14 AM, Matt Lantz mattla...@gmail.com wrote: Developing a BlackBerry10 App with Cordova 3.0.0 So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any information about the blackberry10.json file I had to modify. After performing: sudo npm update -g cordova It stated I now had 3.0.0 I attempted the cordova -d run blackberry10 again and this time I saw the %home%/.cordova/blackberry10.json statement. I went to the file immediately and added the keystorepass that I had used in my debug token. Called the run command and bam the app uploaded to the device. I was elated. I can honestly say I am stupefied as to how awesome the CLI is for Cordova everyone! I was amazed at how fast I could get something put together. However, documentation is still lacking, in particular with blackberry10.
Re: Plugin / Platform mismatch problems
Oh! Oh! Perhaps have multiple definitions based on CDV version. e.g.: engine min-cdv-version=2.8 max-cdv-version=2.8 default-git-refrefs/head/2.8.x/default-git-ref /engine engine min-cdv-version=2.9 default-git-refrefs/tags/stable/default-git-ref /engine Then, when someone plugman installs the git URL, it can fetch it and checkout a version that best matches your cordova version. Then, when you update your cordova version, it can go through your plugins and update them to different branches (unless you glue them to a ref as a part of your install URL) On Mon, Jul 22, 2013 at 2:44 PM, Braden Shepherdson bra...@chromium.orgwrote: The model I had always imagined was that we would do something similar to npm: Plugin authors decide what the default ref is for their plugin. Could be master, some other branch, a tag, a hash. That's what the discovery tool will return when a user asks to add that plugin without explicitly specifying a version. I think this is a good idea we should implement too. Braden On Fri, Jul 19, 2013 at 10:16 AM, Andrew Grieve agri...@chromium.org wrote: I think it's true that: 1. CLI downloads tagged versions of platforms 2. Plugman downloads plugins from master branch This means that we can't check any code into plugin master branches without them going live immediately. Best solution would be to change plugman to download from a tag by default, but a bit late for that now... Instead, I think we should change all development on plugins: - Commit only to dev branch. - When we want to push an update, we should file a release bug for the plugin, test on all platforms Case 1: The changes work with 3.0 cordova: then merge into master (only if it works of course) Case 2: The changes require a platform API that hasn't been release yet: Wait and release after the next cordova core release. Any other ideas?
cordova plugin add and variables
I didn't see it in the help. For example when trying to install the Facebook Connect plugin it complains about APP_ID variable not being set (plugman supports variables however). Does anyone know the syntax to set a variable, or does this feature need to be filed as an issue?
Re: Plugin / Platform mismatch problems
Like that On Mon, Jul 22, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Oh! Oh! Perhaps have multiple definitions based on CDV version. e.g.: engine min-cdv-version=2.8 max-cdv-version=2.8 default-git-refrefs/head/2.8.x/default-git-ref /engine engine min-cdv-version=2.9 default-git-refrefs/tags/stable/default-git-ref /engine Then, when someone plugman installs the git URL, it can fetch it and checkout a version that best matches your cordova version. Then, when you update your cordova version, it can go through your plugins and update them to different branches (unless you glue them to a ref as a part of your install URL) On Mon, Jul 22, 2013 at 2:44 PM, Braden Shepherdson bra...@chromium.orgwrote: The model I had always imagined was that we would do something similar to npm: Plugin authors decide what the default ref is for their plugin. Could be master, some other branch, a tag, a hash. That's what the discovery tool will return when a user asks to add that plugin without explicitly specifying a version. I think this is a good idea we should implement too. Braden On Fri, Jul 19, 2013 at 10:16 AM, Andrew Grieve agri...@chromium.org wrote: I think it's true that: 1. CLI downloads tagged versions of platforms 2. Plugman downloads plugins from master branch This means that we can't check any code into plugin master branches without them going live immediately. Best solution would be to change plugman to download from a tag by default, but a bit late for that now... Instead, I think we should change all development on plugins: - Commit only to dev branch. - When we want to push an update, we should file a release bug for the plugin, test on all platforms Case 1: The changes work with 3.0 cordova: then merge into master (only if it works of course) Case 2: The changes require a platform API that hasn't been release yet: Wait and release after the next cordova core release. Any other ideas?
Re: blackberry10 build
Wow, this is awesome thanks Bryan! On Mon, Jul 22, 2013 at 3:32 PM, Bryan Higgins br...@bryanhiggins.net wrote: I've entered the following issues into JIRA and we will be working to get them resolved over the next two weeks. Code: - [CB-4273] CLI pass through of command line args - [CB-4340] Query device to get PIN (no longer required in blackberry10.json) - [CB-4342] Auto-detect connected USB device - [CB-4344] Auto-detect started simulator - [CB-4345] Improve error output for common failure scenarios - [CB-4346] Change DEFAULT_BAR_NAME, remove from create script Docs: - [CB-4347] Restore improvements with screen shots / BBNDK path instructions - [CB-4349] Add debug token section - [CB-4351] Add project settings section (config.xml) On Mon, Jul 22, 2013 at 11:49 AM, Bryan Higgins br...@bryanhiggins.netwrote: Matt - thanks for the detailed feedback! I'll be entering in JIRAs for the tasks needed to tighten up the bb10 CLI experience today. On Mon, Jul 22, 2013 at 11:20 AM, Lucas Holmquist lholm...@redhat.comwrote: Nice write up, On Jul 22, 2013, at 11:14 AM, Matt Lantz mattla...@gmail.com wrote: Developing a BlackBerry10 App with Cordova 3.0.0 So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any information about the blackberry10.json file I had to modify. After performing: sudo npm update -g cordova It stated I now had 3.0.0 I attempted the cordova -d run blackberry10 again and this time I saw the %home%/.cordova/blackberry10.json statement. I went to the file immediately and added the keystorepass that I had used in my debug token. Called the run command and bam the app uploaded to the device. I was elated. I can honestly say I am stupefied as to how awesome the CLI is for Cordova everyone! I was
Re: cordova plugin add and variables
Yeah file an issue. Maybe this needs to be encapsulated as a larger feature, I'm thinking, any flags you use with the cli get pushed down to the underlying tools. This way people could do `cordova build --release`, for example. On 7/22/13 12:33 PM, Shazron shaz...@gmail.com wrote: I didn't see it in the help. For example when trying to install the Facebook Connect plugin it complains about APP_ID variable not being set (plugman supports variables however). Does anyone know the syntax to set a variable, or does this feature need to be filed as an issue?
Re: Blog post feedback
Ok. Somehow in the adding of these things I cannot get this to build. =( Could we use the awesome power of svn revision control to see wtf is going on? Also to confirm the changes are what we want? On Fri, Jul 19, 2013 at 6:52 PM, Andrew Grieve agri...@chromium.org wrote: --- layout: post author: name: Brian LeRoux url: https://twitter.com/brianleroux title: Apache Cordova 3.0 date: 2013-07-19 15:45:04 -5 categories: blog releases tags: news releases MAJOR --- # Cordova 3.0 Released Snapshot available on our [download page](https://www.apache.org/dist/cordova/) but before downloading please read on to find out whats new including for more ways to work with Cordova! ## Light Weight Core JUST RAN SPELL CHECKER ON THIS PARAGRAPH Cordova 3 introduces a new unified project structure and ships with a very limited API surface. Developers can now compose a version of Cordova with only the APIs they need. In the past, Cordova shipped with the entire kitchen sink of APIs that most applications only needed a small subset of. This lead to messy, and often not even necessary, upgrading for our community. With the release of Cordova 3 you start with a very light weight core and only add the API surface your application requires. Obviously, this means a performance improvement but the real win here is maintenance and upgrading. We'll continue to maintain core APIs which are the same device APIs you've come to know and love. ## New Command Line Tooling SPELLING GRAMMAR EXPANDED A BIT ORIG We're very excited to share two new command line tools: Cordova and Plugman. Both are implemented using `NodeJS` and thusly distributed via `npm`. The `cordova` command line tool has been a long time coming. It unifies all platforms into a single project structure which enables us to extend with futher tooling around plugins. This is where `plugman` fits in, allowing for automated discovery, installation, and removal of core and custom plugins. NEW We're very excited to share two new command line tools: Cordova and Plugman. Both are implemented using `NodeJS` and thusly distributed via `npm`. The `cordova` command line tool has been a long time coming. It unifies all platforms into a single project structure, making it easy to maintain a single codebase for multiple platforms. The `cordova` tool builds off of our other new tool: `plugman`, which provides automated discovery, installation, and removal of both core and custom plugins. RUN-ON SENTENCE. TWEAKED GRAMMAR ORIG We've been testing for months but keep in mind both tools are new, and bugs happen, so you if you find one or even just have an idea for a new feature please visit our [issue tracker](http://issues.cordova.io). NEW We've been testing for months but keep in mind both tools are new. Bugs happen, so you if you find one or even just have an idea for a new feature please visit our [issue tracker](http://issues.cordova.io ). ## Installing Downloading First, [ensure you have NodeJS installed](http://nodejs.org) and then simply run `npm install -g cordova`. From here its a typical comand line utility. Get started by building an iOS app! ``` $ cordova create MyFunkyApp $ cd MyFunkyApp $ cordova platform add ios $ cordova emulate ios ``` EXPANDED WHAT lazy loads MEANS: ORIG Cordova lazy loads so the first app you create might be a little slow. Same with platform adds. Just use `-d` flag to see progress. For example, `cordova -d platform add ios`. Maybe crack a beer and chill while it goes about its business first run. EXPANDED: Cordova has to download platform files the first time `create` is run, so the first app you create might be a little slow. Just use the `-d` flag to see progress. For example, `cordova -d platform add ios`. Maybe crack a beer and chill while it goes about its business first run. CHANGE lets - let's Now lets add Android, `cordova platform add android`. Yes: that easy! # Installing Plugins If you are working with a `cordova` generated project, then you can install plugins using the `cordova` tool as well: `plugman` is included with `cordova`, and is used by `cordova` internally to manage plugins. ``` $ cd MyFunkyApp $ cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-geolocation.git ``` You now have geolocation enabled your project! CLARIFIED WHAT A native project IS: ORIGINAL If you are working with a native project directly then `plugman` can be used standalone. Again, [ensure you have NodeJS installed](http://nodejs.org) and then simply run `npm install -g plugman`. MY CLARIFICATION If you are working with a platform project directly (one created through a Cordova platform's `bin/create` script instead of through the `cordova` tool), then `plugman` can be used standalone. Again, [ensure you have NodeJS installed](http://nodejs.org) and then simply run `npm install -g plugman`. ``` $ cd
Re: blackberry10 build
Apparently I am getting older faster than I thought, seeing y's where there are i's... Sent from my BlackBerry 10 smartphone. From: Ken Wallis Sent: Monday, July 22, 2013 1:05 PM To: dev@cordova.apache.org; dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Re: blackberry10 build Bryan is the man. Bryan H. that is. :P Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 22, 2013 12:41 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Re: blackberry10 build Wow, this is awesome thanks Bryan! On Mon, Jul 22, 2013 at 3:32 PM, Bryan Higgins br...@bryanhiggins.net wrote: I've entered the following issues into JIRA and we will be working to get them resolved over the next two weeks. Code: - [CB-4273] CLI pass through of command line args - [CB-4340] Query device to get PIN (no longer required in blackberry10.json) - [CB-4342] Auto-detect connected USB device - [CB-4344] Auto-detect started simulator - [CB-4345] Improve error output for common failure scenarios - [CB-4346] Change DEFAULT_BAR_NAME, remove from create script Docs: - [CB-4347] Restore improvements with screen shots / BBNDK path instructions - [CB-4349] Add debug token section - [CB-4351] Add project settings section (config.xml) On Mon, Jul 22, 2013 at 11:49 AM, Bryan Higgins br...@bryanhiggins.netwrote: Matt - thanks for the detailed feedback! I'll be entering in JIRAs for the tasks needed to tighten up the bb10 CLI experience today. On Mon, Jul 22, 2013 at 11:20 AM, Lucas Holmquist lholm...@redhat.comwrote: Nice write up, On Jul 22, 2013, at 11:14 AM, Matt Lantz mattla...@gmail.com wrote: Developing a BlackBerry10 App with Cordova 3.0.0 So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any
Re: blackberry10 build
Bryan is the man. Bryan H. that is. :P Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 22, 2013 12:41 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Re: blackberry10 build Wow, this is awesome thanks Bryan! On Mon, Jul 22, 2013 at 3:32 PM, Bryan Higgins br...@bryanhiggins.net wrote: I've entered the following issues into JIRA and we will be working to get them resolved over the next two weeks. Code: - [CB-4273] CLI pass through of command line args - [CB-4340] Query device to get PIN (no longer required in blackberry10.json) - [CB-4342] Auto-detect connected USB device - [CB-4344] Auto-detect started simulator - [CB-4345] Improve error output for common failure scenarios - [CB-4346] Change DEFAULT_BAR_NAME, remove from create script Docs: - [CB-4347] Restore improvements with screen shots / BBNDK path instructions - [CB-4349] Add debug token section - [CB-4351] Add project settings section (config.xml) On Mon, Jul 22, 2013 at 11:49 AM, Bryan Higgins br...@bryanhiggins.netwrote: Matt - thanks for the detailed feedback! I'll be entering in JIRAs for the tasks needed to tighten up the bb10 CLI experience today. On Mon, Jul 22, 2013 at 11:20 AM, Lucas Holmquist lholm...@redhat.comwrote: Nice write up, On Jul 22, 2013, at 11:14 AM, Matt Lantz mattla...@gmail.com wrote: Developing a BlackBerry10 App with Cordova 3.0.0 So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any information about the blackberry10.json file I had to modify. After performing: sudo npm update -g cordova It stated I now had 3.0.0 I attempted the cordova -d run blackberry10 again and this time I saw the %home%/.cordova/blackberry10.json statement. I went to the file immediately and added
Re: blackberry10 build
Apparently I am getting older faster than I thought, seeing y's where there are i's... Sent from my BlackBerry 10 smartphone. From: Ken Wallis Sent: Monday, July 22, 2013 1:05 PM To: dev@cordova.apache.org; dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Re: blackberry10 build Bryan is the man. Bryan H. that is. :P Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 22, 2013 12:41 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Re: blackberry10 build Wow, this is awesome thanks Bryan! On Mon, Jul 22, 2013 at 3:32 PM, Bryan Higgins br...@bryanhiggins.net wrote: I've entered the following issues into JIRA and we will be working to get them resolved over the next two weeks. Code: - [CB-4273] CLI pass through of command line args - [CB-4340] Query device to get PIN (no longer required in blackberry10.json) - [CB-4342] Auto-detect connected USB device - [CB-4344] Auto-detect started simulator - [CB-4345] Improve error output for common failure scenarios - [CB-4346] Change DEFAULT_BAR_NAME, remove from create script Docs: - [CB-4347] Restore improvements with screen shots / BBNDK path instructions - [CB-4349] Add debug token section - [CB-4351] Add project settings section (config.xml) On Mon, Jul 22, 2013 at 11:49 AM, Bryan Higgins br...@bryanhiggins.netwrote: Matt - thanks for the detailed feedback! I'll be entering in JIRAs for the tasks needed to tighten up the bb10 CLI experience today. On Mon, Jul 22, 2013 at 11:20 AM, Lucas Holmquist lholm...@redhat.comwrote: Nice write up, On Jul 22, 2013, at 11:14 AM, Matt Lantz mattla...@gmail.com wrote: Developing a BlackBerry10 App with Cordova 3.0.0 So, I started by downloading all the appropriate developer SDKs from BlackBerry. Though in retrospect I suppose I only needed the webworks one. After downloading and installing those. I followed the instructions ensuring that I had nodejs installed, and performed an installation of cordova. I performed the create app which went fine. I decided first to test run iOS given that I live in an OSX world. I added iOS, made a couple tweaks and ran it in the simulator flawlessly. Awesome experience. On to BlackBerry. I first attempted to add the blackberry platform. It responded with no platform. Since I knew a handful of stuff that Gord had been working on for BlackBerry builds I attempted, qnx, playbook, bb10, and then blackberry10 that seemed to be the golden key. After getting the platform set, I decided to experiment a bit. I ran the build, and understood how it pulled over the www folder data to the platforms. I had a couple issues with this though. It seemed that any custom writing I had done in the platform itself (blackberry10) was overwritten, including the config.xml which meant if I did an upgrade to the www directory even changed the file config.xml with new name etc it overwrites the custom stuff I set in the blackberry10 platform, with default values of 'WebWorks Application' etc. So I set some details such as name and author and then added some text to the index.html page of the www directory for the blackberry10 platform directory. Then I decided to test run it on a blackberry device. Since I had previous experience doing this, I got my debug tokens and got all that set by following the instructions on BlackBerry's website. This hit a snag in that it appeared I had used a short password. BlackBerry's website says that the csjpin must be between 6-10 alphanumeric characters. But it then turns out that WebWorks needs at least 8 alphanumeric characters. That was a pain, and lots of wasted time but I got through that. I didn't even bother installing the blackberry emulator since my previous experience with it sucked, I decided to try it on a real device. I had all the tokens in place and attempted to do a build with the instructions on the blackberry website. That failed with no signing password provided statement. I did some digging very confusingly since I had set all those details with my signing keys etc according to the blackberry website. I messaged the mailing list in the end, where Fil helped me out by suggesting I run the cordova run command. cordova -d run blackberry10 I had no idea there was such a command since I had been following the CLI instructions on Phonegap's website, and didn't see that anywhere. I attempted that and it failed same statement of the no signing password provided. I was all the more confused, read everything scoured stackoverflow, and finally posted again to the mailing list, and got a response from Jeffrey Heifetz talking about the %home%/.cordova/blackberry10.json. Just before I got Jeff's response I had decided to try upgrading my version of Cordova. According to: cordova -v I had cordova 3.0.0rc1 which was not giving me any
Questions regrading Contribution to the Project
Hi, I am Sharif Ahmed. I want to contribute to the project. I am interested in Android and Docs section. I have checked out the jira issues for these two sections, and found that there are few issues which are un-assigned. What is the process of assigning me any jira issue? I really want to contribute to the next point releases, 3.1 being the next one in September. How can I get involved in the next point releases? -- Regards, Sharif Ahmed Junior Software Engineer Therap Services, LLC +01715438290
