Nice, Uko. We should definitely see next Tuesday how this can complement the future GT efforts :)
In the meantime, you could look at the code critics support from Spotter. It was recently introduced by Stefan Reichhart, Cheers, Doru On Fri, Mar 27, 2015 at 12:05 PM, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote: > Oh, actually it turns out that I didn’t remove my old experiments with GT, > so you can see critics tab in inspector. Navigation in not useful yet > though. > > > Uko > > > On 27 Mar 2015, at 09:47, Damien Cassou <damien.cas...@gmail.com> wrote: > > Hi Yuriy, > > Yuriy Tymchuk <yuriy.tymc...@me.com> writes: > > As you already know I am working on providing better code quality support > in Pharo. You can use Code Critics in Pharo to detect bad practices and > potential bugs. But launching the Critics Browser and running it on your > code every now and then requires additional effort which demotivates many > people in doing it. > It runs SmallLint rules on the code that you save and provides you with a > critic feedback directly in the place where you code: the Nautilus Browser. > > > > that's great news and I'm looking forward to use it! Nevertheless, I > tend to code more and more in the debugger and in the inspector. Maybe > your tool could be shown in the bottom of the Pharo window instead? > > Best > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > > > -- www.tudorgirba.com "Every thing has its own flow"
