#2 Add flexible output specification

[Rob van Dort]

The concept of LimpidLog is great for certain use
cases.
Currently the output of LimpidLog is fixed as built in
LimpidLog code.

It would be a powerful enhancement to be able to
specify the format of the output.

I suggest using Velocity for this:
http://jakarta.apache.org/velocity

LimpidLog should provide a number of context items,
such as:
- current package
- current class
- current method
- current method parameter list
- current time
- whatever appears to be useful

An output specification could be:
"Currently running class $Class method $Method at
$Time"
This would yield: "Currently running com.xyz.test.Foo
method run at Tue, 19 Sep 2006 15:38:56"

Both literal Velocity output specifications and
Velocity template files (*.vm) should be accepted.

Idea: use an output specification hierarchy:
- general
- general by event (e.g. <init>)
- class specific
- class / method specific