Changelog
0.3.1 (2010-06-01)
Eliminated tabindex.
Tested with Plone-4.0b3.
0.3.0 (2009-06-17)
Initial release of eggified version. [taito.horiuchi]
Installation
If you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, just do this:
Add Products.ColorField to the list of eggs to install, e.g.:
[buildout]…eggs =…Products.ColorFieldTell the plone.recipe.zope2instance recipe to install a ZCML slug:
[instance]recipe = plone.recipe.zope2instance…zcml =Products.ColorFieldRe-run buildout, e.g. with:
$ ./bin/buildout
You can skip the ZCML slug if you are going to explicitly include the package from another package’s configure.zcml file.
Because its top level Python namespace package is called Products, this package can also be installed in Zope 2 as an old style Zope 2 Product.
For that, move (or symlink) the ColorField folder of this project (Products.ColorField/Products/ColorField) into the Products directory of the Zope instance it has to be installed for, and restart the server.
You can also skip the ZCML slug if you install this package the Zope 2 Product way.
Set OUTPUT_FORMAT in config.py of the field itself to have the color codes in HTMLColor, RGB, HexColor or PILColor. Default is HTMLColor.
Usage
In your custom Archetype, add:
from Products.ColorField import ColorWidget, ColorFieldUse it like a regular field/widget in your Type’s Schema.
ColorField(‘my_color’,default=’#00FFFF’,output_format=’HexColor’,widget=ColorWidget(label=’My color’,allow_brightness=True)),
Metadata
Release files for Products.ColorField 0.3.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 | |
|---|---|---|---|---|
| Products.ColorField-0.3.1.tar.gz | 27.0 kB | Without provenance | Details |
Release files / Products.ColorField-0.3.1.tar.gz
| Download URL | Products.ColorField-0.3.1.tar.gz |
|---|---|
| Size | 27.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da9554ff347493b12c31b1c78559d1e077811710277d50cc57c8489043961faf
|
|
BLAKE2b-256 checksum How to use checksums |
e2e81ef01ac35d6efc7c12980f63ebb51955c948f2c4d0ef4e79f92ccb1dbb9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.ColorField 0.3.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.