[jira] [Commented] (CB-6726) Android Webview Not Intercepting Resource Requests Properly
[ https://issues.apache.org/jira/browse/CB-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007774#comment-14007774 ] Tim Kim commented on CB-6726: - I'm not sure if I placed the webview.clearCache(true) in the correct place(s), but I still get the same results. Tried it in the onPageStarted and onPageFinished methods in CordovaWebViewClient.java. > Android Webview Not Intercepting Resource Requests Properly > --- > > Key: CB-6726 > URL: https://issues.apache.org/jira/browse/CB-6726 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Tim Kim >Assignee: Andrew Grieve > > The shouldInterceptRequest method in IceCreamCordovaWebViewClient.java > doesn't seem to fire for every request. Only for things like xhrs or > resources prefixed with http:// > Steps to reproduce: > - pull down latest > - ./bin/create test > - cd into test/ > - find the shouldInterceptRequest method in IceCreamCordovaWebViewClient.java > and add a log statement to know when it fired > - ./cordova/run > - ./cordova/log > - only 'file:///android_asset/www/cordova_plugins.js' will make > shouldInterceptRequest fire and not the reference to 'cordova.js' or > 'js/index.js'. > - add in ' src="http://code.jquery.com/jquery-1.11.0.min.js";>' to the > index.html to see the shouldInterceptRequest fire > Tested on 4.4 with cordova-android 3.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6726) Android Webview Not Intercepting Resource Requests Properly
Tim Kim created CB-6726: --- Summary: Android Webview Not Intercepting Resource Requests Properly Key: CB-6726 URL: https://issues.apache.org/jira/browse/CB-6726 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.5.0 Reporter: Tim Kim Assignee: Andrew Grieve The shouldInterceptRequest method in IceCreamCordovaWebViewClient.java doesn't seem to fire for every request. Only for things like xhrs or resources prefixed with http:// Steps to reproduce: - pull down latest - ./bin/create test - cd into test/ - find the shouldInterceptRequest method in IceCreamCordovaWebViewClient.java and add a log statement to know when it fired - ./cordova/run - ./cordova/log - only 'file:///android_asset/www/cordova_plugins.js' will make shouldInterceptRequest fire and not the reference to 'cordova.js' or 'js/index.js'. - add in ' http://code.jquery.com/jquery-1.11.0.min.js";>' to the index.html to see the shouldInterceptRequest fire Tested on 4.4 with cordova-android 3.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6023) Checking the version for Plugman as an engine requirement returns the wrong version
Tim Kim created CB-6023: --- Summary: Checking the version for Plugman as an engine requirement returns the wrong version Key: CB-6023 URL: https://issues.apache.org/jira/browse/CB-6023 Project: Apache Cordova Issue Type: Bug Components: Plugman Affects Versions: 3.3.0 Reporter: Tim Kim Priority: Minor In this file: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=src/util/default-engines.js;h=2ca8b137a9c7a2bcd2099a6a599bf763ed238430;hb=ce8c421481ff04e87eaf81442e9504b6358c13c3 Plugman's version is returned as Node's version. Should return plugman's actual version instead. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5605) plugman install.js:68 crashes
[
https://issues.apache.org/jira/browse/CB-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844688#comment-13844688
]
Tim Kim commented on CB-5605:
-
Hi there,
I don't work on the firefoxos platform but it seems like the cordova/version
script is missing from the cordova directory of the project. I just pinged
Steve who works on the platform and he'll take a look shortly.
> plugman install.js:68 crashes
> -
>
> Key: CB-5605
> URL: https://issues.apache.org/jira/browse/CB-5605
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: Axel Nennker
>
> My app uses two custom plugins.
> I want to add firefoxos as a platform.
> When I issue a
> cordova platform add firefoxos
> install.js:68 fails with the message
> "Cannot access currentVersion of null"
> I guess my custom plugins' plugin.xml are wrong...
> Anyway I think that install.js should not crash here.
> I have no idea why engines[i] is null for some i.
> -Axel
> Maybe this code is a fix:
> function checkEngines(engines) {
> for(var i = 0; i < engines.length; i++) {
> var engine = engines[i];
> if(engine===null) {
> return Q.reject(new Error('Plugin doesn\'t support this project'));
> } else {
> if(semver.satisfies(engine.currentVersion, engine.minVersion) ||
> engine.currentVersion == null){
> // engine ok!
> }else{
> return Q.reject(new Error('Plugin doesn\'t support this
> project\'s '+engine.name+' version. '+engine.name+': ' +
> engine.currentVersion + ', failed version requirement: ' +
> engine.minVersion));
> }
> }
> }
> return Q(true);
> }
> Although I never see the no-support output
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Resolved] (CB-4872) Create os/sdk version scripts for engine tag
[ https://issues.apache.org/jira/browse/CB-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-4872. - Resolution: Fixed > Create os/sdk version scripts for engine tag > > > Key: CB-4872 > URL: https://issues.apache.org/jira/browse/CB-4872 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, BlackBerry, iOS, Plugman, Windows 8, WP7, WP8 >Affects Versions: 3.0.0 >Reporter: Tim Kim >Assignee: Tim Kim >Priority: Minor > Fix For: 3.2.0 > > > The engine tag is now able to check any of Cordova components's version so > it's time to implement the OS/SDK version scripts. This will allow plugin > authors to specify what version of OS/SDK is needed using the tag in > the plugin.xml. > eg, > > > > > > These scripts will be listed in the default engines within Plugman so that a > user may easily reference them in the engine tag without having to provide a > location/platform attribute in the engine tag: > https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=src/util/default-engines.js;h=4fd4a657b9cf6b494fece8b914c7c1ea511e3ca6;hb=1fa97a4161410f411e115362c293d88180319d9d > Related to this ticket: https://issues.apache.org/jira/browse/CB-4036 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4872) Create os/sdk version scripts for engine tag
[ https://issues.apache.org/jira/browse/CB-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807451#comment-13807451 ] Tim Kim commented on CB-4872: - All right, I believe all the platform scripts I set out to do have their version scripts now as well as updates to the docs. Marking this one as resolved! > Create os/sdk version scripts for engine tag > > > Key: CB-4872 > URL: https://issues.apache.org/jira/browse/CB-4872 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, BlackBerry, iOS, Plugman, Windows 8, WP7, WP8 >Affects Versions: 3.0.0 >Reporter: Tim Kim >Assignee: Tim Kim >Priority: Minor > Fix For: 3.2.0 > > > The engine tag is now able to check any of Cordova components's version so > it's time to implement the OS/SDK version scripts. This will allow plugin > authors to specify what version of OS/SDK is needed using the tag in > the plugin.xml. > eg, > > > > > > These scripts will be listed in the default engines within Plugman so that a > user may easily reference them in the engine tag without having to provide a > location/platform attribute in the engine tag: > https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=src/util/default-engines.js;h=4fd4a657b9cf6b494fece8b914c7c1ea511e3ca6;hb=1fa97a4161410f411e115362c293d88180319d9d > Related to this ticket: https://issues.apache.org/jira/browse/CB-4036 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5139) Unable to call the version file from not the project directory
[ https://issues.apache.org/jira/browse/CB-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-5139. - Resolution: Fixed > Unable to call the version file from not the project directory > -- > > Key: CB-5139 > URL: https://issues.apache.org/jira/browse/CB-5139 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.1.0 >Reporter: Tim Kim > Fix For: 3.2.0 > > > The location of the version file is hard coded into the path in > cordova/lib/version.js such that it only works if you are calling it from the > project directory. > Steps to reproduce: > - ./bin/create test com.test test > - cd test > - ./cordova/version // should work > - cd www > - ../cordova/version // returns The file "www/cordova.js" does not exist. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5139) Unable to call the version file from not the project directory
Tim Kim created CB-5139: --- Summary: Unable to call the version file from not the project directory Key: CB-5139 URL: https://issues.apache.org/jira/browse/CB-5139 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.1.0 Reporter: Tim Kim Fix For: 3.2.0 The location of the version file is hard coded into the path in cordova/lib/version.js such that it only works if you are calling it from the project directory. Steps to reproduce: - ./bin/create test com.test test - cd test - ./cordova/version // should work - cd www - ../cordova/version // returns The file "www/cordova.js" does not exist. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4872) Create os/sdk version scripts for engine tag
[ https://issues.apache.org/jira/browse/CB-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791797#comment-13791797 ] Tim Kim commented on CB-4872: - Hey Marcel, Yep some of that info is there already from this commit: https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=9854fb170280c93007c25260fde066b106f46db3 It's a little out of date for the names of the default version scripts so I'll need to update the docs to reflect that. > Create os/sdk version scripts for engine tag > > > Key: CB-4872 > URL: https://issues.apache.org/jira/browse/CB-4872 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, BlackBerry, iOS, Plugman, Windows 8, WP7, WP8 >Affects Versions: 3.0.0 >Reporter: Tim Kim >Assignee: Tim Kim >Priority: Minor > Fix For: 3.2.0 > > > The engine tag is now able to check any of Cordova components's version so > it's time to implement the OS/SDK version scripts. This will allow plugin > authors to specify what version of OS/SDK is needed using the tag in > the plugin.xml. > eg, > > > > > > These scripts will be listed in the default engines within Plugman so that a > user may easily reference them in the engine tag without having to provide a > location/platform attribute in the engine tag: > https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=src/util/default-engines.js;h=4fd4a657b9cf6b494fece8b914c7c1ea511e3ca6;hb=1fa97a4161410f411e115362c293d88180319d9d > Related to this ticket: https://issues.apache.org/jira/browse/CB-4036 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4872) Create os/sdk version scripts for engine tag
[ https://issues.apache.org/jira/browse/CB-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789667#comment-13789667 ] Tim Kim commented on CB-4872: - Cool, thanks for the info! > Create os/sdk version scripts for engine tag > > > Key: CB-4872 > URL: https://issues.apache.org/jira/browse/CB-4872 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, BlackBerry, iOS, Plugman, Windows 8, WP7, WP8 >Affects Versions: 3.0.0 >Reporter: Tim Kim >Assignee: Tim Kim >Priority: Minor > Fix For: 3.2.0 > > > The engine tag is now able to check any of Cordova components's version so > it's time to implement the OS/SDK version scripts. This will allow plugin > authors to specify what version of OS/SDK is needed using the tag in > the plugin.xml. > eg, > > > > > > These scripts will be listed in the default engines within Plugman so that a > user may easily reference them in the engine tag without having to provide a > location/platform attribute in the engine tag: > https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=src/util/default-engines.js;h=4fd4a657b9cf6b494fece8b914c7c1ea511e3ca6;hb=1fa97a4161410f411e115362c293d88180319d9d > Related to this ticket: https://issues.apache.org/jira/browse/CB-4036 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-4872) Create os/sdk version scripts for engine tag
Tim Kim created CB-4872: --- Summary: Create os/sdk version scripts for engine tag Key: CB-4872 URL: https://issues.apache.org/jira/browse/CB-4872 Project: Apache Cordova Issue Type: New Feature Components: Android, BlackBerry, iOS, Plugman, Windows 8, WP7, WP8 Affects Versions: 3.0.0 Reporter: Tim Kim Assignee: Tim Kim Priority: Minor Fix For: 3.2.0 The engine tag is now able to check any of Cordova components's version so it's time to implement the OS/SDK version scripts. This will allow plugin authors to specify what version of OS/SDK is needed using the tag in the plugin.xml. eg, These scripts will be listed in the default engines within Plugman so that a user may easily reference them in the engine tag without having to provide a location/platform attribute in the engine tag: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=src/util/default-engines.js;h=4fd4a657b9cf6b494fece8b914c7c1ea511e3ca6;hb=1fa97a4161410f411e115362c293d88180319d9d Related to this ticket: https://issues.apache.org/jira/browse/CB-4036 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4488) There are no manual tests for capture plugin?
[ https://issues.apache.org/jira/browse/CB-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764805#comment-13764805 ] Tim Kim commented on CB-4488: - Howdy, I added some manual capture tests now. I believe for the test to work properly, you'll need to install the capture, file, and the media plugins. > There are no manual tests for capture plugin? > - > > Key: CB-4488 > URL: https://issues.apache.org/jira/browse/CB-4488 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Affects Versions: 3.0.0 >Reporter: lmnbeyond >Assignee: Tim Kim > > I can't find any manual tests for capture plugin. I think it is necessary to > add some manual tests for it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4488) There are no manual tests for capture plugin?
[ https://issues.apache.org/jira/browse/CB-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-4488. - Resolution: Fixed > There are no manual tests for capture plugin? > - > > Key: CB-4488 > URL: https://issues.apache.org/jira/browse/CB-4488 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Affects Versions: 3.0.0 >Reporter: lmnbeyond >Assignee: Tim Kim > > I can't find any manual tests for capture plugin. I think it is necessary to > add some manual tests for it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-4488) There are no manual tests for capture plugin?
[ https://issues.apache.org/jira/browse/CB-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-4488: --- Assignee: Tim Kim (was: Filip Maj) > There are no manual tests for capture plugin? > - > > Key: CB-4488 > URL: https://issues.apache.org/jira/browse/CB-4488 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Affects Versions: 3.0.0 >Reporter: lmnbeyond >Assignee: Tim Kim > > I can't find any manual tests for capture plugin. I think it is necessary to > add some manual tests for it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751836#comment-13751836 ] Tim Kim commented on CB-4036: - All right, docs are in about the changes. Marking this as resolved! > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Tim Kim > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-4036. - Resolution: Fixed > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Tim Kim > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4494) "plugman search" Should indicate which results are compatible with your configuration
[ https://issues.apache.org/jira/browse/CB-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751716#comment-13751716 ] Tim Kim commented on CB-4494: - Hey all, I think this is a cool feature but I'm unsure how the check against your configuration would work. With the exception of the cordova-plugman engine, all the other engines (ie, cordova, cordova-ios/android/blackberry etc...) need to execute a version script within the platform directory. However, plugman is supposed to agnostic about the platform directories and it's more of the cli's job to know about that directory in the first place. Furthermore, in the case of a custom engine, the version script for the custom engine is to be placed within the plugin's folder so that would mean that having the version info wouldn't be enough. A user must download the plugin first, run the custom engine version script within the plugin folder, and then determine if it's compatible or not. > "plugman search" Should indicate which results are compatible with your > configuration > - > > Key: CB-4494 > URL: https://issues.apache.org/jira/browse/CB-4494 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Andrew Grieve >Assignee: Anis Kadri > > I don't think we should filter by your platform, but it would be nice is we > had some sort of indicator that showed which results were compatible vs not > compatible. > To do this, we'd need version info available in the couchdb schema I > think. > Step 1 to this bug is to design, Step 2 is to implement. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3646) plugman should be able to support per-platform engine specifications
[ https://issues.apache.org/jira/browse/CB-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750763#comment-13750763 ] Tim Kim commented on CB-3646: - Merged in changes here: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=6e76e3a5bfdc4407aa6b32b53188e8c3a54f7be0 > plugman should be able to support per-platform engine specifications > > > Key: CB-3646 > URL: https://issues.apache.org/jira/browse/CB-3646 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim >Priority: Minor > > It would be nice to be able to specify minimum requirements for cordova > version compatibility at a platform level. > Currently plugman only supports top-level (platform agnostic) > elements, but adding support at a platform level would be nice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3646) plugman should be able to support per-platform engine specifications
[ https://issues.apache.org/jira/browse/CB-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3646. - Resolution: Fixed > plugman should be able to support per-platform engine specifications > > > Key: CB-3646 > URL: https://issues.apache.org/jira/browse/CB-3646 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim >Priority: Minor > > It would be nice to be able to specify minimum requirements for cordova > version compatibility at a platform level. > Currently plugman only supports top-level (platform agnostic) > elements, but adding support at a platform level would be nice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4490) version check should check against plugman version
[ https://issues.apache.org/jira/browse/CB-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750762#comment-13750762 ] Tim Kim commented on CB-4490: - Merged in now: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=6e76e3a5bfdc4407aa6b32b53188e8c3a54f7be0 > version check should check against plugman version > --- > > Key: CB-4490 > URL: https://issues.apache.org/jira/browse/CB-4490 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Andrew Grieve >Assignee: Tim Kim > > Currently, we have: > > This checks against the result of platform/bin/version scripts. However, it's > quite possible to have a plugin that works with cordova-android >=3.0 and > cordova-ios >=3.1 > CB-4036 introduces per-platform SDK & OS version checks. > This issue covers have cordova versions be per-platform, as well as having > plugman version requirement. > > > > > > We could still maintain: > > > > as a shorthand for: > > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750761#comment-13750761 ] Tim Kim commented on CB-4036: - Ok, finally merged my stuff into master and is in a good state: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=6e76e3a5bfdc4407aa6b32b53188e8c3a54f7be0 > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Tim Kim > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4490) version check should check against plugman version
[ https://issues.apache.org/jira/browse/CB-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-4490. - Resolution: Fixed > version check should check against plugman version > --- > > Key: CB-4490 > URL: https://issues.apache.org/jira/browse/CB-4490 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Andrew Grieve >Assignee: Tim Kim > > Currently, we have: > > This checks against the result of platform/bin/version scripts. However, it's > quite possible to have a plugin that works with cordova-android >=3.0 and > cordova-ios >=3.1 > CB-4036 introduces per-platform SDK & OS version checks. > This issue covers have cordova versions be per-platform, as well as having > plugman version requirement. > > > > > > We could still maintain: > > > > as a shorthand for: > > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739047#comment-13739047 ] Tim Kim commented on CB-4036: - Hey gang, So I want to check for platform versions, but I'm noticing we are having a few inconsistent results from calling the version/scripts. These are the current return values from the master branch: android: 3.1.0-dev ios: dev blackberry10: 3.0.0 Didn't test windows I'm thinking we need to make some changes to the platform version scripts so that they are more in synch. In addition, the 'dev' version also futzes up the version requirement attribute. Currently, if I see 'dev' in the code, it'll just install it. However, I'm pretty sure that cli or whatever tool is just going to download the master branch so you'll always have dev which kinda ruins the point of the version attribute. > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732831#comment-13732831 ] Tim Kim commented on CB-4036: - Ok, I've made another pass at this with the commit in the comment above. It's not fully tested and I'm not even sure if it works right now (have to change the tests), but I figured I'd push it up just so I could show you all. Anywho, I went with the idea that we do all of our version checks within the engine tag. I've also added support such that there are defaults for the engines we know about (placed in util/default-engines) as well the ability to add custom engines that need to be checked. > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731057#comment-13731057 ] Tim Kim commented on CB-4036: - Hrm ya, I think I like option two. Having the defaults like you mention is a good idea as well. I think we may also need another attribute to point to a script that spits out the information needed for the version requirement. That way we can also cover the use case of a developer who may wish to create their own engine requirements and have the ability to point to a project/platform script that gives that kind of information. So something like: And in somewhere in plugman, we'll have a file with all the defaults for the base engines and their locations for their scriptTargets as well. > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728207#comment-13728207 ] Tim Kim commented on CB-4036: - Hey Andrew, I like the concept of having it all in the engine tag but the problem I feel is what do for platforms that don't care about/need other platform's engines. To me, the solution to that is to specify which of the engines work for what platforms which is kinda redundant if you have a separate platform tag already. Hrm, or maybe we could do something like: > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726988#comment-13726988 ] Tim Kim commented on CB-4036: - Not sure what happened but after my rebase and push to the version_engine_checks branch on apache, some of the history got wiped. However, if I push to my own github, it preserved the history. Hate to switch to a new branch but I did anyway - branch is now versionCheck. > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721121#comment-13721121 ] Tim Kim commented on CB-4036: - Hey guys, Thanks for the comments but I should've added that the test file I submitted is probably going to go away in the future and the tests inside will be added to install.spec.js. The reason for breaking it out into it's small little test file is to test the version/engine stuff quickly and directly as opposed to adding it into install.spec.js and waiting for my test to come around. I also totally agree with having a helper function that takes the inputs for all the version/engine checking. Most of the engine/version checks are really the same code but with different inputs. So having a helper function that takes in all the inputs is probably the best way to go. But yeah, still a work in progress :) > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3646) plugman should be able to support per-platform engine specifications
[ https://issues.apache.org/jira/browse/CB-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720154#comment-13720154 ] Tim Kim commented on CB-3646: - Are there any examples in the wild that we would want to possibly support? It'd be nice to test against something that exists as opposed to just test data. > plugman should be able to support per-platform engine specifications > > > Key: CB-3646 > URL: https://issues.apache.org/jira/browse/CB-3646 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim >Priority: Minor > > It would be nice to be able to specify minimum requirements for cordova > version compatibility at a platform level. > Currently plugman only supports top-level (platform agnostic) > elements, but adding support at a platform level would be nice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720152#comment-13720152 ] Tim Kim commented on CB-4036: - Hey all, I just pushed up some first pass stuff for the engine/platform version stuff. It doesn't do too much right now other than check some hard coded info (went with Shaz's idea for having a script that spits out the sdk/os info). I also did some research for the BlackBerry 10 script that outputs the sdk/os info as well and it should work. I just lack an actual phone though, so I'll wait till Lorin gets back into town to test it on his. > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4226) CLONE - Update Upgrading Guide for 2.9.0 -> 3.0.0 for OSX
[ https://issues.apache.org/jira/browse/CB-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-4226: Component/s: (was: BlackBerry) > CLONE - Update Upgrading Guide for 2.9.0 -> 3.0.0 for OSX > - > > Key: CB-4226 > URL: https://issues.apache.org/jira/browse/CB-4226 > Project: Apache Cordova > Issue Type: Sub-task > Components: OSX >Reporter: Filip Maj >Assignee: Lorin Beer > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4226) CLONE - Update Upgrading Guide for 2.9.0 -> 3.0.0 for OSX
[ https://issues.apache.org/jira/browse/CB-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-4226: Assignee: Lorin Beer (was: Tim Kim) > CLONE - Update Upgrading Guide for 2.9.0 -> 3.0.0 for OSX > - > > Key: CB-4226 > URL: https://issues.apache.org/jira/browse/CB-4226 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry, OSX >Reporter: Filip Maj >Assignee: Lorin Beer > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3406) InAppBrowser option to hide bottom bar with Done/History buttons
[ https://issues.apache.org/jira/browse/CB-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3406: Assignee: Lorin Beer (was: Tim Kim) > InAppBrowser option to hide bottom bar with Done/History buttons > > > Key: CB-3406 > URL: https://issues.apache.org/jira/browse/CB-3406 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry >Reporter: Shazron Abdullah >Assignee: Lorin Beer > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-2542) Support list of button labels for confirm dialogs on BlackBerry
[ https://issues.apache.org/jira/browse/CB-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-2542: Assignee: Lorin Beer (was: Tim Kim) > Support list of button labels for confirm dialogs on BlackBerry > --- > > Key: CB-2542 > URL: https://issues.apache.org/jira/browse/CB-2542 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry >Reporter: Max Woghiren >Assignee: Lorin Beer >Priority: Minor > > Notification.confirm now passes a list of button label strings instead of a > comma separated string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3014) Wrong documentation for create in README.md
[ https://issues.apache.org/jira/browse/CB-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3014: Assignee: Lorin Beer (was: Tim Kim) > Wrong documentation for create in README.md > --- > > Key: CB-3014 > URL: https://issues.apache.org/jira/browse/CB-3014 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: Master >Reporter: Shazron Abdullah >Assignee: Lorin Beer > > On this page: > https://github.com/apache/cordova-blackberry/blob/master/README.md > Under: > 1. > https://github.com/apache/cordova-blackberry/blob/master/README.md#creating-a-new-cordova-blackberry-project > 2. > https://github.com/apache/cordova-blackberry/blob/master/README.md#general-commands > The create arguments are reversed. They should be > create [path package appname] , verified in bin/create -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3541) [blackberry] Remove deprecated device.name field.
[ https://issues.apache.org/jira/browse/CB-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3541: Assignee: Lorin Beer (was: Tim Kim) > [blackberry] Remove deprecated device.name field. > - > > Key: CB-3541 > URL: https://issues.apache.org/jira/browse/CB-3541 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry >Reporter: Andrew Grieve >Assignee: Lorin Beer > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3424) BB - InAppBrowser Option to Start Hidden
[ https://issues.apache.org/jira/browse/CB-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3424: Assignee: Lorin Beer (was: Tim Kim) > BB - InAppBrowser Option to Start Hidden > > > Key: CB-3424 > URL: https://issues.apache.org/jira/browse/CB-3424 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry >Reporter: Andrew Grieve >Assignee: Lorin Beer >Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-4005) InApp Browser continuously throws errors on Android
[ https://issues.apache.org/jira/browse/CB-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-4005: --- Assignee: Joe Bowser (was: Tim Kim) > InApp Browser continuously throws errors on Android > --- > > Key: CB-4005 > URL: https://issues.apache.org/jira/browse/CB-4005 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 2.8.0 >Reporter: Tim Kim >Assignee: Joe Bowser > Fix For: 3.0.0 > > > Related to issue: > https://issues.apache.org/jira/browse/CB-3665#comment-13692456 > Steps to reproduce: > - Go to the In App Browser manual tests > - Under Local URL, hit any of the last three tests (eg, Target=Blank: > InAppBrowser, Target=Random: InAppBrowser, Target=Random, no location bar: > InAppBrowser). > - App will launch inapp browser > - Hit back button > - App unresponsive (can still scroll), but can't click on any buttons > - Logcat shows a stream of error messages: I/Web Console( 5375): > processMessage failed: invalid message: at > file:///android_asset/www/cordova.js:977 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4005) InApp Browser continuously throws errors on Android
[ https://issues.apache.org/jira/browse/CB-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695814#comment-13695814 ] Tim Kim commented on CB-4005: - Hey Joe, Here's some more info: Galaxy Nexus Android version 4.2.1 On both Android master and 3.0.0 branch I think Fil also reported the same error. I'll ping him and ask him what device(s) he used. > InApp Browser continuously throws errors on Android > --- > > Key: CB-4005 > URL: https://issues.apache.org/jira/browse/CB-4005 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 2.8.0 >Reporter: Tim Kim >Assignee: Tim Kim > Fix For: 3.0.0 > > > Related to issue: > https://issues.apache.org/jira/browse/CB-3665#comment-13692456 > Steps to reproduce: > - Go to the In App Browser manual tests > - Under Local URL, hit any of the last three tests (eg, Target=Blank: > InAppBrowser, Target=Random: InAppBrowser, Target=Random, no location bar: > InAppBrowser). > - App will launch inapp browser > - Hit back button > - App unresponsive (can still scroll), but can't click on any buttons > - Logcat shows a stream of error messages: I/Web Console( 5375): > processMessage failed: invalid message: at > file:///android_asset/www/cordova.js:977 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4005) InApp Browser continuously throws errors on Android
Tim Kim created CB-4005: --- Summary: InApp Browser continuously throws errors on Android Key: CB-4005 URL: https://issues.apache.org/jira/browse/CB-4005 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.8.0 Reporter: Tim Kim Assignee: Joe Bowser Fix For: 3.0.0 Related to issue: https://issues.apache.org/jira/browse/CB-3665#comment-13692456 Steps to reproduce: - Go to the In App Browser manual tests - Under Local URL, hit any of the last three tests (eg, Target=Blank: InAppBrowser, Target=Random: InAppBrowser, Target=Random, no location bar: InAppBrowser). - App will launch inapp browser - Hit back button - App unresponsive (can still scroll), but can't click on any buttons - Logcat shows a stream of error messages: I/Web Console( 5375): processMessage failed: invalid message: at file:///android_asset/www/cordova.js:977 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3665) Breakout InAppBrowser Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692456#comment-13692456 ] Tim Kim commented on CB-3665: - Ok, now I figured out how to reproduce it - these tests are for both 3.0.0 and master branch of Android: - Go to the In App Browser manual tests - Under Local URL, hit any of the last three tests (eg, Target=Blank: InAppBrowser, Target=Random: InAppBrowser, Target=Random, no location bar: InAppBrowser). - App will launch inapp browser - Hit back button - App unresponsive (can still scroll), but can't click on any buttons - Logcat shows a stream of error messages similar to Fil's > Breakout InAppBrowser Plugin for Android > > > Key: CB-3665 > URL: https://issues.apache.org/jira/browse/CB-3665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin InAppBrowser >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3665) Breakout InAppBrowser Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692374#comment-13692374 ] Tim Kim commented on CB-3665: - I got the same error Fil did when testing with regular Android. It seems to be more of a problem with the plugin itself than the ripping out of the plugin. The bug is also hard to reproduce, I'm not sure what I did other than just trying the manual test. > Breakout InAppBrowser Plugin for Android > > > Key: CB-3665 > URL: https://issues.apache.org/jira/browse/CB-3665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin InAppBrowser >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3680) Breakout Contacts Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689728#comment-13689728 ] Tim Kim commented on CB-3680: - Fixed and tested on this commit: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;a=commit;h=bfe59ee1e6a972b4e5622a59fb4a265f76e448fd > Breakout Contacts Plugin for Android > > > Key: CB-3680 > URL: https://issues.apache.org/jira/browse/CB-3680 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Contacts >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3680) Breakout Contacts Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3680. - Resolution: Fixed > Breakout Contacts Plugin for Android > > > Key: CB-3680 > URL: https://issues.apache.org/jira/browse/CB-3680 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Contacts >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3680) Breakout Contacts Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-3680: --- Assignee: Tim Kim > Breakout Contacts Plugin for Android > > > Key: CB-3680 > URL: https://issues.apache.org/jira/browse/CB-3680 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Contacts >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3725) Breakout File Transfer Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3725. - Resolution: Fixed > Breakout File Transfer Plugin for Android > - > > Key: CB-3725 > URL: https://issues.apache.org/jira/browse/CB-3725 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File Transfer >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3725) Breakout File Transfer Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689629#comment-13689629 ] Tim Kim commented on CB-3725: - Retested using this commit: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;a=commit;h=48f8ede7376ea17d528e682540db9d89951f5255 Has two extra failing tests in mobile spec, but the failing tests refer to device.name so no biggie. > Breakout File Transfer Plugin for Android > - > > Key: CB-3725 > URL: https://issues.apache.org/jira/browse/CB-3725 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File Transfer >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3724) Breakout File Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3724. - Resolution: Fixed > Breakout File Plugin for Android > > > Key: CB-3724 > URL: https://issues.apache.org/jira/browse/CB-3724 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3724) Breakout File Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689622#comment-13689622 ] Tim Kim commented on CB-3724: - Got it retested using this commit: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;a=commit;h=f008d2e9a14219ee57463ceab77569c859024a62 > Breakout File Plugin for Android > > > Key: CB-3724 > URL: https://issues.apache.org/jira/browse/CB-3724 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3640) Breakout Media Capture Plugin
[ https://issues.apache.org/jira/browse/CB-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3640: Assignee: (was: Tim Kim) > Breakout Media Capture Plugin > - > > Key: CB-3640 > URL: https://issues.apache.org/jira/browse/CB-3640 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Media Capture >Reporter: Steve Gill > Fix For: 3.0.0 > > > Breakout the Media Capture Plugin for all platforms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3700) Breakout Media Capture Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3700. - Resolution: Fixed > Breakout Media Capture Plugin for Android > - > > Key: CB-3700 > URL: https://issues.apache.org/jira/browse/CB-3700 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media Capture >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3700) Breakout Media Capture Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688605#comment-13688605 ] Tim Kim commented on CB-3700: - Looking good and tested: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;a=commit;h=0243aad65f4e40a8a2f1f4fa6fba3049dec29b28 > Breakout Media Capture Plugin for Android > - > > Key: CB-3700 > URL: https://issues.apache.org/jira/browse/CB-3700 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media Capture >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3700) Breakout Media Capture Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-3700: --- Assignee: Tim Kim > Breakout Media Capture Plugin for Android > - > > Key: CB-3700 > URL: https://issues.apache.org/jira/browse/CB-3700 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media Capture >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3640) Breakout Media Capture Plugin
[ https://issues.apache.org/jira/browse/CB-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-3640: --- Assignee: Tim Kim > Breakout Media Capture Plugin > - > > Key: CB-3640 > URL: https://issues.apache.org/jira/browse/CB-3640 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Media Capture >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > > Breakout the Media Capture Plugin for all platforms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3709) Breakout Media Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3709. - Resolution: Fixed > Breakout Media Plugin for Android > - > > Key: CB-3709 > URL: https://issues.apache.org/jira/browse/CB-3709 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3709) Breakout Media Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687440#comment-13687440 ] Tim Kim commented on CB-3709: - Mark it resolved: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;a=commit;h=c3ebb3e4f883bdc13ee94ce1f27cf4845e222955 > Breakout Media Plugin for Android > - > > Key: CB-3709 > URL: https://issues.apache.org/jira/browse/CB-3709 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3709) Breakout Media Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686219#comment-13686219 ] Tim Kim commented on CB-3709: - I've updated the plugin but it still throwing a few errors in mobile spec. Almost got this one down. https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;a=commit;h=a6be9efd168dc34cb8592441d847f05251241b94 > Breakout Media Plugin for Android > - > > Key: CB-3709 > URL: https://issues.apache.org/jira/browse/CB-3709 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3709) Breakout Media Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-3709: --- Assignee: Tim Kim > Breakout Media Plugin for Android > - > > Key: CB-3709 > URL: https://issues.apache.org/jira/browse/CB-3709 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3725) Breakout File Transfer Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683840#comment-13683840 ] Tim Kim commented on CB-3725: - Just tested on android and has the same number of tests passing as master branch. Using this plugin commit: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;a=commit;h=62e365cbc1f482cc629489d7e8e4bd3535f65da2 > Breakout File Transfer Plugin for Android > - > > Key: CB-3725 > URL: https://issues.apache.org/jira/browse/CB-3725 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File Transfer >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3725) Breakout File Transfer Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3725. - Resolution: Fixed > Breakout File Transfer Plugin for Android > - > > Key: CB-3725 > URL: https://issues.apache.org/jira/browse/CB-3725 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File Transfer >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3724) Breakout File Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682843#comment-13682843 ] Tim Kim commented on CB-3724: - Fixed up some stuff and tested: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;a=commit;h=1e6162e0e7bcc2f4b50a592ab1385465e0774e37 > Breakout File Plugin for Android > > > Key: CB-3724 > URL: https://issues.apache.org/jira/browse/CB-3724 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3724) Breakout File Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3724. - Resolution: Fixed > Breakout File Plugin for Android > > > Key: CB-3724 > URL: https://issues.apache.org/jira/browse/CB-3724 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3724) Breakout File Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-3724: --- Assignee: Tim Kim (was: Steve Gill) > Breakout File Plugin for Android > > > Key: CB-3724 > URL: https://issues.apache.org/jira/browse/CB-3724 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin File >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3660) Breakout Vibration Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681692#comment-13681692 ] Tim Kim commented on CB-3660: - Tested vibration plugin on this commit: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-vibration.git;a=commit;h=d592e6d08b545b881e3765963ddc779935bb3536 Works. > Breakout Vibration Plugin for Android > - > > Key: CB-3660 > URL: https://issues.apache.org/jira/browse/CB-3660 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Vibration >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3718) Breakout Globalization Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681663#comment-13681663 ] Tim Kim commented on CB-3718: - Had to merge in some changes and fix a few things, but looks good now: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-globalization.git;a=commit;h=46f5670be4ece571a389c9ab0858399b625ec4a8 > Breakout Globalization Plugin for Android > - > > Key: CB-3718 > URL: https://issues.apache.org/jira/browse/CB-3718 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Globalization >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3718) Breakout Globalization Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3718. - Resolution: Fixed > Breakout Globalization Plugin for Android > - > > Key: CB-3718 > URL: https://issues.apache.org/jira/browse/CB-3718 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Globalization >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3691) Breakout Geolocation Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3691. - Resolution: Fixed > Breakout Geolocation Plugin for Android > --- > > Key: CB-3691 > URL: https://issues.apache.org/jira/browse/CB-3691 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Geolocation >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3691) Breakout Geolocation Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681628#comment-13681628 ] Tim Kim commented on CB-3691: - Pushed up to apache repo: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=commit;h=16aab6d19a650ee55c938bb613e83bfbaee7c9a4 > Breakout Geolocation Plugin for Android > --- > > Key: CB-3691 > URL: https://issues.apache.org/jira/browse/CB-3691 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Geolocation >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3643) Breakout Globalization Plugin
[ https://issues.apache.org/jira/browse/CB-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680795#comment-13680795 ] Tim Kim commented on CB-3643: - Still need docs and cordova js needs to have globalization ripped out as well. > Breakout Globalization Plugin > - > > Key: CB-3643 > URL: https://issues.apache.org/jira/browse/CB-3643 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Globalization >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > > Breakout the Globalization Plugin for all platforms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3718) Breakout Globalization Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680793#comment-13680793 ] Tim Kim commented on CB-3718: - Updated plugin.xml and fixed here: https://github.com/timkim/cordova-plugin-globalization > Breakout Globalization Plugin for Android > - > > Key: CB-3718 > URL: https://issues.apache.org/jira/browse/CB-3718 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Globalization >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3691) Breakout Geolocation Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680790#comment-13680790 ] Tim Kim commented on CB-3691: - Welp, while the git servers are down I pushed to my github account: https://github.com/timkim/cordova-plugin-geolocation > Breakout Geolocation Plugin for Android > --- > > Key: CB-3691 > URL: https://issues.apache.org/jira/browse/CB-3691 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Geolocation >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3671) Breakout Battery Status Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680772#comment-13680772 ] Tim Kim commented on CB-3671: - Tested and looks good. Closing. > Breakout Battery Status Plugin for Android > -- > > Key: CB-3671 > URL: https://issues.apache.org/jira/browse/CB-3671 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Battery Status >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3671) Breakout Battery Status Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3671. - Resolution: Fixed > Breakout Battery Status Plugin for Android > -- > > Key: CB-3671 > URL: https://issues.apache.org/jira/browse/CB-3671 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Battery Status >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3509) network information javascript is tied into cordovajs
[ https://issues.apache.org/jira/browse/CB-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677532#comment-13677532 ] Tim Kim commented on CB-3509: - Ok, ya definitely not getting the deviceready event to fire. I'm not sure what the solution to fix this, will ping list. > network information javascript is tied into cordovajs > - > > Key: CB-3509 > URL: https://issues.apache.org/jira/browse/CB-3509 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaJS, Plugin Network Information >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > > cordovajs 3.0.0 branch > When we remove the network/connection javascript code from cordova-js, device > ready doesn't fire. Will need more investigation. > Remove code required by network information plugin from cordova js. > Build cordova js by running jake > Copy over newly created javascript files to android/ios 3.0.0 branches. > cordova-ios/CordovaLib/cordova.js > cordova-android/framework/assets/www/cordova.js > create android + ios projects using create scripts > run created projects, device ready doesn't fire. No need to even install > plugins. > Need to go to cordova-js and see why device ready doesn't fire after removing > these files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3509) network information javascript is tied into cordovajs
[ https://issues.apache.org/jira/browse/CB-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676505#comment-13676505 ] Tim Kim commented on CB-3509: - Oh wait, I didn't realise I had to rip out the common/network stuff - thought it had been done already. Let me try that again. > network information javascript is tied into cordovajs > - > > Key: CB-3509 > URL: https://issues.apache.org/jira/browse/CB-3509 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaJS, Plugin Network Information >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > > cordovajs 3.0.0 branch > When we remove the network/connection javascript code from cordova-js, device > ready doesn't fire. Will need more investigation. > Remove code required by network information plugin from cordova js. > Build cordova js by running jake > Copy over newly created javascript files to android/ios 3.0.0 branches. > cordova-ios/CordovaLib/cordova.js > cordova-android/framework/assets/www/cordova.js > create android + ios projects using create scripts > run created projects, device ready doesn't fire. No need to even install > plugins. > Need to go to cordova-js and see why device ready doesn't fire after removing > these files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3509) network information javascript is tied into cordovajs
[ https://issues.apache.org/jira/browse/CB-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676485#comment-13676485 ] Tim Kim commented on CB-3509: - Hrm, I just tested on device with android with the 3.0.0 branches and it seems to work okay. It did complain about the Network Connection class not being found in the logs though. I'll need to reconvene with Steve and ask him about the device ready not firing. > network information javascript is tied into cordovajs > - > > Key: CB-3509 > URL: https://issues.apache.org/jira/browse/CB-3509 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaJS, Plugin Network Information >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > > cordovajs 3.0.0 branch > When we remove the network/connection javascript code from cordova-js, device > ready doesn't fire. Will need more investigation. > Remove code required by network information plugin from cordova js. > Build cordova js by running jake > Copy over newly created javascript files to android/ios 3.0.0 branches. > cordova-ios/CordovaLib/cordova.js > cordova-android/framework/assets/www/cordova.js > create android + ios projects using create scripts > run created projects, device ready doesn't fire. No need to even install > plugins. > Need to go to cordova-js and see why device ready doesn't fire after removing > these files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3538) Update Upgrading Guide for 2.7.0 -> 2.8.0 for BlackBerry
[ https://issues.apache.org/jira/browse/CB-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3538: Assignee: Lorin Beer (was: Tim Kim) > Update Upgrading Guide for 2.7.0 -> 2.8.0 for BlackBerry > > > Key: CB-3538 > URL: https://issues.apache.org/jira/browse/CB-3538 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry, Docs >Reporter: Andrew Grieve >Assignee: Lorin Beer > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3509) network information javascript is tied into cordovajs
[ https://issues.apache.org/jira/browse/CB-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1386#comment-1386 ] Tim Kim commented on CB-3509: - Ok, I think I kinda figured out why deviceready isn't firing: 1) In the network.js file, it deals with firing the online/offline events for Cordova - so removing this will cause these events not to fire. 2) In the the android exec.js file, it uses the network online/offline events to start up the communication with the native side. 3) Therefore, the removal of the network.js file is not starting the js communication with the native side which is a good cause for the device ready event not firing. I'm not sure what a good work around for this right now. I'm too familiar with the internals of cordova js for android. I will seek help for this quest. > network information javascript is tied into cordovajs > - > > Key: CB-3509 > URL: https://issues.apache.org/jira/browse/CB-3509 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaJS, Plugin Network Information >Reporter: Steve Gill >Assignee: Tim Kim > Fix For: 3.0.0 > > > cordovajs 3.0.0 branch > When we remove the network/connection javascript code from cordova-js, device > ready doesn't fire. Will need more investigation. > Remove code required by network information plugin from cordova js. > Build cordova js by running jake > Copy over newly created javascript files to android/ios 3.0.0 branches. > cordova-ios/CordovaLib/cordova.js > cordova-android/framework/assets/www/cordova.js > create android + ios projects using create scripts > run created projects, device ready doesn't fire. No need to even install > plugins. > Need to go to cordova-js and see why device ready doesn't fire after removing > these files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665728#comment-13665728 ] Tim Kim commented on CB-3234: - Pushed up the changes here: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=ec82bfaa406860255cc1c4f3d5e49c9fd8a6b26a > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3234. - Resolution: Fixed > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664577#comment-13664577 ] Tim Kim commented on CB-3234: - Just tested on ios and android and got all three plugins installed on both platforms. The installation step is good, but the cordova/build step is causing compilation errors in Android. On ios, I can't build right now cause my xcode is out of date. Otherwise, it seems like the engine tag is good aside from those installation errors (pretty sure non-engine related). I'm going to merge this in after a few more tests. > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663432#comment-13663432 ] Tim Kim commented on CB-3234: - Ok, just tested with all three plugins with plain ole vanilla settings. Of the three plugins, the only one that works from the get-go is the GAPlugin. I get a weird compile error for PushPlugin and the FacebokConnect plugin complains about some config.xml issues. I'll update once I figure out what's going on. > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662178#comment-13662178 ] Tim Kim commented on CB-3234: - Not yet actually. I just had a simple dummy plugin that had an engine value in its plugin.xml. I'll give those ones a shot and see how they do. > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661084#comment-13661084 ] Tim Kim commented on CB-3234: - First pass here: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=eb363bee2e667115cdeacd8a6d34bccb83c4b23f > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3415) FileTransfer for BB10 should work with new File implementation
[ https://issues.apache.org/jira/browse/CB-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3415: Assignee: Lorin Beer (was: Tim Kim) > FileTransfer for BB10 should work with new File implementation > -- > > Key: CB-3415 > URL: https://issues.apache.org/jira/browse/CB-3415 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry > Environment: BB10 >Reporter: Hasan Ahmad >Assignee: Lorin Beer > > FileTransfer implementation should work with the new File implementation in > BB10 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3340) add version script
[ https://issues.apache.org/jira/browse/CB-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656469#comment-13656469 ] Tim Kim commented on CB-3340: - Added this in here: https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=3917284f713c5073262e4020cf372858291d428d Still needs some changes in the create script to copy this version file over as well as the windows version. > add version script > -- > > Key: CB-3340 > URL: https://issues.apache.org/jira/browse/CB-3340 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Affects Versions: 2.8.0 >Reporter: Brian LeRoux >Assignee: Benn Mapes > Fix For: 2.8.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3362) Native geolocation doesn't work anymore from 1.5.0 version
[
https://issues.apache.org/jira/browse/CB-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim updated CB-3362:
Assignee: Lorin Beer (was: Tim Kim)
> Native geolocation doesn't work anymore from 1.5.0 version
> ---
>
> Key: CB-3362
> URL: https://issues.apache.org/jira/browse/CB-3362
> Project: Apache Cordova
> Issue Type: Bug
> Components: BlackBerry
>Reporter: Ariel Falduto
>Assignee: Lorin Beer
> Labels: geolocation
>
> Hi guys, im not uderstand why native getCurrentPosition stop working from
> 1.5.0 version of phonegap ... probably you are making test with html5
> built-in getCurrentPosition in OS6+ ?? ... its a really huge mistake take a
> look ...
> the interfaces definitions / action names (and arguments too)...
> Phonegap 2.7:
> javascript:
> {code}
> exec(win, fail, "Geolocation", "getLocation", [options.enableHighAccuracy,
> options.maximumAge]);
> {code}
> java:
> {code}
> protected static int getAction(String action) {
> if ("watchPosition".equals(action)) return ACTION_WATCH;
> if ("stop".equals(action)) return ACTION_CLEAR_WATCH;
> if ("getCurrentPosition".equals(action)) return ACTION_GET_POSITION;
> if ("shutdown".endsWith(action)) return ACTION_SHUTDOWN;
> return -1;
> }
> {code}
> of course ... it never match the action specified ...
> but in Phonegap 1.5.0:
> javascript:
> {code}
> Cordova.exec(null, errorCallback, "Geolocation", "getCurrentPosition", [id,
> maximumAge, timeout, enableHighAccuracy]);
> {code}
> java:
> {code}
> protected static int getAction(String action) {
> if ("watchPosition".equals(action)) return ACTION_WATCH;
> if ("stop".equals(action)) return ACTION_CLEAR_WATCH;
> if ("getCurrentPosition".equals(action)) return ACTION_GET_POSITION;
> if ("shutdown".endsWith(action)) return ACTION_SHUTDOWN;
> return -1;
> }
> {code}
> it will be great to fix it soon ...
> thks !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3341) add version script
[ https://issues.apache.org/jira/browse/CB-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650153#comment-13650153 ] Tim Kim commented on CB-3341: - I've got a fix for this here on my github: https://github.com/timkim/cordova-blackberry/commit/5c598a08c0aaba3fd7ae17336e984fb1149f5126 I'm just waiting till the new bb10 repo takes over since I based my changes on that. > add version script > -- > > Key: CB-3341 > URL: https://issues.apache.org/jira/browse/CB-3341 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry >Affects Versions: 2.8.0 >Reporter: Brian LeRoux >Assignee: Tim Kim > Fix For: 2.8.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-3347) iOS ./cordova/version script
[ https://issues.apache.org/jira/browse/CB-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim closed CB-3347. --- Resolution: Fixed > iOS ./cordova/version script > - > > Key: CB-3347 > URL: https://issues.apache.org/jira/browse/CB-3347 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Affects Versions: 2.8.0 >Reporter: Tim Kim >Assignee: Tim Kim > Fix For: 2.8.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-3349) Windows ./cordova/version script
[ https://issues.apache.org/jira/browse/CB-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim closed CB-3349. --- Resolution: Invalid > Windows ./cordova/version script > - > > Key: CB-3349 > URL: https://issues.apache.org/jira/browse/CB-3349 > Project: Apache Cordova > Issue Type: Sub-task > Components: Windows 8 >Reporter: Tim Kim >Assignee: Tim Kim > Fix For: 2.8.0 > > > See top issue for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-3348) Android ./cordova/version script
[ https://issues.apache.org/jira/browse/CB-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim closed CB-3348. --- Resolution: Invalid > Android ./cordova/version script > - > > Key: CB-3348 > URL: https://issues.apache.org/jira/browse/CB-3348 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Reporter: Tim Kim >Assignee: Tim Kim > Fix For: 2.8.0 > > > See top issue for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-3346) BlackBerry ./cordova/version script
[ https://issues.apache.org/jira/browse/CB-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim closed CB-3346. --- Resolution: Fixed > BlackBerry ./cordova/version script > > > Key: CB-3346 > URL: https://issues.apache.org/jira/browse/CB-3346 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry >Affects Versions: 2.8.0 >Reporter: Tim Kim >Assignee: Tim Kim > Fix For: 2.8.0 > > > See top issue for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-3345) ./cordova/version script
[ https://issues.apache.org/jira/browse/CB-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim closed CB-3345. --- Resolution: Duplicate > ./cordova/version script > - > > Key: CB-3345 > URL: https://issues.apache.org/jira/browse/CB-3345 > Project: Apache Cordova > Issue Type: New Feature >Affects Versions: 2.7.0 >Reporter: Tim Kim > Fix For: 2.8.0 > > > The relevant discussion thread: http://markmail.org/thread/ibg4qm3wrzgy3apv > Basically we need a way to determine what version of Cordova is in a project > for plugin install. Since all the platforms currently have different ways of > determining this, a ./cordova/version script would be handy to have. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3345) ./cordova/version script
[ https://issues.apache.org/jira/browse/CB-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648764#comment-13648764 ] Tim Kim commented on CB-3345: - Gah, Brian and I created these duplicate issues at the same time: https://issues.apache.org/jira/browse/CB-3338 Closing this one and using the other. > ./cordova/version script > - > > Key: CB-3345 > URL: https://issues.apache.org/jira/browse/CB-3345 > Project: Apache Cordova > Issue Type: New Feature >Affects Versions: 2.7.0 >Reporter: Tim Kim > Fix For: 2.8.0 > > > The relevant discussion thread: http://markmail.org/thread/ibg4qm3wrzgy3apv > Basically we need a way to determine what version of Cordova is in a project > for plugin install. Since all the platforms currently have different ways of > determining this, a ./cordova/version script would be handy to have. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3349) Windows ./cordova/version script
[ https://issues.apache.org/jira/browse/CB-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim reassigned CB-3349: --- Assignee: Tim Kim (was: Jesse MacFadyen) > Windows ./cordova/version script > - > > Key: CB-3349 > URL: https://issues.apache.org/jira/browse/CB-3349 > Project: Apache Cordova > Issue Type: Sub-task > Components: Windows 8 >Reporter: Tim Kim >Assignee: Tim Kim > Fix For: 2.8.0 > > > See top issue for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3318) Not able to write data into a file on BB10, same code is working fine for playbook and BB7. i am using cordova 2.7.0.
[ https://issues.apache.org/jira/browse/CB-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim updated CB-3318: Assignee: Lorin Beer (was: Tim Kim) > Not able to write data into a file on BB10, same code is working fine for > playbook and BB7. i am using cordova 2.7.0. > - > > Key: CB-3318 > URL: https://issues.apache.org/jira/browse/CB-3318 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Reporter: ankit agarwal >Assignee: Lorin Beer > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3348) Android ./cordova/version script
Tim Kim created CB-3348: --- Summary: Android ./cordova/version script Key: CB-3348 URL: https://issues.apache.org/jira/browse/CB-3348 Project: Apache Cordova Issue Type: Sub-task Components: Android Reporter: Tim Kim Assignee: Tim Kim Fix For: 2.8.0 See top issue for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3349) Windows ./cordova/version script
Tim Kim created CB-3349: --- Summary: Windows ./cordova/version script Key: CB-3349 URL: https://issues.apache.org/jira/browse/CB-3349 Project: Apache Cordova Issue Type: Sub-task Components: Windows 8 Reporter: Tim Kim Assignee: Jesse MacFadyen Fix For: 2.8.0 See top issue for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3347) iOS ./cordova/version script
Tim Kim created CB-3347: --- Summary: iOS ./cordova/version script Key: CB-3347 URL: https://issues.apache.org/jira/browse/CB-3347 Project: Apache Cordova Issue Type: Sub-task Components: iOS Affects Versions: 2.8.0 Reporter: Tim Kim Assignee: Tim Kim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3345) ./cordova/version script
Tim Kim created CB-3345: --- Summary: ./cordova/version script Key: CB-3345 URL: https://issues.apache.org/jira/browse/CB-3345 Project: Apache Cordova Issue Type: New Feature Affects Versions: 2.7.0 Reporter: Tim Kim Fix For: 2.8.0 The relevant discussion thread: http://markmail.org/thread/ibg4qm3wrzgy3apv Basically we need a way to determine what version of Cordova is in a project for plugin install. Since all the platforms currently have different ways of determining this, a ./cordova/version script would be handy to have. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
