January 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

by Mariano Martinez Peck

On Wed, Jan 18, 2012 at 8:30 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks. > Mariano I remember that with marcus we got the same impression: that the > copyFrom: trick to avoid > a full scan was the cause of the trouble. > But I remember that you said that you had still a problem. > I notice that the compact/rehash of CompiledMethod is involved to reproduce this problem, but also I notice that the problem happens with the old version of #compact/#rehash > > > Here's the fix: > > > > I reverted MethodDictionary>>#compact to its previous version: > > > > compact > > "Make sure that I have the highest possible load factor (at least > 50%)." > > > > self become: self compactWithoutBecome > > > > > > The non-working version was: > > > > compact > > "Make sure that I have the highest possible load factor (between > 37.5% and 75%)." > > > > | newInstance | > > newInstance := self compactWithoutBecome. > > newInstance capacity = self capacity > > ifTrue: [ self copyFrom: newInstance ] > > ifFalse: [ self becomeForward: newInstance ] > > > > After reverting, #cleanUpForRelease worked without problem. > > > > > > > -- Mariano http://marianopeck.wordpress.com

Jan. 18, 2012

Re: [Pharo-project] New IDE alternative (was Misc. newbie questions)

by Denis Kudriashov

2012/1/18 laurent laffont <laurent.laffont(a)gmail.com> > Ah yes another thing which wouuld be nice to have something with one can >> understand without studying it for years and repeated tries. A simple >> way of building somewhat resembling GUI applications in Pharo/Squeak. Ah >> yes flame me that I do appreciate the fantastic Morph world. It's so >> fantastic that just the developers can build a somewhat "usable" >> interface with it. Tell me about the "great" applicatons using Morph >> (anything besides yet another Browser please) >> > > > I has two financial domain applications based on Presenty which works with Morphic backend. I think morphic is the best UI. It is only UI framework which reflect smalltalk live object enviroment. Any primitive UI part is live object which you can touch (debug, inspect,...) But Morphic has many problems in design and implementation part which I sure will be fixed in future.

Jan. 18, 2012

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

by Mariano Martinez Peck

On Wed, Jan 18, 2012 at 8:29 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > Rats, that's not the fix. > > Even though #cleanUpForRelease ran to completion, running the code: > > > Smalltalk > allClassesAndTraitsDo: [ :class | > [ :each | > each > removeEmptyCategories; > sortCategories ] > value: class organization; > value: class class > organization ]. > > still gives a ByteSymbol DNU for #run:with:in: > > I give up for now. > > > hahhah thanks Yanni. You see? it is really difficult to reproduce and understand :( thanks for your effort... -- Mariano http://marianopeck.wordpress.com

Jan. 18, 2012

Re: [Pharo-project] Saga of trying to integrate IDE with OpenGL continuesRe: [squeak-dev] Re:NativeBoost and NBOpenGL on Mac?

by Lawson English

