- Pharo-dev - lists.pharo.org

[Pharo-project] fix GoferOperationTest failure
by Pavel Krivanek March 6, 2012

March 6, 2012

There is a new failure related to Camillo's changes to UIManagers. http://code.google.com/p/pharo/issues/detail?id=5439 I proposed a fix. Cheers, -- Pavel

1 0

[Pharo-project] in 14379...
by StÃ©phane Ducasse March 6, 2012

March 6, 2012

Hi guys when I try to load MCSqueaksourceRepository location: 'http://squeaksource.com/Games' user: '' password: '' load MorphicGames-md.1.mcz I get a DNU isPostMortem "return whether we're inspecting a frozen exception without a process attached" |selectedContext| selectedContext := self selectedContext. (interruptedProcess suspendedContext == selectedContext) ifTrue: [ ^ false ]. ^ (interruptedProcess suspendedContext findContextSuchThat: [:c | c sender == selectedContext]) isNil ^^^^^^ DNU findContextSuchThat: interruptedProcess suspendedContext is a MethodContext Now I do not understand since find findContextSuchThat: is defined in ContextPart the super class of MethodContext. Stef

3 3

Re: [Pharo-project] in 14379...
by Marcus Denker March 6, 2012

March 6, 2012

On Mar 6, 2012, at 12:08 PM, StÃ©phane Ducasse wrote: > Hi guys > > when I try to load > > MCSqueaksourceRepository > location: 'http://squeaksource.com/Games' > user: '' > password: '' > > load MorphicGames-md.1.mcz > > I get a DNU > > isPostMortem > "return whether we're inspecting a frozen exception without a process attached" > |selectedContext| > selectedContext := self selectedContext. > (interruptedProcess suspendedContext == selectedContext) > ifTrue: [ ^ false ]. > ^ (interruptedProcess suspendedContext findContextSuchThat: [:c | c sender == selectedContext]) isNil > > ^^^^^^ DNU findContextSuchThat: > > > interruptedProcess suspendedContext is a MethodContext > > Now I do not understand since find findContextSuchThat: is defined in ContextPart the super class of MethodContext. > This is related to the startup changes we integrated yesterday. (there is no change that has no side effect...) Marcus -- Marcus Denker -- http://marcusdenker.de

4 3

Re: [Pharo-project] The event handling mechanism implemented in Gaucho
by Fernando Olivero March 6, 2012

March 6, 2012

Here is the code, the categories which include the mentioned classes. I'm preparing a one-click image of Gaucho for the Mac, so you can play with it also. And as the official release of the tool also! On Tue, Mar 6, 2012 at 12:33 PM, fernando.olivero(a)usi.ch <fernando.olivero(a)usi.ch> wrote: > Hi, Stef and Esteban, i'm sending an overview of the event handling > mechanism of Gaucho. So we can discuss the additions of multitouch > events and the design as well. > > > Key classes: GUserInterface, GPeripheralDevice, GDisplay, GView and > the new event model. > > GUserInterface: Collaborates with a sensor, and double dispatches the > event to the proper peripheral device. > > GMouse,GKeyboard: a peripheral device that distinguishes the system > event, and sends the user interface Â specific reactions: such as > > #mouse: aGMouse entered: aGShape > #keystroke: aGKeystroke from: aGKeyboard > > No reification of the events, just message passing amongst the user > interface, the peripherals, the display, the views, and the shapes. > > EXAMPLE > -------------------------------------------------------- > EVENTS: from the user to the shape > -------------------------------------------------------- > 1)the user clicks on the mouse > 2) a system event is announced > 3) the user interface dispatches it to the attached mouse > 4) the mouse detects that its a click to a particular shape on a view > of the display and informs the user interface > 5) the user interface informs the display of the click > > ------------------------------------------------------------------------ > VIEW: shape reacting to events and redrawing > -------------------------------------------------------------------------- > 6) the display informs the active view > 7) the active view informs the shape > 8) the shape reacts to the click. > 9)the display asks the shape wether it should redraw, and informs the > damage recorder. Gaucho implements a visual garbage collector scheme, > so the code is not polluted with #changed ,similar to eliminating the > need to send #alloc and #dealloc on memory garbage collector. But this > is surely for another thread. >

2 1

[Pharo-project] looking for Morphic-Games package
by StÃ©phane Ducasse March 6, 2012

