April 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] HelpBrowser takes too much time to open
by Torsten Bergmann April 30, 2011

April 30, 2011

This is because the help book "Pharo" includes an API reference for the WHOLE system (starting from ProtoObject all subclasses down) and converts all class comments in the system into help text. Accessing sources is slow... Just run MessageTally spyOn: [SystemReference asHelpTopic] If nobody uses this full API reference then we can eliminate the class "PharoAPIHelp" and it should be much faster (from 3705 down to 1006 in my image). Other books like the ones on announcements and on regular expression also contain an API reference ... but only with classes for these packages. Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

[Pharo-project] [update 1.3] #13177
by Marcus Denker April 30, 2011

April 30, 2011

13177 ----- Issue 4127: little bit faster traitNames, allTraitsDo:, allClassesDo:, allClassesAndTraitsDo: Issue 4126: Speeding up HelpBrowser by 50% Issue 4115: Deprecate IdentityGlyphMap and HostFont Issue 4098: Fileout - choose another name cancel crashs -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Hudson - Pharo Clients build on 1.2, not 1.3
by Marcus Denker April 30, 2011

April 30, 2011

On Apr 30, 2011, at 4:21 AM, Yanni Chiu wrote: > Can the equivalent builds based on Pharo 1.3 be created? Yes, it's on the TODO list... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] [Pharo-users] [COTDC] 56 - HostFont
by Marcus Denker April 30, 2011

April 30, 2011

On Apr 28, 2011, at 6:23 PM, laurent laffont wrote: > Today: HostFont > Seems to be unused. I vote for removing. (together with IdentityGlyphMap) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

4 3

[Pharo-project] Hudson - Pharo Clients build on 1.2, not 1.3
by Yanni Chiu April 30, 2011

April 30, 2011

Can the equivalent builds based on Pharo 1.3 be created?

1 0

Re: [Pharo-project] UndefinedObject(Object)>>doesNotUnderstand: #findNextHandlerContextStarting
by Marcus Denker April 29, 2011

April 29, 2011

On Apr 29, 2011, at 8:18 PM, Mariano Martinez Peck wrote: > > > On Wed, Apr 27, 2011 at 8:31 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 24, 2011, at 5:12 PM, Mariano Martinez Peck wrote: > > > grrrr I don't know what is happening. I am building a PharoDev 1.3 and at the end, I do: Undeclared removeUnreferencedKeys > > but this throws an error that I attach. It is a big loop of such error. > > The progress bar is showing "Clean up in DebuggerMethodMap" > > > > So I added the DebuggerMethodMap intialize (reset the cache) to Smalltalk cleanUp. > > > Thanks Marcus. I don't see this commit. Did you commit it? or we lost it with the squeaksource down ? > This was part of the cleanUp improvements... some time ago. see DebuggerMethodMap>>#cleanUp Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Do you want the option to copy a stacktrace to clipboard?
by Mariano Martinez Peck April 29, 2011

April 29, 2011

Hi guys...with just 2 little methods, I am able to add a button to the debuger and a button to the context of the debugger, to copy the stakctrace to clipboard. Going to PharoDebug.log is anoying: 1) I never know where my image is, so I first need to do print Smalltlak imagePharo 2) then I need to go to such folder, and open the PharoDebug.log 3) most of the times, PharoDebug has appended a lot of other (un) issues so it is quite confusing to use such file for a bug report. Hence I need to: 4) remove PharoDebug.log and 5) Reproduce my problem again, so that to generate a new PharoDebug.log 6) finally search it again, open, and do the copy paste :) So....I think it should be muuuch easier from the debugger. So I added two possibilities 1) copy to clipboard from the "pre debugger windows" See attached screenshot. 2) copy to clipboard from the debugger context menu. See attached screenshot. So...do you like it? which one do you want of them ? both ? Cheers -- Mariano http://marianopeck.wordpress.com

4 6

Re: [Pharo-project] UndefinedObject(Object)>>doesNotUnderstand: #findNextHandlerContextStarting
by Marcus Denker April 29, 2011

April 29, 2011