Doh, I never even tried to run it on Pharo. :-( The croquet opengl package won't load or is it something specific to my stuff? L. On 1/17/12 11:26 PM, Friedrich Dominicus wrote: > Lawson English<lenglish5(a)cox.net> writes: > >> The latest video in the saga: http://www.youtube.com/watch?v=TsJmBwi9lDY >> >> BTW, the video I mentioned a day or so ago now has 90 views, in only 3 >> days. > Just so much I'd tried to get this all running under Pharo. I guess > 32-bit Pharo on 64-bit Debian is not a good base for running OpenGL > stuff ;-( > >

Jan. 18, 2012

[Pharo-project] Question about #becomeForward

by Sven Van Caekenberghe

Hi, I want to create an array that references itself in its second element like this | array | array := #(1 nil). array at: 2 put: array. array I thought that the following would work | array elements | array := Array new. elements := Array with: 1 with: array. array becomeForward: elements. array And it does in a workspace, but not in my code where it looks like this parseArray | array elementsArray | array := Array new. self storeReference: array. elementsArray := self parseArrayInternal. elementsArray size > 0 ifTrue: [ array becomeForward: elementsArray ]. ^ array The #become[Forward] is necessary because the array size is not known up front and one of its elements might refer to itself, possibly deeper down. So I guess I am doing something wrong, the question is what ? Or is there another way to achieve the same effect ? Thx, Sven

Jan. 18, 2012

Re: [Pharo-project] New IDE alternative (was Misc. newbie questions)

by laurent laffont

> > Ah yes another thing which wouuld be nice to have something with one can > understand without studying it for years and repeated tries. A simple > way of building somewhat resembling GUI applications in Pharo/Squeak. Ah > yes flame me that I do appreciate the fantastic Morph world. It's so > fantastic that just the developers can build a somewhat "usable" > interface with it. Tell me about the "great" applicatons using Morph > (anything besides yet another Browser please) > DrGeo: http://www.drgeo.eu/ Laurent > > > > And yes, I am just as opinionated about my perceptions of the > > deficiencies of Python, Clojure, Ruby, Eclipse, Netbeans, ... > > Or my frustrations when using them. > > I just don't go into those communities expecting them to shape their > > favorite tool to my vision. I rather try to use their tools and > > attempt to learn their values and ways, assuming they have reason and > > purpose for their language and tools. > Well at least you get an Editor with Eclipse and Netbeans. But yeah we > don't need not stinking Editor. > > The biggest problem is people visiting a community and believing they > > have the right to speak into that community. If you want that right, > > spend some time here. Develop community relations. Then in time you > > earn that right to be heard. > He has all the right to write what he wants. You have to cope with that, > you can agree or disagree. That's up to you but you are not the ape at > the door to prohibit his entry. > > > > I have limited rights to be heard here because I have been a part of > > the Squeak/Pharo community for a long time. I have less rights than > > others because I haven't contributed anything of consequence. Others > > who have been here far less time but have contributed a lot more, have > > greater rights. > This is poor attitude. Just imagine Denis Ritchie would come here, with > no experience of Smalltalk at all. Wouldn't he have the right to state > his opinion? > > Regards > Friedrich > > > -- > Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim > Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus > >

Jan. 18, 2012

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

by StÃ©phane Ducasse

Thanks. Mariano I remember that with marcus we got the same impression: that the copyFrom: trick to avoid a full scan was the cause of the trouble. But I remember that you said that you had still a problem. > Here's the fix: > > I reverted MethodDictionary>>#compact to its previous version: > > compact > "Make sure that I have the highest possible load factor (at least 50%)." > > self become: self compactWithoutBecome > > > The non-working version was: > > compact > "Make sure that I have the highest possible load factor (between 37.5% and 75%)." > > | newInstance | > newInstance := self compactWithoutBecome. > newInstance capacity = self capacity > ifTrue: [ self copyFrom: newInstance ] > ifFalse: [ self becomeForward: newInstance ] > > After reverting, #cleanUpForRelease worked without problem. > >

Jan. 18, 2012

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

by Yanni Chiu

Rats, that's not the fix. Even though #cleanUpForRelease ran to completion, running the code: Smalltalk allClassesAndTraitsDo: [ :class | [ :each | each removeEmptyCategories; sortCategories ] value: class organization; value: class class organization ]. still gives a ByteSymbol DNU for #run:with:in: I give up for now.

Jan. 18, 2012

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

by Yanni Chiu

Here's the fix: I reverted MethodDictionary>>#compact to its previous version: compact "Make sure that I have the highest possible load factor (at least 50%)." self become: self compactWithoutBecome The non-working version was: compact "Make sure that I have the highest possible load factor (between 37.5% and 75%)." | newInstance | newInstance := self compactWithoutBecome. newInstance capacity = self capacity ifTrue: [ self copyFrom: newInstance ] ifFalse: [ self becomeForward: newInstance ] After reverting, #cleanUpForRelease worked without problem.

Jan. 18, 2012

[Pharo-project] A BlockEventHandler is xxxxxxxxx.

by StÃ©phane Ducasse

Looks to me like HashTableSubclass is crying to get born and usedâ¦ Stef A BlockEventHandler is xxxxxxxxx. Instance Variables allRecipientsBlocOrSelector: <Object> clickBlocOrSelector: <Object> doubleClickBlocOrSelector: <Object> doubleClickTimeoutBlocOrSelector: <Object> firstMouseSelectorBlocOrSelector: <Object> fixReversedValueMessagesBlocOrSelector: <Object> handlesClickOrDragBlocOrSelector: <Object> handlesGestureStartBlocOrSelector: <Object> handlesKeyboardBlocOrSelector: <Object> handlesMouseDownBlocOrSelector: <Object> handlesMouseMoveBlocOrSelector: <Object> handlesMouseOverBlocOrSelector: <Object> handlesMouseOverDraggingBlocOrSelector: <Object> handlesMouseStillDownBlocOrSelector: <Object> keyStrokeBlocOrSelector: <Object> messageListBlocOrSelector: <Object> methodRefListBlocOrSelector: <Object> mouseDownBlocOrSelector: <Object> mouseDownSelectorBlocOrSelector: <Object> mouseEnterBlocOrSelector: <Object> mouseEnterDraggingBlocOrSelector: <Object> mouseLeaveBlocOrSelector: <Object> mouseLeaveDraggingBlocOrSelector: <Object> mouseMoveBlocOrSelector: <Object> mouseStillDownBlocOrSelector: <Object> mouseStillDownRecipientBlocOrSelector: <Object> mouseStillDownSelectorBlocOrSelector: <Object> mouseUpBlocOrSelector: <Object> mouseUpSelectorBlocOrSelector: <Object> onBlocOrSelector: <Object> onGestureSendBlocOrSelector: <Object> printOnBlocOrSelector: <Object> replaceSendsInBlocOrSelector: <Object> sendBlocOrSelector: <Object> startDragBlocOrSelector: <Object> veryDeepFixupWithBlocOrSelector: <Object>

Jan. 18, 2012