March 6, 2012

Hi guys I'm looking for the package containing tetris, free cell, â¦ does any of you know where it is? Stef

3 3

[Pharo-project] The event handling mechanism implemented in Gaucho
by Fernando Olivero March 6, 2012

March 6, 2012

Hi, Stef and Esteban, i'm sending an overview of the event handling mechanism of Gaucho. So we can discuss the additions of multitouch events and the design as well. Key classes: GUserInterface, GPeripheralDevice, GDisplay, GView and the new event model. GUserInterface: Collaborates with a sensor, and double dispatches the event to the proper peripheral device. GMouse,GKeyboard: a peripheral device that distinguishes the system event, and sends the user interface specific reactions: such as #mouse: aGMouse entered: aGShape #keystroke: aGKeystroke from: aGKeyboard No reification of the events, just message passing amongst the user interface, the peripherals, the display, the views, and the shapes. EXAMPLE -------------------------------------------------------- EVENTS: from the user to the shape -------------------------------------------------------- 1)the user clicks on the mouse 2) a system event is announced 3) the user interface dispatches it to the attached mouse 4) the mouse detects that its a click to a particular shape on a view of the display and informs the user interface 5) the user interface informs the display of the click ------------------------------------------------------------------------ VIEW: shape reacting to events and redrawing -------------------------------------------------------------------------- 6) the display informs the active view 7) the active view informs the shape 8) the shape reacts to the click. 9)the display asks the shape wether it should redraw, and informs the damage recorder. Gaucho implements a visual garbage collector scheme, so the code is not polluted with #changed ,similar to eliminating the need to send #alloc and #dealloc on memory garbage collector. But this is surely for another thread.

1 0

[Pharo-project] fixUnderscores is cool to have in the image ; ) but broken
by StÃ©phane Ducasse March 6, 2012

March 6, 2012

I'm fixing it. Stef

1 0

[Pharo-project] Fuel - class loading issue when superclass changed inst vars
by Martin Dias March 6, 2012

March 6, 2012

Hello, I'd like to discuss about a problem found when loading classes with Fuel (for people who don't know it: http://rmod.lille.inria.fr/web/pier/software/Fuel) Fuel can serialize a class either as a global or as a "regular" object. In the latter case, it saves the class with its compiled methods, including their bytecodes. (This was demonstrated in http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… ) Well, the issue I want to talk about happens when loading a class with a method that uses an inherited instance variable. In a short example: - define class A with instVars 'x' - define class B with a method that uses 'x'. - serialize B in a file - remove B from system - redefine A with instVars 'y x' - materialize B from the file -----> the bytecodes of B's method, that should refer to 'x', instead refer to 'y' (because inst vars are encoded in bytecodes just as indexes) Of course, there are variations of this problem: the variable was whether removed or renamed. Some solutions: 1) detect the change in a superclass and then: a) just raise an error b) compile based on attached source c) decompile parse tree from bytecodes, fix it, and generate the method. 2) serialize the parse tree *instead* of bytecodes, and always generate the method when materializing. I am thinking on the use case of package sharing, like Parcels. Note that since Fuel supports multiple strategies for serializing the same object, it is not necessary to choose just one option to fit in every use case. - I'm not sure, but I guess Parcels makes something like 1c). - The alternative 1a) doesn't require any compiler (in a bootstrap image is good) - I am tempted to explore 2), but not sure if that makes sense. I am curious about your opinions. Best regards, MartÃn

3 2

Re: [Pharo-project] Pharo Kernel break...
by Marcus Denker March 6, 2012

March 6, 2012

On Mar 6, 2012, at 11:08 AM, Pavel Krivanek wrote: > I created a fix > > http://code.google.com/p/pharo/issues/detail?id=5438 > Thanks! I will have a look this evening. -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.4] #14379
by Marcus Denker March 6, 2012

March 6, 2012

14379 ----- Issue 5321: DataStreamTest creates files that are not deleted http://code.google.com/p/pharo/issues/detail?id=5321 Issue 5285: HostWindowTests>>testOne (workaround) http://code.google.com/p/pharo/issues/detail?id=5285 Issue 5153: warningAllowed does not work with undefined selectors http://code.google.com/p/pharo/issues/detail?id=5153 -- Marcus Denker -- http://marcusdenker.de

1 0