Re: [Banshee-List] Logging in Banshee: use log4net?

[Julien Sobrier <julien sobrier net>]

Gabriel Burt wrote:
> On 11/7/06, Julien Sobrier <julien sobrier net> wrote:
>> Getting the right log for users is not easier. As you can see in the
>> thread  "[Banshee-List] howto avoid creating dirs on flash mp3 player",
>> a user has to put a Console.WriteLine at the right place in the right
>> file to get critical information about an issue.
> 
> This is a misunderstanding on your part.  The WriteLine I asked that
> person to add in was not something that *should* be logged.  We cannot
> spit out via a logger every single variable in Banshee, this one
> included.
> 
> Gabriel

What I mean is that Banshee could put a lot more debugging information
that can be enabled/disabled very easily. It would make sense to log
information read from HAL at the lowest debug level (Info or Debug) that
would be disabled by default. It does not mean that you have to ouptut
this information to a file or to the console every time your run banshee.

For example, in your log file configuration, you would not output by
default Debug, Info, but only Warn and Error for example:
<root>
    <level value="WARN" />
    <appender-ref ref="Console" />
</root>

Then, if a user need more debug information from Banshee.Dap, the
configuration can be changed:

<root>
    <level value="WARN" />
    <appender-ref ref="Console" />
</root>
<logger name="Banshee.Dap">
    <level value="DEBUG" />
</logger>

The goal is to make a lot of debug information available to
users/developers, but not enabled by default (in the sense not printed
out). Each user/developer can select what information they need by
defining the debug level they need, and from what class it should be
generated. So, if you are working on Plugin that touches, for example,
Banshee.Dap, you would enable the lowest debug level from Banshee.Dap
but keep only the Errors from the other Banshee classes.

I hope I was more clear.

Julien