November 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to access classVariable access with the browser

by HernÃ¡n Morales Durand

Hi Lukas, there is a little bug in the OB installation in Core #11035. To reproduce it open a new system OmniBrowser and try to browse the class Trait. Below is the stack trace, a fix is attached. Cheers HernÃ¡n 7 November 2009 9:26:35 pm VM: Win32 - IX86 - NT - Squeak3.10.2 of '5 June 2008' [latest update: #7179] Image: Pharo1.1a [Latest update: #11035] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir D:\Smalltalk\Pharo Trusted Dir D:\Smalltalk\Pharo\mvs Untrusted Dir C:\Documents and Settings\mvs\Mis documentos\My Squeak ByteSymbol(Object)>>error: Receiver: #category Arguments and temporary variables: aString: 'MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to:' Receiver's instance variables: #category [] in WorldState>>displayWorldSafely: Receiver: a WorldState Arguments and temporary variables: err: 'MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to:' rcvr: #category errCtx: OBLazyListMorph>>display:atRow:on: errMorph: an OBLazyListMorph(2972) Receiver's instance variables: hands: an Array(a HandMorph(3216)) viewBox: 0@0 corner: 978@638 canvas: a FormCanvas on: DisplayScreen(978x638x32) damageRecorder: a DamageRecorder stepList: a Heap(StepMessage(#stepAt: -> a SystemWindow(3984))(a SystemWindow(3...etc... lastStepTime: 25826547 lastStepMessage: nil lastCycleTime: 25826376 commandHistory: a CommandHistory alarms: a Heap() lastAlarmTime: 25826547 BlockClosure>>valueWithPossibleArgs: Receiver: [closure] in WorldState>>displayWorldSafely: Arguments and temporary variables: anArray: #('MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to:' #catego...etc... Receiver's instance variables: outerContext: WorldState>>displayWorldSafely: startpc: 73 numArgs: 2 [] in BlockClosure>>ifError: Receiver: [closure] in WorldState>>displayWorldSafely: Arguments and temporary variables: errorHandlerBlock: MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to: ex: [closure] in WorldState>>displayWorldSafely: Receiver's instance variables: outerContext: WorldState>>displayWorldSafely: startpc: 66 numArgs: 0 BlockClosure>>valueWithPossibleArgs: Receiver: [closure] in BlockClosure>>ifError: Arguments and temporary variables: anArray: an Array(MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to:) Receiver's instance variables: outerContext: BlockClosure>>ifError: startpc: 40 numArgs: 1 [] in MethodContext(ContextPart)>>handleSignal: Receiver: BlockClosure>>on:do: Arguments and temporary variables: exception: MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to: Receiver's instance variables: sender: BlockClosure>>ifError: pc: 17 stackp: 3 method: (BlockClosure>>#on:do: "a CompiledMethod(3772)") closureOrNil: nil receiver: [closure] in WorldState>>displayWorldSafely: BlockClosure>>ensure: Receiver: [closure] in MethodContext(ContextPart)>>handleSignal: Arguments and temporary variables: aBlock: [closure] in MethodContext(ContextPart)>>handleSignal: returnValue: nil b: 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: ByteSymbol>>hasWideCharacterFrom:to: val: nil Receiver's instance variables: sender: BlockClosure>>ifError: pc: 17 stackp: 3 method: (BlockClosure>>#on:do: "a CompiledMethod(3772)") closureOrNil: nil receiver: [closure] in WorldState>>displayWorldSafely: MessageNotUnderstood(Exception)>>signal Receiver: MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to: Arguments and temporary variables: Receiver's instance variables: messageText: nil tag: nil signalContext: MessageNotUnderstood(Exception)>>signal handlerContext: BlockClosure>>on:do: outerContext: nil message: hasWideCharacterFrom: 1 to: 8 receiver: #category reachedDefaultHandler: false ByteSymbol(Object)>>doesNotUnderstand: #hasWideCharacterFrom:to: Receiver: #category Arguments and temporary variables: aMessage: hasWideCharacterFrom: 1 to: 8 exception: MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to: resumeValue: nil Receiver's instance variables: #category StrikeFontSet>>displayString:on:from:to:at:kern:baselineY: Receiver: a StrikeFontSet(Accuny12I 12) Arguments and temporary variables: aString: #category aBitBlt: a GrafPort startIndex: 1 stopIndex: 8 aPoint: 701@160 kernDelta: 0 baselineY: 170 Receiver's instance variables: fontArray: an Array(a StrikeFont(Accuny12 12)) emphasis: 2 derivativeFonts: #(nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil ...etc... name: 'Accuny12I' rIndex: nil StrikeFontSet>>displayString:on:from:to:at:kern: Receiver: a StrikeFontSet(Accuny12I 12) Arguments and temporary variables: aString: #category aBitBlt: a GrafPort startIndex: 1 stopIndex: 8 aPoint: 701@160 kernDelta: 0 Receiver's instance variables: fontArray: an Array(a StrikeFont(Accuny12 12)) emphasis: 2 derivativeFonts: #(nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil ...etc... name: 'Accuny12I' rIndex: nil FormCanvas>>drawString:from:to:in:font:color: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aString: a Text for #category firstIndex: 1 lastIndex: 8 bounds: 14@96 corner: 722@108 fontOrNil: a StrikeFontSet(Accuny12I 12) c: Color black font: a StrikeFontSet(Accuny12I 12) portRect: 684@64 corner: 850@288 Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>drawString:in:font:color: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: s: a Text for #category boundsRect: 14@96 corner: 722@108 fontOrNil: a StrikeFontSet(Accuny12I 12) c: Color black Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil OBLazyListMorph>>display:atRow:on: Receiver: an OBLazyListMorph(2972) Arguments and temporary variables: <<error during printing> Receiver's instance variables: bounds: 0@0 corner: 722@432 owner: a TransformMorph(73) submorphs: #() fullBounds: 0@0 corner: 722@432 color: Color black extension: a MorphExtension (2984) [other: (errorOnDraw -> true)] listItems: an Array(#applyChangesOfNewTraitCompositionReplacing: #asClassDefini...etc... font: a StrikeFontSet(Accuny12 12) selectedRow: 0 selectedRows: a PluggableSet() listSource: an OBPluggableListMorph(274) maxWidth: 702 OBLazyListMorph(LazyListMorph)>>drawOn: Receiver: an OBLazyListMorph(2972) Arguments and temporary variables: aCanvas: a FormCanvas on: DisplayScreen(978x638x32) row: 9 rowLimiT: 19 Receiver's instance variables: bounds: 0@0 corner: 722@432 owner: a TransformMorph(73) submorphs: #() fullBounds: 0@0 corner: 722@432 color: Color black extension: a MorphExtension (2984) [other: (errorOnDraw -> true)] listItems: an Array(#applyChangesOfNewTraitCompositionReplacing: #asClassDefini...etc... font: a StrikeFontSet(Accuny12 12) selectedRow: 0 selectedRows: a PluggableSet() listSource: an OBPluggableListMorph(274) maxWidth: 702 FormCanvas(Canvas)>>draw: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: anObject: an OBLazyListMorph(2972) Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>drawMorph: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aMorph: an OBLazyListMorph(2972) Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil [] in OBLazyListMorph(Morph)>>fullDrawOn: Receiver: an OBLazyListMorph(2972) Arguments and temporary variables: aCanvas: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 0@0 corner: 722@432 owner: a TransformMorph(73) submorphs: #() fullBounds: 0@0 corner: 722@432 color: Color black extension: a MorphExtension (2984) [other: (errorOnDraw -> true)] listItems: an Array(#applyChangesOfNewTraitCompositionReplacing: #asClassDefini...etc... font: a StrikeFontSet(Accuny12 12) selectedRow: 0 selectedRows: a PluggableSet() listSource: an OBPluggableListMorph(274) maxWidth: 702 FormCanvas>>roundCornersOf:in:during: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aMorph: an OBLazyListMorph(2972) bounds: 0@0 corner: 722@432 aBlock: [closure] in OBLazyListMorph(Morph)>>fullDrawOn: Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>roundCornersOf:during: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aMorph: an OBLazyListMorph(2972) aBlock: [closure] in OBLazyListMorph(Morph)>>fullDrawOn: Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil OBLazyListMorph(Morph)>>fullDrawOn: Receiver: an OBLazyListMorph(2972) Arguments and temporary variables: aCanvas: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 0@0 corner: 722@432 owner: a TransformMorph(73) submorphs: #() fullBounds: 0@0 corner: 722@432 color: Color black extension: a MorphExtension (2984) [other: (errorOnDraw -> true)] listItems: an Array(#applyChangesOfNewTraitCompositionReplacing: #asClassDefini...etc... font: a StrikeFontSet(Accuny12 12) selectedRow: 0 selectedRows: a PluggableSet() listSource: an OBPluggableListMorph(274) maxWidth: 702 FormCanvas(Canvas)>>fullDraw: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: anObject: an OBLazyListMorph(2972) Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>fullDrawMorph: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aMorph: an OBLazyListMorph(2972) Receiver's instance variables: target: nil filterSelector: nil origin: 687@64 clipRect: 684@64 corner: 850@288 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil [] in [] in TransformMorph>>drawSubmorphsOn: Receiver: a TransformMorph(73) Arguments and temporary variables: myCanvas: an OBLazyListMorph(2972) m: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 548@0 corner: 714@224 owner: an OBPluggableListMorph(274) submorphs: an Array(an OBLazyListMorph(2972)) fullBounds: 548@0 corner: 714@224 color: Color transparent extension: nil transform: a MorphicTransform(angle = 0.0; scale = 1.0; offset = -551@0) smoothing: 1 localBounds: nil Array(SequenceableCollection)>>reverseDo: Receiver: an Array(an OBLazyListMorph(2972)) Arguments and temporary variables: aBlock: [closure] in [] in TransformMorph>>drawSubmorphsOn: index: 1 Receiver's instance variables: an Array(an OBLazyListMorph(2972)) [] in TransformMorph>>drawSubmorphsOn: Receiver: a TransformMorph(73) Arguments and temporary variables: myCanvas: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 548@0 corner: 714@224 owner: an OBPluggableListMorph(274) submorphs: an Array(an OBLazyListMorph(2972)) fullBounds: 548@0 corner: 714@224 color: Color transparent extension: nil transform: a MorphicTransform(angle = 0.0; scale = 1.0; offset = -551@0) smoothing: 1 localBounds: nil FormCanvas>>transformBy:clippingTo:during:smoothing: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aDisplayTransform: a MorphicTransform(angle = 0.0; scale = 1.0; offset = -551@0...etc... aClipRect: 548@0 corner: 714@224 aBlock: [closure] in TransformMorph>>drawSubmorphsOn: cellSize: 1 innerRect: nil patchRect: nil sourceQuad: nil warp: nil start: nil subCanvas: nil i: nil Receiver's instance variables: target: nil filterSelector: nil origin: 136@64 clipRect: 684@64 corner: 863@301 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil TransformMorph>>drawSubmorphsOn: Receiver: a TransformMorph(73) Arguments and temporary variables: aCanvas: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 548@0 corner: 714@224 owner: an OBPluggableListMorph(274) submorphs: an Array(an OBLazyListMorph(2972)) fullBounds: 548@0 corner: 714@224 color: Color transparent extension: nil transform: a MorphicTransform(angle = 0.0; scale = 1.0; offset = -551@0) smoothing: 1 localBounds: nil [] in TransformMorph(Morph)>>fullDrawOn: Receiver: a TransformMorph(73) Arguments and temporary variables: aCanvas: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 548@0 corner: 714@224 owner: an OBPluggableListMorph(274) submorphs: an Array(an OBLazyListMorph(2972)) fullBounds: 548@0 corner: 714@224 color: Color transparent extension: nil transform: a MorphicTransform(angle = 0.0; scale = 1.0; offset = -551@0) smoothing: 1 localBounds: nil FormCanvas>>roundCornersOf:in:during: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aMorph: a TransformMorph(73) bounds: 548@0 corner: 714@224 aBlock: [closure] in TransformMorph(Morph)>>fullDrawOn: Receiver's instance variables: target: nil filterSelector: nil origin: 136@64 clipRect: 684@64 corner: 863@301 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>roundCornersOf:during: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aMorph: a TransformMorph(73) aBlock: [closure] in TransformMorph(Morph)>>fullDrawOn: Receiver's instance variables: target: nil filterSelector: nil origin: 136@64 clipRect: 684@64 corner: 863@301 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil TransformMorph(Morph)>>fullDrawOn: Receiver: a TransformMorph(73) Arguments and temporary variables: aCanvas: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 548@0 corner: 714@224 owner: an OBPluggableListMorph(274) submorphs: an Array(an OBLazyListMorph(2972)) fullBounds: 548@0 corner: 714@224 color: Color transparent extension: nil transform: a MorphicTransform(angle = 0.0; scale = 1.0; offset = -551@0) smoothing: 1 localBounds: nil FormCanvas(Canvas)>>fullDraw: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: anObject: a TransformMorph(73) Receiver's instance variables: target: nil filterSelector: nil origin: 136@64 clipRect: 684@64 corner: 863@301 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil FormCanvas(Canvas)>>fullDrawMorph: Receiver: a FormCanvas on: DisplayScreen(978x638x32) Arguments and temporary variables: aMorph: a TransformMorph(73) Receiver's instance variables: target: nil filterSelector: nil origin: 136@64 clipRect: 684@64 corner: 863@301 form: DisplayScreen(978x638x32) port: a GrafPort shadowColor: nil [] in [] in OBPluggableListMorph(Morph)>>drawSubmorphsOn: Receiver: an OBPluggableListMorph(274) Arguments and temporary variables: canvas: a TransformMorph(73) m: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 548@0 corner: 727@237 owner: an OBPane(2011) submorphs: an Array(a ScrollBar(3409) a ScrollBar(2541) a TransformMorph(73)) fullBounds: 548@0 corner: 727@237 color: Color white extension: a MorphExtension (990) [other: (dragEnabled -> true) (dropEnabled -...etc... borderWidth: 0 borderColor: Color black model: an OBColumn() slotName: nil open: false scrollBar: a ScrollBar(2541) scroller: a TransformMorph(73) retractableScrollBar: false scrollBarOnLeft: false getMenuSelector: #menu: getMenuTitleSelector: nil hasFocus: false hScrollBar: a ScrollBar(3409) list: nil getListSelector: #list getListSizeSelector: #listSize getListElementSelector: #listAt: getIndexSelector: #selection setIndexSelector: #selection: keystrokeActionSelector: #keystroke:from: autoDeselect: false lastKeystrokeTime: 0 lastKeystrokes: '' doubleClickSelector: #doubleClick handlesBasicKeys: nil potentialDropRow: nil listMorph: an OBLazyListMorph(2972) hScrollRangeCache: nil Array(SequenceableCollection)>>reverseDo: Receiver: an Array(a ScrollBar(3409) a ScrollBar(2541) a TransformMorph(73)) Arguments and temporary variables: aBlock: [closure] in [] in OBPluggableListMorph(Morph)>>drawSubmorphsOn: index: 3 Receiver's instance variables: an Array(a ScrollBar(3409) a ScrollBar(2541) a TransformMorph(73)) [] in OBPluggableListMorph(Morph)>>drawSubmorphsOn: Receiver: an OBPluggableListMorph(274) Arguments and temporary variables: canvas: a FormCanvas on: DisplayScreen(978x638x32) Receiver's instance variables: bounds: 548@0 corner: 727@237 owner: an OBPane(2011) submorphs: an Array(a ScrollBar(3409) a ScrollBar(2541) a TransformMorph(73)) fullBounds: 548@0 corner: 727@237 color: Color white extension: a MorphExtension (990) [other: (dragEnabled -> true) (dropEnabled -...etc... borderWidth: 0 borderColor: Color black model: an OBColumn() slotName: nil open: false scrollBar: a ScrollBar(2541) scroller: a TransformMorph(73) retractableScrollBar: false scrollBarOnLeft: false getMenuSelector: #menu: getMenuTitleSelector: nil hasFocus: false hScrollBar: a ScrollBar(3409) list: nil getListSelector: #list getListSizeSelector: #listSize getListElementSelector: #listAt: getIndexSelector: #selection setIndexSelector: #selection: keystrokeActionSelector: #keystroke:from: autoDeselect: false lastKeystrokeTime: 0 lastKeystrokes: '' doubleClickSelector: #doubleClick handlesBasicKeys: nil potentialDropRow: nil listMorph: an OBLazyListMorph(2972) hScrollRangeCache: nil OBPluggableListMorph(Morph)>>drawSubmorphsOn: Receiver: an OBPluggableListMorph(274) Arguments and temporary variables: aCanvas: a FormCanvas on: DisplayScreen(978x638x32) drawBlock: [closure] in OBPluggableListMorph(Morph)>>drawSubmorphsOn: Receiver's instance variables: bounds: 548@0 corner: 727@237 owner: an OBPane(2011) submorphs: an Array(a ScrollBar(3409) a ScrollBar(2541) a TransformMorph(73)) fullBounds: 548@0 corner: 727@237 color: Color white extension: a MorphExtension (990) [other: (dragEnabled -> true) (dropEnabled -...etc... borderWidth: 0 borderColor: Color black model: an OBColumn() slotName: nil open: false scrollBar: a ScrollBar(2541) scroller: a TransformMorph(73) retractableScrollBar: false scrollBarOnLeft: false getMenuSelector: #menu: getMenuTitleSelector: nil hasFocus: false hScrollBar: a ScrollBar(3409) list: nil getListSelector: #list getListSizeSelector: #listSize getListElementSelector: #listAt: getIndexSelector: #selection setIndexSelector: #selection: keystrokeActionSelector: #keystroke:from: autoDeselect: false lastKeystrokeTime: 0 lastKeystrokes: '' doubleClickSelector: #doubleClick handlesBasicKeys: nil potentialDropRow: nil listMorph: an OBLazyListMorph(2972) hScrollRangeCache: nil --- The full stack --- ByteSymbol(Object)>>error: [] in WorldState>>displayWorldSafely: BlockClosure>>valueWithPossibleArgs: [] in BlockClosure>>ifError: BlockClosure>>valueWithPossibleArgs: [] in MethodContext(ContextPart)>>handleSignal: BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MessageNotUnderstood(Exception)>>signal ByteSymbol(Object)>>doesNotUnderstand: #hasWideCharacterFrom:to: StrikeFontSet>>displayString:on:from:to:at:kern:baselineY: StrikeFontSet>>displayString:on:from:to:at:kern: FormCanvas>>drawString:from:to:in:font:color: FormCanvas(Canvas)>>drawString:in:font:color: OBLazyListMorph>>display:atRow:on: OBLazyListMorph(LazyListMorph)>>drawOn: FormCanvas(Canvas)>>draw: FormCanvas(Canvas)>>drawMorph: [] in OBLazyListMorph(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: OBLazyListMorph(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in TransformMorph>>drawSubmorphsOn: Array(SequenceableCollection)>>reverseDo: [] in TransformMorph>>drawSubmorphsOn: FormCanvas>>transformBy:clippingTo:during:smoothing: TransformMorph>>drawSubmorphsOn: [] in TransformMorph(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: TransformMorph(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in OBPluggableListMorph(Morph)>>drawSubmorphsOn: Array(SequenceableCollection)>>reverseDo: [] in OBPluggableListMorph(Morph)>>drawSubmorphsOn: OBPluggableListMorph(Morph)>>drawSubmorphsOn: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - OBPluggableListMorph(PluggableListMorph)>>drawSubmorphsOn: [] in OBPluggableListMorph(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: OBPluggableListMorph(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in OBPane(Morph)>>drawSubmorphsOn: Array(SequenceableCollection)>>reverseDo: [] in OBPane(Morph)>>drawSubmorphsOn: FormCanvas>>clipBy:during: OBPane(Morph)>>drawSubmorphsOn: [] in OBPane(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: OBPane(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in TransformMorph>>drawSubmorphsOn: Array(SequenceableCollection)>>reverseDo: [] in TransformMorph>>drawSubmorphsOn: FormCanvas>>transformBy:clippingTo:during:smoothing: TransformMorph>>drawSubmorphsOn: [] in TransformMorph(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: TransformMorph(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in OBPaneScroller(Morph)>>drawSubmorphsOn: Array(SequenceableCollection)>>reverseDo: [] in OBPaneScroller(Morph)>>drawSubmorphsOn: OBPaneScroller(Morph)>>drawSubmorphsOn: [] in OBPaneScroller(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: OBPaneScroller(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in OBGroupingMorph(Morph)>>drawSubmorphsOn: Array(SequenceableCollection)>>reverseDo: [] in OBGroupingMorph(Morph)>>drawSubmorphsOn: OBGroupingMorph(Morph)>>drawSubmorphsOn: [] in OBGroupingMorph(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: OBGroupingMorph(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in SystemWindow(Morph)>>drawSubmorphsOn: Array(SequenceableCollection)>>reverseDo: [] in SystemWindow(Morph)>>drawSubmorphsOn: FormCanvas>>clipBy:during: SystemWindow(Morph)>>drawSubmorphsOn: [] in SystemWindow(Morph)>>fullDrawOn: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: SystemWindow(Morph)>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [] in [] in WorldState>>drawWorld:submorphs:invalidAreasOn: Rectangle>>allAreasOutsideList:startingAt:do: Rectangle>>allAreasOutsideList:do: [] in WorldState>>drawWorld:submorphs:invalidAreasOn: Array(SequenceableCollection)>>do: WorldState>>drawWorld:submorphs:invalidAreasOn: [] in WorldState>>displayWorld:submorphs: FormCanvas>>roundCornersOf:in:during: FormCanvas(Canvas)>>roundCornersOf:during: WorldState>>displayWorld:submorphs: PasteUpMorph>>privateOuterDisplayWorld PasteUpMorph>>displayWorld [] in WorldState>>displayWorldSafely: BlockClosure>>on:do: BlockClosure>>ifError: WorldState>>displayWorldSafely: WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: PasteUpMorph>>doOneCycle [] in Project class>>spawnNewProcess [] in BlockClosure>>newProcess 2009/11/7 Lukas Renggli <renggli(a)gmail.com> > 2009/11/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > when you are on the class side if you method has a classVariable and > > you want to know who access it. > > Then chase variables show you the class instance varaibles but not the > > classVariable. > > Yes, that's a bug. When you are on the class side, the class variables > of the meta-class are displayed. Also the labeling of the window is > suboptimal. I fixed these issues. Let me know if this is better now. > > Gofer new > squeaksource: 'rb'; > addPackage: 'AST-Core'; > addPackage: 'Refactoring-Core'; > addPackage: 'Refactoring-Spelling'; > renggli: 'omnibrowser'; > addPackage: 'OmniBrowser'; > addPackage: 'OB-Standard'; > addPackage: 'OB-Morphic'; > addPackage: 'OB-Shout'; > addPackage: 'OB-Refactory'; > addPackage: 'OB-Regex'; > addPackage: 'OB-SUnitIntegration'; > renggli: 'unsorted'; > addPackage: 'Shout'; > addPackage: 'RoelTyper'; > addPackage: 'ECompletion'; > addPackage: 'ECompletionOmniBrowser'; > load; > recompile > > Lukas > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 8, 2009

