This release is a pre-release and may not be stable for production use.
Introduction
horae.properties provides the dynamic property infrastructure used by the client, project, milestone and ticket content objects of the horae.ticketing.
Usage
The package builds up on three main classes:
- Properties
Container for persistent properties
- Property
A property providing one or more fields
- Propertied
An object based on the fields provided by the properties which are defined by the corresponding property containers
Objects using the property architecture have to subclass the horae.properties.propertied.PropertiedMixin mix in class and their add, edit and display forms have to subclass the corresponding base classes PropertiedAddForm, PropertiedEditForm and PropertiedDisplayForm defined in horae.properties.views. The properties for a propertied object are collected from all named adapters implementing horae.properties.interfaces.IProperties and adapting the object. Sample implementations may be found in the horae.ticketing package.
There are five property containers implemented by horae.properties which there are:
- Global properties
Properties available for all propertied objects
- Client properties
Properties available for clients
- Project properties
Properties available for projects
- Milestone properties
Properties available for milestones
- Ticket properties
Properties available for tickets
Properties may be created or customized persistently using the GUI provided by horae.properties. Another way to define properties is by defining them as default properties which is done by registering a named global utility implementing horae.properties.interfaces.IDefaultProperty. Examples of such default properties may be found in the horae.ticketing package.
Property types
The package provides the following Property implementations defined in horae.properties.properties:
- BoolProperty
A boolean property
- TextLineProperty
A textline property
- TextProperty
A text property
- RichTextProperty
A rich text property
- ChoiceProperty
A choice property
- MultipleChoiceProperty
A multiple choice property
- WeightedChoiceProperty
A choice property having weighted options
- FloatProperty
A float property
- PriceProperty
A price property
- UserProperty
A user property
- UserRoleProperty
A user role property
- GroupProperty
A group property
- GroupRoleProperty
A group role property
- DateTimeProperty
A date time property
- DateTimeRangeProperty
A date time range property
History
A Propertied object stores changes in a list of PropertyChange objects to preserve a changelog of the lifecycle. A view of the whole history may be provided by sub-classing the horae.properties.views.History base class.
Dependencies
Horae
Third party
Changelog
1.0a1 (2012-01-16)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for horae.properties 1.0a1
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 |
|---|---|---|---|---|
| horae.properties-1.0a1.tar.gz | 21.5 kB | Without provenance | Details for horae.properties-1.0a1.tar.gz |
Release files / horae.properties-1.0a1.tar.gz
| Download URL | horae.properties-1.0a1.tar.gz |
|---|---|
| Size | 21.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5e511639cb4d2dc9a97c72a11ae47a7504bd60497982bbc0433bd27a8e174a2
|
|
BLAKE2b-256 checksum How to use checksums |
71289db9bba14cebf7ff12b2033cdf7c3ffe08f3c3231d4e02bf812d13868458
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for horae.properties 1.0a1
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.
