X-Git-Url: https://oss.titaniummirror.com/gitweb?a=blobdiff_plain;ds=sidebyside;f=in%2Finheritance.md;fp=in%2Finheritance.md;h=c889a599f9e03c82cc162000c043dd213a4a28f2;hb=b5bc4ffdfbaa76db7cd4cdeb078097ec17024f6b;hp=6167c5f57066645721768c3f2846f13306accde5;hpb=c6d30c7f18e835e0b99032d01b1f8acd7f077ec6;p=webber.git

diff --git a/in/inheritance.md b/in/inheritance.md
index 6167c5f..c889a59 100644
--- a/in/inheritance.md
+++ b/in/inheritance.md
@@ -1,32 +1,58 @@
 title: Configuration inheritance
 linktitle: Inheritance
-parent: Webber
+parent: Configuration
+lang: en
 ctime: 2009-06-24
+mtime: 2010-07-06
+change: various clarifications, a better example
 
 = Overview =
 
-Internally, webber uses a bunch of `Holder` classes to store information
-(command-line options, config file options, parameters for a directory,
-parameters for a file).
+Internally, webber uses a bunch of `Holder` classes to store information.
 
-Each `Holder` "inherits" configuration entries from the layer above:
+We have objects of class `Holder` for this entities:
 
-* `options` for command-line options
-* `cfg` for entries from the command line
-* `direc` for information about a directory
-* `file` (either directly or via `get_current_file()` for data about the
-   currently rendered file
+* "`cfg`" stores [[configuration]] and [[commandline]].
+* "`direc`" stores per-directory variables
+* "`file`" stores attributes for each file that webber processes
 
-= Example =
+This is like the inheritance works:
+
+* "`direc`" inherits everything from "`cfg`". It can, however,
+  override anything. <small>In a future version of webber, the "`direc`"
+  object for directory "`foo/bar/`" will inherit from the
+  directory object for "`bar/`" and only the last one will inherit from
+  "`cfg`". But that's not yet coded.</small>
+* "`file`" inherits from "`direc`" and again is free to override
+  anything on a per-file basis.
 
-Due to parsing the [[command line|commandline]] there will exist an entry
-`options.style_dir`.
 
-However, you can also access this same value via `cfg.style_dir`,
-`direc.style_dir` and `file.style_dir`. Any one of them however could
-over-write the settings that originally was in `options`.
+= Example =
 
-Quite often you'll use this for the page template. In `webber.conf`, you
-specify `template: "default"`, which will be used for most pages. Any
-page that needs a different template will get `template: history` entry
-in it's header.
+Due to parsing the [[commandline]] the attribute "`style_dir`" have
+some value. If you don't specify one, it will be "default" by default.
+
+Now the [[configuration]] file "`webber.conf`" gets processed. It may
+set "`style`" to "twoframe", if you want a two-frame template for your
+web-site.
+
+Assuming you have a subdirectory with source-code examples. In this
+directory you have a file "`directory.conf`" which re-sets it to "default".
+This makes the default template work now only for your source-code
+examples.
+
+There's one page where you use the [[hierarchy]] plugin to generate a
+sitemap. This one page should have it's own template. Simply make the
+[[page|pageformat]] be like this:
+
+	title: Sitemap
+	template: sitemap
+
+	<%
+	  site = get_linear_sitemap()
+	%>
+	<ul>
+	% for level, page, link in site:
+	  <li id="sidemap${level}"><a href="${link}">${page.title}</a></li>
+	% endfor
+	</ul>