- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3535 in pharo: I broke SpaceTally in Pharo 1.2

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3535 by marianopeck: I broke SpaceTally in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3535 Fix in Inbox: Name: SLICE-Issue-3535-SpaceTallyIsEmpty-MarianoMartinezPeck.1 Author: MarianoMartinezPeck Time: 12 January 2011, 5:02:29 pm UUID: 2a7e16b7-0962-4bd9-9e6b-f96222fbd4e4 Ancestors: Dependencies: System-Tools-MarianoMartinezPeck.40 Fix to issue 3535

Jan. 12, 2011

[Pharo-project] Issue 3535 in pharo: I broke SpaceTally in Pharo 1.2

by pharo＠googlecode.com

Status: Accepted Owner: marianopeck Labels: Milestone-1.2 New issue 3535 by marianopeck: I broke SpaceTally in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3535 Sorry, but as part of a refactor for 1.2 I screwup the SpaceTally. Pharo core version: 12294 Steps to reproduce: 1. SpaceTally new printSpaceAnalysis 2. Check the file STspace.text in the same directory of the image and you will see that the file is almost empty. Only the header is written. I will commit a fix to the inbox. At the same time, I will commit a little roundTo: for the instance space.

Jan. 12, 2011

[Pharo-project] Issue 3534 in pharo: LargePositiveInteger(Object)>>error

by pharo＠googlecode.com

