[Adium-devl] Log Files

[Augie Fackler]

FWIW, the filtering I built is rather simplistic - it works well for  
the joscar stuff because you will have a reasonable idea of what  
you're looking for in advance - it flushes the contents of the window  
and reloads them whenever you change the search criteria, which makes  
it kind of crappy for long-term logs.

Maybe we should have a hidden pref that dictates how many AILog/ 
joscarLog entries we store?

I have also seen Adium logs get gihuge - over 600 megs in about 2  
days of minor IMing if we start storing joscar logs...

Augie

On Sep 5, 2006, at 10:55 PM, Evan Schoenberg wrote:

>
> On Sep 5, 2006, at 8:09 PM, David Smith wrote:
>
>> 	I have a patch ready that switches us over to using Console to view
>> logs; the main advantage of this is that we can filter them, and we
>> get to delete a nib and a class. The main disadvantage is that we're
>> writing logs to disk. I'm curious about whether people think that's a
>> big problem or not.
>
> Augie added filtering to the joscar debug log, which would be  
> pretty easy to port over to our own... the class is near-zero bytes  
> in deployment, though the nib sticks around (we could delete it in  
> the Makefile).
>
> I'm not averse to using Console instead... in fact, it'd be kinda  
> nice to have a longer backlog of debug logging available even if  
> the window isn't open, and to be able to log things around a  
> crasher and have them be visible (instead of having to use NSLog()  
> if you expect Adium will quit).
>
> -Evan
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com