Re: [Pharo-project] Seaside and SUnit

by Dale Henrichs

Bill, I would use R1.5 with Seaside 2.8 ... I use a version of that package with GemStone with good results. R2.9 should be used with Seaside3.0 ... I haven't ported R2.9 to GemStone yet, so I can't say how it works with the most recent Seaside3.0. Here's a link to the 2.9 announcement: http://lists.squeakfoundation.org/pipermail/seaside/2009-May/020739.html The tutorial link is a good link to follow for info on using Seaside Testing. If I'm not mistaken, the latest version of R2.9 (and r1.5 for that matter) predates the real block closure work for Pharo, so there's an outside chance that a little bit of work may be needed to get it working on Pharo... Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Dale, | | I had lots of luck finding links - all of it bad :) For fun, try some | searches on SqueakSource. Seaside results are huge; Seaside Shaffer; | Seaside testing does work, though it misses Albatross. Also, try | following seaside.st (Community|extensions) to the the Shaffer | framework. | | You raise an interesting question: with the changes in Seaside, which | is the correct version of SeasideTesting? | | Bill | | | | -----Original Message----- | From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale | Henrichs | Sent: Saturday, November 07, 2009 3:49 PM | To: Pharo-project(a)lists.gforge.inria.fr | Cc: Pharo-project(a)lists.gforge.inria.fr | Subject: Re: [Pharo-project] Seaside and SUnit | | Bill, | | Don't what link you followed but, Seaside Testing is at (works for | me:): | http://www.squeaksource.com/SeasideTesting.html | | There's a recent update (June of this year) to the framework for | Seaside3.0 (Seaside 2.9 at the time)... | | Seems you've been having bad luck finding info with google(?)... | | Dale | ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | | | Stef, | | | | Do you have a preference among them? If I am reading correctly, | | Shaffer's framework simulates the browser; Albatross uses JavaScript | | | to control a browser external to Pharo. I can see advantages to | both | | approaches. | | | | There is a lot of link rot on these frameworks. I can't find | | Shaffer's code anywhere; everything seems to ultimately point to | | SqueakMap, and the page just gives an error. His website also has a | | | dead link to a tutorial of yours. The pre-installed Albatross image | | | linked from SqueakSource leads to a corrupt file. | | | | Lunch calls, then I will try to get the pieces of Albatross. | | | | Bill | | | | | | | | -----Original Message----- | | From: pharo-project-bounces(a)lists.gforge.inria.fr | | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of | | StÃ©phane Ducasse | | Sent: Saturday, November 07, 2009 3:27 AM | | To: Pharo-project(a)lists.gforge.inria.fr | | Subject: Re: [Pharo-project] Seaside and SUnit | | | | you have two testing frameworks | | albratross | | and david shaffer testing framework | | | | You also have selenium that people use to test seaside app. | | | | Stef | | | | On Nov 7, 2009, at 1:04 AM, Schwab,Wilhelm K wrote: | | | | > Stef, | | > | | > Is albatross the right place to look for help? | | > | | > Bill | | > | | > | | > _______________________________________________ | | > Pharo-project mailing list | | > Pharo-project(a)lists.gforge.inria.fr | | > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | | | | | _______________________________________________ | | Pharo-project mailing list | | Pharo-project(a)lists.gforge.inria.fr | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | | | _______________________________________________ | | Pharo-project mailing list | | Pharo-project(a)lists.gforge.inria.fr | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 7, 2009

