horae.properties provides the dynamic property infrastructure used by the client, project, milestone and ticket content objects of the horae.ticketing.
The package builds up on three main classes:
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:
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.
The package provides the following Property implementations defined in horae.properties.properties:
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.
TODO: Figure out how to actually get changelog content.
Changelog content for this version goes here.