[Subversion] / PEAK / TODO.txt  

Revision 592


Jump to revision:
Previous Next
Author: pje
Date: Sun Nov 3 15:50:21 2002 UTC (21 years, 4 months ago)

Log Message:

Completed configuration files refactoring.  Configuration files now can
have [Load Settings From] and [Provide Utilities] sections, and property
sections can now define rules instead of just values.  Property values are
eval()'d at rule access time rather than configuration loading time, and
they have access to 'propertyMap', 'propertyName', and 'targetObj' locals,
as well as the full peak.api.* and config_components' globals.  "Load
Settings From" sections can access a potentially infinite variety of
sources for loading configuration data; the sources are defined using
the 'peak.config.loaders.*' property namespace, and thus can be
meta-configured even in the same configuration file.  Builtin loader types
are 'file' and 'mapping'.  GlobalConfig no longer has any hard-wired
configuration steps; everything is now in the peak.ini file.  Subclasses
of GlobalConfig need only perform 'self.config_filenames.append(fname)'
before calling GlobalConfig's 'setup()' method, to cause additional config
files to be loaded after 'peak.ini'.

Everything that is configurable in PEAK, is now (in principle) configurable
via property files.

Changed paths:

Path Action Text Changes Prop Changes Diff to Previous
PEAK/TODO.txt modified X   (diff to previous)
PEAK/src/peak/config/config_components.py modified X   (diff to previous)
PEAK/src/peak/config/interfaces.py modified X   (diff to previous)
PEAK/src/peak/naming/names.py modified X   (diff to previous)
PEAK/src/peak/peak.ini modified X   (diff to previous)

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help