Re: [Pharo-project] invalid sources for unregistered CompiledMethod

by Nicolas Cellier

2009/11/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Nov 7, 2009, at 8:30 PM, Martin McClure wrote: > >> Adrian Lienhard wrote: >>> Yes, in "normal" use of Pharo, holding the sources in memory would >>> only consume a fraction of the available RAM. Some applications, >>> however, have several hundred images running at the same time on a >>> server. In this case the picture looks very different again. >> >> It would be easy to strip all sources from production images, but the >> simple way of doing that would mean any debugging would be done on >> decompiled code. >> >>> >>> I think Marcus' idea of swapping in/out ressources is very >>> interesting. We could get rid of the ancient sources handling but >>> still have a low, or even lower, memory footprint. >>> >> >> This would be even better. >> ImageSegments are a start in this direction. > > yes this is why I always wanted to have tests to make sure that we do > not break them. > > Stef >> >> -Martin >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > Until these great ideas take form, find a workaround attached.

Nov. 7, 2009

Re: [Pharo-project] [ANN] prebuilt 1.1 #11035

by Mariano Martinez Peck

On Sat, Nov 7, 2009 at 6:21 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Yes, we don't use a "pre-alpha" tag [1] but start with alpha even > though the new features are not even being worked on. I think this > makes sense because we already have a running and working system. The > important distinctions between phases we need is alpha (i.e., > unstable, experimental and unfinished stuff can go in), beta (feature > complete but with known problems), RC, and then the final release. I > don't think we would gain anything with an additional tag. > > Yes, I agree with you it has no sense maybe to use the pre-alpha tag. However, I was wondering, not having any tag at this moment. When most of the work of 1.1 is done, then we tag alpha, then beta...etc. If I remember correctly, Pharo 1.0 at the very beginning didn't have a alpha tag ? only at the last months..but during the first year, I don't remember any tag, just Pharo core XXX version. Anyway, I don't want to discuss the life cycle. I just wanted to be sure it wasn't a mistake when putting the name to the zip. Best Mariano > Cheers, > Adrian > > [1] http://en.wikipedia.org/wiki/Development_stage > On Nov 7, 2009, at 20:57 , Mariano Martinez Peck wrote: > > > On Sat, Nov 7, 2009 at 5:38 PM, Adrian Lienhard <adi(a)netstyle.ch> > > wrote: > > > >> Yes, we have a 1.0 and a 1.1 stream now (actually since the sprint in > >> Lille). > >> > >> > > Yes I know that. > > > > > >> I'm integrating remaining critical fixes for 1.0, while Stef and the > >> other integrators have started working on 1.1. I don't think it's too > >> early at all. It allows us to keep the pace to move forward with new > >> stuff, while stabilizing and afterwards maintaining the 1.0 release. > >> > >> > > Yes, but this is done just with separating the streams in 1.0 and > > 1.1. What > > I don't know if it is ok is to put alpha to 1.1. > > > > I mean, when you tag something with alpha it means it is almost done > > and > > there are some bugs yet. But I think the job to be done for 1.1 is > > far more > > than just a couple of bugs. Maybe I wrong. > > > > But it sound strange to me to see a RC of one version and an alpha > > of the > > following at the same time. > > > > Cheers > > > > Mariano > > > > > >> Just as a reminder, here are the main goals we have set for 1.1: > >> > >> - New preferences system > >> - Integrate Alien > >> - Improve code quality (e.g., make selected Lint tests pass) > >> - Continuous integration system > >> > >> (http://code.google.com/p/pharo/wiki/Milestones) > >> > >> Cheers, > >> Adrian > >> > >> On Nov 7, 2009, at 20:15 , Mariano Martinez Peck wrote: > >> > >>> mmmmmmm are we already in 1.1 alpha ??? isn't it to early ? > >>> > >>> Best > >>> > >>> Mariano > >>> > >>> On Sat, Nov 7, 2009 at 2:26 PM, Marcus Denker <denker(a)acm.org> > >>> wrote: > >>> > >>>> > >>>> > >>>> > >> > http://gforge.inria.fr/frs/download.php/24734/PharoCore-1.1-11035-alpha.zip > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 7, 2009

