[jira] [Updated] (CB-4738) MediaError.message is not supported?
[
https://issues.apache.org/jira/browse/CB-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shingo Toda updated CB-4738:
Description:
I just tried to get an error message from MediaError.message but I failed. As I
see cordova.js, it seems that this property is not supported.
{code:title=cordova.js|borderStyle=solid}
var _MediaError = window.MediaError;
if(!_MediaError) {
window.MediaError = _MediaError = function(code, msg) {
this.code = (typeof code != 'undefined') ? code : null;
this.message = msg || ""; // message is NON-standard! do not use!
};
}
{code}
This is just my assumption that it look like Cordova try to get browser's
MediaError at first. If it fails, Cordova will add original implementation. But
as commented, message property is not standard in W3C
[http://dev.w3.org/html5/spec-author-view/video.html#mediaerror]
If it is really not supported, please remove this property from document.
was:
I just tried to get an error message from MediaError.message but I failed. As I
see cordova.js, it seems that this property is not supported.
{code:title=cordova.js|borderStyle=solid}
var _MediaError = window.MediaError;
if(!_MediaError) {
window.MediaError = _MediaError = function(code, msg) {
this.code = (typeof code != 'undefined') ? code : null;
this.message = msg || ""; // message is NON-standard! do not use!
};
}
{code}
If so, please remove this property from document.
> MediaError.message is not supported?
>
>
> Key: CB-4738
> URL: https://issues.apache.org/jira/browse/CB-4738
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
>
> I just tried to get an error message from MediaError.message but I failed. As
> I see cordova.js, it seems that this property is not supported.
> {code:title=cordova.js|borderStyle=solid}
> var _MediaError = window.MediaError;
> if(!_MediaError) {
> window.MediaError = _MediaError = function(code, msg) {
> this.code = (typeof code != 'undefined') ? code : null;
> this.message = msg || ""; // message is NON-standard! do not use!
> };
> }
> {code}
> This is just my assumption that it look like Cordova try to get browser's
> MediaError at first. If it fails, Cordova will add original implementation.
> But as commented, message property is not standard in W3C
> [http://dev.w3.org/html5/spec-author-view/video.html#mediaerror]
> If it is really not supported, please remove this property from document.
--
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-4738) MediaError.message is not supported?
[
https://issues.apache.org/jira/browse/CB-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shingo Toda updated CB-4738:
Description:
I just tried to get an error message from MediaError.message but I failed. As I
see cordova.js, it seems that this property is not supported.
{code:title=cordova.js|borderStyle=solid}
var _MediaError = window.MediaError;
if(!_MediaError) {
window.MediaError = _MediaError = function(code, msg) {
this.code = (typeof code != 'undefined') ? code : null;
this.message = msg || ""; // message is NON-standard! do not use!
};
}
{code}
If so, please remove this property from document.
was:
I just tried to get an error message from MediaError.message but I failed. As I
see cordova.js, it seems that this property is not supported.
{code:title=cordova.js|borderStyle=solid}
if(!_MediaError) {
window.MediaError = _MediaError = function(code, msg) {
this.code = (typeof code != 'undefined') ? code : null;
this.message = msg || ""; // message is NON-standard! do not use!
};
}
{code}
If so, please remove this property from document.
> MediaError.message is not supported?
>
>
> Key: CB-4738
> URL: https://issues.apache.org/jira/browse/CB-4738
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
>
> I just tried to get an error message from MediaError.message but I failed. As
> I see cordova.js, it seems that this property is not supported.
> {code:title=cordova.js|borderStyle=solid}
> var _MediaError = window.MediaError;
> if(!_MediaError) {
> window.MediaError = _MediaError = function(code, msg) {
> this.code = (typeof code != 'undefined') ? code : null;
> this.message = msg || ""; // message is NON-standard! do not use!
> };
> }
> {code}
> If so, please remove this property from document.
--
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-4738) MediaError.message is not supported?
Shingo Toda created CB-4738:
---
Summary: MediaError.message is not supported?
Key: CB-4738
URL: https://issues.apache.org/jira/browse/CB-4738
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 2.9.0
Reporter: Shingo Toda
Assignee: Michael Brooks
Priority: Minor
I just tried to get an error message from MediaError.message but I failed. As I
see cordova.js, it seems that this property is not supported.
{code:title=cordova.js|borderStyle=solid}
if(!_MediaError) {
window.MediaError = _MediaError = function(code, msg) {
this.code = (typeof code != 'undefined') ? code : null;
this.message = msg || ""; // message is NON-standard! do not use!
};
}
{code}
If so, please remove this property from document.
--
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-4492) Ensure download counts from plugman-registry are being tracked
[
https://issues.apache.org/jira/browse/CB-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757432#comment-13757432
]
Andrew Grieve commented on CB-4492:
---
Original Commit:
https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=cfa431bc0eca19398a3ca5e3ba79029e42d85104
One question about the code:
{quote}
75 // Update the download count for this plugin.
76 // Fingers crossed that the timestamps are unique, and
that no plugin is downloaded
77 // twice in a single millisecond.
{quote}
Where do the milliseconds come into play? I just see day-month-year being
inserting into the JSON. Does couch not handle Date objects? is there no syntax
to have couch use the server timestamp?
Also wondering if we can have the plugin version included in the download
record. That way we can see how many people are upgrading vs. not for a plugin.
> Ensure download counts from plugman-registry are being tracked
> --
>
> Key: CB-4492
> URL: https://issues.apache.org/jira/browse/CB-4492
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugman
>Reporter: Andrew Grieve
>Assignee: Braden Shepherdson
>
> Don't need to have a dashboard or anything fancy at the start, but we should
> be able to manually query download counts of plugin fetches.
--
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-4400) can't build from some "www" subdirs
[ https://issues.apache.org/jira/browse/CB-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve updated CB-4400: -- Assignee: Mark Koudritsky (was: Filip Maj) > can't build from some "www" subdirs > --- > > Key: CB-4400 > URL: https://issues.apache.org/jira/browse/CB-4400 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac >Reporter: Mike Sierra >Assignee: Mark Koudritsky >Priority: Minor > > With various platforms installed, run "cordova build" from platforms/ios/www. > Fails, but OK to run cmd from elsewhere. Output: > Ulothrix:ios sierra$ pwd > /Users/sierra/sandbox/pg/hello/platforms/ios > Ulothrix:ios sierra$ cd www > Ulothrix:www sierra$ cordova platforms > [ 'android', 'blackberry10', 'ios' ] > Ulothrix:www sierra$ cordova build > [Error: An error occurred while building the blackberry10 project. > shell-init: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > node.js:810 > var cwd = process.cwd(); > ^ > Error: ENOENT, no such file or directory > at Function.startup.resolveArgv0 (node.js:810:23) > at startup (node.js:58:13) > at node.js:901:3 > ] > Ulothrix:www sierra$ cd .. > Ulothrix:ios sierra$ cordova build > Ulothrix:ios sierra$ -- 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-4622) Allow git URLs to contain tags / hashes
[ https://issues.apache.org/jira/browse/CB-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756993#comment-13756993 ] ASF subversion and git services commented on CB-4622: - Commit 73c3aa72046dd649d4dca6660c983ff540f1d01d in branch refs/heads/master from [~shepheb] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=73c3aa7 ] [CB-4622]: Allow git URLs with a hash specifying git ref and subdir Format is https://github.com/foo/bar.git#gitref:subdir. Subdir is optional, so #gitref is valid, and git refs can be omitted to use HEAD with some subdir (#:subdir). > Allow git URLs to contain tags / hashes > --- > > Key: CB-4622 > URL: https://issues.apache.org/jira/browse/CB-4622 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Reporter: Andrew Grieve >Assignee: Mark Koudritsky > > plugman.fetch allows you to pass in a git ref to checkout after fetching. > It's not currently exposed by the command-line though (only exposed through > CLI) > Instead of having this as a separate argument to the fetch function, we > should build it into the URL. > NPM (refer to https://npmjs.org/doc/install.html): uses > ://[@][#] > We also need to specify a sub-directory, so let's use: > ://[@][#][:subdir] > subdir does *not* start with a /. > Our 3.0 instruction could then look like: > "Install via plugman install http://.../cordova-plugin-geolocation.git#stable"; > Note that we'll also need to update tag handling to allow this > format of URIs (might just be a docs update) -- 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-4588) Documentation for notification.confirm should say to pass buttonLabels as Array
[
https://issues.apache.org/jira/browse/CB-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757173#comment-13757173
]
Peter commented on CB-4588:
---
Thanks for the change, but shouldn't the new description say
{quote}
Array of strings specifying button labels. _(Array)_ (Optional, defaults to
[`OK,Cancel`])
{quote}
(with the square brackets) instead of
{quote}
Array of strings specifying button labels. _(Array)_ (Optional, defaults to
`OK,Cancel`)
{quote}
> Documentation for notification.confirm should say to pass buttonLabels as
> Array
> ---
>
> Key: CB-4588
> URL: https://issues.apache.org/jira/browse/CB-4588
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> Compare navigator.notification.confirm and navigator.notification.prompt.
> Both APIs allow caller to specifiy *buttonLabels* as 4th parameter, but
> confirm expects a comma separated String and prompt expects an array. The
> parameter passing mechanism should be consistent for these similar APIs.
> It looks like the cordova.js is already handling the scenario, because it
> says:
> {code}
> console.log("Notification.confirm(string, function, string, string) is
> deprecated. Use Notification.confirm(string, function, string, array).");
> {code}
> But the documentation for navigator.confirm is out-of-step with the code; it
> should be updated to say to pass Array, not String.
> Seems related to CB-1933
--
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] [Reopened] (CB-4588) Documentation for notification.confirm should say to pass buttonLabels as Array
[
https://issues.apache.org/jira/browse/CB-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter reopened CB-4588:
---
> Documentation for notification.confirm should say to pass buttonLabels as
> Array
> ---
>
> Key: CB-4588
> URL: https://issues.apache.org/jira/browse/CB-4588
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> Compare navigator.notification.confirm and navigator.notification.prompt.
> Both APIs allow caller to specifiy *buttonLabels* as 4th parameter, but
> confirm expects a comma separated String and prompt expects an array. The
> parameter passing mechanism should be consistent for these similar APIs.
> It looks like the cordova.js is already handling the scenario, because it
> says:
> {code}
> console.log("Notification.confirm(string, function, string, string) is
> deprecated. Use Notification.confirm(string, function, string, array).");
> {code}
> But the documentation for navigator.confirm is out-of-step with the code; it
> should be updated to say to pass Array, not String.
> Seems related to CB-1933
--
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-4494) "plugman info pluginID" should display extended info about plugin
[ https://issues.apache.org/jira/browse/CB-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anis Kadri resolved CB-4494. Resolution: Fixed Fix Version/s: 3.1.0 > "plugman info pluginID" should display extended info about plugin > - > > 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 > Fix For: 3.1.0 > > > 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-4494) "plugman info pluginID" should display extended info about plugin
[ https://issues.apache.org/jira/browse/CB-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757191#comment-13757191 ] ASF subversion and git services commented on CB-4494: - Commit 07d2a49edb26e7e91ec30e6681218e476bb31068 in branch refs/heads/master from [~anis] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=07d2a49 ] CB-4494 adding info command and storing engine data in registry > "plugman info pluginID" should display extended info about plugin > - > > 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-4071) Capture error callback (should be an object)
[
https://issues.apache.org/jira/browse/CB-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757179#comment-13757179
]
Joe Bowser commented on CB-4071:
[~jbondc] Did you get time to work on it? Ping us on the mailing list about it
so we don't forget.
> Capture error callback (should be an object)
>
>
> Key: CB-4071
> URL: https://issues.apache.org/jira/browse/CB-4071
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Docs, iOS, Windows 8
>Affects Versions: 2.9.0
> Environment: All
>Reporter: Jonathan Bond-Caron
>Assignee: Joe Bowser
> Fix For: 3.1.0
>
>
> When using camera.getPicture(), the cameraError is documented as a string but
> on Android & iOS, it's actually an object.
> On the native side in 2.7:
> Android:
> private static final int CAPTURE_INTERNAL_ERR = 0;
> // private static final int CAPTURE_APPLICATION_BUSY = 1;
> // private static final int CAPTURE_INVALID_ARGUMENT = 2;
>
> private static final int CAPTURE_NO_MEDIA_FILES = 3;
> iOS:
> enum CDVCaptureError {
>
> CAPTURE_INTERNAL_ERR = 0,
>
> CAPTURE_APPLICATION_BUSY = 1,
>
> CAPTURE_INVALID_ARGUMENT = 2,
>
> CAPTURE_NO_MEDIA_FILES = 3,
>
> CAPTURE_NOT_SUPPORTED = 20
> };
> Windows 8:
> only string errors
> Android and iOS have the same looking api on the native side, error callback
> Android returns JSON: {message: '', code: int}, iOS returns JSON: {message:
> '', status: int},
> Looking at the javascript api, it looks like it should return a 'new
> CaptureError()' on the errorCallback, is that the direction for 3.0?
> Windows only sends a string as the callback error, it's difficult to know if
> the user just cancelled taking a picture or what kind of specific error
> occurred.
> Should I look into creating a patch?
> This probably affects other apis, overall I'd like to see the CaptureError()
> returned more consistently instead of strings.
> It would make sense to improve this in 3.0 and possibly break BC for those
> expecting strings.
> CaptureError() could implement 'toString()' to mitigate potential issues.
--
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-4736) LocalFileSystem requestFileSystem function
Lorin Beer created CB-4736: -- Summary: LocalFileSystem requestFileSystem function Key: CB-4736 URL: https://issues.apache.org/jira/browse/CB-4736 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Lorin Beer Assignee: Michael Brooks Fix For: 3.1.0 write full documentation for the LocalFileSystem function -- 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-4725) device.cordova returns 'dev' on Android
[ https://issues.apache.org/jira/browse/CB-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756968#comment-13756968 ] Andrew Grieve commented on CB-4725: --- We drop the git hash for release versions > device.cordova returns 'dev' on Android > --- > > Key: CB-4725 > URL: https://issues.apache.org/jira/browse/CB-4725 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Device >Affects Versions: 3.0.0 > Environment: Android >Reporter: Stefan Dobrev >Assignee: Andrew Grieve >Priority: Minor > > device.cordova returns 'dev' on Android platform. Expected value is '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] [Created] (CB-4737) LocalFileSystem resolveLocalFileSystemURI function documentation
Lorin Beer created CB-4737: -- Summary: LocalFileSystem resolveLocalFileSystemURI function documentation Key: CB-4737 URL: https://issues.apache.org/jira/browse/CB-4737 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Lorin Beer Assignee: Michael Brooks Fix For: 3.1.0 write full documentation for the resolveLocalFileSytemURI function -- 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-4527) Unix and Windows Scripts should both be included in a project
[
https://issues.apache.org/jira/browse/CB-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser reassigned CB-4527:
--
Assignee: Joe Bowser (was: Benn Mapes)
> Unix and Windows Scripts should both be included in a project
> -
>
> Key: CB-4527
> URL: https://issues.apache.org/jira/browse/CB-4527
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 3.0.0
>Reporter: Michael Brooks
>Assignee: Joe Bowser
>
> **Problem:**
> When a new Android project is created, only the OS-specific the
> platform-scripts ({{my-project/cordova/}}) are copied over.
> For example, on Windows only the batch files are copied; on Unix only the
> bash files are copied.
> **Solution:**
> Both sets of scripts should be copied.
> Many projects involve multiple collaborators. On Android, it is not uncommon
> for those collaborators to use both Windows and Unix. So, the generated
> Android project should support both environments.
> **Reference:**
> [phonegap/phonegap-cli#136|https://github.com/phonegap/phonegap-cli/issues/136#issuecomment-22238361]
--
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-4617) size parameter not documented for requestFileSystem method
[
https://issues.apache.org/jira/browse/CB-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorin Beer reassigned CB-4617:
--
Assignee: Lorin Beer (was: Michael Brooks)
> size parameter not documented for requestFileSystem method
> --
>
> Key: CB-4617
> URL: https://issues.apache.org/jira/browse/CB-4617
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> The 2nd parameter of requestFileSystem
> {code}
> window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onSuccess, onError);
> {code}
> is not documented anywhere in the online API guide. The examples always pass
> 0. Apparently (from looking at _cordova.js_) this parameter indicates how
> much storage space, in bytes the application expects to need, and 0 has some
> special meaning.
> Ref:
> http://cordova.apache.org/docs/en/2.9.0/cordova_file_file.md.html#LocalFileSystem
--
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-4617) size parameter not documented for requestFileSystem method
[
https://issues.apache.org/jira/browse/CB-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorin Beer resolved CB-4617.
Resolution: Fixed
resolution to CB-4736 addresses this.
> size parameter not documented for requestFileSystem method
> --
>
> Key: CB-4617
> URL: https://issues.apache.org/jira/browse/CB-4617
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> The 2nd parameter of requestFileSystem
> {code}
> window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onSuccess, onError);
> {code}
> is not documented anywhere in the online API guide. The examples always pass
> 0. Apparently (from looking at _cordova.js_) this parameter indicates how
> much storage space, in bytes the application expects to need, and 0 has some
> special meaning.
> Ref:
> http://cordova.apache.org/docs/en/2.9.0/cordova_file_file.md.html#LocalFileSystem
--
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-4736) LocalFileSystem requestFileSystem function
[ https://issues.apache.org/jira/browse/CB-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer resolved CB-4736. Resolution: Fixed resolved, commit in comments > LocalFileSystem requestFileSystem function > -- > > Key: CB-4736 > URL: https://issues.apache.org/jira/browse/CB-4736 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.0.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 3.1.0 > > > write full documentation for the LocalFileSystem function -- 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-4660) Cordova Android project created using Cordova CLI is not compiling in eclipse.
[ https://issues.apache.org/jira/browse/CB-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-4660: --- Component/s: (was: App Hello World) (was: Android) Docs CLI Priority: Minor (was: Major) We need to support Eclipse and Android Studio better. It'd be good to have the steps reflected in a document. The point of the CLI is to avoid having to use Eclipse and speed up development. > Cordova Android project created using Cordova CLI is not compiling in eclipse. > -- > > Key: CB-4660 > URL: https://issues.apache.org/jira/browse/CB-4660 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, Docs >Affects Versions: 3.0.0 > Environment: Window 7, eclipse Juno, Android 2.3 - 4.3 >Reporter: Venkata Kiran >Assignee: Joe Bowser >Priority: Minor > > When an Android project is created using cordova command line and then > imported into eclipse, the blank project created is not compiling. > The following errors are shown during compilation. > error: Error: String types not allowed (at 'configChanges' with value > 'orientation|keyboardHidden|keyboard|screenSize|locale'). > error: No resource identifier found for attribute 'hardwareAccelerated' in > package 'android' > After changing the project target build to 18 from 10, then these errors are > resolved, but the below errors continue even before changing the API version > and also the API version. > DroidGap cannot be resolved to a type > Config cannot be resolved > The import org.apache.cordova cannot be resolved > The method onCreate(Bundle) of type HelloCordova must override or implement a > supertype method > The blank project created by cordova should compile without any issues. -- 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-4587) Console.log output does not work on Cordova 2.8.1 with Android 2.1
[ https://issues.apache.org/jira/browse/CB-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-4587. Resolution: Unresolved I know that console.log works on most models of phones, but it'd help if we knew what phone it was failing on. Please re-open the ticket and update this with the model of device so that we can continue work on this issue. > Console.log output does not work on Cordova 2.8.1 with Android 2.1 > -- > > Key: CB-4587 > URL: https://issues.apache.org/jira/browse/CB-4587 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 2.8.0 >Reporter: Thilo Planz >Assignee: Joe Bowser > Labels: android, compatibility, console > > Cordova 2.8.x is the last version to support Android 2.1, but it seems that > not everything actually works on that platform. > When you run the demo "HelloCordova" app that gets installed as a template by > the CLI tool on Android 2.1, there is no log output. (It is supposed to say > "report:deviceready" and that works on current Android). > The following error messages that appear on startup may be related: > 08-15 10:44:47.014: W/dalvikvm(316): VFY: unable to find class referenced in > signature (Landroid/webkit/ConsoleMessage;) > 08-15 10:44:47.014: I/dalvikvm(316): Could not find method > android.webkit.ConsoleMessage.message, referenced from method > org.apache.cordova.CordovaChromeClient.onConsoleMessage > 08-15 10:44:47.014: W/dalvikvm(316): VFY: unable to resolve virtual method > 299: Landroid/webkit/ConsoleMessage;.message ()Ljava/lang/String; > 08-15 10:44:47.023: D/dalvikvm(316): VFY: replacing opcode 0x6e at 0x > 08-15 10:44:47.023: D/dalvikvm(316): Making a copy of > Lorg/apache/cordova/CordovaChromeClient;.onConsoleMessage code (108 bytes) > 08-15 10:44:49.023: I/dalvikvm(316): Could not find method > android.util.Base64.encodeToString, referenced from method > org.apache.cordova.api.PluginResult. > 08-15 10:44:49.023: W/dalvikvm(316): VFY: unable to resolve static method > 265: Landroid/util/Base64;.encodeToString ([BI)Ljava/lang/String; > 08-15 10:44:49.023: D/dalvikvm(316): VFY: replacing opcode 0x71 at 0x0012 -- 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-4736) LocalFileSystem requestFileSystem function
[ https://issues.apache.org/jira/browse/CB-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757069#comment-13757069 ] ASF subversion and git services commented on CB-4736: - Commit 064d57ed82925481f5ae9a7402b8d43ef84b27ac in branch refs/heads/master from [~lorin] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=064d57e ] [CB-4736] documentation for the requestFileSystem function. Also addresses CB-4617 > LocalFileSystem requestFileSystem function > -- > > Key: CB-4736 > URL: https://issues.apache.org/jira/browse/CB-4736 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.0.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 3.1.0 > > > write full documentation for the LocalFileSystem function -- 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-4617) size parameter not documented for requestFileSystem method
[
https://issues.apache.org/jira/browse/CB-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757070#comment-13757070
]
ASF subversion and git services commented on CB-4617:
-
Commit 064d57ed82925481f5ae9a7402b8d43ef84b27ac in branch refs/heads/master
from [~lorin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=064d57e ]
[CB-4736] documentation for the requestFileSystem function. Also addresses
CB-4617
> size parameter not documented for requestFileSystem method
> --
>
> Key: CB-4617
> URL: https://issues.apache.org/jira/browse/CB-4617
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Michael Brooks
>Priority: Minor
>
> The 2nd parameter of requestFileSystem
> {code}
> window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onSuccess, onError);
> {code}
> is not documented anywhere in the online API guide. The examples always pass
> 0. Apparently (from looking at _cordova.js_) this parameter indicates how
> much storage space, in bytes the application expects to need, and 0 has some
> special meaning.
> Ref:
> http://cordova.apache.org/docs/en/2.9.0/cordova_file_file.md.html#LocalFileSystem
--
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-4736) LocalFileSystem requestFileSystem function
[ https://issues.apache.org/jira/browse/CB-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer reassigned CB-4736: -- Assignee: Lorin Beer (was: Michael Brooks) > LocalFileSystem requestFileSystem function > -- > > Key: CB-4736 > URL: https://issues.apache.org/jira/browse/CB-4736 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.0.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 3.1.0 > > > write full documentation for the LocalFileSystem function -- 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-4735) Support optional plugin dependancies
Michal Mocny created CB-4735: Summary: Support optional plugin dependancies Key: CB-4735 URL: https://issues.apache.org/jira/browse/CB-4735 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.0.0 Reporter: Michal Mocny Assignee: Braden Shepherdson plugins (and perhaps soon apps, and perhaps some future day platforms, too) support plugin dependencies. However, right now all dependents are mandatory for the successful use of the depending plugin. It would be nice to be able to list optional dependencies which allow for conditional enhancement, but are not a core requirement. One quick example: Logger for iOS would be a nice default dependency of the platform, but should be safely removeable, and CLI should remember and respect the users decision to remove it if they chose to. -- 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-4714) Allow removing a plugin that is a dependency (using -f or -force flag)
[ https://issues.apache.org/jira/browse/CB-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve updated CB-4714: -- Assignee: Braden Shepherdson (was: Andrew Grieve) > Allow removing a plugin that is a dependency (using -f or -force flag) > -- > > Key: CB-4714 > URL: https://issues.apache.org/jira/browse/CB-4714 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, Plugman >Affects Versions: 3.0.0 > Environment: Windows 8 >Reporter: Jonathan Bond-Caron >Assignee: Braden Shepherdson >Priority: Minor > Labels: patch > Fix For: 3.1.0 > > > Some context: > I wanted to start using the mobile spec app for cordova. The problem is I > didn't know which dependencies were required for the application. > So I created a plugin which just lists some dependencies: > https://github.com/jbondc/cordova-plugin-mobile-spec > > cordova create test > > cordova platform add android > >cordova plugin list > No plugins added. Use `cordova plugin add `. > >cordova plugin add https://github.com/jbondc/cordova-plugin-mobile-spec > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.file', > 'org.apache.cordova.core.media-capture', > 'org.apache.cordova.core.mobile-spec' ] > To test a modifications/patches to a specific plugin (media-capture), I > wanted to do: > >cordova plugin rm org.apache.cordova.core.media-capture > [Error: Another top-level plugin (org.apache.cordova.core.mobile-spec) relies > on plugin org.apache.cordova.core.media-capture, therefore aborting > uninstallation > .] > A lot of dependency management systems (freebsd ports, debian packages) allow > you to forcefully remove a dependency. > That's what I'm proposing: > >cordova plugin rm org.apache.cordova.core.media-capture -f > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.mobile-spec' ] > >cordova plugin add F:\Jonathan\GitHub\Cordova\cordova-plugin-media-capture > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.media-capture', > 'org.apache.cordova.core.mobile-spec' ] > It makes it easier to add/remove a plugin even if some dependencies are not > met. > -- 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-4497) SDK prerequisite in "Embedding Cordova WebView on Android" guide says needs API level 15
[ https://issues.apache.org/jira/browse/CB-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-4497. Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=blobdiff;f=docs/en/3.0.0/guide/platforms/android/webview.md;h=c3eb8f8ee768338514bc8b8814a0df7d193c0d6d;hp=dd45a3340a2c26263f29b804a5f3df495630cff9;hb=7cec63347ab4384854ea1559845cd34102e81327;hpb=f792d76afbc0e24988fa760d62f03f36722a0b22 > SDK prerequisite in "Embedding Cordova WebView on Android" guide says needs > API level 15 > > > Key: CB-4497 > URL: https://issues.apache.org/jira/browse/CB-4497 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Docs >Affects Versions: 2.9.0 >Reporter: Peter >Assignee: Joe Bowser >Priority: Minor > > The guide is misleading because it says "Android SDK updated with 15" is the > pre-requisite, when in fact there is nothing special about API level 15. It > turns out "You should actually have the latest Android SDK". > For more details, refer to dev-list: > http://markmail.org/message/r7zofsnqnbnvqgvl -- 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-4714) Allow removing a plugin that is a dependency (using -f or -force flag)
[ https://issues.apache.org/jira/browse/CB-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve reassigned CB-4714: - Assignee: Andrew Grieve (was: Braden Shepherdson) > Allow removing a plugin that is a dependency (using -f or -force flag) > -- > > Key: CB-4714 > URL: https://issues.apache.org/jira/browse/CB-4714 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, Plugman >Affects Versions: 3.0.0 > Environment: Windows 8 >Reporter: Jonathan Bond-Caron >Assignee: Andrew Grieve >Priority: Minor > Labels: patch > Fix For: 3.1.0 > > > Some context: > I wanted to start using the mobile spec app for cordova. The problem is I > didn't know which dependencies were required for the application. > So I created a plugin which just lists some dependencies: > https://github.com/jbondc/cordova-plugin-mobile-spec > > cordova create test > > cordova platform add android > >cordova plugin list > No plugins added. Use `cordova plugin add `. > >cordova plugin add https://github.com/jbondc/cordova-plugin-mobile-spec > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.file', > 'org.apache.cordova.core.media-capture', > 'org.apache.cordova.core.mobile-spec' ] > To test a modifications/patches to a specific plugin (media-capture), I > wanted to do: > >cordova plugin rm org.apache.cordova.core.media-capture > [Error: Another top-level plugin (org.apache.cordova.core.mobile-spec) relies > on plugin org.apache.cordova.core.media-capture, therefore aborting > uninstallation > .] > A lot of dependency management systems (freebsd ports, debian packages) allow > you to forcefully remove a dependency. > That's what I'm proposing: > >cordova plugin rm org.apache.cordova.core.media-capture -f > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.mobile-spec' ] > >cordova plugin add F:\Jonathan\GitHub\Cordova\cordova-plugin-media-capture > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.media-capture', > 'org.apache.cordova.core.mobile-spec' ] > It makes it easier to add/remove a plugin even if some dependencies are not > met. > -- 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-4054) WP8 file requests are not relative to www folder
[
https://issues.apache.org/jira/browse/CB-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-4054.
-
Resolution: Fixed
Fix Version/s: 3.1.0
Resolved along with CB-4421
> WP8 file requests are not relative to www folder
>
>
> Key: CB-4054
> URL: https://issues.apache.org/jira/browse/CB-4054
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs, Plugin File, WP8
>Affects Versions: 2.9.0
> Environment: Windows 8 x64
>Reporter: Frederico Costa Galvão
>Assignee: Jesse MacFadyen
> Labels: patch
> Fix For: 3.1.0
>
>
> I started migrating my app (http://tippz.mobi) to *WP8* and found that all
> files requested via js (xhr) are expected to be served relative to the
> project root (at least on development/emulator, but I can't imagine it to be
> different on other environments), which is not according to the way it
> happens on iOS and Android.
> On both iOS and Android, working directory for the code serving files via xhr
> is the 'www' folder (or is it the folder where my 'index.html' is located?),
> while on WP8 it is 'www/..' (the project root, in other words). Resources
> mapped directly on the html file however are served from the right directory
> on all cases.
> There is also no word about it on the docs, the only thing I found was an
> answer on stackoverflow.
> Adding the following code on line 717 of Plugins/File.cs@readResourceAsText()
> solved the problem (so far!, can't be sure it didn't have side effects as I
> could not make my app work well enough on WP8 yet):
> {code:java}
> pathToResource = "www/" + pathToResource;
> {code}
> Also, on the same method and file, +optStrings+ variable is expected to
> always have 5 fields, but everytime I ran my app Visual Studio threw me an
> exception because +optStrings+ never have more than 2 fields. I solved it
> surrounding remaining variables attribution with an if(optStrings.Length>2){}.
--
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-4622) Allow git URLs to contain tags / hashes
[ https://issues.apache.org/jira/browse/CB-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4622. Resolution: Fixed Assignee: Braden Shepherdson (was: Mark Koudritsky) > Allow git URLs to contain tags / hashes > --- > > Key: CB-4622 > URL: https://issues.apache.org/jira/browse/CB-4622 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Reporter: Andrew Grieve >Assignee: Braden Shepherdson > > plugman.fetch allows you to pass in a git ref to checkout after fetching. > It's not currently exposed by the command-line though (only exposed through > CLI) > Instead of having this as a separate argument to the fetch function, we > should build it into the URL. > NPM (refer to https://npmjs.org/doc/install.html): uses > ://[@][#] > We also need to specify a sub-directory, so let's use: > ://[@][#][:subdir] > subdir does *not* start with a /. > Our 3.0 instruction could then look like: > "Install via plugman install http://.../cordova-plugin-geolocation.git#stable"; > Note that we'll also need to update tag handling to allow this > format of URIs (might just be a docs update) -- 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-4734) Plugins are not added to frameworkModules.js
[ https://issues.apache.org/jira/browse/CB-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756957#comment-13756957 ] ASF subversion and git services commented on CB-4734: - Commit 29ba97c8b77fc939ad34f4992b53a50d3296145d in branch refs/heads/master from [~daudino] [ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=29ba97c ] [CB-4734] Fixed issue where plugins are not added to frameworkModules Reviewed By: Jeffrey Heifetz Tested By: Rowell Cruz > Plugins are not added to frameworkModules.js > > > Key: CB-4734 > URL: https://issues.apache.org/jira/browse/CB-4734 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Reporter: Daniel Audino >Assignee: Lorin Beer > > When building a project with plugins the index.js is not added to > frameworkModules.ks -- 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-4609) relative path to cordova.js & windows path
[
https://issues.apache.org/jira/browse/CB-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756898#comment-13756898
]
Braden Shepherdson commented on CB-4609:
Here's the commit, for the record:
https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=f276c21dc1e550316d9728361c2202c5a3338610
> relative path to cordova.js & windows path
> --
>
> Key: CB-4609
> URL: https://issues.apache.org/jira/browse/CB-4609
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, Plugman
>Affects Versions: 3.0.0
> Environment: Window 8, node v0.10.16
>Reporter: Jonathan Bond-Caron
>Assignee: Filip Maj
> Attachments: Result of 'plugin add'.jpg
>
>
> I'm experimenting with a new plugin:
> https://github.com/jbondc/cordova-plugin-gesture
> To reproduce:
> - Download https://github.com/jbondc/mtlhack-PhoneGap-gesture
> 1) Issue #1
> {code}
> cd cordova
> plugin add https://github.com/jbondc/cordova-plugin-gesture
> {code}
> Since cordova.js isn't in the default path (www/resources/cordova.js), the
> plugins gets copied to (www/plugins/) instead of (www/resources/js/plugins).
> The same for 'cordova_plugins.js' (see attached screenshot)
> Fix is likely in the cli/plugman to set find the appropriate root/base path
> to cordova.js
> 2) Issue #2
> Adding a plugin from a Windows path
> {code}
> cordova plugin add F:\Jonathan\GitHub\Cordova\cordova-plugin-gesture
> {code}
> In cordova_plugins.js, I see:
> {code}
> cordova.define('cordova/plugin_list', function(require, exports, module) {
> module.exports = [
> {
> "file": "plugins\\org.apache.cordova.core.Gesture\\www\\gesture.js",
> "id": "org.apache.cordova.core.Gesture.Gesture",
> "clobbers": [
> "cordova.gesture"
> ]
> }
> ]
> });
> {code}
> That path should be normalized to:
> "plugins/org.apache.cordova.core.Gesture/www/gesture.js"
> Fix is likely in cli/plugman:
> {code}path.replace("\\", "/"){code}
--
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-4609) relative path to cordova.js & windows path
[
https://issues.apache.org/jira/browse/CB-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756897#comment-13756897
]
Braden Shepherdson commented on CB-4609:
[~jbondc] can you check out the latest plugman from master, and use it? It's
working for me on Mac, but I want to make sure it's working on Windows.
Here's the incantation:
git clone https://git-wip-us.apache.org/repos/asf/cordova-plugman.git plugman
cd plugman
npm install
sudo npm link
cd ..
git clone https://git-wip-us.apache.org/repos/asf/cordova-cli.git
cd cordova-cli
npm install
sudo npm link
npm link plugman
Now you're running the latest versions of plugman and CLI. Then please test and
let me know if it's handling the paths correctly now.
> relative path to cordova.js & windows path
> --
>
> Key: CB-4609
> URL: https://issues.apache.org/jira/browse/CB-4609
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, Plugman
>Affects Versions: 3.0.0
> Environment: Window 8, node v0.10.16
>Reporter: Jonathan Bond-Caron
>Assignee: Filip Maj
> Attachments: Result of 'plugin add'.jpg
>
>
> I'm experimenting with a new plugin:
> https://github.com/jbondc/cordova-plugin-gesture
> To reproduce:
> - Download https://github.com/jbondc/mtlhack-PhoneGap-gesture
> 1) Issue #1
> {code}
> cd cordova
> plugin add https://github.com/jbondc/cordova-plugin-gesture
> {code}
> Since cordova.js isn't in the default path (www/resources/cordova.js), the
> plugins gets copied to (www/plugins/) instead of (www/resources/js/plugins).
> The same for 'cordova_plugins.js' (see attached screenshot)
> Fix is likely in the cli/plugman to set find the appropriate root/base path
> to cordova.js
> 2) Issue #2
> Adding a plugin from a Windows path
> {code}
> cordova plugin add F:\Jonathan\GitHub\Cordova\cordova-plugin-gesture
> {code}
> In cordova_plugins.js, I see:
> {code}
> cordova.define('cordova/plugin_list', function(require, exports, module) {
> module.exports = [
> {
> "file": "plugins\\org.apache.cordova.core.Gesture\\www\\gesture.js",
> "id": "org.apache.cordova.core.Gesture.Gesture",
> "clobbers": [
> "cordova.gesture"
> ]
> }
> ]
> });
> {code}
> That path should be normalized to:
> "plugins/org.apache.cordova.core.Gesture/www/gesture.js"
> Fix is likely in cli/plugman:
> {code}path.replace("\\", "/"){code}
--
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-4734) Plugins are not added to frameworkModules.js
Daniel Audino created CB-4734: - Summary: Plugins are not added to frameworkModules.js Key: CB-4734 URL: https://issues.apache.org/jira/browse/CB-4734 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Reporter: Daniel Audino Assignee: Lorin Beer When building a project with plugins the index.js is not added to frameworkModules.ks -- 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-4648) FileReader example code is incorrect
[
https://issues.apache.org/jira/browse/CB-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorin Beer resolved CB-4648.
Resolution: Fixed
corrected error callback parameter names, commit in comments
> FileReader example code is incorrect
>
>
> Key: CB-4648
> URL: https://issues.apache.org/jira/browse/CB-4648
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Michael Brooks
>Priority: Minor
>
> In the File API guide it seems almost all of the FileReader example code is
> incorrect for the error callbacks.
> For example,
> * readAsDataURL QuickExample - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
> * readAsText Quick Example - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
> * readAsText Full example - evt arg should be error?
> console.log(evt.target.error.code) should be console.log(error.code)?
> {code}
> function fail(evt) {
> console.log(evt.target.error.code);
> }
> {code}
> * readAsBinaryString - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
> * readAsArrayBuffer - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
--
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-4648) FileReader example code is incorrect
[
https://issues.apache.org/jira/browse/CB-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756927#comment-13756927
]
ASF subversion and git services commented on CB-4648:
-
Commit 80df88110a7ca8eff9d7a7087885c1b62dfc5e53 in branch refs/heads/master
from [~lorin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=80df881 ]
[CB-4648] corrected error callback parameter names
> FileReader example code is incorrect
>
>
> Key: CB-4648
> URL: https://issues.apache.org/jira/browse/CB-4648
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Michael Brooks
>Priority: Minor
>
> In the File API guide it seems almost all of the FileReader example code is
> incorrect for the error callbacks.
> For example,
> * readAsDataURL QuickExample - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
> * readAsText Quick Example - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
> * readAsText Full example - evt arg should be error?
> console.log(evt.target.error.code) should be console.log(error.code)?
> {code}
> function fail(evt) {
> console.log(evt.target.error.code);
> }
> {code}
> * readAsBinaryString - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
> * readAsArrayBuffer - evt should be error?
> {code}
> var fail = function (evt) {
> console.log(error.code);
> };
> {code}
--
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-3904) List all platforms
[ https://issues.apache.org/jira/browse/CB-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-3904. Resolution: Fixed Fix Version/s: 3.1.0 Done. No "unavailable" section. That's implementable, but I'm not convinced it's that helpful. The "available" list is NOT based on the check_reqs scripts; those aren't to hand unless the platform is already downloaded, which it may not be. So instead it's just whether the platform can be installed in principle: ie. whether your platform support it at all. Therefore, Android and BB10 are always available, ios is only available when os.platform() === 'darwin', and wp7+8 only when os.platform() === 'win32'. > List all platforms > -- > > Key: CB-3904 > URL: https://issues.apache.org/jira/browse/CB-3904 > Project: Apache Cordova > Issue Type: Wish > Components: CLI >Reporter: Mike Sierra >Assignee: Braden Shepherdson > Fix For: 3.1.0 > > > Current "platform ls" lists currently installed platforms. Ideally it should > also present a separate list of platforms available for installation. Perhaps > also list platforms potentially available if running the command on another > machine. Suggested output: > Installed: ios, android > Available: blackberry > Unavailable on this machine: win7, win8 -- 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] [Comment Edited] (CB-4725) device.cordova returns 'dev' on Android
[ https://issues.apache.org/jira/browse/CB-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756869#comment-13756869 ] Stefan Dobrev edited comment on CB-4725 at 9/3/13 6:25 PM: --- I saw that we are setting the version to the CORDOVA_JS_BUILD_LABEL constant which has the format of [versionNumber]-[commitId]. This will break the backward compatibility because the version should be without the commitId. was (Author: sdobrev): I saw that we are setting the version to the CORDOVA_JS_BUILD_LABEL constant which has the format of [versionNumber]-[commitId]. This will break the backwords compatibility because the version should be without the commitId. > device.cordova returns 'dev' on Android > --- > > Key: CB-4725 > URL: https://issues.apache.org/jira/browse/CB-4725 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Device >Affects Versions: 3.0.0 > Environment: Android >Reporter: Stefan Dobrev >Assignee: Andrew Grieve >Priority: Minor > > device.cordova returns 'dev' on Android platform. Expected value is '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-4725) device.cordova returns 'dev' on Android
[ https://issues.apache.org/jira/browse/CB-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756869#comment-13756869 ] Stefan Dobrev commented on CB-4725: --- I saw that we are setting the version to the CORDOVA_JS_BUILD_LABEL constant which has the format of [versionNumber]-[commitId]. This will break the backwords compatibility because the version should be without the commitId. > device.cordova returns 'dev' on Android > --- > > Key: CB-4725 > URL: https://issues.apache.org/jira/browse/CB-4725 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Device >Affects Versions: 3.0.0 > Environment: Android >Reporter: Stefan Dobrev >Assignee: Andrew Grieve >Priority: Minor > > device.cordova returns 'dev' on Android platform. Expected value is '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-3904) List all platforms
[ https://issues.apache.org/jira/browse/CB-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756828#comment-13756828 ] ASF subversion and git services commented on CB-3904: - Commit 66f15d23fd783746d2955e080a0aa90b59c8a045 in branch refs/heads/master from [~shepheb] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=66f15d2 ] [CB-3904]: platform ls now shows installed and available platforms. > List all platforms > -- > > Key: CB-3904 > URL: https://issues.apache.org/jira/browse/CB-3904 > Project: Apache Cordova > Issue Type: Wish > Components: CLI >Reporter: Mike Sierra >Assignee: Braden Shepherdson > > Current "platform ls" lists currently installed platforms. Ideally it should > also present a separate list of platforms available for installation. Perhaps > also list platforms potentially available if running the command on another > machine. Suggested output: > Installed: ios, android > Available: blackberry > Unavailable on this machine: win7, win8 -- 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-4733) webworks build or run reverts the content under www back to be the default content
[ https://issues.apache.org/jira/browse/CB-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tracy Li closed CB-4733. Resolution: Not A Problem according to Jeff, it's an expected behavior. > webworks build or run reverts the content under www back to be the default > content > -- > > Key: CB-4733 > URL: https://issues.apache.org/jira/browse/CB-4733 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Reporter: Tracy Li >Assignee: Lorin Beer > > 1.webworks create sampleTest > 2.cd sampleTest/platforms/blackberry10/www > 3.modify config.xml > 4.webworks target add London 169.254.0.1 > 5.webworks build --debug or webworks run London > expected: bar file can be generated > fact: the content under sampleTest/platforms/blackberry10/www have been > changed to the default content and the bar file generated is based on the > default content -- 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-4588) Documentation for notification.confirm should say to pass buttonLabels as Array
[
https://issues.apache.org/jira/browse/CB-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorin Beer resolved CB-4588.
Resolution: Fixed
resovled, commits in comments
> Documentation for notification.confirm should say to pass buttonLabels as
> Array
> ---
>
> Key: CB-4588
> URL: https://issues.apache.org/jira/browse/CB-4588
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> Compare navigator.notification.confirm and navigator.notification.prompt.
> Both APIs allow caller to specifiy *buttonLabels* as 4th parameter, but
> confirm expects a comma separated String and prompt expects an array. The
> parameter passing mechanism should be consistent for these similar APIs.
> It looks like the cordova.js is already handling the scenario, because it
> says:
> {code}
> console.log("Notification.confirm(string, function, string, string) is
> deprecated. Use Notification.confirm(string, function, string, array).");
> {code}
> But the documentation for navigator.confirm is out-of-step with the code; it
> should be updated to say to pass Array, not String.
> Seems related to CB-1933
--
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-4588) Documentation for notification.confirm should say to pass buttonLabels as Array
[
https://issues.apache.org/jira/browse/CB-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756822#comment-13756822
]
ASF subversion and git services commented on CB-4588:
-
Commit 15ee26ddf96337a2908cc48f6537da122c3dadce in branch refs/heads/master
from [~lorin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=15ee26d ]
[CB-4588] updated button labels example code to use array syntax, from
deprecated comma separated string syntax
> Documentation for notification.confirm should say to pass buttonLabels as
> Array
> ---
>
> Key: CB-4588
> URL: https://issues.apache.org/jira/browse/CB-4588
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> Compare navigator.notification.confirm and navigator.notification.prompt.
> Both APIs allow caller to specifiy *buttonLabels* as 4th parameter, but
> confirm expects a comma separated String and prompt expects an array. The
> parameter passing mechanism should be consistent for these similar APIs.
> It looks like the cordova.js is already handling the scenario, because it
> says:
> {code}
> console.log("Notification.confirm(string, function, string, string) is
> deprecated. Use Notification.confirm(string, function, string, array).");
> {code}
> But the documentation for navigator.confirm is out-of-step with the code; it
> should be updated to say to pass Array, not String.
> Seems related to CB-1933
--
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-4588) Documentation for notification.confirm should say to pass buttonLabels as Array
[
https://issues.apache.org/jira/browse/CB-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756821#comment-13756821
]
ASF subversion and git services commented on CB-4588:
-
Commit 4c962ee28026f31ce63250ef2a5f6ff8f7fc277f in branch refs/heads/master
from [~lorin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=4c962ee ]
[CB-4588] updated function parameter description to button labels as array of
strings
> Documentation for notification.confirm should say to pass buttonLabels as
> Array
> ---
>
> Key: CB-4588
> URL: https://issues.apache.org/jira/browse/CB-4588
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> Compare navigator.notification.confirm and navigator.notification.prompt.
> Both APIs allow caller to specifiy *buttonLabels* as 4th parameter, but
> confirm expects a comma separated String and prompt expects an array. The
> parameter passing mechanism should be consistent for these similar APIs.
> It looks like the cordova.js is already handling the scenario, because it
> says:
> {code}
> console.log("Notification.confirm(string, function, string, string) is
> deprecated. Use Notification.confirm(string, function, string, array).");
> {code}
> But the documentation for navigator.confirm is out-of-step with the code; it
> should be updated to say to pass Array, not String.
> Seems related to CB-1933
--
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-4625) The File API online guide has some bad hyperlinks
[ https://issues.apache.org/jira/browse/CB-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756823#comment-13756823 ] ASF subversion and git services commented on CB-4625: - Commit 2ba0b3f7b1e20bf5a225610f5992e618e4f01da9 in branch refs/heads/master from [~lorin] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=2ba0b3f ] [CB-4625] lower case the w3c reference to avoid match and replace > The File API online guide has some bad hyperlinks > - > > Key: CB-4625 > URL: https://issues.apache.org/jira/browse/CB-4625 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 2.9.0 >Reporter: Peter >Assignee: Lorin Beer >Priority: Minor > > The ambiguity between "File" (the API) and "File" (the Object) causes some > hyperlink problems > * see "...based on the W3C File API" should only link to > http://www.w3.org/TR/FileAPI/ ; not to #File, > * see "File" in the Objects list - #File anchor name is duplicated so does > not go where expected -- 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-4733) webworks build or run reverts the content under www back to be the default content
Tracy Li created CB-4733: Summary: webworks build or run reverts the content under www back to be the default content Key: CB-4733 URL: https://issues.apache.org/jira/browse/CB-4733 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Reporter: Tracy Li Assignee: Lorin Beer 1.webworks create sampleTest 2.cd sampleTest/platforms/blackberry10/www 3.modify config.xml 4.webworks target add London 169.254.0.1 5.webworks build --debug or webworks run London expected: bar file can be generated fact: the content under sampleTest/platforms/blackberry10/www have been changed to the default content and the bar file generated is based on the default content -- 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-4644) File API documentation - FileReader headings are incorrect
[ https://issues.apache.org/jira/browse/CB-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer reassigned CB-4644: -- Assignee: Lorin Beer (was: Michael Brooks) > File API documentation - FileReader headings are incorrect > -- > > Key: CB-4644 > URL: https://issues.apache.org/jira/browse/CB-4644 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 2.9.0 >Reporter: Peter >Assignee: Lorin Beer >Priority: Minor > > Many the headings in the *FileReader* section are incorrect and/or > inconsistent with other sections making it difficult to read > For example, > * "Read As Data URL" - this is a function name. Heading should be > "readAsDataURL" > * Quick Example for readAsDataURL - should be h3 not h2 > * "Abort Quick Example" - should be h2 "abort" (because it is a function name) > * This abort section seems misplaced - it is currently between the Quick and > Full example for readAsText? > * "Quick Example" should be h3. > * "Read As Text" - this is a function name. Heading should be "readAsText" > * Quick Example for readAsText - should be h3 not h2 > * Full Example for readAsText - should be h3 instead of h2 > * iOS Quirks for readAsText - should be h3 not h2 > * "Read As Binary String" - this is a function name. Heading should be > "readAsBinaryString" > * Quick Example for readAsBinaryString - should be h3 not h2 > * "Read As Array Buffer" - this is a function name. Heading should be > "readAsArrayBuffer" > * Quick Example for readAsArrayBuffer - should be h3 not h2 -- 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-4644) File API documentation - FileReader headings are incorrect
[ https://issues.apache.org/jira/browse/CB-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer resolved CB-4644. Resolution: Fixed resolved, commit in comments > File API documentation - FileReader headings are incorrect > -- > > Key: CB-4644 > URL: https://issues.apache.org/jira/browse/CB-4644 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 2.9.0 >Reporter: Peter >Assignee: Lorin Beer >Priority: Minor > > Many the headings in the *FileReader* section are incorrect and/or > inconsistent with other sections making it difficult to read > For example, > * "Read As Data URL" - this is a function name. Heading should be > "readAsDataURL" > * Quick Example for readAsDataURL - should be h3 not h2 > * "Abort Quick Example" - should be h2 "abort" (because it is a function name) > * This abort section seems misplaced - it is currently between the Quick and > Full example for readAsText? > * "Quick Example" should be h3. > * "Read As Text" - this is a function name. Heading should be "readAsText" > * Quick Example for readAsText - should be h3 not h2 > * Full Example for readAsText - should be h3 instead of h2 > * iOS Quirks for readAsText - should be h3 not h2 > * "Read As Binary String" - this is a function name. Heading should be > "readAsBinaryString" > * Quick Example for readAsBinaryString - should be h3 not h2 > * "Read As Array Buffer" - this is a function name. Heading should be > "readAsArrayBuffer" > * Quick Example for readAsArrayBuffer - should be h3 not h2 -- 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-4644) File API documentation - FileReader headings are incorrect
[ https://issues.apache.org/jira/browse/CB-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756839#comment-13756839 ] ASF subversion and git services commented on CB-4644: - Commit 87c6d9b80394bf34f8b0b488323c9ad7c0b21fa1 in branch refs/heads/master from [~lorin] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=87c6d9b ] [CB-4644] updated file reader section headings to be more consistent with rest of docs > File API documentation - FileReader headings are incorrect > -- > > Key: CB-4644 > URL: https://issues.apache.org/jira/browse/CB-4644 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 2.9.0 >Reporter: Peter >Assignee: Michael Brooks >Priority: Minor > > Many the headings in the *FileReader* section are incorrect and/or > inconsistent with other sections making it difficult to read > For example, > * "Read As Data URL" - this is a function name. Heading should be > "readAsDataURL" > * Quick Example for readAsDataURL - should be h3 not h2 > * "Abort Quick Example" - should be h2 "abort" (because it is a function name) > * This abort section seems misplaced - it is currently between the Quick and > Full example for readAsText? > * "Quick Example" should be h3. > * "Read As Text" - this is a function name. Heading should be "readAsText" > * Quick Example for readAsText - should be h3 not h2 > * Full Example for readAsText - should be h3 instead of h2 > * iOS Quirks for readAsText - should be h3 not h2 > * "Read As Binary String" - this is a function name. Heading should be > "readAsBinaryString" > * Quick Example for readAsBinaryString - should be h3 not h2 > * "Read As Array Buffer" - this is a function name. Heading should be > "readAsArrayBuffer" > * Quick Example for readAsArrayBuffer - should be h3 not h2 -- 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-4625) The File API online guide has some bad hyperlinks
[ https://issues.apache.org/jira/browse/CB-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer resolved CB-4625. Resolution: Fixed resolved, commit in comments > The File API online guide has some bad hyperlinks > - > > Key: CB-4625 > URL: https://issues.apache.org/jira/browse/CB-4625 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 2.9.0 >Reporter: Peter >Assignee: Lorin Beer >Priority: Minor > > The ambiguity between "File" (the API) and "File" (the Object) causes some > hyperlink problems > * see "...based on the W3C File API" should only link to > http://www.w3.org/TR/FileAPI/ ; not to #File, > * see "File" in the Objects list - #File anchor name is duplicated so does > not go where expected -- 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-4588) Documentation for notification.confirm should say to pass buttonLabels as Array
[
https://issues.apache.org/jira/browse/CB-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorin Beer reassigned CB-4588:
--
Assignee: Lorin Beer (was: Michael Brooks)
> Documentation for notification.confirm should say to pass buttonLabels as
> Array
> ---
>
> Key: CB-4588
> URL: https://issues.apache.org/jira/browse/CB-4588
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Minor
>
> Compare navigator.notification.confirm and navigator.notification.prompt.
> Both APIs allow caller to specifiy *buttonLabels* as 4th parameter, but
> confirm expects a comma separated String and prompt expects an array. The
> parameter passing mechanism should be consistent for these similar APIs.
> It looks like the cordova.js is already handling the scenario, because it
> says:
> {code}
> console.log("Notification.confirm(string, function, string, string) is
> deprecated. Use Notification.confirm(string, function, string, array).");
> {code}
> But the documentation for navigator.confirm is out-of-step with the code; it
> should be updated to say to pass Array, not String.
> Seems related to CB-1933
--
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-4731) Adding config entries in plugin.xml results in duplicate .plist entries
Tim Croydon created CB-4731:
---
Summary: Adding config entries in plugin.xml results in duplicate
.plist entries
Key: CB-4731
URL: https://issues.apache.org/jira/browse/CB-4731
Project: Apache Cordova
Issue Type: Bug
Components: Plugman
Affects Versions: 3.0.0
Environment: macosx
Reporter: Tim Croydon
Assignee: Braden Shepherdson
Priority: Minor
I have the following in the plugin.xml file for a custom plugin:
{code}
location
voip
{code}
However, this does not generate the expected entries in the .plist file. I get:
{code}
UIBackgroundModes
location
voip
location
voip
{code}
i.e. elements are repeated. I have tried with a single element in the source
plugin.xml and get the same result.
I am using the cordova CLI to manage my plugins, platforms and build.
(p.s. I'm new to Cordova so apologies if this is filed under the incorrect
component)
--
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-2533) App crashes after taking a picture with the camera
[
https://issues.apache.org/jira/browse/CB-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756696#comment-13756696
]
roey sagie commented on CB-2533:
After upgrade to 2.9.0 it does not crash anymore for me.
> App crashes after taking a picture with the camera
> --
>
> Key: CB-2533
> URL: https://issues.apache.org/jira/browse/CB-2533
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.4.0
> Environment: Samsung Galaxy S3, Android 4.1.1
>Reporter: Dean Kooiman
>Assignee: Joe Bowser
>Priority: Minor
>
> Hi,
> I found a bug in cordova during tests on my Samsung Galaxy S3 with android
> 4.1.1
> I have tried using both camera.getPicture as well as capture.captureImage
> In both cases the CameraLauncher successfully starts.
> Both functions only succeed when the user takes a picture in landscape mode
> (phone is horizontal). When the picture is taken in portrait mode (phone
> vertical) the application will fail with a NPE in DroidGap, this is due to
> DroidGap loosing its reference to the activityResultCallback when its
> orientation changes.
> I am able to reproduce this using the default creation and camera examples:
> 1. Create the project:
> C:\Programming\cordova\cordova-android\framework>bin\create
> C:\Users\dean\workspace-android\DeanTest2 com.kooiman DeanTest2
> 2. Overwrite assets/www/index.html with the complete example from:
> http://docs.phonegap.com/en/2.4.0/cordova_camera_camera.md.html#Camera
> 3. Deploy the application to a Samsung Galaxy S3
> 4. Take a picture in portrait mode and see the failure.
> I can successfully get the callback by caching the reference when the
> Activity is destroyed, however the page is reloaded on orientation changes as
> well (so my image is rendered and immediately cleared). In-fact if you were
> to take a picture in Landscape or show an image from the library and then
> changed the orientation the images are removed, due to page reload.
> Here is my code to at least get past the NPE: (Still would like a fix for the
> page reload on orientation changes)
> public class DeanTest2 extends DroidGap
> {
> private static final Object CALLBACK_LOCK = new Object();
> private static CordovaPlugin destroySafeActivityCallback = null;
>
> @Override
> public void onCreate(Bundle savedInstanceState)
> {
> super.onCreate(savedInstanceState);
> synchronized(CALLBACK_LOCK) {
> if (destroySafeActivityCallback != null) {
> activityResultCallback = destroySafeActivityCallback;
> destroySafeActivityCallback = null;
> }
> }
>
> super.loadUrl(Config.getStartUrl());
> }
>
> @Override
> public void onDestroy() {
> if (activityResultCallback != null) {
> synchronized(CALLBACK_LOCK) {
> destroySafeActivityCallback = activityResultCallback;
> }
> }
>
> super.onDestroy();
> }
> }
--
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-4544) BlackBerry cordova/run --device should prompt for password
[ https://issues.apache.org/jira/browse/CB-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756718#comment-13756718 ] Jeffrey Heifetz commented on CB-4544: - this will happen with the --query flag, but could not be done by default and work through shellJs > BlackBerry cordova/run --device should prompt for password > -- > > Key: CB-4544 > URL: https://issues.apache.org/jira/browse/CB-4544 > Project: Apache Cordova > Issue Type: Bug >Reporter: Jeffrey Heifetz >Assignee: Jeffrey Heifetz > > Since the app cannot be deployed without a password to a device, if > "--device" is passed in and no target currently exists, it should prompt the > developer for their password. > This password should not be saved to the targets file. -- 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-4730) Cordova-BlackBerry has issues with long paths on win 7 64 bit
[ https://issues.apache.org/jira/browse/CB-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Heifetz resolved CB-4730. - Resolution: Fixed > Cordova-BlackBerry has issues with long paths on win 7 64 bit > - > > Key: CB-4730 > URL: https://issues.apache.org/jira/browse/CB-4730 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: Master >Reporter: Jeffrey Heifetz >Assignee: Jeffrey Heifetz >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] [Closed] (CB-4730) Cordova-BlackBerry has issues with long paths on win 7 64 bit
[ https://issues.apache.org/jira/browse/CB-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Heifetz closed CB-4730. --- > Cordova-BlackBerry has issues with long paths on win 7 64 bit > - > > Key: CB-4730 > URL: https://issues.apache.org/jira/browse/CB-4730 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: Master >Reporter: Jeffrey Heifetz >Assignee: Jeffrey Heifetz >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] [Commented] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756702#comment-13756702
]
Joe Bowser commented on CB-4404:
When an app is full screen, you can't see the top bar. You can turn this off
in config.xml by setting fullscreen to false. (It's false by default, but
PhoneGap Build adds this setting for some reason.
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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-4728) jarsigner does not always work
[ https://issues.apache.org/jira/browse/CB-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4728. Resolution: Duplicate > jarsigner does not always work > -- > > Key: CB-4728 > URL: https://issues.apache.org/jira/browse/CB-4728 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X >Reporter: Steve Husting >Assignee: Braden Shepherdson > Fix For: 3.0.0 > > > When I used jarsigner like so: > > jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore > TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 > > ... sometimes I get the return from terminal: > > jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry > compressed size (expected 15088 but got 15506 bytes) > > This error comes because it has already been signed. Does this mean that > "cordova build android" is automatically applying the .keystore file in the > TestApp2/ folder, and we no longer need to do a jarsigner after the first > keytool has been applied? -- 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-4732) Build script does not always error out with the correct code
Jeffrey Heifetz created CB-4732: --- Summary: Build script does not always error out with the correct code Key: CB-4732 URL: https://issues.apache.org/jira/browse/CB-4732 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Reporter: Jeffrey Heifetz Assignee: Jeffrey Heifetz When build encounters an error, it does not always provide a valid output code, output below. ~/Coding/Test/space test/AAA ⚡ ./platforms/blackberry10/cordova/build --release -k abcd1234 [BUILD] Populating application source [BUILD] Parsing config.xml [ERROR] Cannot sign application - No buildId provided [--buildId] ~/Coding/Test/space test/AAA ⚡ echo $? 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] [Created] (CB-4729) "cordova emulate android" does not run emulator
Steve Husting created CB-4729: - Summary: "cordova emulate android" does not run emulator Key: CB-4729 URL: https://issues.apache.org/jira/browse/CB-4729 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Environment: Mac OS X Reporter: Steve Husting Assignee: Braden Shepherdson When I run "cordova emulate android" then the screen flickers about 20 seconds later, but no emulator appears. The Eclipse SDK is installed and I've created other apps with it pre-CLI 3.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] [Created] (CB-4728) jarsigner does not always work
Steve Husting created CB-4728: - Summary: jarsigner does not always work Key: CB-4728 URL: https://issues.apache.org/jira/browse/CB-4728 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Environment: Mac OS X Reporter: Steve Husting Assignee: Braden Shepherdson Fix For: 3.0.0 When I used jarsigner like so: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 ... sometimes I get the return from terminal: jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 15088 but got 15506 bytes) This error comes because it has already been signed. Does this mean that "cordova build android" is automatically applying the .keystore file in the TestApp2/ folder, and we no longer need to do a jarsigner after the first keytool has been applied? -- 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-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756686#comment-13756686
]
Joseph Palermo commented on CB-4404:
What does it mean for an app to be fullscreen. Is that something we can turn
off easily?
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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-4730) Cordova-BlackBerry has issues with long paths on win 7 64 bit
Jeffrey Heifetz created CB-4730: --- Summary: Cordova-BlackBerry has issues with long paths on win 7 64 bit Key: CB-4730 URL: https://issues.apache.org/jira/browse/CB-4730 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: Master Reporter: Jeffrey Heifetz Assignee: Jeffrey Heifetz 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] [Commented] (CB-4730) Cordova-BlackBerry has issues with long paths on win 7 64 bit
[ https://issues.apache.org/jira/browse/CB-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756681#comment-13756681 ] ASF subversion and git services commented on CB-4730: - Commit d7d78a82f06ef06018648f8d7f40e6d7d4cd in branch refs/heads/master from [~jeffheifetz] [ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=d7d78a8 ] [CB-4730] [BlackBerry10] Updating init calls to work on Win 7 64 with long paths. Reviewed By: James Keshavarzi Tested By: Daniel Audino > Cordova-BlackBerry has issues with long paths on win 7 64 bit > - > > Key: CB-4730 > URL: https://issues.apache.org/jira/browse/CB-4730 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: Master >Reporter: Jeffrey Heifetz >Assignee: Jeffrey Heifetz >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] [Commented] (CB-4622) Allow git URLs to contain tags / hashes
[ https://issues.apache.org/jira/browse/CB-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756627#comment-13756627 ] Andrew Grieve commented on CB-4622: --- Note that there is a pull request in CB-4715 that does some of what we want here. It uses a different URL scheme though. > Allow git URLs to contain tags / hashes > --- > > Key: CB-4622 > URL: https://issues.apache.org/jira/browse/CB-4622 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Reporter: Andrew Grieve >Assignee: Mark Koudritsky > > plugman.fetch allows you to pass in a git ref to checkout after fetching. > It's not currently exposed by the command-line though (only exposed through > CLI) > Instead of having this as a separate argument to the fetch function, we > should build it into the URL. > NPM (refer to https://npmjs.org/doc/install.html): uses > ://[@][#] > We also need to specify a sub-directory, so let's use: > ://[@][#][:subdir] > subdir does *not* start with a /. > Our 3.0 instruction could then look like: > "Install via plugman install http://.../cordova-plugin-geolocation.git#stable"; > Note that we'll also need to update tag handling to allow this > format of URIs (might just be a docs update) -- 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-4715) Allow adding a plugin from cli in a git subdirectory
[ https://issues.apache.org/jira/browse/CB-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-4715. --- Resolution: Duplicate Thanks Jonathan! Loving your contributions! > Allow adding a plugin from cli in a git subdirectory > > > Key: CB-4715 > URL: https://issues.apache.org/jira/browse/CB-4715 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI >Affects Versions: 3.0.0 > Environment: Windows 8 >Reporter: Jonathan Bond-Caron >Assignee: Braden Shepherdson >Priority: Minor > Fix For: 3.1.0 > > > Context: > While trying to setup my environment for testing cordova, I had a hard time > with 'mobile spec' (didn't realize a dependency plugin already was in the > folder) > I created a simple patch that allows to specify a sub-directory for git > within the command line: > cordova plugin add > https://github.com/jbondc/cordova-labs?subdir=cordova-deps-mobile-spec > It works by pulling all the dependencies from: > https://github.com/jbondc/cordova-labs/blob/master/cordova-deps-mobile-spec/plugin.xml > Patch is here: > https://github.com/jbondc/cordova-cli/commit/40bc57c86545e7ccb3770013a63e793ce713736d -- 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-4725) device.cordova returns 'dev' on Android
[ https://issues.apache.org/jira/browse/CB-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756619#comment-13756619 ] Andrew Grieve commented on CB-4725: --- Update the core JS to expose the version. The plugin won't be able to take advantage of this until the next cordova release though. > device.cordova returns 'dev' on Android > --- > > Key: CB-4725 > URL: https://issues.apache.org/jira/browse/CB-4725 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Device >Affects Versions: 3.0.0 > Environment: Android >Reporter: Stefan Dobrev >Assignee: Andrew Grieve >Priority: Minor > > device.cordova returns 'dev' on Android platform. Expected value is '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-4725) device.cordova returns 'dev' on Android
[ https://issues.apache.org/jira/browse/CB-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve reassigned CB-4725: - Assignee: Andrew Grieve (was: Steve Gill) > device.cordova returns 'dev' on Android > --- > > Key: CB-4725 > URL: https://issues.apache.org/jira/browse/CB-4725 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Device >Affects Versions: 3.0.0 > Environment: Android >Reporter: Stefan Dobrev >Assignee: Andrew Grieve >Priority: Minor > > device.cordova returns 'dev' on Android platform. Expected value is '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-4725) device.cordova returns 'dev' on Android
[ https://issues.apache.org/jira/browse/CB-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756616#comment-13756616 ] ASF subversion and git services commented on CB-4725: - Commit e2942e162e1db06446d44d0b814ba450eb22a028 in branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=e2942e1 ] [all] [CB-4725] Export cordova version as "cordova.version" > device.cordova returns 'dev' on Android > --- > > Key: CB-4725 > URL: https://issues.apache.org/jira/browse/CB-4725 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Device >Affects Versions: 3.0.0 > Environment: Android >Reporter: Stefan Dobrev >Assignee: Steve Gill >Priority: Minor > > device.cordova returns 'dev' on Android platform. Expected value is '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-4708) injectPluginScript() can't find cordova_plugins.js when app is on an HTML file in a sub folder of www
[ https://issues.apache.org/jira/browse/CB-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756540#comment-13756540 ] Chris Emerson commented on CB-4708: --- I tried throwing together a test app this AM to show the behavior here - but findCordovaPath() actually seems to be working regardless if I do my cordova.js include via
[jira] [Created] (CB-4727) Implementation of Cordova using WinRT and C#
Sheetal Shinde created CB-4727: -- Summary: Implementation of Cordova using WinRT and C# Key: CB-4727 URL: https://issues.apache.org/jira/browse/CB-4727 Project: Apache Cordova Issue Type: New Feature Components: Windows 8 Environment: Windows 8,Visual Studio 2012. Reporter: Sheetal Shinde Assignee: Jesse MacFadyen Priority: Minor You can build Windows 8 apps also using the "HTML/JavaScript track" available in Windows Store apps. The purpose of Windows8PhonegapWinRT is to expose the same APIs used on all the other Cordova platforms, now on WinRT. In Windows8PhonegapWinRT all the plugins are created using WinRT and C#. Download the Windows8PhonegapWinRT and open it in visual studio 2012. Create application using HTML, CSS and JavaScript using Phonegap APIs and put the above files in the “www” folder of the project. Build and run the application. Here the splash screen is LNT logo (SplashScreenImage.png). If required the default Splash screen can be changed. Windows8PhonegapWinRT code is to build Apache Cordova applications that target WinRT framework for Windows 8. -- 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-4726) Implementation of Cordova using WinRT and C#
Sheetal Shinde created CB-4726: -- Summary: Implementation of Cordova using WinRT and C# Key: CB-4726 URL: https://issues.apache.org/jira/browse/CB-4726 Project: Apache Cordova Issue Type: New Feature Components: Windows 8 Environment: Windows 8,Visual Studio 2012. Reporter: Sheetal Shinde Assignee: Jesse MacFadyen Priority: Minor You can build Windows 8 apps also using the "HTML/JavaScript track" available in Windows Store apps. The purpose of Windows8PhonegapWinRT is to expose the same APIs used on all the other Cordova platforms, now on WinRT. In Windows8PhonegapWinRT all the plugins are created using WinRT and C#. Download the Windows8PhonegapWinRT and open it in visual studio 2012. Create application using HTML, CSS and JavaScript using Phonegap APIs and put the above files in the “www” folder of the project. Build and run the application. Here the splash screen is LNT logo (SplashScreenImage.png). If required the default Splash screen can be changed. Windows8PhonegapWinRT code is to build Apache Cordova applications that target WinRT framework for Windows 8. -- 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
