[Kss-devel] Getting rid of the KSS-log

[Balazs Ree]

On Tue, 13 Nov 2007 00:36:53 +0100, Godefroid Chapelle wrote:

> Malthe Borch wrote:
>> Hey Godefroid, –––
>> 
>> Could we not have KSS in debug-mode unless the KSS-tool is in
>> debug-mode? It makes it almost impossible to do js-development.
>> 
>> \malthe
> 
> I think it makes sense.
> 
> What does the list think of this ?


Duncan also asked for this. I agree we ahould have a second cookie and in 
the ui a second button: "follow/ignore tool setting" which by default 
should stand on "follow".

I may add this soon to trunk if there are no objections.
 
> PS : However, why do you want to do js development if not to contribute
> to KSS ;-) ?

There is another thing that may make sense actually. We should manage log 
levels from within kss and enable filtering of different log levels from 
the kss level. (info/debug/etc.) This could also be governed by cookies, 
and later by the to-be-developed kss config tool.

Originally when we only had the MochiKit logger the logging level and 
filtering was handled by the logger itself. But now we have different 
loggers, and all loggers handle this differently so this does not work 
well any more. For example in FireBug we should not issue "debug" 
messages at all, they put the traceback 
information on the right of the line and cover important part of the 
message. For FireBug we should issue "info" level messages instead of 
"debug" and handle the info/debug level difference ourselves. Then the 
filtering I propose makes even more sense. Similarly each logger may 
require a different handling for this.


-- 
Balazs Ree