This project has been archived by its maintainers, and is no longer receiving any updates.
Products.IntelliDateTime
Field and Widget using bda.intellidatetime converter functions for date and time input.
Target:
Plone 2.5+, 3.x, 4.x
Requires:
bda.intellidatetime
plone of course
archetypes, sadly
TODO:
branch me for 2.5 and focus 3.0 in trunk
make installation via generic setup
get rid of jscalendar stuff and alter by jquery calendar widget.
Credits:
- Written by Robert Niederreiter <rnix@squarewave.at>
Squarewave Computing, BlueDynamics Alliance Austria
- Bugfixes by Jens Klein <jens@bluedynamics.com>
BlueDynamics Alliance, Klein & Partner KEG, Austria
- Contributions & Bugfixes by Harald Friessnegger
Webmeisterei, Austria
Changes for IntelliDateTime
1.3.2 (2010/01/26)
adjust the output datetime for the widget to the users timezone using ITimeZone [2009-04-27 jensens]
removed the additional calendar javascripts added in http://dev.plone.org/archetypes/changeset/10556 since they broke the popup
at least in plone4 loading calendar.js in addition to calendar_stripped.js (which is loaded as helper.js by the calendarwidget) results in recursion errors and the date picked in the popup is not written to the input fields.
[2010-01-26 fRiSi]
1.3.1
correct show_hm condition for datetime.datetime rendering [2009-04-15 rnix]
1.3
view macro - render datetime.datetime properly [2009-04-15 rnix]
remove view_later macro [2009-04-15 rnix]
1.2
overwrite validate_required in field.py [2009-03-01 jensens]
remove wrong condition in widget.py [2009-03-01 jensens]
1.1
eggified [2009-03-05 rnix]
1.0
widget now can return zope DateTime or python datetime [Jensens]
widget now displays time input only if show_hm is set to True (as does CalendarWidget) [2008-07-28 fRiSi]
locale for parsing the date in bda.indellidatetime.converter is obtained from the site_property default_language (widged was simply using ‘de’ before) this might break your testcases since for a default plone site the english dateformat is expected. you need to set the default language in your testsuite’s setUp method to fix this. [2008-09-12 fRiSi]
Release files for Products.IntelliDateTime 1.3.2
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 |
|---|---|---|---|---|
| Products.IntelliDateTime-1.3.2.tar.gz | 9.2 kB | Without provenance | Details for Products.IntelliDateTime-1.3.2.tar.gz |
Release files / Products.IntelliDateTime-1.3.2.tar.gz
| Download URL | Products.IntelliDateTime-1.3.2.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f02c384e099faff45c8e85157d1e94abc1d5069ca0dcb134a728487be0b9068
|
|
BLAKE2b-256 checksum How to use checksums |
e651f7e1af318d03e15d29b3ab8715ea6b907387a5ecc5c1c1a0e0b33048b3c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.IntelliDateTime 1.3.2
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.
