Consider using `logging` methods instead of `IJ.log()`

[ehrenfeu]

Question:

• Is there a different effect between e.g. log.warning() and IJ.log()?
• If yes, what's the rationale behind using IJ.log()?
• Should we have a function abstracting the IJ.log() call?
  • Additional things could be done there (timestamp-prefix, extra logging targets, ...).
  • We'd have a single place where changes could be applied when necessary, instead of doing stuff at each and every occurrence of an IJ.log() call.

Relevant lines specifically in this module:

python-imcflibs/src/imcflibs/imagej/misc.py

Lines 253 to 263 in 9ad2b0f

	IJ.log(
	"\\Update%i:%s[%s%s] %i/%i\r"
	% (
	line_number,
	timed_log(prefix, True),
	"#" * x,
	"." * (size - x),
	progress,
	total,
	)
	)

python-imcflibs/src/imcflibs/imagej/misc.py

Line 276 in 9ad2b0f

IJ.log(time.strftime("%H:%M:%S", time.localtime()) + ": " + message + " ")

[lguerard]

From my understanding log.warning() will output in the console of Fiji, not in the log window.

My approach is to use everything log.* for things that aren't important to the users but could be important to me if/when getting back to the script, and use IJ.log for everything that would be important to the user (eg. the progress bar, the explanation of the current step...)

[ehrenfeu]

So glad I remembered this issue when I created #53 today 🤦🏼

I'll move this one out of milestone 1.5.0 as this should not be blocking us from a release...