September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Peter UhnÃ¡k

This is happening since last week (or maybe even earlier), you can also keep telling the monkey to try again until it succeeds. On Wed, Sep 9, 2015 at 8:27 PM, stepharo <stepharo(a)free.fr> wrote: > Not much mark it as fix to include. > 4 > > Le 9/9/15 19:07, Alexandre Bergel a Ã©crit : > > Hi! > > Apparently the fix needs more work. But I am not sure how to proceed. The > monkey says: > > - a CIAndRule: Timeout (after 0:01:00:00) occured while loading "Help > topic for how to contribute to Pharo basecode" > > What can I do? > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker < > do-not-reply(a)pharo.fogbugz.com> wrote: > > [image: avatar] > *Ulysse The Galactic Monkey From Outer Space*edited *Case 16520*: Help > topic for how to contribute to Pharo basecode > <https://pharo.fogbugz.com/f/cases/16520>: > *Bug* in [image: Project:] CI and Bugtracker: 1. Pharo Image > Issue Validation Failed: > <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/val…> > https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/val… > Errors: 1 | > *Status* changed: > Resolved (Monkey is checking) [image: changed to] Work Needed > > [image: Priority] *Priority*: 5 â Fix If Time [image: Status] *Status*: > Work Needed [image: Assigned To] *Assigned to*: Alexandre Bergel [image: > Milestone] *Milestone*: Pharo5.0 > > Go to Case > <https://pharo.fogbugz.com/f/cases/16520> > Don't want FogBugz notifications anymore? Update your preferences. > <https://pharo.fogbugz.com/f/userPrefs> > > [image: FogBugz] > > > >

Sept. 9, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Marcus Denker

> On 09 Sep 2015, at 20:27, stepharo <stepharo(a)free.fr> wrote: > > Not much mark it as fix to include. The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests. Marcus

Sept. 9, 2015

Re: [Pharo-dev] [ANN] MessageFlowBrowser

by Torsten Bergmann

Sept. 9, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by stepharo

Not much mark it as fix to include. 4 Le 9/9/15 19:07, Alexandre Bergel a Ã©crit : > Hi! > > Apparently the fix needs more work. But I am not sure how to proceed. > The monkey says: > > * > > > a CIAndRule: Timeout (after 0:01:00:00) occured while > loading "Help topic for how to contribute to Pharo basecode" > > What can I do? > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker >> <do-not-reply(a)pharo.fogbugz.com >> <mailto:do-not-reply@pharo.fogbugz.com>> wrote: >> >> avatar >> *Ulysse The Galactic Monkey From Outer Space*edited*Case 16520*: Help >> topic for how to contribute to Pharo basecode >> <https://pharo.fogbugz.com/f/cases/16520>: >> *Bug*inProject: CI and Bugtracker: 1. Pharo Image >> >> Issue Validation >> Failed:https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/validationReport.html >> Errors: 1 | >> >> *Status*changed: >> Resolved (Monkey is checking)changed to Work Needed >> >> Priority *Priority*: 5 â Fix If Time Status *Status*: Work Needed >> Assigned To *Assigned to*: Alexandre Bergel Milestone *Milestone*: >> Pharo5.0 >> >> >> Go to Case >> <https://pharo.fogbugz.com/f/cases/16520> >> Don't want FogBugz notifications anymore?Update your preferences. >> <https://pharo.fogbugz.com/f/userPrefs> >> >> FogBugz >> >

Sept. 9, 2015

Re: [Pharo-dev] [ANN] MessageFlowBrowser

by Alexandre Bergel

Also, it would be great to have it accessible from the World/Tools menu. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Sep 9, 2015, at 9:07 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > A new tool to browse and dive deep into the flow of messages > using a tree representation (messages, senders, implementors, ...) > and further on. I know such a tool from Smalltalk/MT and it is really > helpful to trace a message flow without running in the debugger. > > See the attached screenshot, the best is to try it: > > In a latest Pharo 5.0 image (Pharo5.0 Latest update: #50314) > you can evaluate: > > Gofer new > url: 'http://smalltalkhub.com/mc/TorstenBergmann/MessageFlowBrowser/main'; > package: 'Tool-MessageFlowBrowser'; > load > > to load it. > > Then open whatever method in Nautilus and choose "Message Flow" from the context > menu. The nice thing is that you can dive into senders, implementors, messages sent > deeper and deeper (or up again) and you do not open more and more windows but stay > in a single window !!! > > Alternatively you can start the tool from the playground: > > MessageFlowBrowser openOn: #inspect "open the flow browser on a selector" > > MessageFlowBrowser openOn: (Compiler>>#evaluate) "open the flow browser on a method" > > MessageFlowBrowser openOn: Object "open the flow browser on a class" > > 1 messageFlow. "open the flow browser on the class of an instance" > > > If someone with GT knowledge and time could help to correct the syntax highlighting > in the code pane this would be super cool (see method MessageFlowBrowser #openOn:). > Also selection could be improved to show/highlight the messages sent directly > in the code. Unfortunately I'm not so familar with the current code editors - so > any help is appreciated. > > Repo is open for contribution. > > Thanks > T. > > <messageflow.png>

Sept. 9, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Alexandre Bergel

Hi! Apparently the fix needs more work. But I am not sure how to proceed. The monkey says: a CIAndRule: Timeout (after 0:01:00:00) occured while loading "Help topic for how to contribute to Pharo basecode" What can I do? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> wrote: > > > Ulysse The Galactic Monkey From Outer Spaceedited Case 16520: Help topic for how to contribute to Pharo basecode <https://pharo.fogbugz.com/f/cases/16520>: > > Bug in CI and Bugtracker: 1. Pharo Image > > Issue Validation Failed: https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/val… <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/val…> > Errors: 1 | > > Status changed: > Resolved (Monkey is checking) Work Needed > > Priority: 5 â Fix If Time Status: Work Needed > Assigned to: Alexandre Bergel Milestone: Pharo5.0 > > > Go to Case > > <https://pharo.fogbugz.com/f/cases/16520> > Don't want FogBugz notifications anymore? Update your preferences. <https://pharo.fogbugz.com/f/userPrefs>

Sept. 9, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] MessageFlowBrowser

