var fireBugTarget:FireBugTarget = new FireBugTarget()
Log.addTarget(fireBugTarget);

so I didn’t feel like I was hindering anyone one with this approach.

But I may still go back to making the LC Logger a Target so you’re not locked into importing our base classes. I’ll play around with it later this wk.

The logger will always be coupled to the Flex SDK, as I didn’t make it for Flash/AS3 apps.

I think that using LocalConnectionLog is a bit intrusive in the code and highly couples the code to proposed logging solution. I normally prefer using something more like:

private var logger : ILogger = Log.getLogger(”path.to.my.Clazz”)

which is not only coupled to Flex SDK and configure any specific Logger (LocalConnectionLogger) as a target from a configuration point of view. This way the logging code is not tighted to any implementation, swapping to a different impl would then be just a matter of changing configuration.

Using this approach you can even have different possible targets (i.e: TraceTarget for development, ServerLogTarget that sends logs across the wire, etc.)

Thanks for sharing this.