Status: Accepted Owner: Torsten....(a)astares.de CC: eliot.miranda Labels: Milestone-1.2 New issue 3534 by Torsten....(a)astares.de: LargePositiveInteger(Object)>>error http://code.google.com/p/pharo/issues/detail?id=3534 It was already discussed here: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/039447.ht… but I havent found an issue yet. From time to time I now also get the following error when opening the world menu (the menu with the help icon is red crossed due to display error) I use the latest prebuilt Cog VM Here is the stack: VM: Win32 - IX86 - 5.1 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.45] Image: Pharo1.2beta [Latest update: #12297] LargePositiveInteger(Object)>>error: Receiver: 4278190081 Arguments and temporary variables: aString: 'MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:' Receiver's instance variables: 4278190081 [:err :rcvr | | errCtx errMorph | errCtx := thisContext. [errCtx := errCtx sender. [errCtx notNil and: [errCtx receiver isMorph not]] whileTrue: [errCtx := errCtx sender]. errCtx ifNil: [^ self handleFatalDrawingError: err]. errMorph := errCtx receiver. errMorph hasProperty: #errorOnDraw] whileTrue. errMorph setProperty: #errorOnDraw toValue: true. rcvr error: err] in WorldState>>displayWorldSafely: Receiver: a WorldState Arguments and temporary variables: err: 'MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:' rcvr: 4278190081 errCtx: ToggleMenuItemMorph>>drawIcon:on:in: errMorph: a ToggleMenuItemMorph(17825792)'Help' Receiver's instance variables: hands: an Array(a HandMorph(843055104)) viewBox: 0@0 corner: 1672@982 canvas: a FormCanvas on: DisplayScreen(1672x982x32) damageRecorder: a DamageRecorder stepList: a Heap(StepMessage(#stepAt: -> an OverflowRowMorph(157810688))(an Ove...etc... lastStepTime: 105085 lastStepMessage: nil lastCycleTime: 105055 alarms: a Heap() lastAlarmTime: 105085 menuBuilder: a PragmaMenuBuilder BlockClosure>>cull:cull: Receiver: [:err :rcvr | | errCtx errMorph | errCtx := thisContext. [errCtx := errCtx sender. [err...etc... Arguments and temporary variables: firstArg: 'MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:' secondArg: 4278190081 Receiver's instance variables: outerContext: WorldState>>displayWorldSafely: startpc: 73 numArgs: 2 [:ex | errorHandlerBlock cull: ex description cull: ex receiver] in BlockClosure>>ifError: Receiver: [aWorld displayWorld] Arguments and temporary variables: errorHandlerBlock: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDep...etc... ex: [:err :rcvr | | errCtx errMorph | errCtx := thisContext. [errCtx := errCt...etc... Receiver's instance variables: outerContext: WorldState>>displayWorldSafely: startpc: 66 numArgs: 0 BlockClosure>>cull: Receiver: [:ex | errorHandlerBlock cull: ex description cull: ex receiver] Arguments and temporary variables: anArg: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: Receiver's instance variables: outerContext: BlockClosure>>ifError: startpc: 40 numArgs: 1 [(self tempAt: 2) cull: exception] in MethodContext(ContextPart)>>handleSignal: Receiver: BlockClosure>>on:do: Arguments and temporary variables: exception: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: Receiver's instance variables: sender: BlockClosure>>ifError: pc: 17 stackp: 3 method: (BlockClosure>>#on:do: "a CompiledMethod(88866816)") closureOrNil: nil receiver: [aWorld displayWorld] BlockClosure>>ensure: Receiver: [(self tempAt: 2) cull: exception] Arguments and temporary variables: aBlock: [self tempAt: 3 put: true] complete: nil returnValue: nil Receiver's instance variables: outerContext: MethodContext(ContextPart)>>handleSignal: startpc: 90 numArgs: 0 MethodContext(ContextPart)>>handleSignal: Receiver: BlockClosure>>on:do: Arguments and temporary variables: exception: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: val: nil Receiver's instance variables: sender: BlockClosure>>ifError: pc: 17 stackp: 3 method: (BlockClosure>>#on:do: "a CompiledMethod(88866816)") closureOrNil: nil receiver: [aWorld displayWorld] MessageNotUnderstood(Exception)>>signal Receiver: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: Arguments and temporary variables: Receiver's instance variables: messageText: nil tag: nil signalContext: MessageNotUnderstood(Exception)>>signal handlerContext: BlockClosure>>on:do: outerContext: nil message: pixelValueForDepth: 32 receiver: 4278190081 reachedDefaultHandler: false LargePositiveInteger(Object)>>doesNotUnderstand: #pixelValueForDepth: Receiver: 4278190081 Arguments and temporary variables: aMessage: pixelValueForDepth: 32 exception: MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth: resumeValue: nil Receiver's instance variables: 4278190081 ColorForm>>colormapIfNeededForDepth: Receiver: ColorForm(5x9x1) Arguments and temporary variables: destDepth: 32 newMap: a Bitmap of length 2 i: 2 iLimiT: 2 Receiver's instance variables: bits: a Bitmap of length 9 width: 5 height: 9 depth: 1 offset: nil colors: {(Color transparent). 4278190081} cachedDepth: nil cachedColormap: nil ColorForm>>colormapIfNeededFor: Receiver: ColorForm(5x9x1) Arguments and temporary variables: destForm: DisplayScreen(1672x982x32) newMap: nil color: nil pv: nil i: nil iLimiT: nil Receiver's instance variables: bits: a Bitmap of length 9 width: 5 height: 9 depth: 1 offset: nil colors: {(Color transparent). 4278190081} cachedDepth: nil cachedColormap: nil FormCanvas>>image:at:sourceRect:rule: Receiver: a FormCanvas on: DisplayScreen(1672x982x32) Arguments and temporary variables: aForm: ColorForm(5x9x1) aPoint: 689@404 sourceRect: 0@0 corner: 5@9 rule: 24 Receiver's instance variables: target: nil filterSelector: nil origin: 0@0 clipRect: 544@234 corner: 699@501 form: DisplayScreen(1672x982x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>translucentImage:at:sourceRect: Receiver: a FormCanvas on: DisplayScreen(1672x982x32) Arguments and temporary variables: aForm: ColorForm(5x9x1) aPoint: 689@404 sourceRect: 0@0 corner: 5@9 Receiver's instance variables: target: nil filterSelector: nil origin: 0@0 clipRect: 544@234 corner: 699@501 form: DisplayScreen(1672x982x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>translucentImage:at: Receiver: a FormCanvas on: DisplayScreen(1672x982x32) Arguments and temporary variables: aForm: ColorForm(5x9x1) aPoint: 689@404 Receiver's instance variables: target: nil filterSelector: nil origin: 0@0 clipRect: 544@234 corner: 699@501 form: DisplayScreen(1672x982x32) port: a GrafPort shadowColor: nil ToggleMenuItemMorph>>drawIcon:on:in: Receiver: a ToggleMenuItemMorph(17825792)'Help' Arguments and temporary variables: aForm: ColorForm(5x9x1) aCanvas: a FormCanvas on: DisplayScreen(1672x982x32) aRectangle: 689@404 corner: 694@413 iconForm: ColorForm(5x9x1) Receiver's instance variables: bounds: 549@399 corner: 694@417 owner: a MenuMorph(415236096) submorphs: #() fullBounds: 549@399 corner: 694@417 color: Color black extension: a MorphExtension (20447232) [other: (errorOnDraw -> true)] font: a StrikeFont(Bitmap DejaVu Sans 9 14) emphasis: 0 contents: 'Help' hasFocus: false isEnabled: true subMenu: a MenuMorph(37486592) isSelected: false target: nil selector: nil arguments: nil icon: Form(16x16x32) getStateSelector: nil enablementSelector: nil keyText: nil ToggleMenuItemMorph>>drawSubMenuMarker:on:in: Receiver: a ToggleMenuItemMorph(17825792)'Help' Arguments and temporary variables: aForm: ColorForm(5x9x1) aCanvas: a FormCanvas on: DisplayScreen(1672x982x32) aRectangle: 567@401 corner: 694@417 markerRect: 689@404 corner: 694@413 Receiver's instance variables: bounds: 549@399 corner: 694@417 owner: a MenuMorph(415236096) submorphs: #() fullBounds: 549@399 corner: 694@417 color: Color black extension: a MorphExtension (20447232) [other: (errorOnDraw -> true)] font: a StrikeFont(Bitmap DejaVu Sans 9 14) emphasis: 0 contents: 'Help' hasFocus: false isEnabled: true subMenu: a MenuMorph(37486592) isSelected: false target: nil selector: nil arguments: nil icon: Form(16x16x32) getStateSelector: nil enablementSelector: nil keyText: nil

