Why there is no setting to disable QA?
Hi nicolai Le 17/1/16 11:29, Nicolai Hess a écrit :
Hi
Why there is no setting for that?
Stef
You can remove the Nautilus plugin (Nautilus window menu -> plugin manager)
Yes I saw looking around. Now I have to dive into it to script it so that I avoid to be forced as today to redo my screenshots (to avoid all the false positive on class creation). Because else
For the spotter and inspector integration, there is a setting (default "disabled")
You can simply do `QANautilusPlugin uninstall`. I have not figured out how to put it in the prefs. Now about the false positives⦠I donât know what you are talking about, but I suspect that it is about something like âclass not being usedâ. Now if it is not being used itâs not a false positive, itâs just a useless information. What we can do, is put this rules into âinformationâ category and disable it in settings. Cheers. Uko
On 17 Jan 2016, at 11:47, stepharo <stepharo@free.fr> wrote:
Hi nicolai
Le 17/1/16 11:29, Nicolai Hess a écrit :
Hi
Why there is no setting for that?
Stef
You can remove the Nautilus plugin (Nautilus window menu -> plugin manager) Yes I saw looking around. Now I have to dive into it to script it so that I avoid to be forced as today to redo my screenshots (to avoid all the false positive on class creation). Because else For the spotter and inspector integration, there is a setting (default "disabled")
On Sun, Jan 17, 2016 at 7:33 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
You can simply do `QANautilusPlugin uninstall`. I have not figured out how to put it in the prefs.
Now about the false positives⦠I donât know what you are talking about, but I suspect that it is about something like âclass not being usedâ. Now if it is not being used itâs not a false positive, itâs just a useless information. What we can do, is put this rules into âinformationâ category and disable it in settings.
Or check class creation time and don't display message until its a week old ??. cheers -ben
Cheers. Uko
On 17 Jan 2016, at 11:47, stepharo <stepharo@free.fr> wrote:
Hi nicolai
Le 17/1/16 11:29, Nicolai Hess a écrit :
Hi
Why there is no setting for that?
Stef
You can remove the Nautilus plugin (Nautilus window menu -> plugin manager)
Yes I saw looking around. Now I have to dive into it to script it so that I avoid to be forced as today to redo my screenshots (to avoid all the false positive on class creation). Because else
For the spotter and inspector integration, there is a setting (default "disabled")
We have also instance variables not written or read class comment is empty And I find that disruptive for a student starting with Pharo. Le 17/1/16 12:33, Yuriy Tymchuk a écrit :
You can simply do `QANautilusPlugin uninstall`. I have not figured out how to put it in the prefs.
Now about the false positives⦠I donât know what you are talking about, but I suspect that it is about something like âclass not being usedâ. Now if it is not being used itâs not a false positive, itâs just a useless information. What we can do, is put this rules into âinformationâ category and disable it in settings.
Cheers. Uko
On 17 Jan 2016, at 11:47, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Hi nicolai
Le 17/1/16 11:29, Nicolai Hess a écrit :
Hi
Why there is no setting for that?
Stef
You can remove the Nautilus plugin (Nautilus window menu -> plugin manager)
Yes I saw looking around. Now I have to dive into it to script it so that I avoid to be forced as today to redo my screenshots (to avoid all the false positive on class creation). Because else
For the spotter and inspector integration, there is a setting (default "disabled")
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user. Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity. Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future. Cheers. Uko
On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
"Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future." Amen ! On Sun, Jan 17, 2016 at 7:07 PM Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user.
Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity.
Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future.
Cheers. Uko
On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
On Jan 17, 2016, at 9:06 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user.
Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity.
Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future.
+1000!
Cheers. Uko
On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
On 17 Jan 2016, at 18:12, Eliot Miranda <eliot.miranda@gmail.com> wrote:
On Jan 17, 2016, at 9:06 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user.
Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity.
Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future.
+1000!
+1 me too. I remember when Stef introduced the mark on uncomment classes I was against: I was finding the exclamation mark too disruptive. Then time proved me wrong: is a nice way to remember people they need to add class comments (and my own production of comments increased considerably). I think QA will do the same: it might look disruptive, but is educative in fact. cheers, Esteban
Cheers. Uko
On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
On Jan 17, 2016, at 9:06 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user.
Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity.
Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future. +1000! +1 me too. I remember when Stef introduced the mark on uncomment classes I was against: I was finding the exclamation mark too disruptive. Then time proved me wrong: is a nice way to remember people they need to add class comments (and my own production of comments increased considerably). ;D I think QA will do the same: it might look disruptive, but is educative in fact. Yes but you see when this is really first first first class you write in Pharo.... So I want everybody to have QA on! and to fix them! And I want more rules I want specific rules for everything every frameworks but not on the first class a newbie is writing. People should remember when is the last time they defined a class for the first time. I did Python exercises with my son and it was in plain text editor and it was working.
Stef
Ok I'm wrong and stupid. Thanks for the reminder. I disabled QA in the Mooc images.
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user.
Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity.
Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future.
Cheers. Uko
On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
We all hate you Stef , its not you , its us :D Seriously though its not that necessary to baby sit begineers, the important thing for a beginner is to love coding. I remember when I started I would have begged to have an IDE like Pharo and a language like pharo, instead all I had was Locomotive Basic, command line and a really badly written and even worse translated book. I would have begged for code critics . An IDE that tells me what I do wrong ? Are you serious ? It would have been sci fiction in 1988. Did I hate coding ? No Seriously who expectes coding to be easy at start.... only lazy and naive people. Neither make good coders anyway. I think with your passion about coding and the great design of Pharo as an IDE it will be hard not to fall in love with coding. All begineer hand is friendly hand to point them towards the right direction, just some reassurance that they do things right and that their mind is on the right path. A side note, I am a bit sceptical for your decision to go down the Pharo 5 route, are we sure Pharo 5 will be stable enough for a begineer to use in the time of the MOOC ? Esteban already fixed most of my problems with pharo 5, I am actually closing my bug reports now, but still it seems to me a bit risky and maybe it puts unnecessary pressure on Esteban and the Moose people. I any case I wish you success with MOOC :) On Sun, Jan 17, 2016 at 7:27 PM stepharo <stepharo@free.fr> wrote:
Ok I'm wrong and stupid. Thanks for the reminder. I disabled QA in the Mooc images.
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user.
Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity.
Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future.
Cheers. Uko
On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
Seriously though its not that necessary to baby sit begineers, the important thing for a beginner is to love coding. I remember when I started I would have begged to have an IDE like Pharo and a language like pharo, instead all I had was Locomotive Basic, command line and a really badly written and even worse translated book. I would have begged for code critics .
Not for the first class :)
An IDE that tells me what I do wrong ? Are you serious ? It would have been sci fiction in 1988. :) but now there is eclipse. Did I hate coding ? No
Seriously who expectes coding to be easy at start.... only lazy and naive people. Neither make good coders anyway. I think with your passion about coding and the great design of Pharo as an IDE it will be hard not to fall in love with coding. All begineer hand is friendly hand to point them towards the right direction, just some reassurance that they do things right and that their mind is on the right path.
A side note, I am a bit sceptical for your decision to go down the Pharo 5 route, are we sure Pharo 5 will be stable enough for a begineer to use in the time of the MOOC ? WE MUST MAKE IT STABLE BY THEN! We should release often and stable. And Pharo 50 should be. Because after we have Pharo 6.0 and I want Xtreams and Bloc
Esteban already fixed most of my problems with pharo 5, I am actually closing my bug reports now, but still it seems to me a bit risky and maybe it puts unnecessary pressure on Esteban and the Moose people.
I any case I wish you success with MOOC :)
On Sun, Jan 17, 2016 at 7:27 PM stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Ok I'm wrong and stupid. Thanks for the reminder. I disabled QA in the Mooc images.
> Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user. > > Thatâs why I kindly ask not to call this things âfalse positivesâ :). > I thinks that it makes sense to be bale to disable some critics by their severity. > > Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future. > > Cheers. > Uko > > > > >> On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: >> >> Le 17/01/2016 16:04, stepharo a écrit : >>> We have also >>> instance variables not written or read >>> class comment is empty >>> >>> And I find that disruptive for a student starting with Pharo. >>> >> I find that instructing. >> When I create a class and I see those messages it's like "objectives". I >> need to correct that and it help me not to avoid the documentation. >> >> -- >> Cyril Ferlicot >> >> http://www.synectique.eu >> >> 165 Avenue Bretagne >> Lille 59000 France >> > >
you are the boss... go for it and anywhere I can help I am here. I want Pharo to succeed :) On Sun, Jan 17, 2016 at 7:48 PM stepharo <stepharo@free.fr> wrote:
Seriously though its not that necessary to baby sit begineers, the important thing for a beginner is to love coding. I remember when I started I would have begged to have an IDE like Pharo and a language like pharo, instead all I had was Locomotive Basic, command line and a really badly written and even worse translated book. I would have begged for code critics .
Not for the first class :)
An IDE that tells me what I do wrong ? Are you serious ? It would have been sci fiction in 1988.
:) but now there is eclipse.
Did I hate coding ? No
Seriously who expectes coding to be easy at start.... only lazy and naive people. Neither make good coders anyway. I think with your passion about coding and the great design of Pharo as an IDE it will be hard not to fall in love with coding. All begineer hand is friendly hand to point them towards the right direction, just some reassurance that they do things right and that their mind is on the right path.
A side note, I am a bit sceptical for your decision to go down the Pharo 5 route, are we sure Pharo 5 will be stable enough for a begineer to use in the time of the MOOC ?
WE MUST MAKE IT STABLE BY THEN! We should release often and stable. And Pharo 50 should be. Because after we have Pharo 6.0 and I want Xtreams and Bloc
Esteban already fixed most of my problems with pharo 5, I am actually closing my bug reports now, but still it seems to me a bit risky and maybe it puts unnecessary pressure on Esteban and the Moose people.
I any case I wish you success with MOOC :)
On Sun, Jan 17, 2016 at 7:27 PM stepharo <stepharo@free.fr> wrote:
Ok I'm wrong and stupid. Thanks for the reminder. I disabled QA in the Mooc images.
Thatâs the point. Someone finds this disruptive, someone instructing. But itâs always a true information. So here we are not dealing with the faults of algorithm but with a way we are communicating a data with a user.
Thatâs why I kindly ask not to call this things âfalse positivesâ :). I thinks that it makes sense to be bale to disable some critics by their severity.
Also I think that itâs a good thing to teach beginners to write class comments. You donât need special skills for that and making it a habit from the beginning will payoff in the future.
Cheers. Uko
On 17 Jan 2016, at 16:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 17/01/2016 16:04, stepharo a écrit :
We have also instance variables not written or read class comment is empty
And I find that disruptive for a student starting with Pharo.
I find that instructing. When I create a class and I see those messages it's like "objectives". I need to correct that and it help me not to avoid the documentation.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
participants (8)
-
Ben Coman -
Cyril Ferlicot D. -
Dimitris Chloupis -
Eliot Miranda -
Esteban Lorenzano -
Nicolai Hess -
stepharo -
Yuriy Tymchuk