Re: [Pharo-project] [ANN] prebuilt 1.1 #11035

by Schwab,Wilhelm K

Adrian, That's in www.squeaksource.com/Pharo/ ?? I think I found it, and it loaded(!!!) :) Time for a run, then I will retry the RC1 build. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Adrian Lienhard Sent: Saturday, November 07, 2009 4:39 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [ANN] prebuilt 1.1 #11035 Hi Bill, On Nov 7, 2009, at 21:23 , Schwab,Wilhelm K wrote: > Adrian, > > Whatever you guys think about underscores timing is fine by me. > From my own perspective, there is no "too soon" but there might be for > others. > > My code is unlikely to load in the core. Since the slice fixing > SharedQueue2 was marked depdendent on sequenceable collection fixes > that I can't load, I'm hesitant to get overly creative. I suppose I > could try loading the web image install script into a core image to > see if it runs in a reasonable time. Yes, the slice has quite some other changes. I just picked the three methods that were added to SharedQueue2. If you want to try out these changes, you can load Collection-Sequenceable-AdrianLienhard.39 from the Pharo repository into your image. Adrian > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of Adrian Lienhard > Sent: Saturday, November 07, 2009 3:12 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [ANN] prebuilt 1.1 #11035 > > > On Nov 7, 2009, at 20:59 , Schwab,Wilhelm K wrote: > >> A 1.1 alpha under construction is great. When do underscores appear, >> especially in class names? I thought I saw that creeping forward, >> and want to register my encouragement of any effort to have that >> appear in 1.1. Ok, I'll stop nagging :) > > It shouldn't be hard to do in 1.1. I discussed with Lukas today and > one open question is whether we want to enforce _ not being a valid > assignment already in 1.0. I fear a bit that people will complain > because they have to fix their code before being able to load it into > Pharo. Does anybody see a problem with this? From the previous > discussion I understand that most people would favor the change. But > is 1.0 too early? > >> >> For 1.0, I'm still stuck by the SharedQueue2 problem. I cannot load >> the sequencable collection fixes into either RC image - I thought I >> might be able to load it into RC1-dev and then file out the needed >> pieces into RC1-web, but no-go :( > > Can you also try to load your code into a core image? The update I did > yesterday includes the SharedQueue2 fixes. Please let us know if it > does not fix the problem. > > Adrian > >> >> Bill >> >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr >> ] On Behalf Of Adrian Lienhard >> Sent: Saturday, November 07, 2009 2:38 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [ANN] prebuilt 1.1 #11035 >> >> Yes, we have a 1.0 and a 1.1 stream now (actually since the sprint in >> Lille). >> >> I'm integrating remaining critical fixes for 1.0, while Stef and the >> other integrators have started working on 1.1. I don't think it's too >> early at all. It allows us to keep the pace to move forward with new >> stuff, while stabilizing and afterwards maintaining the 1.0 release. >> >> Just as a reminder, here are the main goals we have set for 1.1: >> >> - New preferences system >> - Integrate Alien >> - Improve code quality (e.g., make selected Lint tests pass) >> - Continuous integration system >> >> (http://code.google.com/p/pharo/wiki/Milestones) >> >> Cheers, >> Adrian >> >> On Nov 7, 2009, at 20:15 , Mariano Martinez Peck wrote: >> >>> mmmmmmm are we already in 1.1 alpha ??? isn't it to early ? >>> >>> Best >>> >>> Mariano >>> >>> On Sat, Nov 7, 2009 at 2:26 PM, Marcus Denker <denker(a)acm.org> >>> wrote: >>> >>>> >>>> >>>> http://gforge.inria.fr/frs/download.php/24734/PharoCore-1.1-11035- >>>> alp >>>> ha.zip >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 7, 2009

