-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jens Vagelpohl wrote: > > On 15 Nov 2005, at 14:24, yuppie wrote: > >> The notes should be logged *and* used for reporting in the ZMI. >> >> >> Implementation: >> >> I'm no logging expert, so I might well be missing something. The >> state of the art seems to be using the Python logging package (PEP >> 282). Is it possible to use that framework for reporting as well? It >> doesn't look like that. >> >> Replacing the 'note' method in ISetupContext with a more logger like >> API and sending the notes to the Python logger *and* to TTW reports >> might be the way to go. > > > There could be a "multiplexer" that logs to the standard Zope event log > *and* keeps the messages in a memory buffer to be displayed in the > browser. This could be done in a separate class or a logging API could > be added to ISetupContext. Should be easy to do, really.
I *think* the current setup tool creates a text file with log messages in it, and stores that file inside the tool. I would prefer to maintain the data persistently, rather than in RAM; the API for that could be extended, of course. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDekyJ+gerLs4ltQ4RApNNAKCMFTWqwLFrhl3618ecitJPQYB8zwCgkMhT k0O0Ef4I2DTQhHMactiF/CM= =NOSF -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - [email protected] http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
