From 53e64ab8f1cb2835e686feb677e8209aff13bfef Mon Sep 17 00:00:00 2001 From: Matthew Wall Date: Sun, 3 Feb 2013 00:27:44 +0000 Subject: [PATCH] make the introductory flow of customizing slightly easier to follow --- docs/customizing.htm | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/customizing.htm b/docs/customizing.htm index 8460fd54..f98a52ec 100644 --- a/docs/customizing.htm +++ b/docs/customizing.htm @@ -109,12 +109,13 @@ True. These advanced topics are covered later in the section Customizing the weewx service engine.

-

The standard reporting - service, StdReport

+ +

The standard reporting + service, StdReport

For the moment, let us focus on the last service, weewx.wxengine.StdReport, the standard service for creating reports. This will be what most users will want to customize even if it means changing just a few options.

-

Reports

+

Reports

The Standard Report Service runs zero or more Reports. Which reports get run is set in the configuration file weewx.conf, in section [StdReport].

@@ -144,7 +145,7 @@ in that it they don't actually generate anything. Instead, they use the reporting service engine to arrange for things to be transferred to a remote server.

-

Skins

+

Skins

Each report has a Skin associated with it. For most reports, the relationship with the skin is an obvious one: it contains the templates, any auxiliary files such as background GIFs or CSS style sheets, and a skin @@ -160,7 +161,7 @@ and include a skin configuration file, although they are quite minimal.

Skins live in their own subdirectory located in $HTML_ROOT/skins.

-

Generators

+

Generators

To create their output, skins rely on one or more Generators, code that actually create useful things such as HTML files or plot images. Generators can also copy files around or FTP/rsync them to remote locations. The default