Re: [Pharo-project] [ANN] prebuilt 1.1 #11035

by Miguel Enrique CobÃ¡ Martinez

El sÃ¡b, 07-11-2009 a las 21:12 +0100, Adrian Lienhard escribiÃ³: > On Nov 7, 2009, at 20:59 , Schwab,Wilhelm K wrote: > > > A 1.1 alpha under construction is great. When do underscores > > appear, especially in class names? I thought I saw that creeping > > forward, and want to register my encouragement of any effort to have > > that appear in 1.1. Ok, I'll stop nagging :) > > It shouldn't be hard to do in 1.1. I discussed with Lukas today and > one open question is whether we want to enforce _ not being a valid > assignment already in 1.0. I fear a bit that people will complain > because they have to fix their code before being able to load it into > Pharo. Does anybody see a problem with this? From the previous > discussion I understand that most people would favor the change. But > is 1.0 too early? > Not too early for new projects that always used := for assigment but older code has _ sometimes and they could't load them in 1.0 without modification. It should be allowed _ assignment on 1.0 but fully forbidden on 1.1. Also, the release notes of 1.0 should remark quite loud that the _ assigment is obsolete and should never again be allowed. > > > > For 1.0, I'm still stuck by the SharedQueue2 problem. I cannot load > > the sequencable collection fixes into either RC image - I thought I > > might be able to load it into RC1-dev and then file out the needed > > pieces into RC1-web, but no-go :( > > Can you also try to load your code into a core image? The update I did > yesterday includes the SharedQueue2 fixes. Please let us know if it > does not fix the problem. > > Adrian > > > > > Bill > > > > > > > > -----Original Message----- > > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > > ] On Behalf Of Adrian Lienhard > > Sent: Saturday, November 07, 2009 2:38 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] [ANN] prebuilt 1.1 #11035 > > > > Yes, we have a 1.0 and a 1.1 stream now (actually since the sprint > > in Lille). > > > > I'm integrating remaining critical fixes for 1.0, while Stef and the > > other integrators have started working on 1.1. I don't think it's > > too early at all. It allows us to keep the pace to move forward with > > new stuff, while stabilizing and afterwards maintaining the 1.0 > > release. > > > > Just as a reminder, here are the main goals we have set for 1.1: > > > > - New preferences system > > - Integrate Alien > > - Improve code quality (e.g., make selected Lint tests pass) > > - Continuous integration system > > > > (http://code.google.com/p/pharo/wiki/Milestones) > > > > Cheers, > > Adrian > > > > On Nov 7, 2009, at 20:15 , Mariano Martinez Peck wrote: > > > >> mmmmmmm are we already in 1.1 alpha ??? isn't it to early ? > >> > >> Best > >> > >> Mariano > >> > >> On Sat, Nov 7, 2009 at 2:26 PM, Marcus Denker <denker(a)acm.org> wrote: > >> > >>> > >>> > >>> http://gforge.inria.fr/frs/download.php/24734/PharoCore-1.1-11035- > >>> alp > >>> ha.zip > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Nov. 7, 2009

