Smalltalk › Frameworks & Tools › Moose

QualityAssistant v0.4

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Uko2

QualityAssistant v0.4

Hi everyone!

Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter.

I’m happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta-. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects.

Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didn’t forget some details about your code.

Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues

Have a nice week!

Uko

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

EstebanLM

Re: [Pharo-dev] QualityAssistant v0.4

this is so good.

what about integrate it to Pharo?

cheers,

Esteban

On 22 Apr 2015, at 08:58, Yuriy Tymchuk <[hidden email]> wrote:

Hi everyone!

Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter.

I’m happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta-. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects.

Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didn’t forget some details about your code.

Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues

Have a nice week!
Uko

<critics.jpg>

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Uko2

Re: [Pharo-dev] QualityAssistant v0.4

I am definitely interested in it. Let me know what I should do for this.

I haven’t got a lot of feedback from users, but I fixed problems reported by my group and Alex Bergel. The remaining reported issues are quite minor and related to how SmallLint works. Changes to SmallLint will arrive later after I figure out what the rules are about and what is the way to improve them.

Cheers,

Uko

On 22 Apr 2015, at 12:23, Esteban Lorenzano <[hidden email]> wrote:

this is so good.
what about integrate it to Pharo?

cheers,
Esteban

On 22 Apr 2015, at 08:58, Yuriy Tymchuk <[hidden email]> wrote:

Hi everyone!

Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter.

I’m happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta-. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects.

Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didn’t forget some details about your code.

Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues

Have a nice week!
Uko

<critics.jpg>

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Tudor Girba-2

Re: [Pharo-dev] QualityAssistant v0.4

In reply to this post by Uko2

Hi,

I only took a brief look, but I think that reaching the no-input-required situation is a major step forward.

Nice job. Keep it up.

Cheers,

Doru

On Wed, Apr 22, 2015 at 8:58 AM, Yuriy Tymchuk <[hidden email]> wrote:

Hi everyone!

Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter.

I’m happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta-. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects.

Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didn’t forget some details about your code.

Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues

Have a nice week!
Uko

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

jfabry

Re: QualityAssistant v0.4

In reply to this post by Uko2

Hola,

It looks like a really cool tool! I just added it to my LRP development image and I plan on using it full time. I am always interested in writing cleaner code.

So expect comments from me :-) Actually I already have one:

For one class I got the critic ‘References an abstract class’ and 'Subclass responsibility not defined’. Excellent that you found it, but now I have to go through all the methods of the class to see where the first critic comes from, and through all methods of all leaf classes for the second one. :-( :-( :-( That’s a lot of work for me to rescue some information which apparently the tool already knows. Please add more information on where the issue is on these kinds of errors, so I can fix them more easily ...

Thanks and keep up the good work!

On Apr 22, 2015, at 03:58, Yuriy Tymchuk <[hidden email]> wrote:

Hi everyone!

Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter.

I’m happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta-. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects.

Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didn’t forget some details about your code.

Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues

Have a nice week!
Uko

<critics.jpg>
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

jfabry

Re: [Pharo-users] QualityAssistant v0.4

In reply to this post by Uko2

Some weird behavior in quality assistant. Have a look at this method:

duplicateVar: aVarName

self show: 'Var: ', aVarName, ' redefinition ignored'.

This raises the issue: ‘Use cascaded nextPutAll:’s instead of #, in nextPutAll:’ It also pops up the automatic rewrite icon, so I clicked on it to see how it would transform the code. Result:

duplicateVar: aVarName

self

show: 'Var: ' , aVarName;

show: ' redefinition ignored'

Needless to say, that’s not a behavior preserving transformation.

On Apr 22, 2015, at 03:58, Yuriy Tymchuk <[hidden email]> wrote:

Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev