- Pharo-dev - lists.pharo.org

[Pharo-project] Looking for a package to do some statistics in Pharo
by StÃ©phane Ducasse March 5, 2012

March 5, 2012

Hi guys I would like to know if there is a package doing some statistics in Pharo. I should check the work of didier besset but I want to know if there is more. It would be good to have such kind of package. Stef

6 11

[Pharo-project] [OT] Pharo Conference - want to share a room?
by Francisco Garau March 4, 2012

March 4, 2012

Sorry for the off topic - this is about the coming Pharo Conference in 24/25th May. If anybody is interested in sharing a hotel room in Lille, please send me an email. Cheers, Francisco

1 0

[Pharo-project] problem: nautilus forked moose-algos
by Tudor Girba March 4, 2012

March 4, 2012

Hi, Nautilus includes NautilusCommon and this in turn includes NautilusCommon-Plugin-JannikAlgo which copies verbatim a part of the classes from the Moose-Algos-Graph package from http://www.squeaksource.com/MooseAlgos. These classes are used in a plugin. Because of this, we cannot use Nautilus in Moose. So, I would suggest one of these: - remove the plugin, at least from the default configuration - load Moose-Algos-Graph properly - fork with a different name Cheers, Doru -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

3 5

Re: [Pharo-project] pharo-seed and pharo
by Marcus Denker March 4, 2012

March 4, 2012

On Mar 2, 2012, at 2:38 PM, Tudor Girba wrote: > > That is even better. But, even without, I think that the current image > can be loaded quite fast if we work on it. > > So, how can I find/obtain a seed image? > https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%201.4/ reload worked last time in september, though... https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%20Reload/ ??? all a bit broken right now, because keeping shrink scripts current is nearly impossible. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

Re: [Pharo-project] Pharo Kernel break...
by Pavel Krivanek March 4, 2012

March 4, 2012

Hi, I shortly looked at it. To reproduce the key problem without need to start shrinking process we may use this expression. Behavior removeCategory: '*Deprecated14' It fails but for any other category with methods it passes without errors. So this class has simply some special organization structure that uncovered an unknown error. The failure of the Pharo Kernel shrinking is not result of content of this patches. I currently have no time to find out more. Cheers, -- Pavel Behavior removeCategory: '*Deprecated14' On Fri, Mar 2, 2012 at 11:44 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > thank you. I was on vacation this week. I will look at the the issues > at weekend. > > Cheers, > -- Pavel > > On Thu, Mar 1, 2012 at 8:54 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Build broken: >> #314 Â Â Feb 28, 2012 9:32:45 PM >> Build ok: >> #313 Â Â Feb 28, 2012 8:48:31 PM >> >> >> This means that I broke it with this update: >> >> >> 14366 >> ----- >> >> Issue 5418: Â Â compressedSourceCodeAt: is not used >> Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=5418 >> >> Issue 5414: Â Â class FormStub is unused and undocumented >> Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=5414 >> >> Issue 5417: Â Â FlatMessageListBrowser error on method removal >> Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=5417 >> >> Issue 5160: Â Â sourceCodeAt: vs. sourceMethodAt: >> Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=5160 >> >> >> strange.... >> >> -- >> Marcus Denker -- http://marcusdenker.de >>

1 0

[Pharo-project] [update 1.4] #14373
by Marcus Denker March 4, 2012

March 4, 2012

14373 ----- Issue 4902: deprecated: users should be rewritten into deprecated:on:in: http://code.google.com/p/pharo/issues/detail?id=4902 Issue 5429: clean: Monticello #updateInstVars http://code.google.com/p/pharo/issues/detail?id=5429 Issue 5430: Move some extension methods from Polymorph to morpic http://code.google.com/p/pharo/issues/detail?id=5430 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] ConfigurationOfRefactoringBrowser fails
by Benjamin March 3, 2012

March 3, 2012

In the method postLoadRBSpelling "We want to initialize and download the dictionary file so that tests can be run without internet." Smalltalk at: #RBInternalSpellChecker ifPresent: [:cl | cl new ]. the new invocation leads to Error: Improper store into indexable object. And due to that, Nautilus builds fail. I have to go to bed now, but if someone could have a look, I will appreciate :) Thanks in advance, Ben

3 5

[Pharo-project] loading nautilus
by Tudor Girba March 3, 2012

March 3, 2012

Hi, I am trying to load Nautilus in 1.4, but there seems to be a problem with the configuration. I run: Gofer it url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (Smalltalk at: #ConfigurationOfNautilus) loadRelease. But, the Growl dependency is incorrect: spec project: 'Growl' with:[ spec repository: 'http://www.squeaksource.com/Growl'; package: 'Growl' ]. We could create a ConfigurationOfGrowl, or just load the package directly: spec package: 'Growl' with: [spec repository: 'http://www.squeaksource.com/Growl' ]. Which one do you prefer? Btw, the Moose build is failing because of this :). Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 1

[Pharo-project] Just a thought... default inspector window title
by Ben Coman March 3, 2012

March 3, 2012

Just a random idea as I am inspecting variables from the debugger as I trace through the code execution. The default window title of the inspector is the class being inspected however I end up with several windows of the same class and it is hard to distinguish between them. It would be nice (in this particular circumstance of mine) if the inspector window title was the item being inspected rather than the class being inspected. For instance, if the debugger shows variables 'innerRectangle' & 'outerRectangle' each holding a Rectangle, the when I inspect each, each window title would be 'innerRectance' & 'outerRectangle' rather than currently each being 'Rectangle'. I actually have been setting these manually using the halos but wondered a change to the default behvaiour might be considered. Taking this further, if I inspect code 'innerRectangle offset' in the debugger, then the window title of the inspector would be 'innerRectangle offset' rather than currently being a third window titled 'Rectangle'. The lost 'class type' information from the inspector title bar might be reinstated as a hover over 'self'. This might also end up useful where classes override their default printOn: behaviour such that the class is not shown in the inspector. I've not given thought to any downsides of this - particularly with respect to difficulty to implement or expected conventions - but I thought the current behaviour might be something just taken for granted. cheers, -ben

1 0

[Pharo-project] [update 1.4] #14372
by Marcus Denker March 3, 2012

March 3, 2012

14372 ----- Issue 4145: PluggableButtonButtonMorph>>#target http://code.google.com/p/pharo/issues/detail?id=4145 Issue 3403: should remove addServices2:for:extraLines: http://code.google.com/p/pharo/issues/detail?id=3403 Issue 2520: sourceMatchesBytecodeAt http://code.google.com/p/pharo/issues/detail?id=2520 Issue 5206: better api for browser http://code.google.com/p/pharo/issues/detail?id=5206 -- Marcus Denker -- http://marcusdenker.de

1 0