KMessage/KMessageHandler: a core/ui seperation for displaying message.

[Kevin Krammer]

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 at gmx.at>
Qt/KDE Developer, Debian User
Moderator: www.mrunix.de (German), www.qtcentre.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060529/05c5a301/attachment.sig>