This project has been archived by its maintainers, and is no longer receiving any updates.
Changes
1.4.1 (2012-02-20)
Fixed a sequence problem when loading the calendar.
1.4 (2012-02-16)
Fixed compatability to newer versions if fanstatic.
1.3.1 (2012-02-15)
Moved install requirement fanstatic to an extra requirement.
Provide direct fanstatic resources for the javascript, css and language files.
1.2 (2012-02-15)
Provided a library to be able to use the zc.datetimewidget resources with fanstatic.
1.1 (2011-02-18)
changed external to use resources of zc.datetimewidget 0.6.4, which contains a fix for IE in calendar.js
1.0 (2009-05-20)
initial revision
How to use zc.datetimewidget with Zope2
1. Add gocept.datetimewidget egg to your instance
This should automatically install the following dependencies:
zc.datetimewidget, zc.i18n and zc.resourcelibrary
2. Make sure the correct set of zcml gets loaded.
If you use a custom site.zcml, Include the following IN THIS ORDER:
<!-- Enable zc.datetimewidget to load its zcml.
Do not include zc.resourcelibrarys configure.zcml, as this
will not work in z2. -->
<include package="zc.resourcelibrary" file="meta.zcml" />
<!-- Contains a copy of the resource directory of zc.datetimewidget
registered as a browser:resourceDirectory.
Also contains a viewlet manager with viewlets providing html
snippets for including the javascripts in your templates (see below). -->
<include package="gocept.datetimewidget" />
<include package="zc.datetimewidget" />
<!-- Replace the formlib datetimewidget with the zc one. -->
<includeOverrides package="zc.datetimewidget" />
<!-- Overwrite the zc.resourcelibrary resourcedirectory
of zc.datetimewidget with a browser:resourceDirectory. -->
<includeOverrides package="gocept.datetimewidget" />
If you use the zcml parameter of plone.recipe.zope2instance you can just set:
zcml = zc.resourcelibrary-meta
gocept.datetimewidget
zc.datetimewidget
zc.datetimewidget-overrides
gocept.datetimewidget-overrides
3. Add javascript resources to your templates.
Place a line like this in a template where your forms will be displayed:
<tal:jsviewlets replace="structure provider:zc.datetimewidget.resources" />
Or make sure the following resources are loaded (i.e. using plone portal_javascript/portal_css):
/++resource++zc.datetimewidget/calendar-system.css /++resource++zc.datetimewidget/calendar.js /++resource++zc.datetimewidget/datetimewidget.js /++resource++zc.datetimewidget/languages/calendar-en.js /++resource++zc.datetimewidget/calendar-setup.js
Or use Fanstatic:
import gocept.datetimewidget.resource gocept.datetimewidget.resource.datetimewidget.need()
Metadata
Release files for gocept.datetimewidget 1.4.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 |
|---|---|---|---|---|
| gocept.datetimewidget-1.4.1.tar.gz | 39.7 kB | Without provenance | Details for gocept.datetimewidget-1.4.1.tar.gz |
Release files / gocept.datetimewidget-1.4.1.tar.gz
| Download URL | gocept.datetimewidget-1.4.1.tar.gz |
|---|---|
| Size | 39.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d2e75477ef9aaf13dac90b16f63dde40f2e4f59a0e561ebd030e33c37a11f0b
|
|
BLAKE2b-256 checksum How to use checksums |
9fb467517d681d6d0dbf73de034c5914d719a847368a53d42f59498ae6e9c807
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gocept.datetimewidget 1.4.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.