- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Moose-dev] loading Glamour in Pharo 4

by Johan Fabry

OK thanks for taking care of this! > On Mar 27, 2015, at 14:48, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > The same problem appeared on jenkins now. To be fixed really soon. > > > Cheers, > Andrei > > On Fri, Mar 27, 2015 at 6:44 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > Running the update script in the latest image (40585) causes a DNU: Instances of UndefinedObject are not indexable. :-( > > I can only see the stack trace in the pre-debugger. Clicking in the pre-debugger or trying to close a window causes the DNU again. The problem seems to be in RubFindReplaceService>>textArea: > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

March 27, 2015

How to silently generate and remove code

by Johan Fabry

Hi all, for LRP I am auto generating classes and methods, and removing them when I no longer need them. This however produces a lot of entries in the change file that are not needed at all. So I am looking into generating and removing them silently, however with not much success. Can anybody help me out in how to do the following without having entries in the changes file? - add a class (The standard subclass:instanceVariableNames:classVariableNames:category: message does not seem to have a âsilentâ equivalent) - remove a class ( aClass removeFromSystem: false. still logs to changes, apparently) - compile a method (aClass compileSilently: methodstring classified: #generated. still logs to changes, apparently) - remove a method (removeSelector: does not seem to have a âsilentâ option) - add / remove class variables (again, no âsilentâ option) - run a RBCreateAccessorsForVariableRefactoring Thanks in advance! ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

March 27, 2015

Re: [Pharo-users] [ANN] Quality Assistant: live code critics feedback

by Tudor Girba

Great. There are some features we are thinking of for the Inspector that will likely fit your interest nicely. Let's look at them next week. Cheers, Doru On Fri, Mar 27, 2015 at 6:04 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Oh, I was checking in vanilla Pharo 4. > > GTCritics gave me some ideas about IU, during the weekend Iâll release > next minor version with critics objects, severity indicators and better > GTInspector support. > > > > We will criticize you! :) > Uko > > > > > On 27 Mar 2015, at 14:56, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Hi Uko, > > You found no mail, as there is no email about that. It's a recent addition. > > Search for the class GTCritics in Spotter and then dive in the class. > There should be a category Critics that lets's you see and search through > all the critics of that class. > > > Cheers, > Andrei > > On Fri, Mar 27, 2015 at 2:53 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> >> On 27 Mar 2015, at 14:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Nice, Uko. >> >> >> Thank you. >> >> >> We should definitely see next Tuesday how this can complement the future >> GT efforts :) >> >> >> Yes, Iâm looking forward. >> >> >> In the meantime, you could look at the code critics support from Spotter. >> It was recently introduced by Stefan Reichhart, >> >> >> Can you give me more information, because searching mail/image and >> goggling didnât help :) >> >> Cheers, >> Uko >> >> >> Cheers, >> Doru >> >> >> >> >> On Fri, Mar 27, 2015 at 12:05 PM, Yuriy Tymchuk <yuriy.tymchuk(a)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. >>> >>> <Screen Shot 2015-03-27 at 11.38.21.png> >>> >>> Uko >>> >>> >>> On 27 Mar 2015, at 09:47, Damien Cassou <damien.cassou(a)gmail.com> wrote: >>> >>> Hi Yuriy, >>> >>> Yuriy Tymchuk <yuriy.tymchuk(a)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" >> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

March 27, 2015

Re: [Pharo-users] Pharo sprint on Friday, 3rd April

by Cyril Ferlicot

Pharo sprint are some event organize the Friday at INRIA Lille where people come and works on a theme. For exemple that can be a bug hunt: "Choose a bug from FogBugz and try to solve it". Everyone is on a big room and we can help each other. Some sprint are announce on the news on Pharo's website : http://pharo.org/news/ Like for this sprint : http://pharo.org/news/Pharo-Sprints ;) On 27 March 2015 at 17:05, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > Hi Jean-Christophe Bach ! > I am new to Pharo and would like to know more about Pharo Sprint. > It would be great if you could elucidate a bit. > Thanks and Regards > Jigyasa Grover > > > > -- > View this message in context: > http://forum.world.st/Pharo-sprint-on-Friday-3rd-April-tp4815604p4815605.ht… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Cheers Cyril Ferlicot

March 27, 2015

Re: [Pharo-users] Packaging for Mac OS

by Cyril Ferlicot

That works for me too On 27 March 2015 at 09:53, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> writes: > > >> https://ci.inria.fr/pharo/view/all/job/Launcher-Mac/ > > > Thank you Damien, > > Unfortunately the link displays "503 Service Temporarily Unavailable" > > But I will check later. > > works for me > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > > -- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Cheers Cyril Ferlicot

March 27, 2015

Re: [Pharo-users] [ANN] Quality Assistant: live code critics feedback

by Alexandre Bergel

This is really cool. You guys are changing the way we program. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 27, 2015, at 2:04 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Oh, I was checking in vanilla Pharo 4. > > GTCritics gave me some ideas about IU, during the weekend Iâll release next minor version with critics objects, severity indicators and better GTInspector support. > > <Screen Shot 2015-03-27 at 17.42.26.png> > > <Screen Shot 2015-03-27 at 17.50.29.png> > > We will criticize you! :) > Uko > > > >> On 27 Mar 2015, at 14:56, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: >> >> Hi Uko, >> >> You found no mail, as there is no email about that. It's a recent addition. >> >> Search for the class GTCritics in Spotter and then dive in the class. >> There should be a category Critics that lets's you see and search through all the critics of that class. >> >> >> Cheers, >> Andrei >> >> On Fri, Mar 27, 2015 at 2:53 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >>> On 27 Mar 2015, at 14:40, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>> >>> Nice, Uko. >> >> Thank you. >> >>> >>> We should definitely see next Tuesday how this can complement the future GT efforts :) >> >> Yes, Iâm looking forward. >> >>> >>> In the meantime, you could look at the code critics support from Spotter. It was recently introduced by Stefan Reichhart, >> >> Can you give me more information, because searching mail/image and goggling didnât help :) >> >> Cheers, >> Uko >> >>> >>> Cheers, >>> Doru >>> >>> >>> >>> >>> On Fri, Mar 27, 2015 at 12:05 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@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. >>> >>> <Screen Shot 2015-03-27 at 11.38.21.png> >>> >>> Uko >>> >>> >>>> On 27 Mar 2015, at 09:47, Damien Cassou <damien.cassou(a)gmail.com <mailto:damien.cassou@gmail.com>> wrote: >>>> >>>> Hi Yuriy, >>>> >>>> Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@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 <http://damiencassou.seasidehosting.st/> >>>> >>>> "Success is the ability to go from one failure to another without >>>> losing enthusiasm." --Winston Churchill >>>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> >>> "Every thing has its own flow" >> >> >

