KMessage/KMessageHandler: a core/ui seperation for displaying message.
mattr at kde.org
Sun May 28 21:13:51 BST 2006
On Sunday 28 May 2006 14:22, Frans Englich wrote:
> On Sunday 28 May 2006 19:01, Matt Rogers wrote:
> > On Sunday 28 May 2006 12:06, Michaël Larouche wrote:
> > > The patch include:
> > > -KMessage,KMessageHandler,KMessageBoxMessageHandler,KPassivePopupMessag
> > >eH an dler -KMessage_Test in kdeui/tets
> > Why are you making KMessage::internalShowStdOutMessage a generic logging
> > mechanism? We have kDebug for debug messages, so we should remove any
> > sort of debug message handling from KMessage.
> I disagree on removing the enum(e.g, removing the possibility), but I can
> understand skipping using KMessage for debugging in some scenarios. I want
> the possibility to exist, because in some cases a kDebug call is
> insufficient. For example, you want to receive debug data in an ordered
> fashion somewhere else, or in some other way intercept & display it.
I didn't say anything about removing the enum. Where do you get that idea?
Please don't put words into my mouth or assume I meant something other than
what I wrote.
More information about the kde-core-devel