Add sections and automatic indentation of messages

--* SECTION "Doing this, doing that"
--* /SECTION

Actually, /SECTION is not needed because the section is implicitly closed by 
the next section, or 
by closing the upgrade block.

But if we choose nested sections, than /SECTION is needed. But why would we 
want nested sections? 
Only when we want to display progress in an advanced way.

But then it might be better to add the nesting level to the command itself:

--* SECTION.1 "Doing this, doing that"
--* SECTION.2 "This"
--* SECTION.2 "That"
--* SECTION.1 "Something else"

SECTION is of course implicitly the same as SECTION.1, in case you don't want 
to nest the 
sections.

And we should add automatic indenting, so that the upgrade file writer doesn't 
have to, and the 
upgrade file becomes user-interface independent.

In fact, section closing seems ridiculous, you never close a section to go back 
to the parent 
section. If you choose to divide a section in subsections, than its all the 
way. I wouldn't know 
where to place the progress dots on the command line. With an advance 
swing-like user interface it 
would be different, but you could always end a section with a child section 
"Cleaning up" or 
something like that.

In the future when we find out that this was a horrible decision we can always 
add an option like:

SECTION NESTING MARKER which nests using section start and end markers.
SECTION NESTING SUFFIX which does nesting through the section suffix.

This issue is related to issue #74.

Original issue reported on code.google.com by rene.de....@gmail.com on 23 May 2010 at 12:08

sindicate / solidbase

Add sections and automatic indentation of messages #79