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

Magritte-XMLBinding causes DNU when using Seaside editor example

by Skip

Hello, Magritte-XMLBinding (loaded by MagritteAddons) appears to go bad when you use descriptions of descriptions. Try to add a description using the MADescriptionEditor example in Seaside. I get the following: âMessageNotUnderstoord: MXXmlNamedElementTarget>>attributeNameâ. Is it just me?

Sept. 9, 2015

Re: [Pharo-dev] FTDataSource API

by Esteban Lorenzano

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

AbstractNautilusUI class >> #on: versus onModel:

by Ben Coman

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

Re: [Pharo-dev] merging in a filetree repository

by Damien Cassou

Esteban Lorenzano <estebanlm(a)gmail.com> writes: > Most of our problems here is because we insist on being interchangeable between git and mcz. > While treating git as âjust another repositoryâ can feel appealable in certain cases (for example, in the super-uncommon way of handle vm building we have, when we use git and Eliot uses squeak source, then we are kind of a mirror), this is not the most common usage: if you start a project on git, you are expected other contributors use git tooâ¦ same as in any other SVC tool (there is not compatibility between SVN, HG, GIT, etc.) > > Of course, it looked like a good idea at the beginning, but now I think is counterproductive (is the kind of ideas that are great at the beginning because it provides security/confortability to users, but with time demonstrate obsolete). > > What we actually need is tools that can load configurations from different sources (for example, I have a project in git who uses seaside and I want a configuration who loads bothâ¦). > Butâ¦ guess what? WE ALREADY HAVE IT!!!! Metacello is perfectly capable of doing that. Gofer is capable of doing that. Heck, even monticello is capable of doing that as long as we do not pretend their are interchangeable! > > So, againâ¦ what we actually need is to accept reality: we do not need all that metadata in 99% of cases! do you propose to stop using Monticello completely? Just have a snippet to load code from a directory and store packages to a directory? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 9, 2015

Re: [Pharo-dev] merging in a filetree repository

by Damien Cassou