Jan. 12, 2011

Re: [Pharo-project] Issue 2897 in pharo: Compiler visitor fixes

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 2897 by stephane.ducasse: Compiler visitor fixes http://code.google.com/p/pharo/issues/detail?id=2897 in 12298

Jan. 12, 2011

Re: [Pharo-project] [update 1.2] #12297

by Mariano Martinez Peck

On Wed, Jan 12, 2011 at 4:45 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 12 Jan 2011, at 16:30, StÃ©phane Ducasse wrote: > > > - Glamourous setting as default. > > Yes! Maybe a bit dull, but clean and professional, my favorite! > > But it is not about that. As torsten said, there are books, screencasts, screnshots, tutorials, etc, which are done with Watery2. you, and all Pharo advanced users can easily change the theme, and you probbaly even have a script prepare that you run in each clean image to adapt it to your taste. But I think we should make the life easier for new comers. In addition, it was never discussed in the mailing list such change (at least I didn't see it). cheers mariano

Jan. 12, 2011

Re: [Pharo-project] Issue 2897 in pharo: Compiler visitor fixes

by pharo＠googlecode.com

Updates: Summary: Compiler visitor fixes Comment #3 on issue 2897 by stephane.ducasse: Compiler visitor fixes http://code.google.com/p/pharo/issues/detail?id=2897 (No comment was entered for this change.)

Jan. 12, 2011

Re: [Pharo-project] Xtreams up to date

by mkobetic＠gmail.com

"Henrik Sperre Johansen"<henrik.s.johansen(a)veloxit.no> wrote: > Can't just load the CoreTests and have all tests pass though, due to > the isAbstract implementation in XTReadingWritingTest. > Maybe XTReadingWritingTest, XTInfiniteReadingWritingTests and > XTFiniteReadingWritingTests should be moved to the Terminals-Tests package? I could go both ways on this one. They are in CoreTests because the tests themselves test core functionality, but you can't run any of those without the Terminals, so I can see the argument your way too. I wonder though if the move buys us much. There won't be much left in CoreTests if we move the tests that need terminals, it will be basically just the buffer tests. So running the CoreTests without the rest won't tell you much about the state of the port. Thanks for the additional details on the test failures. Cheers! Martin

Jan. 12, 2011

Re: [Pharo-project] [SPAM] Default Theme (was [update 1.2] #12297)

by Sven Van Caekenberghe

On 12 Jan 2011, at 16:41, Torsten Bergmann wrote: >> - Glamourous setting as default. > > Arrghhh ... how ugly. I like the Watery2 theme > more and would like to keep it as default. > Any chance we can put it back ... should we > vote? > > It is also used in various screenshots and > screencasts and has given Pharo already a visual > identity. > > So why switch to Glamourous as default? > > Thx > T. de gustibus et coloribus non est disputandum this cannot be settled I guess. Sven

Jan. 12, 2011

Re: [Pharo-project] [update 1.2] #12297

by Sven Van Caekenberghe

On 12 Jan 2011, at 16:30, StÃ©phane Ducasse wrote: > - Glamourous setting as default. Yes! Maybe a bit dull, but clean and professional, my favorite! Sven

Jan. 12, 2011

Re: [Pharo-project] Default Theme (was [update 1.2] #12297)

by Mariano Martinez Peck

On Wed, Jan 12, 2011 at 4:41 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >- Glamourous setting as default. > > Arrghhh ... how ugly. I like the Watery2 theme > more and would like to keep it as default. > Any chance we can put it back ... should we > vote? > > It is also used in various screenshots and > screencasts and has given Pharo already a visual > identity. > > So why switch to Glamourous as default? > +1 This is a radical change and I don't agree. > > Thx > T. > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > >

Jan. 12, 2011