UI

UI and logs

Expose to the rascal

Having correct logs in a framework is not so easy. The best approach would be to expose one "ui" object to the rascal. It would be great for the users to be able to tune the output the way the want it (filtering, modifying, etc).

Since imapfw is relying on the logging module we might like to use more advanced features from it. However, I have no clue to say this would be the best. We might want our own logging sub-system and use the official logging module as a low-level driver.

This would be great to write a proof of concept so we can see where we go.

• Allow tuning the UI by exposing object(s) to the rascal.

  • Introduce --logfile.
  • Better intregation with logging formatters.

• Colorized output.

• Remove passwords from logs.

• Sometimes, exceptions are delayed in logs: print reason ASAP and raise.