Re: When to log? (best practices and localization)
- From: Karsten Wutzke <kwutzke@xxxxxx>
- Date: Fri, 31 Aug 2007 06:05:17 -0700
On 31 Aug., 13:59, ap...@xxxxxxxxxxxxxxxxxx wrote:
On 31 Aug, 12:16, Karsten Wutzke <kwut...@xxxxxx> wrote:
What is the best way to implement a log window? Find the log file and
display it in a text component? Again, would the best practice be to
localize those messages? I tend to rather not doing it, as opposed to
messages displayed on the GUI...
Don't. Log to a file instead. There are plenty of third-party tools
that can examine logfiles and take appropriate configurable actions
based on their contents. If the app needs to report a user error then
this is normal interaction and is separate from logging.
-Andrew Marlow
You mean not to localize log messages or those on the GUI? Didn't
become clear to me. As I wrote, I tend not to localize the log
messages, but those seen on the GUI.
Karsten
.
- Follow-Ups:
- References:
- When to log? (best practices and localization)
- From: Karsten Wutzke
- Re: When to log? (best practices and localization)
- From: apm35
- When to log? (best practices and localization)
- Prev by Date: Re: When to log? (best practices and localization)
- Next by Date: Re: When to log? (best practices and localization)
- Previous by thread: Re: When to log? (best practices and localization)
- Next by thread: Re: When to log? (best practices and localization)
- Index(es):
Relevant Pages
|