New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jsmva issues #1520
Jsmva issues #1520
Conversation
Can one of the admins verify this patch? |
@phsft-bot build |
Starting build on |
Build failed on mac1013/native. Warnings:
And 10 more Failing tests: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Up to @lmoneta to decide.
@ashlaban among the fixes of this PR, there is one related to the d3 issue in JsMVA you are currently fixing. Can you have a look? Perhaps you can also incorporate the other fixes. |
Thanks for the catch. Actually I don’t understand why this PR is not integrated. It seems to be a more extensive version of my change. I will update my PR with the d3 name change I missed and discuss with Lorenzo how to best respond to this PR. |
For reference: Parts of these changes are included in PR#2353. |
As @ellert points out, we need to port jsmva to d3 v4 that jsroot uses. Right now jsmva is basically unusable; Most of it's functionality depends on d3. Incorporating this PR will allow most of jsmva functionality to run, but a few things will be missing due to an api change. I suggest to integrate this PR as is and provide the update to the rest of jsmva in a separate PR (unless you @ellert would volunteer to update this PR). Details (and for future reference): The problems arise when calling:
List of changes for 3 -> 4 can be found here: https://github.com/d3/d3/blob/master/CHANGES.md#changes-in-d3-40. Important ones to note are:
|
I think then we can finally merge this now, and having further changes in a separate PR. |
The Fedora Packaging Guidelines some time ago added a section on packaging javascript files. This section says that minified scripts should be treated as compiled code. And like for programs written in other languages, pre-compiled code that is part of the sources must not be used in packaging, but must be regenerated from sources during the package build. I recently implemented these guidelines in the root package and found some issues.
This pull request has three commits.