Alexandre Bergel <alexandre.bergel(a)me.com> writes: > Also, if I understand correctly, at each new repository I need to create a file .gitattributes : > > *.package/monticello.meta/version merge=mcVersion > *.package/*.class/methodProperties.json merge=mcMethodProperties > *.package/*.class/properties.json merge=mcProperties > *.package/*.extension/methodProperties.json merge=mcMethodProperties > *.package/*.extension/properties.json merge=mcProperties there are many potential places for these attributes: - the git project level (you can even commit it so all contributors benefit from it) - a top-level directory where git projects are cloned - ~/.config/git/attributes if you want it for all your git projects (that's what I'm trying) - /etc/gitattributes if you want it for all users of your environment - anywhere provided the place is referenced in your global git configuration Read http://git-scm.com/docs/gitattributes for more information -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 9, 2015

Re: [Pharo-dev] [ANN] MessageFlowBrowser

by Torsten Bergmann

Nicolai wrote: >You need to set the class this method belongs to: > >a smalltalkCode > smalltalkClass: [:each | each <class/behavior> ]; > display: [:each | each sourceCode ]]. Yes - I know that. At least from the code I found in the image. But how do I do that in the context of Glamour where the tree is transmitted to the code pane... See #openOn: in MessageFlowBrowser. Thanks T.

Sept. 9, 2015

FTDataSource API

by Yuriy Tymchuk

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] ANSICompatibility package

by Ben Coman

On Wed, Sep 9, 2015 at 4:31 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Whoever created http://smalltalkhub.com/#!/~PharoExtras/Compatibility/ > > I would rename it to SmalltalkCompatibility to ANSICompatibility because > "Compatibility" is a too general term and could mean backward compatibility > of Pharo versions or compatibility to other languages as well. That was me :) I was thinking more broadly that over time the "repository" might hold different packages Compatibility-ANSI, Compatibility-VW, Compatibility-Dolphin. But maybe that is overreaching and its better to be more focussed. Let me know what you think on this and restate what you think the repository name should be. > Also see http://wiki.squeak.org/squeak/2384 and http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec > which could be a start. I saw those, but they interact with existing classes, so I thought it easier to kickstart by loading in the tests first, which are all new classes. I only created the repository since the tests were *hard* to find eventually at http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compatibility/ So I thought it would be good make them more accessible as a Monticello Package. cheers -ben P.S. I don't quite follow "to SmalltalkCompatibility to ANSICompatibility" do you mean "to SmalltalkCompatibility or ANSICompatibility" ? > >> Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr >> Von: stepharo <stepharo(a)free.fr> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] ANSICompatibility package >> >> We should have a SmalltalkCompatibility (not Ansi per se) package >> were we can add some methods to help migration. >> >> Stef >> >> >> Le 8/9/15 06:04, Ben Coman a Ã©crit : >> > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: >> >> Hi, >> >> >> >> is there actually such a thing like ANSICompatibility package? >> >> (it has been mentioned here lately, but I cannot find it) >> >> >> >> Thanks, Jan >> >> >> > I made it up for the purpose of discussion to see what interest it generated. >> > Should we start one ? >> > cheers -ben >> > >> > >> >> >> >

Sept. 9, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Ben Coman

The interactive graph is cool. Some suggestions: * Mark nodes of dependencies you want to prune in red. * Allow nodes to be pinned * http://bl.ocks.org/GerHobbelt/3637711 * http://stackoverflow.com/questions/11584757/interactively-fixing-a-node-in-… * http://stackoverflow.com/questions/12496851/d3-force-graph-sticky-nodes * http://bl.ocks.org/mbostock/3750558 * Node size to reflect size of package. A small number of dependencies to a fat node might be best to tackle first. * Highlighting & Fisheye * http://www.coppelia.io/2014/07/an-a-to-z-of-extra-features-for-the-d3-force… * Mark in bootstrap-dependency-report-graph-data.csv <https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/ws/bootstrap-dep…> which dependencies you want to eliminate, so that others might have a play with visualisation. More exotic... * Serve the bootstrap-dependency-report-graph.html <https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/ws/bootstrap-dep…> and bootstrap-dependency-report-graph-data.csv <https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/ws/bootstrap-dep…> out from Zinc, so I can point my browser at my local Pharo Image, and when a dependency is deleted, the graph updates automagically * When I double-click a node in the graph, it selects that item in the dependency analyzer in Image. * I guess the same might be done with two local Images - Moose as the observer and Pharo as the subject. cheers -ben On Wed, Sep 9, 2015 at 5:33 PM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > Hi, > > We now have a best overview of bootstrap dependencies. > You can check the latest report at > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > . > With Max, we reused Dijkstra algo in Moose to help finding dependencies > leading to Morphic and co. > It is now possible to have a visualization that is usable (there is also a > button to open it in the report): > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > > Next steps are to cut dependencies in red in the report table. > > Christophe. > > ps: by the way the dependency analyzer (with fixes asked) will be > introduced soon in the image. > > > Le 4 sept. 2015 Ã 15:13, Christophe Demarey a Ã©crit : > > Hi, > > I created a job to automatically generate a report of the Pharo image > dependencies as well as current bootstrap dependencies. > You can find them here: > > - > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > - > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > > > There are a lot (too many) dependencies but you can focus on some of them > with the search field. > Dependencies inside orange boxes are dependencies that are there but that > we ignore (for example, an example method adds an extra-dependency). It > should be fixed later but is not a problem for now. Ignored dependencies > are declared in the package manifest in #ignoredDependencies. > Dependencies inside red boxes are dependencies we want to remove for the > bootstrap. For now, they are listed in the bootstrap dependency report. > > People that are willing to help to have a more modular Pharo could first > take a look at the bootstrap dependency report and check dependencies that > we should cut. > Once we know, we can open issues on fogbugz in the 'bootstrap category' > and update manifests accordingly. > To investigate more deeply dependencies, you can use the > DependencyAnalyzer (in the Pharo Catalog) to actually check dependencies > (inheritance, reference, extension, traits, message send). > > Regards, > Christophe. > > >

Sept. 9, 2015

Strategies with Nautilus announcements

by Yuriy Tymchuk

Hi, as NautilusMethodSelected contains also an information about protocol, class, package; NautilusProtocolSelected contains an information about class and package; . . . Iâve inherited NautilusClassSelected from NautilusPackageSelected and NautilusProtocolSelected from NautilusClassSelectedâ¦ to remove duplication. But as announcement subscription also includes itâs subclasses, if you subscribe to NautilusPackageSelected, you end up receiving also NautilusClassSelected, NautilusProtocolSelected and NautilusMethodSelected. What is a good way to resolve this (I can simply separate all the classes, but maybe there is something important from conceptual point of view)? Uko

Sept. 9, 2015

[ANN] MessageFlowBrowser

by Torsten Bergmann

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.

Sept. 9, 2015

Ctrl-Click on selectors doesn't jump on the method (Linux)

by phil＠highoctane.be

Under Linux, I can't Ctrl-click on these things and wondered where I'd have to look as under OSX things do work. Clues? Phi

Sept. 9, 2015

Re: [Pharo-dev] ANSICompatibility package

by Jan Vrany

On Wed, 2015-09-09 at 10:31 +0200, Torsten Bergmann wrote: > Whoever created > http://smalltalkhub.com/#!/~PharoExtras/Compatibility/ > > I would rename it to SmalltalkCompatibility to ANSICompatibility > because > "Compatibility" is a too general term and could mean backward > compatibility > of Pharo versions or compatibility to other languages as well. +1 to ANSICompatibility > > Also see http://wiki.squeak.org/squeak/2384 and > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec > which could be a start. > > > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr > > Von: stepharo <stepharo(a)free.fr> > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Betreff: Re: [Pharo-dev] ANSICompatibility package > > > > We should have a SmalltalkCompatibility (not Ansi per se) package > > were we can add some methods to help migration. > > > > Stef > > > > > > Le 8/9/15 06:04, Ben Coman a Ã©crit : > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> > > > wrote: > > > > Hi, > > > > > > > > is there actually such a thing like ANSICompatibility package? > > > > (it has been mentioned here lately, but I cannot find it) > > > > > > > > Thanks, Jan > > > > > > > I made it up for the purpose of discussion to see what interest > > > it generated. > > > Should we start one ? > > > cheers -ben > > > > > > > > > > > > > >

Sept. 9, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Craig Latta

Hoi Christophe-- > We now have a best overview of bootstrap dependencies. That's a pretty grim picture. :) Can you post a movie of you picking through that ball of connections? (E.g., with the search feature as you described, or any with any other UI affordance that you have with this system.) thanks! -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 9, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Christophe Demarey

Hi, We now have a best overview of bootstrap dependencies. You can check the latest report at https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM…. With Max, we reused Dijkstra algo in Moose to help finding dependencies leading to Morphic and co. It is now possible to have a visualization that is usable (there is also a button to open it in the report): https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… Next steps are to cut dependencies in red in the report table. Christophe. ps: by the way the dependency analyzer (with fixes asked) will be introduced soon in the image. Le 4 sept. 2015 Ã 15:13, Christophe Demarey a Ã©crit : > Hi, > > I created a job to automatically generate a report of the Pharo image dependencies as well as current bootstrap dependencies. > You can find them here: > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > > There are a lot (too many) dependencies but you can focus on some of them with the search field. > Dependencies inside orange boxes are dependencies that are there but that we ignore (for example, an example method adds an extra-dependency). It should be fixed later but is not a problem for now. Ignored dependencies are declared in the package manifest in #ignoredDependencies. > Dependencies inside red boxes are dependencies we want to remove for the bootstrap. For now, they are listed in the bootstrap dependency report. > > People that are willing to help to have a more modular Pharo could first take a look at the bootstrap dependency report and check dependencies that we should cut. > Once we know, we can open issues on fogbugz in the 'bootstrap category' and update manifests accordingly. > To investigate more deeply dependencies, you can use the DependencyAnalyzer (in the Pharo Catalog) to actually check dependencies (inheritance, reference, extension, traits, message send). > > Regards, > Christophe.

Sept. 9, 2015

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

by Nicolas Cellier

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). 2015-09-09 8:49 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > > > > > > Am 08.09.2015 um 22:49 schrieb stepharo <stepharo(a)free.fr>: > > > > Me too :) > > I do not care that they is a registration mechanism behind. > > > But you get a subscription back. Und the user should be aware of that > there is no magical unsubscribe mechanism. So this no reason for me but I > still like when:send:to: better although it feels a bit awkward. > > Norbert > > Stef > > > > Le 8/9/15 16:30, Ferlicot D. Cyril a Ã©crit : > >> Le 08/09/2015 10:13, Stephan Eggermont a Ã©crit : > >> > >>> When looking at the implementation, it looks as if we should > >>> replace all #when:send:to: by #subscribe:when:do:, not the other way > >>> around. > >>> > >>> Where is this all coming from? > >>> > >>> Stephan > >> I think that #when:send:to: is more explicit and more understandable, > >> but this is a personal opinion. > > > > > >

Sept. 9, 2015

Re: [Pharo-dev] ANSICompatibility package

by Torsten Bergmann

Whoever created http://smalltalkhub.com/#!/~PharoExtras/Compatibility/ I would rename it to SmalltalkCompatibility to ANSICompatibility because "Compatibility" is a too general term and could mean backward compatibility of Pharo versions or compatibility to other languages as well. Also see http://wiki.squeak.org/squeak/2384 and http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec which could be a start. > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr > Von: stepharo <stepharo(a)free.fr> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] ANSICompatibility package > > We should have a SmalltalkCompatibility (not Ansi per se) package > were we can add some methods to help migration. > > Stef > > > Le 8/9/15 06:04, Ben Coman a Ã©crit : > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > >> Hi, > >> > >> is there actually such a thing like ANSICompatibility package? > >> (it has been mentioned here lately, but I cannot find it) > >> > >> Thanks, Jan > >> > > I made it up for the purpose of discussion to see what interest it generated. > > Should we start one ? > > cheers -ben > > > > > > >

Sept. 9, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50314 Home: https://github.com/pharo-project/pharo-core

Sept. 9, 2015

[pharo-project/pharo-core] 8afa38: 50314

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 8afa388a82651c08ea4af40f346923593f6868ce https://github.com/pharo-project/pharo-core/commit/8afa388a82651c08ea4af40f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-09 (Wed, 09 Sep 2015) Changed paths: M BlueInk-Core.package/BIConfigurableFormatter.class/instance/private-formatting/formatBlock_.st M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F4%5F2_.st A ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/README.md A ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/as yet unclassified/bookName.st A ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/as yet unclassified/pages.st A ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/pages/AddingYourProject.st A ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/pages/introduction.st A ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/definition.st A QualityAssistant.package/QANautilusPlugin.class/instance/accessing/morph.st M QualityAssistant.package/QANautilusPlugin.class/instance/initialization/initialize.st M Refactoring-Critics.package/RBAssignmentInIfTrueRule.class/instance/accessing/rationale.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50313.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50314.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50313.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50314.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50314 16524 Assignment is misspelled in RBAssignmentInIfTrueRule>>#rationale https://pharo.fogbugz.com/f/cases/16524 16515 Adding an instance variable to Model broken by QualityAssistant https://pharo.fogbugz.com/f/cases/16515 16454 BlueInk block formatting https://pharo.fogbugz.com/f/cases/16454 16521 Help topic for contributing to the catalog https://pharo.fogbugz.com/f/cases/16521 http://files.pharo.org/image/50/50314.zip

Sept. 9, 2015

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

by Norbert Hartl

> Am 08.09.2015 um 22:49 schrieb stepharo <stepharo(a)free.fr>: > > Me too :) > I do not care that they is a registration mechanism behind. > But you get a subscription back. Und the user should be aware of that there is no magical unsubscribe mechanism. So this no reason for me but I still like when:send:to: better although it feels a bit awkward. Norbert > Stef > > Le 8/9/15 16:30, Ferlicot D. Cyril a Ã©crit : >> Le 08/09/2015 10:13, Stephan Eggermont a Ã©crit : >> >>> When looking at the implementation, it looks as if we should >>> replace all #when:send:to: by #subscribe:when:do:, not the other way >>> around. >>> >>> Where is this all coming from? >>> >>> Stephan >> I think that #when:send:to: is more explicit and more understandable, >> but this is a personal opinion. > >

Sept. 9, 2015

Re: [Pharo-dev] Nautilus strange pattern

by Ben Coman

On Wed, Sep 9, 2015 at 4:41 AM, stepharo <stepharo(a)free.fr> wrote: > just a question that came to my mind while reading your old mail. > > > ">>>" SystemAnnouncer uniqueInstance unsubscribe: mod. "<<<added" > > Are you sure that this is to this one that Nautilus is registered? I'm not sure if its the best approach, but apart from the steps to reproduce in previous link, you can do the following experiment. In a fresh image... "(1)" SystemAnnouncer uniqueInstance inspect. "and review subscriptions tab" "(2)" window := Smalltalk tools openClassBrowser ui window. SystemAnnouncer uniqueInstance inspect. "and review subscriptions tab" "(3)" window delete. Smalltalk garbageCollect. Smalltalk garbageCollect. Smalltalk garbageCollect. SystemAnnouncer uniqueInstance inspect. "and review subscriptions tab" You will find leftover "a PackageTreeNautilusUI" subscriptions. Now repeat starting again with a fresh image, and after evaluating the following... NautilusWindow compile: 'delete | mod | mod := self model. super delete. SystemAnnouncer uniqueInstance unsubscribe: mod. mod ifNotNil: [ mod announce: (WindowClosed new window: self) ] ' "a PackageTreeNautilusUI" is now correctly absent from the SystemAnnouncer subscriptions. A further experiment before and after ammending NautilusWindow>>delete is... 20 timesRepeat: [ window := Smalltalk tools openClassBrowser ui window. window delete. ]. SystemAnnouncer uniqueInstance inspect. I've now logged https://pharo.fogbugz.com/default.asp?16525 cheers -ben

Sept. 9, 2015

Re: [Pharo-dev] garbage on transcript

by stepharo

The idea was to reduce the amount of Parsers (and models of methods) in the systemâ¦ > > I understand that. But parsing for code generation is very different > from the quick and simple parsing for syntax highlighting that Shout > provides, and if one ends up complicating the former to make it > encompass the latter then maybe that's not such a good idea. I'd > rather have a number of smaller simpler parsers than one great big > complex difficult to understand and full of special cases parser > (think... Morphic). Just a thought. Elliot when I start to think about Morphic.... :) > > Marcus > > > _,,,^..^,,,_ > best, Eliot

Sept. 8, 2015

Re: [Pharo-dev] ANSICompatibility package

by stepharo

We should have a SmalltalkCompatibility (not Ansi per se) package were we can add some methods to help migration. Stef Le 8/9/15 06:04, Ben Coman a Ã©crit : > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: >> Hi, >> >> is there actually such a thing like ANSICompatibility package? >> (it has been mentioned here lately, but I cannot find it) >> >> Thanks, Jan >> > I made it up for the purpose of discussion to see what interest it generated. > Should we start one ? > cheers -ben > >

Sept. 8, 2015

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

by stepharo

Me too :) I do not care that they is a registration mechanism behind. Stef Le 8/9/15 16:30, Ferlicot D. Cyril a Ã©crit : > Le 08/09/2015 10:13, Stephan Eggermont a Ã©crit : > >> When looking at the implementation, it looks as if we should >> replace all #when:send:to: by #subscribe:when:do:, not the other way >> around. >> >> Where is this all coming from? >> >> Stephan >> >> >> > I think that #when:send:to: is more explicit and more understandable, > but this is a personal opinion. >

Sept. 8, 2015

Re: [Pharo-dev] Nautilus strange pattern

by stepharo

just a question that came to my mind while reading your old mail. ">>>" SystemAnnouncer uniqueInstance unsubscribe: mod. "<<<added" Are you sure that this is to this one that Nautilus is registered? Today I discussed with esteban and we agreed that the GroupAnnouncer should be just a class instance var of the Group class. No need to have a subclass of Announcer + a singletong when we can use an announcer. Stef

Sept. 8, 2015

Re: [Pharo-dev] Nautilus strange pattern

by stepharo

Le 8/9/15 01:50, Ben Coman a Ã©crit : > On Tue, Sep 8, 2015 at 5:32 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> We should make sure to unregister to all announcement when the window is >> closed. > +1. Nautilus seems to leak announcements. Sorry I forgot to log an > issue already for this... > https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg31953.html > > So should I log a new issue now, sure because we should go slowly with Nautilus. I would like to get the state machine that all the if are trying to rebuild in permanence. > or do you want to pick it up under > existing work? > > cheers -ben > >> (Or is there any reason or situation in which nautilus can properly work >> after the window is closed?) >> >> 2015-09-06 10:41 GMT+02:00 stepharo <stepharo(a)free.fr>: >>> Hi >>> >>> I'm trying to understand what there is a need for this window ifNil: [^ >>> self ] >>> And I wonder is this is not problem due to a global announcer that would >>> keep announcer even when the nautilus widget >>> has been deleted. >>> Any other suggestions? >>> >>> Stef >>> >>> classRemoved: anAnnouncement >>> | class oldPackage | >>> window ifNil: [ ^ self ]. >>> window isDisplayed >>> ifFalse: [ ^ self ]. >>> class := anAnnouncement classRemoved. >>> (self classWidget getClassesList includes: class) >>> ifTrue: >>> [ >>> >>> classRecategorized: anAnnouncement >>> >>> window ifNil: [ ^ self ]. >>> window isDisplayed ifFalse: [ ^ self ]. >>> self selectedPackage ifNotNil:[:selection | >>> ({ anAnnouncement oldCategory. anAnnouncement newCategory } >>> anySatisfy: [ :each | selection includesCategory: each ]) >>> ifTrue: [ self updatePackageGroupAndClassList ]] >>> >>> >>> classRemoved: anAnnouncement >>> | class oldPackage | >>> window ifNil: [ ^ self ]. >>> window isDisplayed >>> ifFalse: [ ^ self ]. >>> class := anAnnouncement classRemoved. >>> (self classWidget getClassesList includes: cla >>> >

Sept. 8, 2015

Re: [Pharo-dev] Nautilus strange pattern

by stepharo

Le 7/9/15 23:32, Nicolai Hess a Ã©crit : > We should make sure to unregister to all announcement when the window > is closed. > (Or is there any reason or situation in which nautilus can properly > work after the window is closed?) Yes I was thinking about this too. I took an image and removed all the window ifNil: [ ^ self ]. window isDisplayed ifFalse: [ ^ self ]. and tried all kind of combination I could imagine. It seemed to work but I should continue to experiment. Stef > > 2015-09-06 10:41 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Hi > > I'm trying to understand what there is a need for this window > ifNil: [^ self ] > And I wonder is this is not problem due to a global announcer > that would keep announcer even when the nautilus widget > has been deleted. > Any other suggestions? > > Stef > > classRemoved: anAnnouncement > | class oldPackage | > window ifNil: [ ^ self ]. > window isDisplayed > ifFalse: [ ^ self ]. > class := anAnnouncement classRemoved. > (self classWidget getClassesList includes: class) > ifTrue: > [ > > classRecategorized: anAnnouncement > > window ifNil: [ ^ self ]. > window isDisplayed ifFalse: [ ^ self ]. > self selectedPackage ifNotNil:[:selection | > ({ anAnnouncement oldCategory. anAnnouncement newCategory } > anySatisfy: [ :each | selection includesCategory: each ]) > ifTrue: [ self updatePackageGroupAndClassList ]] > > > classRemoved: anAnnouncement > | class oldPackage | > window ifNil: [ ^ self ]. > window isDisplayed > ifFalse: [ ^ self ]. > class := anAnnouncement classRemoved. > (self classWidget getClassesList includes: cla > >

Sept. 8, 2015

Re: [Pharo-dev] Two new help topics

by stepharo

Thanks alex. Le 8/9/15 20:11, Alexandre Bergel a Ã©crit : > Hi! > > I made two contribution in the Pharo inbox: > 16521 - Help topic for contributing to the catalog > 16520 - Help topic for how to contribute to Pharo basecode > > I think they are good candidates for an inclusion in the base image. > > Cheers, > Alexandre

Sept. 8, 2015

Re: [Pharo-dev] fly-by-helph on icons do not work anymore on the catalog

by stepharo

In fact I have the impression that they were broken before. Not even sure that they worked (many only when we added some of them). Stef Le 8/9/15 22:09, stepharo a Ã©crit : > Hi > > I have the impression that after > > 16496 Provide context menu icons in Catalog browser > https://pharo.fogbugz.com/f/cases/16496 > > the fly-by-help on the icons in the toolbard does not work anymore and > this is really a problem. > > Stef > > >

Sept. 8, 2015

confused about 16496 Provide context menu icons in Catalog browser

by stepharo

Hi torsten this is nice that you improve the catalog browser. 50312 16496 Provide context menu icons in Catalog browser https://pharo.fogbugz.com/f/cases/16496 Now I'm totally confused by the diff on githib. Many changes marked as additions were in fact my code and already there. So I add at lot of problems to understand what you did at the code level. Did you do something special so that all the old changes went marked as new changes? Tx Stef

Sept. 8, 2015

fly-by-helph on icons do not work anymore on the catalog

by stepharo

Hi I have the impression that after 16496 Provide context menu icons in Catalog browser https://pharo.fogbugz.com/f/cases/16496 the fly-by-help on the icons in the toolbard does not work anymore and this is really a problem. Stef

Sept. 8, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50313 Home: https://github.com/pharo-project/pharo-core

Sept. 8, 2015

[pharo-project/pharo-core] 13ac63: 50313

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 13ac639a4883cfa47974ac3f74d11dab8d52031f https://github.com/pharo-project/pharo-core/commit/13ac639a4883cfa47974ac3f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-08 (Tue, 08 Sep 2015) Changed paths: A Collections-Streams.package/ManifestCollectionsStreams.class/class/meta-data - dependency analyser/ignoredDependencies.st M Collections-Streams.package/ManifestCollectionsStreams.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M FileSystem-Core.package/FileReference.class/instance/utility/nextVersion.st M FontChooser.package/FontChooser.class/definition.st R FontChooser.package/FontChooser.class/instance/accessing/announcer.st M Kernel.package/ManifestKernel.class/class/meta-data - dependency analyser/ignoredDependencies.st M MonticelloGUI.package/MCTool.class/definition.st R MonticelloGUI.package/MCTool.class/instance/accessing/announcer.st A MonticelloGUI.package/MCTool.class/instance/utils/interactionModel.st M Morphic-Core.package/WorldState.class/class/world menu items/saveAs.st M Morphic-Widgets-Tree.package/MorphTreeModel.class/definition.st R Morphic-Widgets-Tree.package/MorphTreeModel.class/instance/accessing/announcer.st M PragmaCollector.package/PragmaCollector.class/definition.st R PragmaCollector.package/PragmaCollector.class/instance/accessing/announcer.st M PragmaCollector.package/PragmaCollector.class/instance/initialization/initialize.st A PragmaCollector.package/PragmaCollector.class/instance/initialization/reset.st R PragmaCollector.package/PragmaCollector.class/instance/initializing/reset.st M PragmaCollector.package/PragmaCollector.class/instance/subscription/announce_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50312.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50313.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50312.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50313.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Versionner-Core-DependenciesModel.package/MTProject.class/definition.st R Versionner-Core-DependenciesModel.package/MTProject.class/instance/accessing/announcer.st M Versionner-Core-Model.package/MBConfigurationRoot.class/definition.st R Versionner-Core-Model.package/MBConfigurationRoot.class/instance/accessing/announcer.st R Versionner-Core-Model.package/MBConfigurationRoot.class/instance/initialize-release/initialize.st Log Message: ----------- 50313 16512 "Save As" should increment a version number https://pharo.fogbugz.com/f/cases/16512 16517 Update manifest for the bootstrap https://pharo.fogbugz.com/f/cases/16517 16411 implementors of announcer not subclass of Model should be subclass of Model https://pharo.fogbugz.com/f/cases/16411 http://files.pharo.org/image/50/50313.zip

Sept. 8, 2015

Re: [Pharo-dev] Nautilus strange pattern

by Nicolai Hess

a new one. 2015-09-08 1:50 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > On Tue, Sep 8, 2015 at 5:32 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > We should make sure to unregister to all announcement when the window is > > closed. > > +1. Nautilus seems to leak announcements. Sorry I forgot to log an > issue already for this... > https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg31953.html > > So should I log a new issue now, or do you want to pick it up under > existing work? > > cheers -ben > > > (Or is there any reason or situation in which nautilus can properly work > > after the window is closed?) > > > > 2015-09-06 10:41 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> > >> Hi > >> > >> I'm trying to understand what there is a need for this window ifNil: [^ > >> self ] > >> And I wonder is this is not problem due to a global announcer that > would > >> keep announcer even when the nautilus widget > >> has been deleted. > >> Any other suggestions? > >> > >> Stef > >> > >> classRemoved: anAnnouncement > >> | class oldPackage | > >> window ifNil: [ ^ self ]. > >> window isDisplayed > >> ifFalse: [ ^ self ]. > >> class := anAnnouncement classRemoved. > >> (self classWidget getClassesList includes: class) > >> ifTrue: > >> [ > >> > >> classRecategorized: anAnnouncement > >> > >> window ifNil: [ ^ self ]. > >> window isDisplayed ifFalse: [ ^ self ]. > >> self selectedPackage ifNotNil:[:selection | > >> ({ anAnnouncement oldCategory. anAnnouncement newCategory } > >> anySatisfy: [ :each | selection includesCategory: each ]) > >> ifTrue: [ self updatePackageGroupAndClassList ]] > >> > >> > >> classRemoved: anAnnouncement > >> | class oldPackage | > >> window ifNil: [ ^ self ]. > >> window isDisplayed > >> ifFalse: [ ^ self ]. > >> class := anAnnouncement classRemoved. > >> (self classWidget getClassesList includes: cla > >> > > >

Sept. 8, 2015

Two new help topics

by Alexandre Bergel

Hi! I made two contribution in the Pharo inbox: 16521 - Help topic for contributing to the catalog 16520 - Help topic for how to contribute to Pharo basecode I think they are good candidates for an inclusion in the base image. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 8, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by Yuriy Tymchuk

Iâm happy to get feedback. Just wanted to know that I care about the issues :) > On 07 Sep 2015, at 22:07, stepharo <stepharo(a)free.fr> wrote: > > I'm not complaining. I know that there is a good chance that we break the system when improving it. > I have no problem with that and I prefer a living system with some bugs for a while than a dead system with no bug :) > I'm just trying to help handling this problem. > This is alpha with all the risks. > Stef > > Le 7/9/15 00:46, Yuriy Tymchuk a Ã©crit : >> I think that it is related to how I was working with Nautilus announcements. Now as announcements are changed, I can improve that. Just give me a bit of time :) >> >> Uko >> >>> On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr> wrote: >>> >>> I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method >>> but I failed. >>> I got again this bug. >>> What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. >>> But I cannot reproduce it. >>> >>> Stef >>> >> >> > >

Sept. 8, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-07 until: 2015-09-20

by phil＠highoctane.be

> > Le 7/9/15 07:00, seaside(a)rmod.lille.inria.fr a Ã©crit : > >> Hi! We're sending this automatic email twice a month, to give the >> community an opportunity to easily know what's happening and to coordinate >> efforts. Just answer informally, and feel free to spawn discussions >> thereafter! >> >> ### Here's what I've been up to since the last WhatsUp: >> > > Provided Cable-eXpertise success story. Continued development of the app, some more elements with DataTables using JQuery. Paid my consortium fee (about time...) > >> ### What's next, until 2015-09-20 (*): >> >> >> Looking for a new development opportunity. Getting into Pharo 4. > >> (*) we'll be expecting results by then ;) >> >> >> > >

Sept. 8, 2015

[ANN] The next Pharo Sprints at Lille

by Marcus Denker

Hello, We looked at the calendar and fixed the dates for all public sprints that we will do this year here locally. These are all Fridays: Sept 11 Oct 23 Nov 27 Dec 18 Here is the invitation for this Friday: âââââââââââââââââââââââ We will organize a Pharo sprint / Moose dojo Friday, 11th September, starting at 10:00am. (Local Time Lille). It will be at the Inria Lille, Building B, third floor (RMoD offices). Remotely, you can join us on the official IRC channel #pharo on irc.freenode.net server. During the sprint, we will try to synchronize local and remote Pharo sprinters. As the building is not open to the public, please contact us before if you plan to come.

Sept. 8, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-07 until: 2015-09-20

by Stephan Eggermont

On 07-09-15 07:00, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - a few bugfixes all over the place - a lot of bug entries - improvements to PetitDelphi > ### What's next, until 2015-09-20 (*): Looking at improved/other LayoutPolicies Stephan

Sept. 8, 2015

Re: [Pharo-dev] [Pharo-users] Modifying the AST of a method

by Marcus Denker

> On 08 Sep 2015, at 03:02, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > From GÃ¼nter Khyo: > > GÃ¼nter Khyo wrote >> Hello! >> >> I want to replace particular nodes of an AST (such as Assignments or Self >> sends) with my own nodes. >> Is there an easy (high-level) way to do this without being familiar with >> the entire compiler infrastructure? >> >> The problem I am having is that AST nodes maintain internal state such as >> parent links and, in the case of RBVariables, links to scopes and >> bindings. There might be many other dependencies I am missing and missing >> one of them can trigger exceptions with stack traces buried deep in the IR >> Code-Generator and visitor calls. >> >> For example, if I want to replace an assignment such as >> >> Morph>>position: aPoint >> >> "box := self fullBounds." >> >> with something like >> >> "self assignAndNotifiyDependents: self fullBounds to: 'box' " >> >> Btw: I know there is a rewrite tool, but I want to do it programmatically. Hello, With Pharo5 there are two mechanism that can help you. 1) MetaLinks (aka reflectivity). ======================= They allow you to reflectively define that a meta object to be called before/after or instead of an AST node. as you want to do something in addition here, you can add the notification as a #before link: link := MetaLink new metaObject: #object; selector: #assignAndNotifiyDependents:; arguments: #(newValue). this is a link that when installed on an AssignmentNode, will call #assignAndNotifiyDependents on the object with the new value (the to be assigned value) as the argument. To install this on all ivar assignments, do: MyClass assignmentNodes do: [ :each | each variable isInstance ifTrue: [each link: link ]]. to get rid of the link: link uninstall But MetaLinks are very hidden: you do not see them in your design. So they should be used with care. 2) First class Instance variable (aka Slots). ================================= In your example, what you really want is a âspecialâ kind of variable that always notifies depends. Wouldnât it be nice if you could define such a special kind of Variable and, in the class definition of you class, specify that the ivar âboxâ is that special kind? In Pharo5, you can do just that. 1) define your special variable. IndexedSlot subclass: #NotifyDependsSlot slots: { } classVariables: { } category: 'Demoâ change what it means to write these kind of variables by implementing: write: aValue to: anObject super write: aValue to: anObject. anObject assignAndNotifiyDependents: aValue. Now change the class definition of your class to make âboxâ into this special kind of variable: Object subclass: #MyClass slots: { #box => NotifyDependsSlot } classVariables: { } category: âDemo' DONE. Ah, but reflective slot write is slow, so if you use this a lot, add these two method: emitValue: methodBuilder methodBuilder pushInstVar: index. emitStore: methodBuilder | tempName | tempName := Object new. methodBuilder addTemp: tempName; storeTemp: tempName; pushReceiver; pushTemp: tempName; send: #assignAndNotifiyDependents:; popTop; storeInstVar: index. These generate byte code inline for the read and write instead of calling the #write:to: method. (I attach a fillout of MyClass that i used to test this)

Sept. 8, 2015