Application log level

[Andreas]

Hi

I have a suggestion that would be great if someone implemented. I
think it would be great with another log level for application level
informational messages. I have a server for an application i'm
building and I want to print informational messages to the servers log
when a client connects for example so that the end user can see what's
going on instead of just a black terminal.

For now I've solved this by creating a subclass of Log.Logger and I
store an instance of it in my own application but it's kinda ugly.

Thanks for a great simplistic logging library by the way!

Regards,
Andreas Falk

[Nate]

Hi Andreas,

You can use the INFO and other logging level for your application. Any 3rd party libraries you may be using (eg, KryoNet) should do all their logging with a specific category string, eg:

if (INFO) info("kryonet", "Some KryoNet message...");

You can use this category string to differentiate 3rd party messages from your application's messages. I usually don't pass a category string for my application to cut down on typing, eg:

if (INFO) info("My application's message...");

Subclassing Logger is the right way to filter messages. Eg, this code will only log messages that don't have a category:

Log.setLogger(new Log.Logger() {
    public void log (int level, String category, String message, Throwable ex) {
        if (category != null) return;
        super.log(level, category, message, ex);
    }
});

-Nate

--
You received this message because you are subscribed to the "minlog-users" group.
http://groups.google.com/group/minlog-users

To unsubscribe, reply using "remove me" as the subject.

[Andreas]

Subclassing in the way you show to filter messages is probably a lot
better solution than the way I was subclassing it. Thanks for the
help!

Andreas