- Pharo-dev - lists.pharo.org

[Pharo-project] About UITheme, Widgets and coupling
by StÃ©phane Ducasse Dec. 6, 2011

Dec. 6, 2011

Hi guys we got rid of preferences as a ugly facade and now we have UITheme and UIManager. I would like to understand how we can skin widgets while be as loosely coupled as possible. May be a UI builder is missingâ¦. I was looking at SystemProgressMorph we setDefaultParameters self theme setSystemProgressMorphDefaultParameters: self updateColor "update the apareance of aMorph" self theme preferGradientFill ifFalse: [^ self]. self fillStyle: (self theme progressFillStyleFor: self) and SystemProgressBarMorph has initialize "Initialize the receiver from the current theme." super initialize. barSize := 0. self fillStyle: ( self theme progressBarFillStyleFor: self); borderStyle: (self theme progressBarBorderStyleFor: self); barFillStyle: ( self theme progressBarProgressFillStyleFor: self) extent: aPoint "Update the bar fillStyle if appropriate." super extent: aPoint. self fillStyle isOrientedFill ifTrue: [ self fillStyle: (self theme progressBarFillStyleFor: self)]. self barFillStyle isOrientedFill ifTrue: [ self barFillStyle: ( self theme progressBarProgressFillStyleFor: self)] So to help me understanding the problem, I thought about the flow of things. I would really to avoid to have - widgets construction code in UITheme and UImanager (ref to debugger UI as mentioned by henryk) - UITheme invocation inside the widgets. May be a widget should have its own state and when we build it the class creation only push the info from the UITheme to the widgets What do you think? Stef

1 0

Re: [Pharo-project] could you test the attached?
by Marcus Denker Dec. 6, 2011

Dec. 6, 2011

Hi, With this change set, we get an error when doing the following: In the workspace do a "debug it" on this code: Transcript show: Class name then two times "step over" --> Subscript out of bounds error. Without the change it works. On Wed, Nov 16, 2011 at 8:58 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi All, > > Â Â I've found a bug inÂ ContextPart>>#runUntilErrorOrReturnFrom: that in a > certain rare circumstance causes the method to peel back too much of the > stack. Â This method is used in the debugger (e.g. completeStep: et al) but > also in Process termination. Â So it is right at the heart of the system. > Â I'm loath to simply commit it Â I'd really appreciate y'all testing with the > fix and reporting any changes you see. Â It does not affect the trunk test > suite (there is a test, WeakSetInspectorTest, which is unreliable, but apart > form that no observed effects). Â So, brave souls, please try with the > attached and see if you come to grief or not. > -- > thanks, > Eliot > -- -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

3 5

[Pharo-project] [COTDC] 91 - WeakOrderedCollection
by DeNigris Sean Dec. 6, 2011

Dec. 6, 2011

Awesome momentum! There are 20 comments waiting to be integrated + some already in from Squeak!!! Continuing in Collections... Today: WeakOrderedCollection Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest

4 3

[Pharo-project] Zinc problem
by Norbert Hartl Dec. 6, 2011

Dec. 6, 2011

As Zinc is now part of pharo may I assume that bug reports belong to the pharo tracker? I've discovered a problem in Zinc. If you execute this piece of code | client entity | client := ZnNeoClient new. entity := client applicationFormUrlEncodedEntity. entity at: 'testkey' put: 'Ã¶'. Transcript show: 'entity type: ', entity contentType printString; cr. Transcript show: 'encoded body: ', (String streamContents: [:stream| entity writeRepresentationOn: stream ]) You'll get (in pharo #13315) entity type: application/x-www-form-urlencoded;charset=iso-8859-1 encoded body: testkey=%C3%B6 As you can see the content type contains latin-1 as encoding while the body is utf-8 encoded. The utf-8 encoding comes from ZnUtils class>>writeQueryFields:on: that uses encodeForHTTP which uses utf-8 by default. Norbert

2 7

[Pharo-project] Questions about Weak classes
by Mariano Martinez Peck Dec. 6, 2011

Dec. 6, 2011

Hi guys. I have two small questions related to weak objects. 1) It seems all Weak objects are variable. ALWAYS. Why? It doesn't make sense to have a fixed weak object ? 2) We have the methods: variableByteSubclass: t instanceVariableNames: f classVariableNames: d poolDictionaries: s category: cat variableSubclass: t instanceVariableNames: f classVariableNames: d poolDictionaries: s category: cat variableWordSubclass: t instanceVariableNames: f classVariableNames: d poolDictionaries: s category: cat So... WHY we have then: weakSubclass: t instanceVariableNames: f classVariableNames: d poolDictionaries: s category: cat rather than variableWeakSubclass: t instanceVariableNames: f classVariableNames: d poolDictionaries: s category: cat is there any reason I am not seeing? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 1

[Pharo-project] UIManager
by Henrik Sperre Johansen Dec. 6, 2011

Dec. 6, 2011

Is it just me, or is UIManager gradually turning into a new SystemDictionary/Project? Cheers, Henry

2 1

Re: [Pharo-project] VM freezes sending #basicNew to Stream subclass
by Marcus Denker Dec. 6, 2011

Dec. 6, 2011

>>>>>> >>>>>> I'm stuck too, and the Debugger is currently unusable in Pharo 1.4 (I >>>>>> just can't step overâ¦) >>>>> >>>>> Strange. Because I use it. >>>>> Do you have a scenario that we can focus on to fix the problem you see. >>>>> >>>>> So with Camillo, we found that reverting the change of Eliot (that we added for testing...) helps: http://code.google.com/p/pharo/issues/detail?id=4998 I will do that revert in 14246 (And no, we should not have added the change. But than, how can one test without testing?) -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

2 1

[Pharo-project] Why CompiledMethod print string shows #identityHah ?
by Mariano Martinez Peck Dec. 6, 2011

Dec. 6, 2011

Hi guys. When printing compiled methods we get something like: TestCase >> #assert: -> (TestCase>>#assert: "a CompiledMethod(585629696)") Where the number is the #identityHash. I have never really needed that, and even more, I always want to print: TestCase >> #assert: -> 'TestCase>>#assert:' So...my question is, is there any reason why it makes so much sense to print the identityHash of a CompiledMethod ? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 2

[Pharo-project] [COTDC] 92 - TSortable
by sean＠clipperadams.com Dec. 6, 2011

Dec. 6, 2011

92 classes done 793 classes remaining Continuing in Collections... Today: TSortable Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest p.s. this message was sent from a pharo image. Did you know you could easily do that?!

1 0

[Pharo-project] pharo on lion
by Tudor Girba Dec. 6, 2011

Dec. 6, 2011

Hi, Is Pharo working Ok on the new OS X Lion? I am asking because I am considering to upgrade. Cheers, Doru -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

10 16