widelands-dev team mailing list archive

[Paul Pogonyshev <pogonyshev@xxxxxxxxx>]

I wanted to try at writing an AI, but currently it's impossible to write
any useful debug messages, because they get clogged with stuff I have no
interest in. Note that by default it doesn't filter anything, so with this
patch Widelands works just as before. What I want to achieve is to give
developers ability to silence uninteresting stuff and concentrate on what
they need only.


On 15 March 2013 01:46, SirVer <SirVer@xxxxxx> wrote:

> I did not jet look at the code - but I feel like this is a bad idea: we
> should just cut the logging down if possible and not introduce filtering to
> it. Also, sometimes you filter out the messages that show the real problem
> because you are too focused on your own little problem and expect your bugs
> in there - dumping to a file and then looking at the output in an editor is
> nearly always the better option. And there is always grep to filter output.
>
> So in general I am not too fond of merging this feature. I'd like to hear
> more opinions though, so people speak up.
>
> I just wished you told anyone that you wanted to work on this beforehand :/
> --
>
> https://code.launchpad.net/~doublep/widelands/improved-logging/+merge/153200
> You are the owner of lp:~doublep/widelands/improved-logging.
>

-- 
https://code.launchpad.net/~doublep/widelands/improved-logging/+merge/153200
Your team Widelands Developers is requested to review the proposed merge of lp:~doublep/widelands/improved-logging into lp:widelands.