March 27, 2015

Re: [Pharo-users] [Moose-dev] loading Glamour in Pharo 4

by Andrei Chis

The same problem appeared on jenkins now. To be fixed really soon. Cheers, Andrei On Fri, Mar 27, 2015 at 6:44 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Running the update script in the latest image (40585) causes a DNU: > Instances of UndefinedObject are not indexable. :-( > > I can only see the stack trace in the pre-debugger. Clicking in the > pre-debugger or trying to close a window causes the DNU again. The problem > seems to be in RubFindReplaceService>>textArea: > > > On Mar 23, 2015, at 14:53, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > There are several tools in Pharo that depend on Glamour. > If you update glamour to the latest version you also need to update the > tools that depend on it. > > This script updated everything: > > { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. > { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. > { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. > } do: [ :spec | > Gofer new > smalltalkhubUser: spec second project: spec third; > package: spec first; > load ]. > ConfigurationOfGToolkitCore loadDevelopment. > > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

March 27, 2015

Re: [Pharo-users] [Moose-dev] loading Glamour in Pharo 4

by Johan Fabry

Running the update script in the latest image (40585) causes a DNU: Instances of UndefinedObject are not indexable. :-( I can only see the stack trace in the pre-debugger. Clicking in the pre-debugger or trying to close a window causes the DNU again. The problem seems to be in RubFindReplaceService>>textArea: > On Mar 23, 2015, at 14:53, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > There are several tools in Pharo that depend on Glamour. > If you update glamour to the latest version you also need to update the tools that depend on it. > > This script updated everything: > > { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. > { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. > { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. > } do: [ :spec | > Gofer new > smalltalkhubUser: spec second project: spec third; > package: spec first; > load ]. > ConfigurationOfGToolkitCore loadDevelopment. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

March 27, 2015

Re: [Pharo-users] [ANN] Quality Assistant: live code critics feedback

by Yuriy Tymchuk

Oh, I was checking in vanilla Pharo 4. GTCritics gave me some ideas about IU, during the weekend Iâll release next minor version with critics objects, severity indicators and better GTInspector support. We will criticize you! :) Uko > On 27 Mar 2015, at 14:56, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Hi Uko, > > You found no mail, as there is no email about that. It's a recent addition. > > Search for the class GTCritics in Spotter and then dive in the class. > There should be a category Critics that lets's you see and search through all the critics of that class. > > > Cheers, > Andrei > > On Fri, Mar 27, 2015 at 2:53 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > >> On 27 Mar 2015, at 14:40, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Nice, Uko. > > Thank you. > >> >> We should definitely see next Tuesday how this can complement the future GT efforts :) > > Yes, Iâm looking forward. > >> >> In the meantime, you could look at the code critics support from Spotter. It was recently introduced by Stefan Reichhart, > > Can you give me more information, because searching mail/image and goggling didnât help :) > > Cheers, > Uko > >> >> Cheers, >> Doru >> >> >> >> >> On Fri, Mar 27, 2015 at 12:05 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@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. >> >> <Screen Shot 2015-03-27 at 11.38.21.png> >> >> Uko >> >> >>> On 27 Mar 2015, at 09:47, Damien Cassou <damien.cassou(a)gmail.com <mailto:damien.cassou@gmail.com>> wrote: >>> >>> Hi Yuriy, >>> >>> Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@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 <http://damiencassou.seasidehosting.st/> >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." --Winston Churchill >>> >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" > >

March 27, 2015

Pharo sprint on Friday, 3rd April

by Jean-Christophe Bach

Hi Pharoers, This email as a reminder for the next Pharo sprint: it will be next Friday (3rd April) at Inria Lille. You can also join us on the IRC channel (#pharo on irc.freenode.net server). During the sprint, we will try to synchronize local and remote Pharo sprinters. JC

March 27, 2015