This release is a pre-release and may not be stable for production use.
Introduction
From Google Libraries: The Libraries API is a content distribution network and loading architecture for the most popular, open-source JavaScript libraries.
This add-on integrate that google service into Plone
How to use
Add this add-on to your setup configuration and install it as usual: http://plone.org/documentation/kb/add-ons/installing
A control panel is provided in the backoffice to let you setup your google api keys and to choose what libraries you want to include.
This add-on serialize the configuration throw the portal_properties. So you can also configure it throw a generic setup profile.
How it works
It overrides throw a browserlayer the plone javascript resources iterator. It first add the jsapi if you have a api key setup for your host.
The jsapi and libraries are included only if you have provided a key. A default key is initialized for localhost:8080 and for testing:8080 domains
Changelog
1.0b1 (2010-12-08)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.googlelibraries 1.0b1
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.googlelibraries-1.0b1.tar.gz | 31.8 kB | Without provenance | Details for collective.googlelibraries-1.0b1.tar.gz |
Release files / collective.googlelibraries-1.0b1.tar.gz
| Download URL | collective.googlelibraries-1.0b1.tar.gz |
|---|---|
| Size | 31.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e9bf4aac3a1771e2c04a214865f13a2c917e6de03141bbed2365494cf9316a8
|
|
BLAKE2b-256 checksum How to use checksums |
95b1c16e702d9b938f12fd750d78b18de96392bcc17e635e3648c3d5d68c13f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.googlelibraries 1.0b1
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.
