This package provides an new Application Management skin for Zope3
CHANGES
0.8.0 (2011-01-27)
Moved ZCML installation of zope.app.server from site.zcml to app.zcml as it is required by the zamplugin.* packages, too.
0.7.0 (2011-01-19)
Depends on zam.api >= 0.7 to run with ZTK 1.0.
Version 0.6.0 (2009-07-06)
Removed duplicated zam.api configure.zcml file include
Import IDefaultViewName from the new location at zope.publisher.interfaces
Removed zc.configuration package from dependency list since this is a part of zope.configuration
Version 0.5.2 (2008-04-16)
bugfix: Move the existing index.html and contents.html page to index.zcml This allows us to exclude them with the zc.configuration <exclude> directive Restrict the default index.html and contents.html to the IContainmentRoot this will avoid to adding such views on object which do not have such views.
Version 0.5.1 (2008-04-13)
Cleanup ftesting configuration, make it possbile to load ftesting.zcml additional to the app.zcml configuration.
Version 0.5.0 (2008-04-13)
Moved contens.html page to zamplugin.contents
Update CSS, use overflow: auto; for ISideBar boxes
Initial Release
Metadata
Release files for zam.skin 0.8.0
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 |
|---|---|---|---|---|
| zam.skin-0.8.0.tar.gz | 190.9 kB | Without provenance | Details for zam.skin-0.8.0.tar.gz |
Release files / zam.skin-0.8.0.tar.gz
| Download URL | zam.skin-0.8.0.tar.gz |
|---|---|
| Size | 190.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3f46a82bd834fe51c86979817cfb795ecf13c303fc422c7403a9e55a0fe9b30
|
|
BLAKE2b-256 checksum How to use checksums |
5038fe3316baac2f49070b13dcf16ce0b35d9bc2c964a915ef3c7263a0779fd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zam.skin 0.8.0
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.