[GitHub] cordova-docs pull request: CB-7983 Indicate that volume up and vol...
GitHub user kant2002 opened a pull request: https://github.com/apache/cordova-docs/pull/255 CB-7983 Indicate that volume up and volume down button events supported on Android You can merge this pull request into a Git repository by running: $ git pull https://github.com/kant2002/cordova-docs CB-7983 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/255.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #255 commit 3f20dc34f33b3415d28271d704e02dc1cbdaf90a Author: Andrey Kurdyumov Date: 2015-01-07T09:49:35Z Indicate that volume up and volume down button events supported on Android --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-docs pull request: CB-5116: Fix links
GitHub user kant2002 opened a pull request: https://github.com/apache/cordova-docs/pull/256 CB-5116: Fix links Links to configuration description page fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kant2002/cordova-docs CB-5116 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/256.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #256 commit 3d7b1ad7686b7ab1afcea0128a1176b83ac3ef53 Author: Andrey Kurdyumov Date: 2015-01-07T10:10:13Z Fix links Links to configuration description page fixed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-docs pull request: CB-8259 Report error when generation fo...
GitHub user kant2002 opened a pull request: https://github.com/apache/cordova-docs/pull/257 CB-8259 Report error when generation for language failed You can merge this pull request into a Git repository by running: $ git pull https://github.com/kant2002/cordova-docs CB-8259 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/257.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #257 commit 9f5b766c10d3ee5941bc85adda4e351f8e971137 Author: Andrey Kurdyumov Date: 2015-01-07T10:41:36Z Report error during generation commit 3f6feb88d8459f83cc367edbfac83364eb40eb1f Author: Andrey Kurdyumov Date: 2015-01-07T10:41:56Z Report when file to merge is missing and continue processing --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-ios pull request: Fixed callbackFromNative
GitHub user mdudek opened a pull request: https://github.com/apache/cordova-ios/pull/123 Fixed callbackFromNative NO_RESULT status was resolved as failure. This bug is there from Oct 14, 2014. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mdudek/cordova-ios patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/123.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #123 commit b59679c4512044f3abaf54f4dc0b3ef17b3f44f9 Author: Michael Dudek Date: 2015-01-07T13:25:03Z Fixed callbackFromNative NO_RESULT status was resolved as failure. This bug is there from Oct 14, 2014. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Thought on improving translation and docs
One more speed improvement and https://github.com/apache/cordova-docs/pull/257 After that I only improve speed by movign joDoc-js inside our generation process, and start moving to Make-ish processing. Right now generation speed almos doubled, so I could concentrate on translation tools. If no other ideas popped up, I will start with my verification tools which I describe in the start of the topic. Definitely would like to have some feedback from other guys 2015-01-06 5:45 GMT+06:00 Andrey Kurdumov : > Also, just find out why non-English docs takes more time to generate. > See CB-8248 [1] for explanation. > > [1] https://issues.apache.org/jira/browse/CB-8248 > > 2015-01-06 4:53 GMT+06:00 Andrey Kurdumov : > >> Make is good idea. I definitely interested in faster generation time. >> The only reasonable tool for me from JS community is Jake. Gulp and Grunt >> would not provide any additional benefit for my implementation. >> I'm not even sure that Rake would be more maintainable solution then >> implementing logic in the application itself. >> >> With my last improvements for CB-8246. On my PC full generation time went >> down from 1584 sec to sec. See [1] >> >> Right now the fastest way to improve overall generation time is to chain >> post-processing steps in such way that >> a) cheerio would not parse HTML each step >> b) Intermediate results would not be written to the disk. >> That's hopefully would bring us additional ~20-30% improvements from >> current state. >> >> After that bottleneck would be in joDoc-js, hopefully that's also has >> enough places for improvements. >> >> Maybe after that changes I would be able to regenerate single file, to >> speedup subsequent generation even further. >> >> [1] https://github.com/apache/cordova-docs/pull/253 >> >> >> 2015-01-05 22:15 GMT+06:00 Josh Soref : >> >>> We should consider trying to have Make like rules so that we can avoid >>> rebuilding content if the underlying elements haven't changed… >>> >>> I'm also in favor of trying to share images across things. >>> >>> On 1/5/15, 10:17 AM, "Andrew Grieve" wrote: >>> >>> >Awesome stuff. I'll look at your PR today. >>> > >>> >Only reason I suspected images as a problem is that the docs directory >>> on >>> >the website (http://svn.apache.org/repos/asf/cordova/site/public/) is >>> >currently 773MB. Not great, but I guess not too terrible :P >>> > >>> >On Mon, Jan 5, 2015 at 7:24 AM, Andrey Kurdumov < >>> kant2...@googlemail.com> >>> >wrote: >>> > >>> >> I take measures and find that most of the time is spend inside of >>> >>'Adding >>> >> Title', 'Building TOC' and 'Merging files' step. >>> >> Each of that steps take 3-4 seconds. Other steps takes less then half >>> >>of a >>> >> second. >>> >> >>> >> Average generation time for language is 24 seconds. Upper part of >>> >> distribution is non-English translations. >>> >> Most English docs takes 13-15 seconds to generate. >>> >> Other European languages 20-24 seconds. >>> >> Japanese, Korean and Chinese 25-31 >>> >> >>> >> The pull request for the docs generator with timing swtich is >>> >> https://github.com/apache/cordova-docs/pull/252 >>> >> >>> >> @Andrew From what I see that static content ~9M is not give us too >>> much >>> >> problem if we not upload everything again after regeneration. >>> >> If uploading only new docs it will be ~100M overhead. I definitely >>> will >>> >>try >>> >> to reduce duplication, but right now it does not give me too much >>> >> pain so I will improve that specific place. Maybe I'm not aware about >>> >>other >>> >> side-effects and processes where this duplication is increased? >>> >> >> >
Re: Thought on improving translation and docs
I just ran genjs to generate the docs for all versions and languages, and it is roughly the same time as it took using the old Ruby system. I certainly don't want to dampen your enthusiasm, but I don't think the speed is enough of a pain to require a lot more investment of your effort. Generating all versions/languages is not a common task. Generating en-edge is common, and fast enough for me. Using the new JS system is way better than the Ruby system. That was a pain point (at least for me) that you have made much better. Many thanks for that! > On Jan 7, 2015, at 8:34 AM, Andrey Kurdumov wrote: > > One more speed improvement and > https://github.com/apache/cordova-docs/pull/257 > > After that I only improve speed by movign joDoc-js inside our generation > process, and start moving to Make-ish processing. > > Right now generation speed almos doubled, so I could concentrate on > translation tools. > If no other ideas popped up, I will start with my verification tools which > I describe in the start of the topic. > Definitely would like to have some feedback from other guys - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-vibration pull request: index.md(jp)
GitHub user HirofumiTamori opened a pull request: https://github.com/apache/cordova-plugin-vibration/pull/32 index.md(jp) Correct Japanese Translation You can merge this pull request into a Git repository by running: $ git pull https://github.com/HirofumiTamori/cordova-plugin-vibration master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-vibration/pull/32.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #32 commit 2348d71cad62432dfd14910d7c3b70165440bcf7 Author: Hirofumi Tamori Date: 2015-01-07T15:07:21Z index.md(jp) Correct Japanese Translation --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-cli pull request: CB-7739 document installing specific ver...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-cli/pull/195 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-cli pull request: CB-7950 CLI make CordovaCliCreate.protot...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-cli/pull/201 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-cli pull request: CB-7950 CLI make CordovaCliCreate.protot...
GitHub user jsoref opened a pull request: https://github.com/apache/cordova-cli/pull/201 CB-7950 CLI make CordovaCliCreate.prototype.run vaguely correct You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-cli cb_7950 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-cli/pull/201.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #201 commit 106d8801a70a9b97cd606e27f80c6c7988f368cc Author: Josh Soref Date: 2015-01-07T15:15:25Z CB-7950 CLI make CordovaCliCreate.prototype.run vaguely correct --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-cli pull request: CB-5316 Spell Cordova as a brand unless ...
GitHub user jsoref opened a pull request: https://github.com/apache/cordova-cli/pull/202 CB-5316 Spell Cordova as a brand unless it's a command or script * Change `cordova command` to `cordova-cli command` to match the rest of the file * Change `cordova library` to `Cordova library` to match the actual output * Change `cordova project` to `Cordova project` You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-cli cb_5316 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-cli/pull/202.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #202 commit 143176e716696eca60ecfd6ef2b7a5158d530b9d Author: Josh Soref Date: 2013-12-12T22:32:04Z CB-5316 Spell Cordova as a brand unless it's a command or script --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-cli pull request: CB-5316 Spell Cordova as a brand unless ...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-cli/pull/202 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: How to test the cordova-android 4.0 by mobile spec
Hmm, I hadn't tried the key event manual tests with 4.0.x in MS. I do think that would break based on the version being MSTEST, since there is now code to make an exec() to CoreAndroid based on the platformVersion. Maybe let's just set the plugin bridge name back to "App" on 4.0.x so that the js exec() will always work (but still leave the class name as "CoreAndroid") On Tue, Jan 6, 2015 at 10:06 PM, Fu, Junwei wrote: > Yes, I set up mobilespec following > https://github.com/apache/cordova-mobile-spec . > > -Original Message- > From: Joe Bowser [mailto:bows...@gmail.com] > Sent: Wednesday, January 07, 2015 10:54 AM > To: dev@cordova.apache.org > Subject: Re: How to test the cordova-android 4.0 by mobile spec > > So, it's not using the cordova that's installed locally via npm? I'll have > to check that again. > > On Tue Jan 06 2015 at 6:33:14 PM Andrew Grieve > wrote: > > > I've just been checkout out 4.0.x branch of cordova-android, then > > running the script. I think the script requires that > > cordova-mobile-spec, cordova-android, and cordova-js all be sibling > directories. > > > > On Tue, Jan 6, 2015 at 7:58 PM, Joe Bowser wrote: > > > > > I haven't been able to get mobile-spec working reliably since it was > > > refactored and we were forced to use the createmobilespec.sh script > (i.e. > > > Tests don't run on Android 2.3) How did you manage to get it to work > > > with 4.0.x? > > > > > > On Tue Jan 06 2015 at 6:24:51 AM Andrew Grieve > > > > > > wrote: > > > > > > > I think you had it right. use cordova-mobile-spec@master and > > > > cordova-android@4.0.x. Failing tests are likely issues (in android > > > > or > > in > > > > the tests). Just fixed last night that the JS on 4.0.x was not > > > > properly registering with the CoreAndroid plugin due to it being > > > > renamed, so > > that > > > > could be the cause of the key event test failing. > > > > > > > > On Tue, Jan 6, 2015 at 3:47 AM, Fu, Junwei > > wrote: > > > > > > > > > Hi, > > > > > > > > > > Because There are no cordova-mobile-spec 4.0 branch, so I used > > > > > cordova-mobile-spec master branch to test cordova-android 4.0, > > > > > but > > the > > > > key > > > > > event test cases failed. And the splash screen test cases failed > > > > > with cordova-mobile-spec 3.6 branch, I don't know how to test > > > > > the cordova-android 4.0 by mobile spec. > > > > > > > > > > Thanks, > > > > > Junwei. > > > > > > > > > > > > > > >
[GitHub] cordova-registry-web pull request: CB-8175 Expose Fire OS
Github user asfgit closed the pull request at: https://github.com/apache/cordova-registry-web/pull/8 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-media-capture pull request: CB-7977 Mention devicer...
GitHub user jsoref reopened a pull request: https://github.com/apache/cordova-plugin-media-capture/pull/29 CB-7977 Mention deviceready in plugin docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-plugin-media-capture deviceready Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-media-capture/pull/29.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #29 commit 6a7cd162f118b38f6ae211ca7b687e6d452f43ca Author: Josh Soref Date: 2014-11-06T22:13:05Z CB-7977 Mention deviceready in plugin docs --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-blackberry pull request: CB-7807 Add BlackBerry10 platform...
GitHub user jsoref opened a pull request: https://github.com/apache/cordova-blackberry/pull/179 CB-7807 Add BlackBerry10 platform to a project on any workstation OS * Split init reqs checks out of init * Consistently use CORDOVA_DIR (instead of occasionally using BIN_DIR) r? @bryanhiggins You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-blackberry cb_7807 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-blackberry/pull/179.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #179 commit d9c4c5345a15fe16dda8878e782ec9c009b2998c Author: Josh Soref Date: 2014-11-13T18:50:36Z CB-7807 Add BlackBerry10 platform to a project on any workstation OS * Split init reqs checks out of init * Consistently use CORDOVA_DIR (instead of occasionally using BIN_DIR) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-media-capture pull request: CB-7977 Mention devicer...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-media-capture/pull/29 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-docs pull request: CB-8261 Brand: BlackBerry
GitHub user jsoref opened a pull request: https://github.com/apache/cordova-docs/pull/258 CB-8261 Brand: BlackBerry You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-docs blackberry Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/258.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #258 commit bd265628de93a0cd2070e984cc0bb32448445494 Author: Josh Soref Date: 2015-01-07T16:31:33Z CB-8261 Brand: BlackBerry --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-contacts pull request: Windows phone contact picker...
Github user Hurtyto commented on the pull request: https://github.com/apache/cordova-plugin-contacts/pull/51#issuecomment-69048639 Haven't signed yet. When I get some time will do, but feel free to use my contribution if needed --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-docs pull request: CB-8261 Brand: BlackBerry
Github user asfgit closed the pull request at: https://github.com/apache/cordova-docs/pull/258 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-8226 'cordova platform add' : Look up...
Github user omefire commented on the pull request: https://github.com/apache/cordova-lib/pull/140#issuecomment-69056950 travis-ci failure not related to my changes. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: How to test the cordova-android 4.0 by mobile spec
Went to try this out and decided it's a bad idea. Much better is to just fix createmobilespec.js to use the proper platform versions when generating the .js. I've done this and checked it in. On Wed, Jan 7, 2015 at 10:45 AM, Andrew Grieve wrote: > Hmm, I hadn't tried the key event manual tests with 4.0.x in MS. I do > think that would break based on the version being MSTEST, since there is > now code to make an exec() to CoreAndroid based on the platformVersion. > > Maybe let's just set the plugin bridge name back to "App" on 4.0.x so that > the js exec() will always work (but still leave the class name as > "CoreAndroid") > > On Tue, Jan 6, 2015 at 10:06 PM, Fu, Junwei wrote: > >> Yes, I set up mobilespec following >> https://github.com/apache/cordova-mobile-spec . >> >> -Original Message- >> From: Joe Bowser [mailto:bows...@gmail.com] >> Sent: Wednesday, January 07, 2015 10:54 AM >> To: dev@cordova.apache.org >> Subject: Re: How to test the cordova-android 4.0 by mobile spec >> >> So, it's not using the cordova that's installed locally via npm? I'll >> have to check that again. >> >> On Tue Jan 06 2015 at 6:33:14 PM Andrew Grieve >> wrote: >> >> > I've just been checkout out 4.0.x branch of cordova-android, then >> > running the script. I think the script requires that >> > cordova-mobile-spec, cordova-android, and cordova-js all be sibling >> directories. >> > >> > On Tue, Jan 6, 2015 at 7:58 PM, Joe Bowser wrote: >> > >> > > I haven't been able to get mobile-spec working reliably since it was >> > > refactored and we were forced to use the createmobilespec.sh script >> (i.e. >> > > Tests don't run on Android 2.3) How did you manage to get it to work >> > > with 4.0.x? >> > > >> > > On Tue Jan 06 2015 at 6:24:51 AM Andrew Grieve >> > > >> > > wrote: >> > > >> > > > I think you had it right. use cordova-mobile-spec@master and >> > > > cordova-android@4.0.x. Failing tests are likely issues (in android >> > > > or >> > in >> > > > the tests). Just fixed last night that the JS on 4.0.x was not >> > > > properly registering with the CoreAndroid plugin due to it being >> > > > renamed, so >> > that >> > > > could be the cause of the key event test failing. >> > > > >> > > > On Tue, Jan 6, 2015 at 3:47 AM, Fu, Junwei >> > wrote: >> > > > >> > > > > Hi, >> > > > > >> > > > > Because There are no cordova-mobile-spec 4.0 branch, so I used >> > > > > cordova-mobile-spec master branch to test cordova-android 4.0, >> > > > > but >> > the >> > > > key >> > > > > event test cases failed. And the splash screen test cases failed >> > > > > with cordova-mobile-spec 3.6 branch, I don't know how to test >> > > > > the cordova-android 4.0 by mobile spec. >> > > > > >> > > > > Thanks, >> > > > > Junwei. >> > > > > >> > > > >> > > >> > >> > >
[GitHub] cordova-plugin-contacts pull request: Windows phone contact picker...
Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-plugin-contacts/pull/51#issuecomment-69064486 Yeah, we can't accept the code without a signed CLA on file. It'll wait. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
picking up task in JIRA
Yesterday I created an issue in JIRA (https://issues.apache.org/jira/browse/CB-8253) intending to pick it up myself and start working on it. But I find that I can't assign it to myself. Do I need someone else to assign it to me or am I missing something obvious? Thanks, Alan
Re: picking up task in JIRA
I assigned it to you. New users cannot have issues assigned to them, you should be good now. Cheers, Jesse @purplecabbage risingj.com On Wed, Jan 7, 2015 at 10:55 AM, Kinzie, Alan wrote: > Yesterday I created an issue in JIRA ( > https://issues.apache.org/jira/browse/CB-8253) intending to pick it up > myself and start working on it. But I find that I can't assign it to > myself. Do I need someone else to assign it to me or am I missing > something obvious? > > Thanks, > Alan >
Reviewboard
Anyone still interested in using ReviewBoard? I feel like we gave it a decent shot, but github pull requests are working better. If no one objects, I'm going to delete the .reviewboardrc files from the repos and update https://github.com/apache/cordova-coho/blob/master/docs/code-reviews.md
Re: Reviewboard
What's reviewboard? j/k, yeah kill it! On Wed Jan 07 2015 at 1:13:55 PM Andrew Grieve wrote: > Anyone still interested in using ReviewBoard? I feel like we gave it a > decent shot, but github pull requests are working better. > > If no one objects, I'm going to delete the .reviewboardrc files from the > repos and update > https://github.com/apache/cordova-coho/blob/master/docs/code-reviews.md >
Re: Reviewboard
Yeah, kill it. gh-pulls are much easier to review I think. @purplecabbage risingj.com On Wed, Jan 7, 2015 at 1:14 PM, Joe Bowser wrote: > What's reviewboard? > > j/k, yeah kill it! > On Wed Jan 07 2015 at 1:13:55 PM Andrew Grieve > wrote: > > > Anyone still interested in using ReviewBoard? I feel like we gave it a > > decent shot, but github pull requests are working better. > > > > If no one objects, I'm going to delete the .reviewboardrc files from the > > repos and update > > https://github.com/apache/cordova-coho/blob/master/docs/code-reviews.md > > >
Re: [Vote] Tools Release Jan 6, 2015
+1 * Confirmed sigs & hashes with `coho verify-archive` * Verified sha1s match tags with `coho verify-tags` * Re-created archives to ensure contents match release candidate (did so for cordova-js and cordova-cli) On Tue, Jan 6, 2015 at 8:46 PM, Steven Gill wrote: > Please review and vote on this Tools Release. > > Release issue: https://issues.apache.org/jira/browse/CB-8256 > > All tools have been published to > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8256/ > > The packages were published from their corresponding git tags: > cordova-js: 3.7.3 (8d6b736a36) > cordova-lib: 4.2.0 (52f7db9dfc) > cordova-plugman: 0.22.17 (016ef62e7e) > cordova-cli: 4.2.0 (afa8016230) > > You can test the rc by going npm install -g cordova@rc. > > I'd especially love if the windows and blackberry guys can test it! > > > Upon a successful vote I will upload the archives to dist/, publish > them to NPM, and post the corresponding blog post. > > Voting guidelines: > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md > > Voting will go on for a minimum of 48 hours. > > I vote +1: > * Ran coho audit-license-headers over the relevant repos > * Ran coho check-license to ensure all dependencies and > subdependencies have Apache-compatible licenses > * ran unit tests + mobile spec on android + ios >
[GitHub] cordova-lib pull request: CB-8226 'cordova platform add' : Look up...
Github user omefire commented on the pull request: https://github.com/apache/cordova-lib/pull/140#issuecomment-69095149 @agrieve, have you had a chance to take another look at this ? --Thanks. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Cordova-Android 3.7.0 and 4.0.x releases.
Hey Do we have a 3.7.0 branch ready yet? I want us to get that ready and merge the 4.0.x stuff into the master branch once we get 3.7.0 out. That way we can finally go back to having a regular dev process. Are people opposed to us merging the 4.0.x branch into master once we release 3.7.x and just treating 4.0.x like a full release branch? Joe
Deprecation Wars: ICS vs Gingerbread
Hey So, 2015 is here, and we have the new Android Pie Chart: http://developer.android.com/about/dashboards/index.html#2015 Due to two percentage points on ICS and three on Gingerbread, we're stuck supporting these platforms for the near future, but it looks like we're in the bad spot of them reaching the magic 5% at the same time. Since I don't like the idea of automatically dropping 10% of devices, I'm wondering what we should deprecate first. Also, can we get better numbers for what's out there? Right now we still have the only single point of reference, which is the Google Play store. This doesn't cover China, or any other emerging markets. That said, things like Android One, and vendors like Xiaomi are making KitKat and Lolipop the standard. I know that I'm once again touching off a flame war between developers who know that these platforms don't get the tests they need to be actually considered supported, and various business interests who for some unknown reason need this support, but we should have this discussion again. Thoughts? Joe
[GitHub] cordova-ios pull request: Fixed callbackFromNative
Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-ios/pull/123#issuecomment-69112909 You cannot fix this here. cordova.js is the output of https://github.com/apache/cordova-js --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [Vote] Tools Release Jan 6, 2015
+1 Tests: - npm install -g cordova@rc - Built and ran the default HelloWorld app on Android - ran "coho verify-tags" On Wed, Jan 7, 2015 at 4:27 PM, Andrew Grieve wrote: > +1 > > * Confirmed sigs & hashes with `coho verify-archive` > * Verified sha1s match tags with `coho verify-tags` > * Re-created archives to ensure contents match release candidate (did so > for cordova-js and cordova-cli) > > On Tue, Jan 6, 2015 at 8:46 PM, Steven Gill > wrote: > > > Please review and vote on this Tools Release. > > > > Release issue: https://issues.apache.org/jira/browse/CB-8256 > > > > All tools have been published to > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8256/ > > > > The packages were published from their corresponding git tags: > > cordova-js: 3.7.3 (8d6b736a36) > > cordova-lib: 4.2.0 (52f7db9dfc) > > cordova-plugman: 0.22.17 (016ef62e7e) > > cordova-cli: 4.2.0 (afa8016230) > > > > You can test the rc by going npm install -g cordova@rc. > > > > I'd especially love if the windows and blackberry guys can test it! > > > > > > Upon a successful vote I will upload the archives to dist/, publish > > them to NPM, and post the corresponding blog post. > > > > Voting guidelines: > > > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md > > > > Voting will go on for a minimum of 48 hours. > > > > I vote +1: > > * Ran coho audit-license-headers over the relevant repos > > * Ran coho check-license to ensure all dependencies and > > subdependencies have Apache-compatible licenses > > * ran unit tests + mobile spec on android + ios > > >
[GitHub] cordova-plugin-statusbar pull request: update docs for StatusBarBa...
GitHub user cjpearson opened a pull request: https://github.com/apache/cordova-plugin-statusbar/pull/20 update docs for StatusBarBackgroundColor The default value is no longer black. (CB-7486) You can merge this pull request into a Git repository by running: $ git pull https://github.com/cjpearson/cordova-plugin-statusbar master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-statusbar/pull/20.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #20 commit 607e5d66add7dea9f791defe97cf62c711741d5e Author: Connor Pearson Date: 2015-01-08T00:55:34Z update docs for StatusBarBackgroundColor The default value is no longer black. (CB-7486) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Deprecation Wars: ICS vs Gingerbread
It seems to me that if we are only going to drop *one*, that it should be Gingerbread first, since it is a lower SDK version. How can an app support GB and *not* ICS? Having said that, I am also interested in the discussion of better numbers on usage than just the Play Store (even if my gut reaction is always “BURN 2.3 WITH FIRE”). -- tommy-carlos williams On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) wrote: Hey So, 2015 is here, and we have the new Android Pie Chart: http://developer.android.com/about/dashboards/index.html#2015 Due to two percentage points on ICS and three on Gingerbread, we're stuck supporting these platforms for the near future, but it looks like we're in the bad spot of them reaching the magic 5% at the same time. Since I don't like the idea of automatically dropping 10% of devices, I'm wondering what we should deprecate first. Also, can we get better numbers for what's out there? Right now we still have the only single point of reference, which is the Google Play store. This doesn't cover China, or any other emerging markets. That said, things like Android One, and vendors like Xiaomi are making KitKat and Lolipop the standard. I know that I'm once again touching off a flame war between developers who know that these platforms don't get the tests they need to be actually considered supported, and various business interests who for some unknown reason need this support, but we should have this discussion again. Thoughts? Joe
Re: Deprecation Wars: ICS vs Gingerbread
I'm just mentioning it because my only Android 4.0.3 devices are an ASUS Transformer 2 tablet and a Motorola RAZR phone that did weird things to my computer when I tried installing the extra software to upgrade it. However, if we did deprecate 2.3, I can just flash 4.0.3 on the Nexus S and use that. On Wed Jan 07 2015 at 5:07:27 PM tommy-carlos williams wrote: > It seems to me that if we are only going to drop *one*, that it should be > Gingerbread first, since it is a lower SDK version. > > How can an app support GB and *not* ICS? > > Having said that, I am also interested in the discussion of better numbers > on usage than just the Play Store (even if my gut reaction is always “BURN > 2.3 WITH FIRE”). > > -- > tommy-carlos williams > > On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) wrote: > > Hey > > So, 2015 is here, and we have the new Android Pie Chart: > > http://developer.android.com/about/dashboards/index.html#2015 > > Due to two percentage points on ICS and three on Gingerbread, we're stuck > supporting these platforms for the near future, but it looks like we're in > the bad spot of them reaching the magic 5% at the same time. Since I don't > like the idea of automatically dropping 10% of devices, I'm wondering what > we should deprecate first. > > Also, can we get better numbers for what's out there? Right now we still > have the only single point of reference, which is the Google Play store. > This doesn't cover China, or any other emerging markets. That said, things > like Android One, and vendors like Xiaomi are making KitKat and Lolipop the > standard. I know that I'm once again touching off a flame war between > developers who know that these platforms don't get the tests they need to > be actually considered supported, and various business interests who for > some unknown reason need this support, but we should have this discussion > again. > > Thoughts? > > Joe >
Re: Deprecation Wars: ICS vs Gingerbread
Also, who actually tests on Gingerbread? Please comment on this thread. On Wed Jan 07 2015 at 5:09:49 PM Joe Bowser wrote: > I'm just mentioning it because my only Android 4.0.3 devices are an ASUS > Transformer 2 tablet and a Motorola RAZR phone that did weird things to my > computer when I tried installing the extra software to upgrade it. > > However, if we did deprecate 2.3, I can just flash 4.0.3 on the Nexus S > and use that. > > > On Wed Jan 07 2015 at 5:07:27 PM tommy-carlos williams > wrote: > >> It seems to me that if we are only going to drop *one*, that it should be >> Gingerbread first, since it is a lower SDK version. >> >> How can an app support GB and *not* ICS? >> >> Having said that, I am also interested in the discussion of better >> numbers on usage than just the Play Store (even if my gut reaction is >> always “BURN 2.3 WITH FIRE”). >> >> -- >> tommy-carlos williams >> >> On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) wrote: >> >> Hey >> >> So, 2015 is here, and we have the new Android Pie Chart: >> >> http://developer.android.com/about/dashboards/index.html#2015 >> >> Due to two percentage points on ICS and three on Gingerbread, we're stuck >> supporting these platforms for the near future, but it looks like we're in >> the bad spot of them reaching the magic 5% at the same time. Since I don't >> like the idea of automatically dropping 10% of devices, I'm wondering what >> we should deprecate first. >> >> Also, can we get better numbers for what's out there? Right now we still >> have the only single point of reference, which is the Google Play store. >> This doesn't cover China, or any other emerging markets. That said, things >> like Android One, and vendors like Xiaomi are making KitKat and Lolipop >> the >> standard. I know that I'm once again touching off a flame war between >> developers who know that these platforms don't get the tests they need to >> be actually considered supported, and various business interests who for >> some unknown reason need this support, but we should have this discussion >> again. >> >> Thoughts? >> >> Joe >> >
RE: How to test the cordova-android 4.0 by mobile spec
Thank you very much, it's fine after update your commit. Is the mobilespec being tested for Cordova 4.0, Because there are still some other issue such as the splash screen can't show in splashscreen manual tests. -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Thursday, January 08, 2015 2:00 AM To: Andrew Grieve Cc: dev Subject: Re: How to test the cordova-android 4.0 by mobile spec Went to try this out and decided it's a bad idea. Much better is to just fix createmobilespec.js to use the proper platform versions when generating the .js. I've done this and checked it in. On Wed, Jan 7, 2015 at 10:45 AM, Andrew Grieve wrote: > Hmm, I hadn't tried the key event manual tests with 4.0.x in MS. I do > think that would break based on the version being MSTEST, since there > is now code to make an exec() to CoreAndroid based on the platformVersion. > > Maybe let's just set the plugin bridge name back to "App" on 4.0.x so > that the js exec() will always work (but still leave the class name as > "CoreAndroid") > > On Tue, Jan 6, 2015 at 10:06 PM, Fu, Junwei wrote: > >> Yes, I set up mobilespec following >> https://github.com/apache/cordova-mobile-spec . >> >> -Original Message- >> From: Joe Bowser [mailto:bows...@gmail.com] >> Sent: Wednesday, January 07, 2015 10:54 AM >> To: dev@cordova.apache.org >> Subject: Re: How to test the cordova-android 4.0 by mobile spec >> >> So, it's not using the cordova that's installed locally via npm? I'll >> have to check that again. >> >> On Tue Jan 06 2015 at 6:33:14 PM Andrew Grieve >> wrote: >> >> > I've just been checkout out 4.0.x branch of cordova-android, then >> > running the script. I think the script requires that >> > cordova-mobile-spec, cordova-android, and cordova-js all be sibling >> directories. >> > >> > On Tue, Jan 6, 2015 at 7:58 PM, Joe Bowser wrote: >> > >> > > I haven't been able to get mobile-spec working reliably since it >> > > was refactored and we were forced to use the createmobilespec.sh >> > > script >> (i.e. >> > > Tests don't run on Android 2.3) How did you manage to get it to >> > > work with 4.0.x? >> > > >> > > On Tue Jan 06 2015 at 6:24:51 AM Andrew Grieve >> > > >> > > wrote: >> > > >> > > > I think you had it right. use cordova-mobile-spec@master and >> > > > cordova-android@4.0.x. Failing tests are likely issues (in >> > > > android or >> > in >> > > > the tests). Just fixed last night that the JS on 4.0.x was not >> > > > properly registering with the CoreAndroid plugin due to it >> > > > being renamed, so >> > that >> > > > could be the cause of the key event test failing. >> > > > >> > > > On Tue, Jan 6, 2015 at 3:47 AM, Fu, Junwei >> > > > >> > wrote: >> > > > >> > > > > Hi, >> > > > > >> > > > > Because There are no cordova-mobile-spec 4.0 branch, so I >> > > > > used cordova-mobile-spec master branch to test >> > > > > cordova-android 4.0, but >> > the >> > > > key >> > > > > event test cases failed. And the splash screen test cases >> > > > > failed with cordova-mobile-spec 3.6 branch, I don't know how >> > > > > to test the cordova-android 4.0 by mobile spec. >> > > > > >> > > > > Thanks, >> > > > > Junwei. >> > > > > >> > > > >> > > >> > >> > >
Re: Deprecation Wars: ICS vs Gingerbread
I say we go 4.x all in and drop everything below. Time to draw a line. On Wed, Jan 7, 2015, 6:24 PM Joe Bowser wrote: > Also, who actually tests on Gingerbread? Please comment on this thread. > > On Wed Jan 07 2015 at 5:09:49 PM Joe Bowser wrote: > > > I'm just mentioning it because my only Android 4.0.3 devices are an ASUS > > Transformer 2 tablet and a Motorola RAZR phone that did weird things to > my > > computer when I tried installing the extra software to upgrade it. > > > > However, if we did deprecate 2.3, I can just flash 4.0.3 on the Nexus S > > and use that. > > > > > > On Wed Jan 07 2015 at 5:07:27 PM tommy-carlos williams < > to...@devgeeks.org> > > wrote: > > > >> It seems to me that if we are only going to drop *one*, that it should > be > >> Gingerbread first, since it is a lower SDK version. > >> > >> How can an app support GB and *not* ICS? > >> > >> Having said that, I am also interested in the discussion of better > >> numbers on usage than just the Play Store (even if my gut reaction is > >> always “BURN 2.3 WITH FIRE”). > >> > >> -- > >> tommy-carlos williams > >> > >> On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) wrote: > >> > >> Hey > >> > >> So, 2015 is here, and we have the new Android Pie Chart: > >> > >> http://developer.android.com/about/dashboards/index.html#2015 > >> > >> Due to two percentage points on ICS and three on Gingerbread, we're > stuck > >> supporting these platforms for the near future, but it looks like we're > in > >> the bad spot of them reaching the magic 5% at the same time. Since I > don't > >> like the idea of automatically dropping 10% of devices, I'm wondering > what > >> we should deprecate first. > >> > >> Also, can we get better numbers for what's out there? Right now we still > >> have the only single point of reference, which is the Google Play store. > >> This doesn't cover China, or any other emerging markets. That said, > things > >> like Android One, and vendors like Xiaomi are making KitKat and Lolipop > >> the > >> standard. I know that I'm once again touching off a flame war between > >> developers who know that these platforms don't get the tests they need > to > >> be actually considered supported, and various business interests who for > >> some unknown reason need this support, but we should have this > discussion > >> again. > >> > >> Thoughts? > >> > >> Joe > >> > > >
Re: Deprecation Wars: ICS vs Gingerbread
! On Wed, Jan 7, 2015, 6:49 PM tommy-carlos williams wrote: > > -- > tommy-carlos williams > > On 8 January 2015 at 12:37:59, Brian LeRoux (b...@brian.io) wrote: > > I say we go 4.x all in and drop everything below. Time to draw a line. > > On Wed, Jan 7, 2015, 6:24 PM Joe Bowser wrote: > > > Also, who actually tests on Gingerbread? Please comment on this thread. > > > > On Wed Jan 07 2015 at 5:09:49 PM Joe Bowser wrote: > > > > > I'm just mentioning it because my only Android 4.0.3 devices are an > ASUS > > > Transformer 2 tablet and a Motorola RAZR phone that did weird things > to > > my > > > computer when I tried installing the extra software to upgrade it. > > > > > > However, if we did deprecate 2.3, I can just flash 4.0.3 on the Nexus > S > > > and use that. > > > > > > > > > On Wed Jan 07 2015 at 5:07:27 PM tommy-carlos williams < > > to...@devgeeks.org> > > > wrote: > > > > > >> It seems to me that if we are only going to drop *one*, that it > should > > be > > >> Gingerbread first, since it is a lower SDK version. > > >> > > >> How can an app support GB and *not* ICS? > > >> > > >> Having said that, I am also interested in the discussion of better > > >> numbers on usage than just the Play Store (even if my gut reaction is > > >> always “BURN 2.3 WITH FIRE”). > > >> > > >> -- > > >> tommy-carlos williams > > >> > > >> On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) wrote: > > >> > > >> Hey > > >> > > >> So, 2015 is here, and we have the new Android Pie Chart: > > >> > > >> http://developer.android.com/about/dashboards/index.html#2015 > > >> > > >> Due to two percentage points on ICS and three on Gingerbread, we're > > stuck > > >> supporting these platforms for the near future, but it looks like > we're > > in > > >> the bad spot of them reaching the magic 5% at the same time. Since I > > don't > > >> like the idea of automatically dropping 10% of devices, I'm wondering > > what > > >> we should deprecate first. > > >> > > >> Also, can we get better numbers for what's out there? Right now we > still > > >> have the only single point of reference, which is the Google Play > store. > > >> This doesn't cover China, or any other emerging markets. That said, > > things > > >> like Android One, and vendors like Xiaomi are making KitKat and > Lolipop > > >> the > > >> standard. I know that I'm once again touching off a flame war between > > >> developers who know that these platforms don't get the tests they > need > > to > > >> be actually considered supported, and various business interests who > for > > >> some unknown reason need this support, but we should have this > > discussion > > >> again. > > >> > > >> Thoughts? > > >> > > >> Joe > > >> > > > > > > >
Re: Deprecation Wars: ICS vs Gingerbread
Those stickers are old! I don't go to Android conferences, sine Android devs hate us these days. On Wed Jan 07 2015 at 5:53:04 PM Brian LeRoux wrote: > ! > > On Wed, Jan 7, 2015, 6:49 PM tommy-carlos williams > wrote: > >> >> -- >> tommy-carlos williams >> >> On 8 January 2015 at 12:37:59, Brian LeRoux (b...@brian.io) wrote: >> >> I say we go 4.x all in and drop everything below. Time to draw a line. >> >> On Wed, Jan 7, 2015, 6:24 PM Joe Bowser wrote: >> >> > Also, who actually tests on Gingerbread? Please comment on this thread. >> > >> > On Wed Jan 07 2015 at 5:09:49 PM Joe Bowser wrote: >> > >> > > I'm just mentioning it because my only Android 4.0.3 devices are an >> ASUS >> > > Transformer 2 tablet and a Motorola RAZR phone that did weird things >> to >> > my >> > > computer when I tried installing the extra software to upgrade it. >> > > >> > > However, if we did deprecate 2.3, I can just flash 4.0.3 on the Nexus >> S >> > > and use that. >> > > >> > > >> > > On Wed Jan 07 2015 at 5:07:27 PM tommy-carlos williams < >> > to...@devgeeks.org> >> > > wrote: >> > > >> > >> It seems to me that if we are only going to drop *one*, that it >> should >> > be >> > >> Gingerbread first, since it is a lower SDK version. >> > >> >> > >> How can an app support GB and *not* ICS? >> > >> >> > >> Having said that, I am also interested in the discussion of better >> > >> numbers on usage than just the Play Store (even if my gut reaction >> is >> > >> always “BURN 2.3 WITH FIRE”). >> > >> >> > >> -- >> > >> tommy-carlos williams >> > >> >> > >> On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) >> wrote: >> > >> >> > >> Hey >> > >> >> > >> So, 2015 is here, and we have the new Android Pie Chart: >> > >> >> > >> http://developer.android.com/about/dashboards/index.html#2015 >> > >> >> > >> Due to two percentage points on ICS and three on Gingerbread, we're >> > stuck >> > >> supporting these platforms for the near future, but it looks like >> we're >> > in >> > >> the bad spot of them reaching the magic 5% at the same time. Since I >> > don't >> > >> like the idea of automatically dropping 10% of devices, I'm >> wondering >> > what >> > >> we should deprecate first. >> > >> >> > >> Also, can we get better numbers for what's out there? Right now we >> still >> > >> have the only single point of reference, which is the Google Play >> store. >> > >> This doesn't cover China, or any other emerging markets. That said, >> > things >> > >> like Android One, and vendors like Xiaomi are making KitKat and >> Lolipop >> > >> the >> > >> standard. I know that I'm once again touching off a flame war >> between >> > >> developers who know that these platforms don't get the tests they >> need >> > to >> > >> be actually considered supported, and various business interests who >> for >> > >> some unknown reason need this support, but we should have this >> > discussion >> > >> again. >> > >> >> > >> Thoughts? >> > >> >> > >> Joe >> > >> >> > > >> > >> >>
Re: Deprecation Wars: ICS vs Gingerbread
I know they are old, but I have always wanted one, heh. -- tommy-carlos williams On 8 January 2015 at 12:54:24, Joe Bowser (bows...@gmail.com) wrote: Those stickers are old! I don't go to Android conferences, sine Android devs hate us these days. On Wed Jan 07 2015 at 5:53:04 PM Brian LeRoux wrote: > ! > > On Wed, Jan 7, 2015, 6:49 PM tommy-carlos williams > wrote: > >> >> -- >> tommy-carlos williams >> >> On 8 January 2015 at 12:37:59, Brian LeRoux (b...@brian.io) wrote: >> >> I say we go 4.x all in and drop everything below. Time to draw a line. >> >> On Wed, Jan 7, 2015, 6:24 PM Joe Bowser wrote: >> >> > Also, who actually tests on Gingerbread? Please comment on this thread. >> > >> > On Wed Jan 07 2015 at 5:09:49 PM Joe Bowser wrote: >> > >> > > I'm just mentioning it because my only Android 4.0.3 devices are an >> ASUS >> > > Transformer 2 tablet and a Motorola RAZR phone that did weird things >> to >> > my >> > > computer when I tried installing the extra software to upgrade it. >> > > >> > > However, if we did deprecate 2.3, I can just flash 4.0.3 on the Nexus >> S >> > > and use that. >> > > >> > > >> > > On Wed Jan 07 2015 at 5:07:27 PM tommy-carlos williams < >> > to...@devgeeks.org> >> > > wrote: >> > > >> > >> It seems to me that if we are only going to drop *one*, that it >> should >> > be >> > >> Gingerbread first, since it is a lower SDK version. >> > >> >> > >> How can an app support GB and *not* ICS? >> > >> >> > >> Having said that, I am also interested in the discussion of better >> > >> numbers on usage than just the Play Store (even if my gut reaction >> is >> > >> always “BURN 2.3 WITH FIRE”). >> > >> >> > >> -- >> > >> tommy-carlos williams >> > >> >> > >> On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) >> wrote: >> > >> >> > >> Hey >> > >> >> > >> So, 2015 is here, and we have the new Android Pie Chart: >> > >> >> > >> http://developer.android.com/about/dashboards/index.html#2015 >> > >> >> > >> Due to two percentage points on ICS and three on Gingerbread, we're >> > stuck >> > >> supporting these platforms for the near future, but it looks like >> we're >> > in >> > >> the bad spot of them reaching the magic 5% at the same time. Since I >> > don't >> > >> like the idea of automatically dropping 10% of devices, I'm >> wondering >> > what >> > >> we should deprecate first. >> > >> >> > >> Also, can we get better numbers for what's out there? Right now we >> still >> > >> have the only single point of reference, which is the Google Play >> store. >> > >> This doesn't cover China, or any other emerging markets. That said, >> > things >> > >> like Android One, and vendors like Xiaomi are making KitKat and >> Lolipop >> > >> the >> > >> standard. I know that I'm once again touching off a flame war >> between >> > >> developers who know that these platforms don't get the tests they >> need >> > to >> > >> be actually considered supported, and various business interests who >> for >> > >> some unknown reason need this support, but we should have this >> > discussion >> > >> again. >> > >> >> > >> Thoughts? >> > >> >> > >> Joe >> > >> >> > > >> > >> >>
[GitHub] cordova-lib pull request: Adding tizen support
Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/16 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-6661 Add platform 'web server' to cor...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/22 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-5082 [cordova info] Add support for B...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/7 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: For platform downloads, support git clon...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/14 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: Breaking src into submodules
Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/62 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: Tizen Support
Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/47 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-7067 run jasmine tests individually
Github user agrieve commented on the pull request: https://github.com/apache/cordova-lib/pull/51#issuecomment-69127345 What's the status of this. Leave open? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-8043 CB-6462 CB-6105 Refactor orienta...
Github user agrieve commented on the pull request: https://github.com/apache/cordova-lib/pull/128#issuecomment-69127706 Think this looks good to me. If you're ready for it to go in, could you attempt to rebase it ontop of master and squash your commits? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-8226 'cordova platform add' : Look up...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/140 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-8226 'cordova platform add' : Look up...
Github user agrieve commented on the pull request: https://github.com/apache/cordova-lib/pull/140#issuecomment-69129747 Merged! However - after a closer look at the unit tests, I highly encourage you to try and refactor things so that the tests do not mock out private methods within modules (e.g. like `resolvePath()`). Tests that do that make it very hard to change the code going forward, as it tests implementation details rather than function pre/post-conditions. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Deprecation Wars: ICS vs Gingerbread
I never test on gingerbread. My opinion is that devs that really need it can just use older Cordova versions, or can fight through the testing themselves. With multi-apk support in the play store, you could even use a different version of Cordova for gingerbread vs. ICS+ On Wed, Jan 7, 2015 at 8:55 PM, tommy-carlos williams wrote: > I know they are old, but I have always wanted one, heh. > > -- > tommy-carlos williams > > On 8 January 2015 at 12:54:24, Joe Bowser (bows...@gmail.com) wrote: > > Those stickers are old! I don't go to Android conferences, sine Android > devs hate us these days. > > On Wed Jan 07 2015 at 5:53:04 PM Brian LeRoux wrote: > > > ! > > > > On Wed, Jan 7, 2015, 6:49 PM tommy-carlos williams > > wrote: > > > >> > >> -- > >> tommy-carlos williams > >> > >> On 8 January 2015 at 12:37:59, Brian LeRoux (b...@brian.io) wrote: > >> > >> I say we go 4.x all in and drop everything below. Time to draw a line. > >> > >> On Wed, Jan 7, 2015, 6:24 PM Joe Bowser wrote: > >> > >> > Also, who actually tests on Gingerbread? Please comment on this > thread. > >> > > >> > On Wed Jan 07 2015 at 5:09:49 PM Joe Bowser > wrote: > >> > > >> > > I'm just mentioning it because my only Android 4.0.3 devices are an > >> ASUS > >> > > Transformer 2 tablet and a Motorola RAZR phone that did weird things > >> to > >> > my > >> > > computer when I tried installing the extra software to upgrade it. > >> > > > >> > > However, if we did deprecate 2.3, I can just flash 4.0.3 on the > Nexus > >> S > >> > > and use that. > >> > > > >> > > > >> > > On Wed Jan 07 2015 at 5:07:27 PM tommy-carlos williams < > >> > to...@devgeeks.org> > >> > > wrote: > >> > > > >> > >> It seems to me that if we are only going to drop *one*, that it > >> should > >> > be > >> > >> Gingerbread first, since it is a lower SDK version. > >> > >> > >> > >> How can an app support GB and *not* ICS? > >> > >> > >> > >> Having said that, I am also interested in the discussion of better > >> > >> numbers on usage than just the Play Store (even if my gut reaction > >> is > >> > >> always “BURN 2.3 WITH FIRE”). > >> > >> > >> > >> -- > >> > >> tommy-carlos williams > >> > >> > >> > >> On 8 January 2015 at 10:39:33, Joe Bowser (bows...@gmail.com) > >> wrote: > >> > >> > >> > >> Hey > >> > >> > >> > >> So, 2015 is here, and we have the new Android Pie Chart: > >> > >> > >> > >> http://developer.android.com/about/dashboards/index.html#2015 > >> > >> > >> > >> Due to two percentage points on ICS and three on Gingerbread, we're > >> > stuck > >> > >> supporting these platforms for the near future, but it looks like > >> we're > >> > in > >> > >> the bad spot of them reaching the magic 5% at the same time. Since > I > >> > don't > >> > >> like the idea of automatically dropping 10% of devices, I'm > >> wondering > >> > what > >> > >> we should deprecate first. > >> > >> > >> > >> Also, can we get better numbers for what's out there? Right now we > >> still > >> > >> have the only single point of reference, which is the Google Play > >> store. > >> > >> This doesn't cover China, or any other emerging markets. That said, > >> > things > >> > >> like Android One, and vendors like Xiaomi are making KitKat and > >> Lolipop > >> > >> the > >> > >> standard. I know that I'm once again touching off a flame war > >> between > >> > >> developers who know that these platforms don't get the tests they > >> need > >> > to > >> > >> be actually considered supported, and various business interests > who > >> for > >> > >> some unknown reason need this support, but we should have this > >> > discussion > >> > >> again. > >> > >> > >> > >> Thoughts? > >> > >> > >> > >> Joe > >> > >> > >> > > > >> > > >> > >> >
[GitHub] cordova-lib pull request: Link java files
GitHub user agrieve opened a pull request: https://github.com/apache/cordova-lib/pull/142 Link java files You can merge this pull request into a Git repository by running: $ git pull https://github.com/agrieve/cordova-lib link-java-files Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/142.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #142 commit 8148a03f794bc505474f484277b36a2c90830a13 Author: Andrew Grieve Date: 2015-01-05T20:20:39Z CB-8244 Pass options object to platform handlers in plugman commit f8fad5c40e4ad62de5ff9a38955cdcbe21e08f75 Author: Andrew Grieve Date: 2015-01-05T20:48:24Z CB-8244 android: Have `plugin add --link` create symlinks for ``, ``, etc Makes editing Java files in Android Studio edit the original .java files. No more copying changes back! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-ios pull request: [CB-8270] rename category methods for JS...
GitHub user lingoer opened a pull request: https://github.com/apache/cordova-ios/pull/124 [CB-8270] rename category methods for JSON handling with a prefix. According to [Apple's documentation](https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/CustomizingExistingClasses/CustomizingExistingClasses.html#//apple_ref/doc/uid/TP40011210-CH6-SW4) , naming a Category method without a prefix would possibly cause a Name Clash In CordovaLib/Classes/CDVJSON.h : NSArray(CDVJSONSerializing) The method name should starts with a prefix Actually, it clashes with the TencentOpenAPI framework which is a major sns platform in China. You can merge this pull request into a Git repository by running: $ git pull https://github.com/lingoer/cordova-ios CB-8270 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/124.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #124 commit 75e72a53f062115066e2fc9305c8dfb0ad5cfeb8 Author: Ruoyu Fu Date: 2015-01-08T04:08:37Z [CB-8270] rename category methods for JSON handling with a prefix. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Thought on improving translation and docs
@Marcel Thanks for feedback and don't worry you don't hurt me. What I want is to improve translation, and I want to double-check that any changes does not hurts in the final results. So this would be a lot of generation of ru-edge. I decide to take any low hanging fruit in the generation speed, since this directly benefit to my workflow. What I want to achieve is following workflow Generate docs -> Validate docs -> Made translation in CrowdIn -> Download translations -> Generate docs -> Validate Docs Right now I'm all-set with speeding up generation process. I will start working on validating of our docs, but before that I want to collect community opinion what kind of docs would be helpful in maintaining docs and translations. 2015-01-07 20:40 GMT+06:00 Marcel Kinard : > I just ran genjs to generate the docs for all versions and languages, and > it is roughly the same time as it took using the old Ruby system. I > certainly don't want to dampen your enthusiasm, but I don't think the speed > is enough of a pain to require a lot more investment of your effort. > Generating all versions/languages is not a common task. Generating en-edge > is common, and fast enough for me. > > Using the new JS system is way better than the Ruby system. That was a > pain point (at least for me) that you have made much better. Many thanks > for that! > > > On Jan 7, 2015, at 8:34 AM, Andrey Kurdumov > wrote: > > > > One more speed improvement and > > https://github.com/apache/cordova-docs/pull/257 > > > > After that I only improve speed by movign joDoc-js inside our generation > > process, and start moving to Make-ish processing. > > > > Right now generation speed almos doubled, so I could concentrate on > > translation tools. > > If no other ideas popped up, I will start with my verification tools > which > > I describe in the start of the topic. > > Definitely would like to have some feedback from other guys > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
[GitHub] cordova-plugin-contacts pull request: Windows phone contact picker...
Github user Hurtyto commented on the pull request: https://github.com/apache/cordova-plugin-contacts/pull/51#issuecomment-69142471 Sure. I will sign it as soon as possible then :) -Original Message- From: "Jesse MacFadyen" Sent: â7.â1.â2015 âг. 20:11 To: "apache/cordova-plugin-contacts" Cc: "Hurtyto" Subject: Re: [cordova-plugin-contacts] Windows phone contact picker filter(#51) Yeah, we can't accept the code without a signed CLA on file. It'll wait. â Reply to this email directly or view it on GitHub.= --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-js pull request: Fixed callbackFromNative method
GitHub user mdudek opened a pull request: https://github.com/apache/cordova-js/pull/98 Fixed callbackFromNative method NO_RESULT status was resolved as failure. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mdudek/cordova-js patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-js/pull/98.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #98 commit 7b1e8e1d68c49ccaa5a38b1805033292d42c2c22 Author: Michael Dudek Date: 2015-01-08T07:28:39Z Fixed callbackFromNative method NO_RESULT status was resolved as failure. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-ios pull request: Fixed callbackFromNative
Github user mdudek commented on the pull request: https://github.com/apache/cordova-ios/pull/123#issuecomment-69145160 Thanks for info. I will fix it there... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-ios pull request: Fixed callbackFromNative
Github user mdudek closed the pull request at: https://github.com/apache/cordova-ios/pull/123 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