On Apr 29, 2011, at 11:23 PM, Mariano Martinez Peck wrote: > > > > > So I added the DebuggerMethodMap intialize (reset the cache) to Smalltalk cleanUp. > > > > > > Thanks Marcus. I don't see this commit. Did you commit it? or we lost it with the squeaksource down ? > > > This was part of the cleanUp improvements... some time ago. > > see DebuggerMethodMap>>#cleanUp > > > ok...after looking for a while, it is never called when you do > Smalltalk cleanUp: true except: #() confirming: false. > > I think it is because such method does: > > "Find all classes implementing #cleanUp or cleanUp:" > classes := Smalltalk allClasses select: [:aClass| > (aClass class includesSelector: #cleanUp) > or: [aClass class includesSelector: #cleanUp:]]. > > it checks for both messages, #cleanUp: or #cleanUp > > But then, it does: > > "Run the cleanup code" > classes > do:[:aClass| aClass cleanUp: aggressive] > displayingProgress: [:aClass| 'Cleaning up in ', aClass name]. > > > In your case, DebuggerMethodMap only implements #cleanUp, hence it is never called. > But there is in Behavior: cleanUp: aggressive "Clean out any caches and other state that should be flushed when trying to get an image into a pristine state. The argument should be used to indicate how aggressive the cleanup should be. Some subclasses may act differently depending on its value - for example, ChangeSet will only delete all unused and reinitialize the current change set if we're asking it to be aggressive." ^self cleanUp So it calls cleanUp even when you do Smalltlak cleanUp: true. Now I wonder if we should remove the displayingProgress and do the call to #cleanUp (the non-agressive one) on image save.... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] UndefinedObject(Object)>>doesNotUnderstand: #findNextHandlerContextStarting
by Marcus Denker April 29, 2011

April 29, 2011

On Apr 24, 2011, at 5:12 PM, Mariano Martinez Peck wrote: > grrrr I don't know what is happening. I am building a PharoDev 1.3 and at the end, I do: Undeclared removeUnreferencedKeys > but this throws an error that I attach. It is a big loop of such error. > The progress bar is showing "Clean up in DebuggerMethodMap" > So I added the DebuggerMethodMap intialize (reset the cache) to Smalltalk cleanUp. But why is that called when calling "Undeclared removeUnreferencedKeys"? > > In addition Undeclared ->>>> a Dictionary(#NoSuchElementError->nil ) > I checked http://code.google.com/p/pharo/issues/detail?id=4043 but there is no such method. NoSuchElementError looks like an exception subclass to me. Is it references somewhere? > Now...if I execute Undeclared removeUnreferencedKeys again, it works. > > The bad news is that this prevents the PharoDev 1.3 to be build.... > > I have no clue of what can be happening, but the only way I found so far to reproduce it is to: > > Gofer new > squeaksource: 'PharoTaskForces'; > pacakge: 'ConfigurationOfPharo'; > load. > > And then: > > (ConfigurationOfPharo project version: '1.3-beta') load > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

4 3

[Pharo-project] Counting Messages as a Proxy for Average Execution Time in Pharo
by Alexandre Bergel April 29, 2011

April 29, 2011

Hi! There has been many discussion on profiling and execution. I believe the paper titled "Counting Messages as a Proxy for Average Execution Time in Pharo" draws some bases for a new generation of code profilers that are not tied to execution sampling. Advantages are numerous without not that many drawbacks. http://bergel.eu/download/papers/Berg11c-compteur.pdf I will put some effort on having "Compteur" in the main Pharo vm. This has to be carefully done and monitored to make sure there is no unwanted overhead. In the experience I have done, there is no overhead. I have started to get in touch with people close to the VM. I will keep you informed, especially when reviews and testing will be needed. One very cool think that everybody can benefit from, is to be able to write assertion in unit tests like: self assertIs: [ "expression1" ] fasterThan: [ "expression2" ] It compares the amount of messages sent by expression1 with the amount of messages sent by expression2, no matter how many messages are sent. Counting messages is, in the average, closely link to the average execution time. This cannot be done with [ ... ] timeToRun or MessageTally. I will keep you informed. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

7 31