On Tuesday 22 April 2014 09:59:39 Martin Klapetek wrote:
> On Tue, Apr 22, 2014 at 12:53 AM, Aleix Pol 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 goin
On Tue, Apr 22, 2014 at 12:53 AM, Aleix Pol 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
On Thu, Apr 17, 2014 at 11:08 PM, Giorgos Tsiapaliokas <
giorgos.tsiapalio...@kde.org> wrote:
> Hello,
>
> I also like the more user friendly ui errors.
>
> On Thursday 17 of April 2014 17:49:35 Aleix Pol wrote:
> > +1, I would like to add though that we should probably adopt a 0 qDebug
> > policy
On Friday 18 of April 2014 10:04:02 Bhushan Shah wrote:
> This is case, but still you are missing two stuffs..
>
> 1) We still have some qDebug and kDebug
kDebug doesn't count because it is deprecated code
which should be replaced.
qDebug is using "default" as its category.
default = false
wil
On Fri, Apr 18, 2014 at 2:38 AM, Giorgos Tsiapaliokas
wrote:
> If we have 0 debug output how does this makes it easier?
> The existing debug output, if you filter it gives some hints about
> what is going on, IMO this is very useful. No?
This is case, but still you are missing two stuffs..
1) We
Hello,
I also like the more user friendly ui errors.
On Thursday 17 of April 2014 17:49:35 Aleix Pol wrote:
> +1, I would like to add though that we should probably adopt a 0 qDebug
> policy as well.
>
> It's useful to have them when working on a feature, but having things like:
> plasma_shell(2
On Thu, Apr 17, 2014 at 5:35 PM, Marco Martin wrote:
> On Thursday 17 April 2014, Mark Gaiser wrote:
> > Does this mean that the console output is also going to be "user
> friendly"?
> > By console output i mean the output you get when you start
> > plasma-desktop from a console.
> >
> > I think
On Thursday 17 April 2014, Mark Gaiser wrote:
> Does this mean that the console output is also going to be "user friendly"?
> By console output i mean the output you get when you start
> plasma-desktop from a console.
>
> I think that output should be as detailed as possible (aka, not user
> frien
On Thu, Apr 17, 2014 at 9:05 PM, Marco Martin wrote:
> for console output, there is one and only one solution. go and hunting every
> error message, fixing it properly
+1 :P
--
Bhushan Shah
http://bhush9.github.io
IRC Nick : bshah on Freenode
__
On Thu, Apr 17, 2014 at 4:06 PM, Bhushan Shah wrote:
> Hello,
>
> Currently in Plasma (both Next/KDE4) we are showing raw qml error
> messages when applet fails to load.
>
> But to our users what thing is useful is "This applet failed to
> load". and to developers "Why?"
>
> So I am thinking to c
On Thu, Apr 17, 2014 at 7:41 PM, Marco Martin wrote:
> may be good, just have a couple of text labels, one that just shows "this
> applet failed to load" then a "Details..." button that shows the real error
> message. if this is done, it should be nothing more complicated, just a few-
> liners mod
On Thursday 17 April 2014, Bhushan Shah wrote:
> Hello,
>
> Currently in Plasma (both Next/KDE4) we are showing raw qml error
> messages when applet fails to load.
>
> But to our users what thing is useful is "This applet failed to
> load". and to developers "Why?"
may be good, just have a coup
Hello,
Currently in Plasma (both Next/KDE4) we are showing raw qml error
messages when applet fails to load.
But to our users what thing is useful is "This applet failed to
load". and to developers "Why?"
So I am thinking to change AppletError somehow so that it shows simple
user friendly error
13 matches
Mail list logo
