[jira] [Commented] (CB-4485) Command line build ignoring content src in config.xml settings
[ https://issues.apache.org/jira/browse/CB-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728436#comment-13728436 ] Joshua McFarland commented on CB-4485: -- I'm not too familiar with the underbelly of Cordova. You're saying that when I use 'cordova build android' from the command prompt it copies everything, but doesn't generate an apk that takes into account the content src in the xml file? > Command line build ignoring content src in config.xml settings > -- > > Key: CB-4485 > URL: https://issues.apache.org/jira/browse/CB-4485 > Project: Apache Cordova > Issue Type: New Feature > Components: CLI >Affects Versions: 3.0.0 > Environment: Windows 8 x64 >Reporter: Joshua McFarland >Assignee: Michael Brooks >Priority: Minor > > I have specifically set the content src, but when building the application is > still uses the default of 'index.html' rather than what I have set. It's not > entirely ignoring the config file, because if I change the app name or id it > does get properly updated on build. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728207#comment-13728207 ] Tim Kim commented on CB-4036: - Hey Andrew, I like the concept of having it all in the engine tag but the problem I feel is what do for platforms that don't care about/need other platform's engines. To me, the solution to that is to specify which of the engines work for what platforms which is kinda redundant if you have a separate platform tag already. Hrm, or maybe we could do something like: > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4494) "plugman search" Should indicate which results are compatible with your configuration
Andrew Grieve created CB-4494: - Summary: "plugman search" Should indicate which results are compatible with your configuration Key: CB-4494 URL: https://issues.apache.org/jira/browse/CB-4494 Project: Apache Cordova Issue Type: Improvement Components: Plugman Reporter: Andrew Grieve Assignee: Anis Kadri I don't think we should filter by your platform, but it would be nice is we had some sort of indicator that showed which results were compatible vs not compatible. To do this, we'd need version info available in the couchdb schema I think. Step 1 to this bug is to design, Step 2 is to implement. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4489) Launch plugman-registry
[ https://issues.apache.org/jira/browse/CB-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728094#comment-13728094 ] Andrew Grieve commented on CB-4489: --- For CB-4494, I think the design should be a prereq to launching the registry, but the implementation only needs to be done enough to be putting the correct fields into the couchdb. > Launch plugman-registry > --- > > Key: CB-4489 > URL: https://issues.apache.org/jira/browse/CB-4489 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Reporter: Andrew Grieve >Assignee: Anis Kadri > > Parent issue for remaining tasks before we can launch plugman-registry. -- 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-4493) cordova-docs for plugman-registry
Andrew Grieve created CB-4493: - Summary: cordova-docs for plugman-registry Key: CB-4493 URL: https://issues.apache.org/jira/browse/CB-4493 Project: Apache Cordova Issue Type: Improvement Components: Docs, Plugman Reporter: Andrew Grieve https://wiki.apache.org/cordova/PluginDiscovery is a good starting point. For the app-developer side, we can put this right in "The Command-line interface" section. For the plugin-developer side, put it in "Plugin Development Guide" -- 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-4492) Ensure download counts from plugman-registry are being tracked
Andrew Grieve created CB-4492: - Summary: 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: Anis Kadri 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] [Created] (CB-4491) Add instructions for maintaining / accessing our iriscouch plugin-registry instance.
Andrew Grieve created CB-4491: - Summary: Add instructions for maintaining / accessing our iriscouch plugin-registry instance. Key: CB-4491 URL: https://issues.apache.org/jira/browse/CB-4491 Project: Apache Cordova Issue Type: Improvement Components: Plugman Reporter: Andrew Grieve Assignee: Anis Kadri I'm not very familiar with couchdb, so don't really know the details here. At minimum: - How to log into the admin part of the instance - How to give someone else admin access to it - What configuration steps are required to configure it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4036) tag should have a "version" attribute
[ https://issues.apache.org/jira/browse/CB-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728073#comment-13728073 ] Andrew Grieve commented on CB-4036: --- Just created CB-4490 for adding separate version checks for cordova-ios vs cordova-android. Made me think that we should *not* add these versions to tags, and instead add them to e.g. What if you had multiple tags? Is there a use-case for that? Might want that if you are going to define all of your JS for all platforms, and then later define all of your assets per-platform? Having the sdk & os checks in would also serve to put all version info in the same place: OTOH, having versions in the tag might serve more as a conditional. E.g. ... some source files ... some additional source files > tag should have a "version" attribute > - > > Key: CB-4036 > URL: https://issues.apache.org/jira/browse/CB-4036 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Shazron Abdullah >Assignee: Filip Maj > > This might be hole that we didn't consider. > I know implicitly if the plugin supported an "engine" version we support what > the engine supports, but here could be one scenario. > For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang > framework. Fine, with iOS 7, you have to of course build with the iOS 7 SDK, > and you can support iOS 6 with a Deploy Target build setting. > It runs on iOS 7 - yay. > It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework > does not exist on iOS 6. > Now you say, why don't you do Obj-C runtime checks and weak link the > framework? Yes, the plugin author can do that but a plugin user, by parsing > the plugin xml (using a tool, or optically, whatever) cannot know that the > plugin does NOT work on iOS 6 - and even though it "runs" on iOS 6, it does > nothing, which is useless and wastes a lot of time. > So - my proposal is, to add a *"version"* attribute on the ** tag. > It should follow the syntax for the version attribute. > What would be the default if the version attribute is not there? Not sure > what a reasonable default is yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-1885) Tizen SDK updated to 2.0
[ https://issues.apache.org/jira/browse/CB-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anis Kadri reassigned CB-1885: -- Assignee: Paul Plaquette (was: Anis Kadri) > Tizen SDK updated to 2.0 > > > Key: CB-1885 > URL: https://issues.apache.org/jira/browse/CB-1885 > Project: Apache Cordova > Issue Type: Bug > Components: Tizen >Reporter: bongjuong kim >Assignee: Paul Plaquette > > Tizen SDK updated to Tizen SDK 2.0a > So, some feature is not work. > So I have a question. > When will you update apache-cordova-tizen for SDK 2.0? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3533) Symbian getting started doc is incorrect
[ https://issues.apache.org/jira/browse/CB-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anis Kadri resolved CB-3533. Resolution: Won't Fix Sorry, Symbian is no longer supported. > Symbian getting started doc is incorrect > > > Key: CB-3533 > URL: https://issues.apache.org/jira/browse/CB-3533 > Project: Apache Cordova > Issue Type: Improvement > Components: Qt >Reporter: John M. Wargo >Assignee: Anis Kadri >Priority: Trivial > Labels: docs > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > The getting started guide at > http://cordova.apache.org/docs/en/2.7.0/guide_getting-started_symbian_index.md.html#Getting%20Started%20with%20Symbian > for Symbian has errors in it. > In step 2 is refers to be working with the Android Directory "We will be > working with the Android directory" > In Cordova 2.6 and 2.7 there is no Symbian directory. In 2.5 it's called QT, > not Symbian. -- 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-3215) Ability to load assets from a downloaded zip file
[ https://issues.apache.org/jira/browse/CB-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anis Kadri resolved CB-3215. Resolution: Fixed registry should satisfy this requirement. > Ability to load assets from a downloaded zip file > - > > Key: CB-3215 > URL: https://issues.apache.org/jira/browse/CB-3215 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Reporter: Chris Anderson >Assignee: Anis Kadri > > We have a library we'd like to host on our CDN instead of in a git repo, so > we want to download a zip file and uncompress it before plugman runs. > Maybe there's a better solution? -- 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-4490) version check should check against plugman version
Andrew Grieve created CB-4490: - Summary: version check should check against plugman version Key: CB-4490 URL: https://issues.apache.org/jira/browse/CB-4490 Project: Apache Cordova Issue Type: Improvement Components: Plugman Reporter: Andrew Grieve Assignee: Filip Maj Currently, we have: This checks against the result of platform/bin/version scripts. However, it's quite possible to have a plugin that works with cordova-android >=3.0 and cordova-ios >=3.1 CB-4036 introduces per-platform SDK & OS version checks. This issue covers have cordova versions be per-platform, as well as having plugman version requirement. We could still maintain: as a shorthand for: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4489) Launch plugman-registry
Andrew Grieve created CB-4489: - Summary: Launch plugman-registry Key: CB-4489 URL: https://issues.apache.org/jira/browse/CB-4489 Project: Apache Cordova Issue Type: Bug Components: Plugman Reporter: Andrew Grieve Assignee: Anis Kadri Parent issue for remaining tasks before we can launch plugman-registry. -- 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-2202) Remove deprecated - Android - org.apache.cordova.api.Plugin in favour of org.apache.cordova.api.CordovaPlugin
[ https://issues.apache.org/jira/browse/CB-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727946#comment-13727946 ] Andrew Grieve commented on CB-2202: --- Hey Maciej, Good suggestion. Simon's blog post doesn't mention threading, so I don't think it's a good idea to link to it. I've instead added a link to our plugin guide. > Remove deprecated - Android - org.apache.cordova.api.Plugin in favour of > org.apache.cordova.api.CordovaPlugin > - > > Key: CB-2202 > URL: https://issues.apache.org/jira/browse/CB-2202 > Project: Apache Cordova > Issue Type: Task > Components: Android >Reporter: Shazron Abdullah >Assignee: Andrew Grieve > Fix For: 2.7.0 > > > Per 6 month deprecation policy: > http://wiki.apache.org/cordova/DeprecationPolicy -- 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-3506) Add a command to coho for uploading a release candidate
[ https://issues.apache.org/jira/browse/CB-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727917#comment-13727917 ] Andrew Grieve commented on CB-3506: --- Looks great Steve, few nits: #1 - Change: var opt = registerRepoFlag(optimist) to: var opt = optimist since you don't use the -r flag. #2 - Might be good to have a check right at the start to ensure the built .zip to upload exists #3 - Might be better to end off with doing an "svn status" and a print-out of the command to execute in order to commit (instead of committing itself). > Add a command to coho for uploading a release candidate > --- > > Key: CB-3506 > URL: https://issues.apache.org/jira/browse/CB-3506 > Project: Apache Cordova > Issue Type: Sub-task > Components: Coho >Reporter: Andrew Grieve >Assignee: Steve Gill >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-4480) CDVFileTransfer - handling big files >2GB is not correct
[
https://issues.apache.org/jira/browse/CB-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve closed CB-4480.
-
Resolution: Fixed
Assignee: Andrew Grieve (was: Steve Gill)
Patched in your change, but just had to fix up using NSInteger in the
connection delegate (it's not our signature to change). And also used long long
instead of unsigned since it will be unsigned once it gets to JS anyways.
> CDVFileTransfer - handling big files >2GB is not correct
>
>
> Key: CB-4480
> URL: https://issues.apache.org/jira/browse/CB-4480
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Affects Versions: 2.9.0, 3.0.0
> Environment: iOS in general
>Reporter: Klaus Schmidt
>Assignee: Andrew Grieve
> Labels: patch
> Attachments: CDVFileTransfer.h.diff, CDVFileTransfer.m.diff
>
>
> Hello Cordova Team,
> we needed to download big files (>2GB) via FileTransfer and use the
> onProgressEvent to display the progress.
> On Android everything is fine. On iOS the reported sizes in the
> onProgressEvent are not valid, if the downloaded file is larger than 2GB:
> {{CDVFileTransfer}} uses {{NSInteger}} for {{bytesTransfered}} and
> {{bytesExpected}}. {{NSInteger}} only is up to 2G-1 as mentioned here:
> http://stackoverflow.com/questions/2107544/types-in-objective-c-on-iphone
> We patched the library files {{CDVFileTransfer.h}} and {{CDVFileTransfer.m}}
> of version 2.9.0 to use "unsigned long long" - now we are able to display
> downloads up to 16Exabytes-1byte correctly. We can see in github, that
> version 3.0.0 has the same issue.
> I will add the diff in the issue after creating it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4480) CDVFileTransfer - handling big files >2GB is not correct
[
https://issues.apache.org/jira/browse/CB-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727879#comment-13727879
]
ASF subversion and git services commented on CB-4480:
-
Commit e09dc3526e1ddbe34c55249720d38d65957d94d7 in branch refs/heads/2.9.x from
[~agrieve]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=e09dc35 ]
[CB-4480] Using 64 bit ints to store file size
Thanks to Klaus Schmidt for the original patch.
> CDVFileTransfer - handling big files >2GB is not correct
>
>
> Key: CB-4480
> URL: https://issues.apache.org/jira/browse/CB-4480
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Affects Versions: 2.9.0, 3.0.0
> Environment: iOS in general
>Reporter: Klaus Schmidt
>Assignee: Steve Gill
> Labels: patch
> Attachments: CDVFileTransfer.h.diff, CDVFileTransfer.m.diff
>
>
> Hello Cordova Team,
> we needed to download big files (>2GB) via FileTransfer and use the
> onProgressEvent to display the progress.
> On Android everything is fine. On iOS the reported sizes in the
> onProgressEvent are not valid, if the downloaded file is larger than 2GB:
> {{CDVFileTransfer}} uses {{NSInteger}} for {{bytesTransfered}} and
> {{bytesExpected}}. {{NSInteger}} only is up to 2G-1 as mentioned here:
> http://stackoverflow.com/questions/2107544/types-in-objective-c-on-iphone
> We patched the library files {{CDVFileTransfer.h}} and {{CDVFileTransfer.m}}
> of version 2.9.0 to use "unsigned long long" - now we are able to display
> downloads up to 16Exabytes-1byte correctly. We can see in github, that
> version 3.0.0 has the same issue.
> I will add the diff in the issue after creating it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4480) CDVFileTransfer - handling big files >2GB is not correct
[
https://issues.apache.org/jira/browse/CB-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727876#comment-13727876
]
ASF subversion and git services commented on CB-4480:
-
Commit d0d4573ac630a4ee4c049df4b54bebb40d663676 in branch refs/heads/dev from
[~agrieve]
[
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=d0d4573
]
[CB-4480] Fix up a couple Unsigned->Signed mistakes from previous commit.
Also - thanks to Klaus Schmidt for the original patch for this fix.
> CDVFileTransfer - handling big files >2GB is not correct
>
>
> Key: CB-4480
> URL: https://issues.apache.org/jira/browse/CB-4480
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Affects Versions: 2.9.0, 3.0.0
> Environment: iOS in general
>Reporter: Klaus Schmidt
>Assignee: Steve Gill
> Labels: patch
> Attachments: CDVFileTransfer.h.diff, CDVFileTransfer.m.diff
>
>
> Hello Cordova Team,
> we needed to download big files (>2GB) via FileTransfer and use the
> onProgressEvent to display the progress.
> On Android everything is fine. On iOS the reported sizes in the
> onProgressEvent are not valid, if the downloaded file is larger than 2GB:
> {{CDVFileTransfer}} uses {{NSInteger}} for {{bytesTransfered}} and
> {{bytesExpected}}. {{NSInteger}} only is up to 2G-1 as mentioned here:
> http://stackoverflow.com/questions/2107544/types-in-objective-c-on-iphone
> We patched the library files {{CDVFileTransfer.h}} and {{CDVFileTransfer.m}}
> of version 2.9.0 to use "unsigned long long" - now we are able to display
> downloads up to 16Exabytes-1byte correctly. We can see in github, that
> version 3.0.0 has the same issue.
> I will add the diff in the issue after creating it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4480) CDVFileTransfer - handling big files >2GB is not correct
[
https://issues.apache.org/jira/browse/CB-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727862#comment-13727862
]
ASF subversion and git services commented on CB-4480:
-
Commit 5f9bcb8da8cd40850ee7998ddc70a062fb0ae49a in branch refs/heads/dev from
[~agrieve]
[
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=5f9bcb8
]
[CB-4480] Using 64 bit ints to store file size
> CDVFileTransfer - handling big files >2GB is not correct
>
>
> Key: CB-4480
> URL: https://issues.apache.org/jira/browse/CB-4480
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Affects Versions: 2.9.0, 3.0.0
> Environment: iOS in general
>Reporter: Klaus Schmidt
>Assignee: Steve Gill
> Labels: patch
> Attachments: CDVFileTransfer.h.diff, CDVFileTransfer.m.diff
>
>
> Hello Cordova Team,
> we needed to download big files (>2GB) via FileTransfer and use the
> onProgressEvent to display the progress.
> On Android everything is fine. On iOS the reported sizes in the
> onProgressEvent are not valid, if the downloaded file is larger than 2GB:
> {{CDVFileTransfer}} uses {{NSInteger}} for {{bytesTransfered}} and
> {{bytesExpected}}. {{NSInteger}} only is up to 2G-1 as mentioned here:
> http://stackoverflow.com/questions/2107544/types-in-objective-c-on-iphone
> We patched the library files {{CDVFileTransfer.h}} and {{CDVFileTransfer.m}}
> of version 2.9.0 to use "unsigned long long" - now we are able to display
> downloads up to 16Exabytes-1byte correctly. We can see in github, that
> version 3.0.0 has the same issue.
> I will add the diff in the issue after creating it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4461) Globalization and I18N - Crowdin Proposal Discussion
[ https://issues.apache.org/jira/browse/CB-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727771#comment-13727771 ] Lisa Seacat DeLuca commented on CB-4461: FYI, a note from crowdin: Hello Lisa, We are very flattered to see Apache Software Foundation in Crowdin. Thanks for your interest. We will do our best to get you comfortable localization environment. Your Open Source project has been approved at Crowdin! We're looking forward to see Cordova project localized. Please let us know if you have any questions. --- Sincerely, Iryna Bilyk > Globalization and I18N - Crowdin Proposal Discussion > - > > Key: CB-4461 > URL: https://issues.apache.org/jira/browse/CB-4461 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Affects Versions: 3.0.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: documentation, globalization, translation, > > I have created a project within Transifex for cordova here: > https://www.transifex.com/projects/p/cordova > The way it works is: > 1.files are upload to the Transifex system. Transifex does not have > markdown files as one of the options for file type to import but they do have > html and plain text. I have chosen plain text for testing and it appears to > work great. I setup a preferences for the resource to be pulled from github > on a daily basis with the latest version of the file. > 2.Users may come in and provide translation or all or part of a file. > 3.A "maintainer" or language expert is assigned to each language and > approves the translations > 4.progress information and status can be shown per file/project. Once > complete, the translated file can be uploaded back into github under the > specific language. This part is a manual process > Other open source projects use Transifex, for example, OpenStack. > I propose we do the following: > Use Transifex for each major release starting with 3.0. If it is relatively > easy to translate for minor releases we can vote to do so with each. > Assign a language "maintainer" for each supported language to monitor > translations. I suggest we start with Spanish and French since those are the > languages our group of committers can best contribute to at this time. (If > we have a consensus to use Transfix, please volunteer if you'd like to be the > maintainer for a specific language). > Once a section of the documentation is approved by the language moderator, we > push the updates to GitHub. > Another thing to think about, Transifex offers automatic translation for > faster translation using google translation services or microsoft's which > require an api key and a paid subscription. I don't know if either of those > companies offer a free key for open source needs. I know we have a few > representatives from those companies that might be able to give us more > information. > Why we should be worried about translation? > Globalization! If we can attract more developers to Cordova and make it > easier for those developers to get up and running with cordova by providing > documentation in their native languages, cordova will continue to grow in > popularity globally. -- 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-4461) Globalization and I18N - Crowdin Proposal Discussion
[ https://issues.apache.org/jira/browse/CB-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-4461: --- Summary: Globalization and I18N - Crowdin Proposal Discussion (was: Globalozation and I18N - Crowdin Proposal Discussion) > Globalization and I18N - Crowdin Proposal Discussion > - > > Key: CB-4461 > URL: https://issues.apache.org/jira/browse/CB-4461 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Affects Versions: 3.0.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: documentation, globalization, translation, > > I have created a project within Transifex for cordova here: > https://www.transifex.com/projects/p/cordova > The way it works is: > 1.files are upload to the Transifex system. Transifex does not have > markdown files as one of the options for file type to import but they do have > html and plain text. I have chosen plain text for testing and it appears to > work great. I setup a preferences for the resource to be pulled from github > on a daily basis with the latest version of the file. > 2.Users may come in and provide translation or all or part of a file. > 3.A "maintainer" or language expert is assigned to each language and > approves the translations > 4.progress information and status can be shown per file/project. Once > complete, the translated file can be uploaded back into github under the > specific language. This part is a manual process > Other open source projects use Transifex, for example, OpenStack. > I propose we do the following: > Use Transifex for each major release starting with 3.0. If it is relatively > easy to translate for minor releases we can vote to do so with each. > Assign a language "maintainer" for each supported language to monitor > translations. I suggest we start with Spanish and French since those are the > languages our group of committers can best contribute to at this time. (If > we have a consensus to use Transfix, please volunteer if you'd like to be the > maintainer for a specific language). > Once a section of the documentation is approved by the language moderator, we > push the updates to GitHub. > Another thing to think about, Transifex offers automatic translation for > faster translation using google translation services or microsoft's which > require an api key and a paid subscription. I don't know if either of those > companies offer a free key for open source needs. I know we have a few > representatives from those companies that might be able to give us more > information. > Why we should be worried about translation? > Globalization! If we can attract more developers to Cordova and make it > easier for those developers to get up and running with cordova by providing > documentation in their native languages, cordova will continue to grow in > popularity globally. -- 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-4397) Move CLI from shelljs.exec() -> child_process.exec()
[ https://issues.apache.org/jira/browse/CB-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Mocny reassigned CB-4397: Assignee: Michal Mocny (was: Filip Maj) > Move CLI from shelljs.exec() -> child_process.exec() > > > Key: CB-4397 > URL: https://issues.apache.org/jira/browse/CB-4397 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: Andrew Grieve >Assignee: Michal Mocny > > We've found that shelljs's exec() function is super slow and leaks file > handles. > We should use child_process.exec() instead. > http://markmail.org/thread/zxpfau7fwc23gwbx -- 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-3439) [BlackBerry10] Add ability to build in release mode with WebInspector enabled
[ https://issues.apache.org/jira/browse/CB-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins resolved CB-3439. --- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commit;h=f3f5d3d62b62da9fd34803f05587222c26421e98 > [BlackBerry10] Add ability to build in release mode with WebInspector enabled > - > > Key: CB-3439 > URL: https://issues.apache.org/jira/browse/CB-3439 > Project: Apache Cordova > Issue Type: Improvement > Components: BlackBerry >Reporter: Bryan Higgins >Assignee: Bryan Higgins > Fix For: 3.1.0 > > > There are some cases (such as Built for BlackBerry testing) where users > require a signed BAR with WebInspector enabled. The build script currently > only enables WebInspector in debug mode. > My suggestion would be to add --web-inspector flag to the build script. -- 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-4360) Updating Cordova Docs on Website should not re-upload all versions
[ https://issues.apache.org/jira/browse/CB-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-4360. --- Resolution: Fixed Seems to work now! The main other problem was using the correct version of nokogiri. > Updating Cordova Docs on Website should not re-upload all versions > -- > > Key: CB-4360 > URL: https://issues.apache.org/jira/browse/CB-4360 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Andrew Grieve >Assignee: Andrew Grieve > > The current instructions for updating the docs on the website are: > svn rm -r public/docs > cp -r path/to/docs public > svn add public/docs > This causes svn to actually delete every file and then re-add every file. > Takes forever to upload, and causes a long time for the next person to > perform an "svn up". > We need to figure out how to get subversion to add only the changed files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4488) There are no manual tests for capture plugin?
[ https://issues.apache.org/jira/browse/CB-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727704#comment-13727704 ] Andrew Grieve commented on CB-4488: --- For sure! That would be great. > There are no manual tests for capture plugin? > - > > Key: CB-4488 > URL: https://issues.apache.org/jira/browse/CB-4488 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Affects Versions: 3.0.0 >Reporter: lmnbeyond >Assignee: Filip Maj > > I can't find any manual tests for capture plugin. I think it is necessary to > add some manual tests for it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4487) phonegap 2.9 file api's big5 or utf8 split character problem
[ https://issues.apache.org/jira/browse/CB-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727705#comment-13727705 ] Andrew Grieve commented on CB-4487: --- Read the forum post, but I'm not sure what the problem is? Is the API not working correctly? > phonegap 2.9 file api's big5 or utf8 split character problem > > > Key: CB-4487 > URL: https://issues.apache.org/jira/browse/CB-4487 > Project: Apache Cordova > Issue Type: Wish > Components: Android >Affects Versions: 2.9.0 > Environment: Android 4.03 HTC Sensation XL >Reporter: Colin Bau >Assignee: Joe Bowser > Labels: cut, lebgth, seek > Original Estimate: 48h > Remaining Estimate: 48h > > all the content in the web address > https://groups.google.com/forum/#!topic/phonegap/-kozb7jlhqk -- 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-4488) There are no manual tests for capture plugin?
lmnbeyond created CB-4488: - Summary: There are no manual tests for capture plugin? Key: CB-4488 URL: https://issues.apache.org/jira/browse/CB-4488 Project: Apache Cordova Issue Type: Bug Components: mobile-spec Affects Versions: 3.0.0 Reporter: lmnbeyond Assignee: Filip Maj I can't find any manual tests for capture plugin. I think it is necessary to add some manual tests for it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4392) Add plugin capture failed
[
https://issues.apache.org/jira/browse/CB-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727505#comment-13727505
]
lmnbeyond commented on CB-4392:
---
Thank you, it works now :)
> Add plugin capture failed
> -
>
> Key: CB-4392
> URL: https://issues.apache.org/jira/browse/CB-4392
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
>Reporter: lmnbeyond
>Assignee: Filip Maj
> Fix For: 3.1.0
>
>
> $ cordova platform add ios
> $ cordova plugin add
> https://git-wip-us.apache.org/repos/asf/cordova-plugin-media-capture.git
> { [Error: ENOENT, no such file or directory
> '/var/folders/rm/53qs6tsj5kvbw12157mkv07rgn/T/plugman-tmp1374738103634/*/plugin.xml']
> errno: 34,
> code: 'ENOENT',
> path:
> '/var/folders/rm/53qs6tsj5kvbw12157mkv07rgn/T/plugman-tmp1374738103634/*/plugin.xml',
> syscall: 'open' }
--
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-4487) phonegap 2.9 file api's big5 or utf8 split character problem
Colin Bau created CB-4487: - Summary: phonegap 2.9 file api's big5 or utf8 split character problem Key: CB-4487 URL: https://issues.apache.org/jira/browse/CB-4487 Project: Apache Cordova Issue Type: Wish Components: Android Affects Versions: 2.9.0 Environment: Android 4.03 HTC Sensation XL Reporter: Colin Bau Assignee: Joe Bowser all the content in the web address https://groups.google.com/forum/#!topic/phonegap/-kozb7jlhqk -- 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-4485) Command line build ignoring content src in config.xml settings
[ https://issues.apache.org/jira/browse/CB-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727445#comment-13727445 ] Joe Bowser commented on CB-4485: [~mwbrooks] Right now, the create scripts don't take in any XML, nor do they know about any pre-defined icons. I would prefer to keep the scripts dumb so that they're easy to debug. I think that this belongs in the CLI, since this is a configuration step after create has been called, not something that the create scripts should handle. Furthermore, it's better that all the image processing be done in one place, and if possible, it'd be good if this didn't block the project creation process if it failed. > Command line build ignoring content src in config.xml settings > -- > > Key: CB-4485 > URL: https://issues.apache.org/jira/browse/CB-4485 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Windows 8 x64 >Reporter: Joshua McFarland >Assignee: Michael Brooks > > I have specifically set the content src, but when building the application is > still uses the default of 'index.html' rather than what I have set. It's not > entirely ignoring the config file, because if I change the app name or id it > does get properly updated on build. > -- 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-4485) Command line build ignoring content src in config.xml settings
[ https://issues.apache.org/jira/browse/CB-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-4485: --- Priority: Minor (was: Major) Issue Type: New Feature (was: Bug) > Command line build ignoring content src in config.xml settings > -- > > Key: CB-4485 > URL: https://issues.apache.org/jira/browse/CB-4485 > Project: Apache Cordova > Issue Type: New Feature > Components: CLI >Affects Versions: 3.0.0 > Environment: Windows 8 x64 >Reporter: Joshua McFarland >Assignee: Michael Brooks >Priority: Minor > > I have specifically set the content src, but when building the application is > still uses the default of 'index.html' rather than what I have set. It's not > entirely ignoring the config file, because if I change the app name or id it > does get properly updated on build. > -- 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
