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

List:       kde-devel
Subject:    Re: one (easy) goal for KDE 1.1.1:
From:       David Faure <faure () kde ! org>
Date:       1999-03-31 22:09:27
[Download RAW message or body]

On Wed, Mar 31, 1999 at 11:57:03PM +0200, Christian Esken wrote:
> On Wed, 31 Mar 1999 David Faure wrote:
> >On Wed, Mar 31, 1999 at 07:18:21PM +0200, Harri Porten wrote:
> >> Preston Brown wrote:
> >> > 
> >> > PLEASE make sure that all your output to stdout is done via debug() or on
> >> > e of the other Qt debugging functions, rather than printf, fprintf, and
> >> > the like.  This means we can simply define -DNO_DEBUG at compile time and
> >> > remove all the crap that goes to stdout.  This is really one of the things
> >> > that makes the apps look more polished, like they aren't still being
> >> > debugged.  While we all know apps are ALWAYS being debugged, the user
> >> > doesn't care and doesn't understand when all the stuff is spewed up on the
> >> > screen.
> >> 
> >> What about the stuff being pumped out by kdebug() ? libspell writes a
> >> _lot_ of info on the screen which makes using kedit quite funny for
> >> beginners. May I change the default value for KDEBUG_INFO messages to
> >> output no 4, i.e. /dev/null ? Developers could change that config
> >> setting later.
> >
> >I totally agree. Remove the crap.
> >Developers can still ask users to use Ctrl+Shift+F12 to re-enable it, in
> >case of a bug report.
> 
> What about non-GUI programs, or if the program crashes on startup???
In both of theses cases, there is very little debug output !
A non-GUI program has none (it would annoy the user)
and about crashes on startup, debug output helps very little.
Better start the program in gdb.

Anyway, do you know any 1.1.x program that crashes ? ;-D
If yes, time to fix it !

-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today

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