- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3981 in pharo: #<= on SourcedMethodReference is very slow

by pharo＠googlecode.com

Updates: Cc: johanbri...(a)me.com Benjamin...(a)gmail.com Comment #1 on issue 3981 by marianopeck: #<= on SourcedMethodReference is very slow http://code.google.com/p/pharo/issues/detail?id=3981 (No comment was entered for this change.)

April 10, 2011

Re: [Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

by pharo＠googlecode.com

Comment #4 on issue 3960 by marcus.d...(a)gmail.com: Catch all: Remove experimental + ancient backward compatibility code http://code.google.com/p/pharo/issues/detail?id=3960 remove #hInitScrollBarTEMPORARY in Scrollpane Attachments: Scrollpane.1.cs 669 bytes

April 10, 2011

[Pharo-project] Issue 3981 in pharo: #<= on SourcedMethodReference is very slow

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3981 by marcus.d...(a)gmail.com: #<= on SourcedMethodReference is very slow http://code.google.com/p/pharo/issues/detail?id=3981 ... as it accesses the sources. (it slows down rendering "senders of" a lot. And there I wonder why we sort them for time at all?)

April 10, 2011

Re: [Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3980 by guillerm...(a)gmail.com: TestResource fails to makeAvailable an never recovers http://code.google.com/p/pharo/issues/detail?id=3980 current should be assigned to nil, not to false. fix proposed in the inbox Name: SLICE-Issue-3980-TestResource-fails-to-makeAvailable-an-never-recovers-GuillermoPolito.1 Author: GuillermoPolito Time: 10 April 2011, 9:31:08 pm UUID: 8959ec71-7ade-47e0-bc26-d0d32d4075c7 Ancestors: Dependencies: SUnit-GuillermoPolito.40123 current initialized to nil in makeAvailable

April 10, 2011

Re: [Pharo-project] TestResource bug?

by Guillermo Polito

Yep, thanks for the response! Issue 3980 <http://code.google.com/p/pharo/issues/detail?id=3980>: TestResource fails to makeAvailable an never recovers On Sun, Apr 10, 2011 at 6:42 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 9, 2011, at 5:40 PM, Guillermo Polito wrote: > > Hi! I'm using pharo 1.2 and I've found a little problem in here > > TestResource>>makeAvailable > > > ... > > Is this a bug or i'm doing a mistake? Shouldn't *current := false be > changed *be changed by *current := nil. *??* > * > > > Yes, I think you are right... can you add a bugreport? > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

April 10, 2011

[Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

by pharo＠googlecode.com

Status: Accepted Owner: guillerm...(a)gmail.com New issue 3980 by guillerm...(a)gmail.com: TestResource fails to makeAvailable an never recovers http://code.google.com/p/pharo/issues/detail?id=3980 Using Pharo 1.2 TestResource>>makeAvailable "This method must be the _only_ way to set a notNil value for the unique instance (current). First, obtain a candidate instance and set current to a notNil placeholder (any notNil object not an instance of me would do; this version uses false). Next, check any subordinate resources needed by this resource. Lastly, setUp the candidate and put it in current if it is available, ensuring that it is torn down otherwise." | candidate | current := false. candidate := self new. .... And everywhere in the class, the check over the current var is done like current isNil ifTrue: .... So once that var is initialized, but the makeAvailable fails, it always fails...

April 10, 2011

[Pharo-project] A question about UIManager

by StÃ©phane Ducasse

Hi pharoers I was trying to change MenuMorph direct reference to use UIManager because I was thinking that a popup menu should not open alone but this is the responsibility of the UIManager and I was not happy. why because we have these UIManager default and I started to think about them (ok I'm dead nearly sleeping at 9 in the evening because I took too much sun and walk today). My gut feeling is that at least for UI code, any UI element could have an access to the current UIManager via an instance variable or a message. self uiManager. Now may be the UI World should point to the UIMAnager and each graphical element should access it like that. For non UI class then this is a different story. But I would like to get your point of view on that point. Tx stef

April 10, 2011

[Pharo-project] [BlogPost] Building the VM from scratch using Git and CMakeVMMaker

by Mariano Martinez Peck

Hi folks. This post took me a lot of time, so at least I will try to share it: http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… Hopefully it is useful for you. Any kind of feedback is more than welcome. Cheers -- Mariano http://marianopeck.wordpress.com

April 10, 2011

Re: [Pharo-project] Issue 3931 in pharo: Move all Exceptions-Kernel to Kernel-Exceptions

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3931 by marcus.d...(a)gmail.com: Move all Exceptions-Kernel to Kernel-Exceptions http://code.google.com/p/pharo/issues/detail?id=3931 cs attached Attachments: Exceptions.1.cs 1.8 KB

April 10, 2011

Re: [Pharo-project] TestResource bug?

by Marcus Denker

On Apr 9, 2011, at 5:40 PM, Guillermo Polito wrote: > Hi! I'm using pharo 1.2 and I've found a little problem in here > > TestResource>>makeAvailable > ... > Is this a bug or i'm doing a mistake? Shouldn't current := false be changed be changed by current := nil. ?? > Yes, I think you are right... can you add a bugreport? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 10, 2011