Re: [Pharo-project] Fwd: nice bug with regex

by Adrian Lienhard

Do we need to update the package also in 1.0? It seems there are quite some important fixes. Stef, did you already create an issue? Adrian On Nov 5, 2009, at 11:28 , StÃ©phane Ducasse wrote: > Thanks I will integrate it. > > On Nov 4, 2009, at 10:46 PM, Lukas Renggli wrote: > >> I committed VB-Regex-lr.34 to the PharoInbox that fixes this issue. >> >> In fact, this is a completely new port of VB-Regex with numerous >> bug-fixes and enhancements. The bug you found was fixed in version >> 1.1c in December 2004. The version 1.1 we used up to now was from >> October 1999. >> >> The detailed log of changes from Vassily you can see below. >> >> Cheers, >> Lukas >> >> Name: VB-Regex-lr.34 >> Author: lr >> Time: 4 November 2009, 10:40:27 pm >> UUID: 9254d5aa-3e22-4e3b-83aa-2d633ff05570 >> Ancestors: VB-Regex-StephaneDucasse.33 >> >> VERSION 1.2.3 (November 2007) >> >> 1. Regexs with ^ or $ applied to copy empty strings caused infinite >> loops, e.g. ('' copyWithRegex: '^.*$' matchesReplacedWith: 'foo'). >> Applied a similar correction to that from version 1.1c, to >> #copyStream:to:(replacingMatchesWith:|translatingMatchesUsing:). >> 2. Extended RxParser testing to run each test for >> #copy:translatingMatchesUsing: as well as #search:. >> 3. Corrected #testSuite test that a dot does not match a null, which >> was passing by luck with Smalltalk code in a literal array. >> 4. Added test to end of test suite for fix 1 above. >> >> VERSION 1.2.2 (November 2006) >> >> There was no way to specify a backslash in a character set. Now [\\] >> is accepted. >> >> VERSION 1.2.1 (August 2006) >> >> 1. Support for returning all ranges (startIndex to: stopIndex) >> matching a regex - #allRangesOfRegexMatches:, #matchingRangesIn: >> 2. Added hint to usage documentation on how to get more information >> about matches when enumerating >> 3. Syntax description of dot corrected: matches anything but NUL >> since 1.1a >> >> VERSION 1.2 (May 2006) >> >> Fixed case-insensitive search for character sets. >> >> VERSION 1.1c (December 2004) >> >> Fixed the issue with #matchesOnStream:do: which caused infinite loops >> for matches >> that matched empty strings. >> >> VERSION 1.1b (November 2001) >> >> Changes valueNowOrOnUnwindDo: to ensure:, plus incorporates some >> earlier fixes. >> >> VERSION 1.1a (May 2001) >> >> 1. Support for keeping track of multiple subexpressions. >> 2. Dot (.) matches anything but NUL character, as it should per >> POSIX spec. >> 3. Some bug fixes. >> >> >> >> 2009/11/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> l := '1Ã¨re partie\nmilieu\nfin'. >>>> '.*' asRegex matchesIn l. >>> >>> -> infinite and freezing loop. >>> >>> Stef >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 7, 2009

