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

List:       kde-core-devel
Subject:    Re: RFC: Strategy for integrating the Nana debugging library
From:       Mirko Sucker <mirko.sucker () unibw-hamburg ! de>
Date:       1999-12-19 20:09:24
[Download RAW message or body]

David Faure wrote:
> > The logging support, the first thing that comes to discussion, does not seem
> > the most important thing for me. Since we have kdebug already, I thing we are
> > able to continue to use some parts of kdebug.
> Agreed.
> > Mostly, I will redirect Nana logging messages to kdebug (the message handler is
> > defineable). This would save us form having to rewrite the dialog and debug area
> > stuff, and all messages written from the Nana logging macros would appear in
> > the same buffer/daemon/whatever that is selected in kdebug. Additionally, this
> > option requires the least code changes and the smoothest way of integration.
> 
> I don't see how that would work. If "nana" redirects the calls to kdebug,
> how does it figure out the debug area code ? This isn't handled by nana...
> Does this mean patching nana to add debug area codes to every macro ?
My point is that I think only few messages will be printed through the
nana macros themselfes. Actually, everything we write in the kde sources
will use kdebug. So, only the messages send through nanas logging should
be emitted through kdebug, using a kind of "general" area (I know, there
is none, currently). This is mainly to support code not coming from KDE
CVS. Should be easy. This way all messages from other code will appear
in syslog, if you selected it in the kdebug dialog. 
Greetings,
--Mirko.
-- 
Denn der  Mensch  liebt und ehrt den  Menschen,  solange er ihn
nicht zu beurteilen vermag, und die Sehnsucht ist ein Erzeugnis
mangelhafter Erkenntnis. (Thomas Mann)

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