This project has been archived by its maintainers, and is no longer receiving any updates.
Changes
2.0 (2014-10-30)
Several enhancements and minor bug fixes. [regebro]
Bunch of fixes for z3cform widget, example types for dx, integration with fixed tree vocabularies of collective.vdexvocabulary and more polishing. Updated to latest jquery.dynatree. Some renamings (attention, imports are changing slightly). [jensens, bennyboy, 2014-01-27]
Add a z3c.form dynatree widget. [jbeyers, thomas_w, jcbrand 2012-02-08]
1.3.4 (2011-03-31)
for some cases we need to explicit iterate over .keys() - thanks to Jess Hix for the patch, jensens 2011-03-31
1.3.3 (2011-03-14)
fixed JS bug with f****g IE. Ported solution used by hpeter at yafowil.widget.dynatree witha regexp instead of trim, jensens 2011-03-14
1.3.2 (2011-03-08)
fixed bug: css-registry merges css, so paths to skin were no longer relative. Adding the resource part helps here. jensens 2011-03-08
1.3.1 (2011-02-18)
fixed bug: required on multi-selection did not work. jensens 2011-02-18
added showKey property to at-widget to show terms key in front of the value. hpeter, jensens, 2010-01-18
1.3 (2011-01-19)
upgraded jquery.dynatree from upstream to version 1.0.3. jensens 2011-01-19
added showKey property to at-widget to show terms key in front of the value. hpeter, jensens, 2011-01-18
1.2.1 (2010-12-03)
fighting with MANIFEST.in, to much was excluded and egg release broken. should now be better. jensens 2010-12-03
1.2 (2010-12-02)
after submit and validation error keep the previous selected values. jensens, 2010-12-02
1.1 (2010-11-29)
add MANIFEST.in, so *.rst gets included in the egg. jensens, 2010-11-29
make dict2dynatree more robust after report by Rigel Di Scala, jensens, 2010-11-29
1.0 (2010-11-22)
Make it work (jensens, hpeter)
License
Copyright (c) 2010, BlueDynamics Alliance, Austria All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the BlueDynamics Alliance nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
5 maintainers
Metadata
5 maintainers
Release files for collective.dynatree 2.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 | |
|---|---|---|---|---|
| collective.dynatree-2.0.zip | 111.7 kB | Without provenance | Details |
Release files / collective.dynatree-2.0.zip
| Download URL | collective.dynatree-2.0.zip |
|---|---|
| Size | 111.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
730fbbabae12bb6d876c5d55289fe7ad873afa79f352211690375c95a16d9ba4
|
|
BLAKE2b-256 checksum How to use checksums |
4ff34579a4b674de9018bf94363066fb21b2e69f2767cf9f8c589bb65a37096a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.dynatree 2.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.