Re: [Pharo-project] [ANN] prebuilt 1.1 #11035

by Adrian Lienhard

Hi Bill, On Nov 7, 2009, at 21:23 , Schwab,Wilhelm K wrote: > Adrian, > > Whatever you guys think about underscores timing is fine by me. > From my own perspective, there is no "too soon" but there might be > for others. > > My code is unlikely to load in the core. Since the slice fixing > SharedQueue2 was marked depdendent on sequenceable collection fixes > that I can't load, I'm hesitant to get overly creative. I suppose I > could try loading the web image install script into a core image to > see if it runs in a reasonable time. Yes, the slice has quite some other changes. I just picked the three methods that were added to SharedQueue2. If you want to try out these changes, you can load Collection-Sequenceable-AdrianLienhard.39 from the Pharo repository into your image. Adrian > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of Adrian Lienhard > Sent: Saturday, November 07, 2009 3:12 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [ANN] prebuilt 1.1 #11035 > > > On Nov 7, 2009, at 20:59 , Schwab,Wilhelm K wrote: > >> A 1.1 alpha under construction is great. When do underscores appear, >> especially in class names? I thought I saw that creeping forward, >> and >> want to register my encouragement of any effort to have that appear >> in >> 1.1. Ok, I'll stop nagging :) > > It shouldn't be hard to do in 1.1. I discussed with Lukas today and > one open question is whether we want to enforce _ not being a valid > assignment already in 1.0. I fear a bit that people will complain > because they have to fix their code before being able to load it > into Pharo. Does anybody see a problem with this? From the previous > discussion I understand that most people would favor the change. But > is 1.0 too early? > >> >> For 1.0, I'm still stuck by the SharedQueue2 problem. I cannot load >> the sequencable collection fixes into either RC image - I thought I >> might be able to load it into RC1-dev and then file out the needed >> pieces into RC1-web, but no-go :( > > Can you also try to load your code into a core image? The update I > did yesterday includes the SharedQueue2 fixes. Please let us know if > it does not fix the problem. > > Adrian > >> >> Bill >> >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr >> ] On Behalf Of Adrian Lienhard >> Sent: Saturday, November 07, 2009 2:38 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [ANN] prebuilt 1.1 #11035 >> >> Yes, we have a 1.0 and a 1.1 stream now (actually since the sprint in >> Lille). >> >> I'm integrating remaining critical fixes for 1.0, while Stef and the >> other integrators have started working on 1.1. I don't think it's too >> early at all. It allows us to keep the pace to move forward with new >> stuff, while stabilizing and afterwards maintaining the 1.0 release. >> >> Just as a reminder, here are the main goals we have set for 1.1: >> >> - New preferences system >> - Integrate Alien >> - Improve code quality (e.g., make selected Lint tests pass) >> - Continuous integration system >> >> (http://code.google.com/p/pharo/wiki/Milestones) >> >> Cheers, >> Adrian >> >> On Nov 7, 2009, at 20:15 , Mariano Martinez Peck wrote: >> >>> mmmmmmm are we already in 1.1 alpha ??? isn't it to early ? >>> >>> Best >>> >>> Mariano >>> >>> On Sat, Nov 7, 2009 at 2:26 PM, Marcus Denker <denker(a)acm.org> >>> wrote: >>> >>>> >>>> >>>> http://gforge.inria.fr/frs/download.php/24734/PharoCore-1.1-11035- >>>> alp >>>> ha.zip >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 7, 2009

Re: [Pharo-project] How to access classVariable access with the browser

by Lukas Renggli

> And so far this is not the case. In fact I preferred the old way > because it was dead simple and > working. accesses to iv /accesses to classVar. I find it dead simple. Clicking on 'variables' always shows you what you can see from the current browsing context: - When you are on the instance side you see instance and class variables. - When you are on the class side you see (class) instance and class variables. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Nov. 7, 2009

Re: [Pharo-project] [ANN] prebuilt 1.1 #11035

by Schwab,Wilhelm K

Great_news :) Thanks!! -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Saturday, November 07, 2009 3:38 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [ANN] prebuilt 1.1 #11035 pay attention alpha does not mean that we will close soon. Alpha is now the wild period where a lot will be integrated. Bill don;t worry as soon as lukas publish a slice we will integrate it. Stef On Nov 7, 2009, at 8:15 PM, Mariano Martinez Peck wrote: > mmmmmmm are we already in 1.1 alpha ??? isn't it to early ? > > Best > > Mariano > > On Sat, Nov 7, 2009 at 2:26 PM, Marcus Denker <denker(a)acm.org> wrote: > > > http://gforge.inria.fr/frs/download.php/24734/PharoCore-1.1-11035-alph > a.zip > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 7, 2009