hi freeminders,
when developing i like, no, i need to have debug
output. in freemind one would fulfill this task using
System.out.println(). but(!), always in and
outcommenting of those statements is somewhat tiresome.
now, there is log4j which is a powerful tool to channel
debug output reasonable. disadvantage would be: we need
to ship log4j.jar when importing the log4j packages.
furthermore, i dont think freemind has reached the
complexity for a reasonable application of all those
log4j features already.
so, i implemented a lightweight class that uses
log4j-syntax, yet is way smaller in features and loc
:-) using this we could write proper debug-logs and
still could discuss whether integration of log4j would
be useful and when it'd be useful...
description:
------------
freemind.main.Freemind now has a static member
freemindLog of type freemind.util.LogFile
use the methods
freemindLog.info("message")
freemindLog.warn("message")
freemindLog.error("message")
freemindLog.fatal("message")
instead of System.out.println("message")
to invoke message-printing start freemind with argument
'--debug'
if you want to redirect output to a file set
freemindlog = %logfilename%
leave it empty to print to System.out
best regards and thanks for your great work...
joerg
diff file and logfileclass
Logged In: YES
user_id=885594
Hi Joerg,
unfortunately there is already a logging/tracing mechanism
in freemind. From the FreeMindMain interface you can
retreive a logger using the standard java logging api
instead of log4j.
Please use this logging facility.
Chris.
Hi,
the usual logging system is used in FreeMind nowadays. Thanks anyway, Chris