Logging is a simple task with bit of complexity thrown in with multi-channel, configurability, formatting to be included.

Picking up from Log4J that seems to be a standard:VisualAge has adopted it as is.. Log4S

* Loggers ( capture )
* Appenders ( stream to multi channel )
* Layouts ( formatting with regex )

formatting especially in emitting the current timestamp and the class>>method automatically

I feel Toothpick can be extended to the above and with clear separation of lean classes it can serve the enterprise class of apps well.

While SimpleLog, seems equally good, but I have not used, seems to offer one more error level and similar appenders capability.

****************************
One observation I have is for all logger libraries to adopt same api for logging error viz:

logger level: #warn message: 'This warning' .� ( category is #default and most often usable)
logger category:#perf level: #warn message: 'Below threshold of 100 trans per second' .

convenience messages thereafter also be the same api viz:
logger info: 'This info' . logger warn: 'This warning' . logger error: 'this exception'� et als..

It will make it easier to switch logging framework if so required in future.



On Wed, Apr 10, 2013 at 10:12 AM, G�ran Krampe <goran@krampe.se> wrote:
On 04/10/2013 03:22 AM, Mariano Martinez Peck wrote:
shouldn't be better to use the newer paulepulpe or something like that
done by Santiago Braga�olo? I guess he did not write it from scratch
just because....

Personally I found Toothpick complicated back when I created SimpleLog.

I also felt that playing nice with the outside world was important when it comes to logging so SimpleLog reuses the syslog levels standard and has a UDP emitter into syslog as an option.

And a friend added a Morphic UI with filtering etc, very nice during development!

regards, G�ran