RERO: Key Structure"> RERO: Key Structure">
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
The key structure represents a tree of settings. This hierarchy allows for easy extension and storage. The root of the tree is represented as the first . in the key from the left. Words to the left of the root represent release profiles. Branches to the right of the root are configurable items that relate to the related release profile on the left.
So much for theory. How does this work in RERO? As an example I will choose the RCS (revision control system) branch of configurable items. The RCS branch has currently four branches and one leaf (variable) beneath it:
rcs |- (cleanup) |- (co) |- (cvs) |- method `- (tag)
Here the ( and ) characters surround branches. So `method' is a variable under `rcs' that can be configured. The associated key name would look like:
If we search further into the `cvs' branch we see:
rcs ... |- cvs ... |- cleanup |- co | `- options |- cvsroot |- module |- tagprefix `- testtagprefix
These values correspond to:
.rcs.cvs.cleanup .rcs.cvs.co.options .rcs.cvs.cvsroot .rcs.cvs.module .rcs.cvs.tagprefix .rcs.cvs.testtagprefix
So each of those variables would pertain to the `cvs' section of the `rcs' branch.