by Alexandre Bergel

Hi Torsten, Can you make it available from the catalog browser ? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Sep 9, 2015, at 9:07 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > A new tool to browse and dive deep into the flow of messages > using a tree representation (messages, senders, implementors, ...) > and further on. I know such a tool from Smalltalk/MT and it is really > helpful to trace a message flow without running in the debugger. > > See the attached screenshot, the best is to try it: > > In a latest Pharo 5.0 image (Pharo5.0 Latest update: #50314) > you can evaluate: > > Gofer new > url: 'http://smalltalkhub.com/mc/TorstenBergmann/MessageFlowBrowser/main'; > package: 'Tool-MessageFlowBrowser'; > load > > to load it. > > Then open whatever method in Nautilus and choose "Message Flow" from the context > menu. The nice thing is that you can dive into senders, implementors, messages sent > deeper and deeper (or up again) and you do not open more and more windows but stay > in a single window !!! > > Alternatively you can start the tool from the playground: > > MessageFlowBrowser openOn: #inspect "open the flow browser on a selector" > > MessageFlowBrowser openOn: (Compiler>>#evaluate) "open the flow browser on a method" > > MessageFlowBrowser openOn: Object "open the flow browser on a class" > > 1 messageFlow. "open the flow browser on the class of an instance" > > > If someone with GT knowledge and time could help to correct the syntax highlighting > in the code pane this would be super cool (see method MessageFlowBrowser #openOn:). > Also selection could be improved to show/highlight the messages sent directly > in the code. Unfortunately I'm not so familar with the current code editors - so > any help is appreciated. > > Repo is open for contribution. > > Thanks > T. > > <messageflow.png>

Sept. 9, 2015

Re: [Pharo-dev] when:send:to: vs. subscribe:send:to:

by Esteban A. Maringolo

2015-09-09 6:21 GMT-03:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > Note that when:send:to: already existed in VW before announcements (it did > work with a symbol like when: #someAspectChanged send: #someAction to: > self, and this was tiggered thru dependents mechanism - self changed: > #someAspectChanged...). > > IMO, it is very expressive, whatever the underlying mechanism (dependents > or Announcement). > > +1 Dolphin Smalltalk also uses #when:send:to:, and also #when:sendTo: and #when:perform: Regards! Esteban A. Maringolo

Sept. 9, 2015

Re: [Pharo-dev] FTDataSource API

by Yuriy Tymchuk

Done https://pharo.fogbugz.com/f/cases/16537/FTDataSource-elementAt-should-not-b… > On 09 Sep 2015, at 17:48, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > mmmâ¦ thatâs an error :) > Iâm using (wrongly) #elementAt: to pick up drag&drop passengers in FTTableMorph>>#startDrag:, and that is a mistake (it should call some #passegerAt: method). > > can you fill a bug report, please? > > Esteban > > > >> On 09 Sep 2015, at 17:03, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Hi, >> >> Iâm a bit confused because FTDataSource has two methods #cellColumn:row: and #elementAt: with subclassResponsibility. I understand when FTSimpleDataSource implements #elementAt: and uses it in #cellColumn:row:. But as #cellColumn:row: is more general, why is there #elementAt: defined in FTDataSource? >> >> Uko > >

Sept. 9, 2015

Re: [Pharo-dev] AbstractNautilusUI class >> #on: versus onModel:

by Franck Warlouzet

It is not the only place where on: is used to set the model, I guess it is a common way to do this kind of things. Franck > From: btc(a)openinworld.com > Date: Wed, 9 Sep 2015 23:47:52 +0800 > To: pharo-dev(a)lists.pharo.org > Subject: [Pharo-dev] AbstractNautilusUI class >> #on: versus onModel: > > This is a small point, but maybe one tiny incremental improvement. > Just thought I'd get some feedback before opening a ticket. While > debug tracing through... > Smalltalk tools openClassBrowser > > in Nautilus>>open I see... > (self uiClass on: self) > > which calls PackageTreeNautilusUI class(AbstractNautilusUI class)>>on: > ^ self new model: aNautilus > > where PackageTreeNautilusUI(AbstractNautilusUI)>>model: > model := aNautilusModel. > ... > > and my passing thought was a nicer API would be > PackageTreeNautilusUI class(AbstractNautilusUI class)>>onModel: > > such that Nautilus>>open would be... > (self uiClass onModel: self) > > > Thoughts? > cheers -ben >

Sept. 9, 2015