[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KMessage/KMessageHandler: a core/ui seperation for displaying
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2006-05-29 15:57:31
Message-ID: 200605291757.38222.kevin.krammer () gmx ! at
[Download RAW message or body]


On Sunday 28 May 2006 23:14, Leo Savernik wrote:
> Am Sonntag, 28. Mai 2006 22:46 schrieb Michaël Larouche:
> > I use internalShowStdOutMessage as a last ressort thing. They don't mean
> > to be really useful, just to show the message if the developer didn't
> > setup a MessageHandler.
>
> Well, it *is* useful. It is the lowest common denominator that is
> guaranteed to work everywhere (even if not readily visible in GUI-apps, but
> proper defaults save us bug reports). In a cli-tool, it's the "natural" way
> of handling messages.
>
> Besides that I'm still of the opinion that all messages should go to stderr
> by default, probably making it configurable.

Maybe it should work on a chain of message handlers, so it can write to 
stderr, display an UI and log with a session equivalent of syslogd

Especially when using passive popups as the GUI representation it might be 
quite useful to have a "history" available.

Cheers,
Kevin

-- 
Kevin Krammer <kevin.krammer@gmx.at>
Qt/KDE Developer, Debian User
Moderator: www.mrunix.de (German), www.qtcentre.org

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]