Introduction
D3.js is a JavaScript library for manipulating documents based on data. D3 helps you bring data to life using HTML, SVG and CSS. D3’s emphasis on web standards gives you the full capabilities of modern browsers without tying yourself to a proprietary framework, combining powerful visualization components and a data-driven approach to DOM manipulation.
This products integrates D3.js library in Plone.
Install
Add collective.js.d3 to your buildout’s eggs and run it.
A genericsetup profile is provided to add d3.min.js to portal_javascript in a minified version with compression option set to none.
Credits
Companies
Changelog
3.0.8.1 (20-03-2013)
Fix egg (missing README.rst)
3.0.8 (19-03-2013)
Initial release [ebrehault]
1 maintainer
Metadata
1 maintainer
Release files for collective.js.d3 3.0.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.js.d3-3.0.8.1.zip | 59.8 kB | Without provenance | Details for collective.js.d3-3.0.8.1.zip |
Release files / collective.js.d3-3.0.8.1.zip
| Download URL | collective.js.d3-3.0.8.1.zip |
|---|---|
| Size | 59.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
676d4b9cc2eafc55d9e1c10f0568d2a745ba92815dd55c4c3c2c8b7a577f31dd
|
|
BLAKE2b-256 checksum How to use checksums |
19b4542efe5ea8fcab48bce98c78c2394f27b5086910a735527dc8110c85b01a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.js.d3 3.0.8.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
