Proposal to hide raw QML errors in Plasma Next

[Martin Gräßlin]

On Tuesday 22 April 2014 09:59:39 Martin Klapetek wrote:
> On Tue, Apr 22, 2014 at 12:53 AM, Aleix Pol <aleixpol at kde.org> wrote:
> > You know what's going on by checking what the code is doing.
> > 
> > Can you imagine how life would be if QString class started to output
> > information "so that you know what's going on"?
> > 
> > We add output if something weird is happening so that the user sees it,
> > like QML which gives us valuable information of what's going wrong. Then
> > we
> > have random output information that somebody, some day, decided to push to
> > our codebase.
> 
> I would like to even go as far as going through all qDebugs in plasma/shell
> and remove 90% of them before the release, the output /is/ unnecessary too
> noisy and I absolutely agree that the production-ready code should just
> output stuff if anything goes wrong, maybe some system status changes like
> "plasma loaded", that's useful for "anchoring" the output that would come
> from users. Absolutely worst are debugs on timers (try opening the
> wallpaper config and look at console), that should be killed with fire.

There's also the option to introduce useful categorized logging. E.g. we could 
have a different category for things like the wallpaper dialog.

And yes I agree that it's too chatty and that obviously results in the 
important messages not being noticed.

Cheers
Martin G.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140422/b44b6ea3/attachment.sig>