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

[Pharo-project] Is there any package to manipulate excel files?

by Guillermo Polito

I was searching in squeaksource, and querying the posts in the list, but I couldn't find anything useful :S. Thank you! Guille

Nov. 1, 2010

Re: [Pharo-project] A pattern for GUI programming (Morphic, Cuis, etc)

by Juan Vuletich

Hi Hannes, I am not currently working on LightWidgets. If you're interested, Cuis includes a working implementation where you can use the UI pattern. Cheers, Juan Vuletich Ps. Please send copy to me of any mail intended for me... I'm not following the Pharo list closely, and I might miss it.

Nov. 1, 2010

[Pharo-project] Smalltalk Labs Browser

by Geert Claes

Just stumbled on this very interesting seaside-based browser via James's blog: http://code.google.com/p/smalltalklabsbrowser -- View this message in context: http://forum.world.st/Smalltalk-Labs-Browser-tp3022069p3022069.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 1, 2010

Re: [Pharo-project] XML package is barking at load time

by Tobias Pape

Am 2010-10-31 um 10:55 schrieb stephane ducasse: > why this is squeakCommon? Does it work if this is in pharo? #squeakCommon is for configuration specs common to Pharo and Squeak. #pharo is for configuration specs for Pharo only. #squeak is for configuration specs for Squeak only. So Long, -Tobias

Nov. 1, 2010

[Pharo-project] [update 1.2] #12226

by stephane ducasse

12226 ----- - Issue 3200: Float do not print exactly when negative. Thanks Nicolas cellier. (I made a silly mistake). - Issue 3178: FractionTest>>#testDegreeCos. Thanks Nicolas cellier. Stef

Nov. 1, 2010

[Pharo-project] Fwd: [squeak-dev] Re: [ENH] Syntax extension for continuations

by StÃ©phane Ducasse

Begin forwarded message: > From: pharo-project-owner(a)lists.gforge.inria.fr > Date: November 1, 2010 7:33:55 AM GMT+01:00 > To: stephane.ducasse(a)gmail.com > Subject: Re: [squeak-dev] Re: [Pharo-project] [ENH] Syntax extension for continuations > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > From: stephane ducasse <stephane.ducasse(a)gmail.com> > Date: November 1, 2010 7:33:52 AM GMT+01:00 > To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> > Subject: Re: [squeak-dev] Re: [Pharo-project] [ENH] Syntax extension for continuations > > > +1 > >> This idea comes up every few years. This post sums up well the last attempt: http://blog.3plus4.org/2007/08/30/message-chains/ . >> >> I don't think it's worth changing the syntax for this. IMHO 1-2 pairs of parentheses usually improve readability. More parenthesis is rarely needed. Also mixing ;; with ; makes the code harder to understand. Try this: self foo ; bar ;; baz ; foo ;; bar ; baz. >> >> Note that the term 'continuation' means a totally different thing: http://en.wikipedia.org/wiki/Continuation . > > Stef > >

Nov. 1, 2010

Re: [Pharo-project] Failing tests in 1.2

by StÃ©phane Ducasse

Thanks nicolas This is strange but I could not find the KernelTests-Nice.297 package in the inbox. and I imagine that you save the slice so this looks like a bug I do not like :(... Stef > Please, please, fix > http://code.google.com/p/pharo/issues/detail?id=3200 before release. > > Cheers > > Nicolas > > 2010/10/30 Marcus Denker <marcus.denker(a)inria.fr>: >> ... bug Issues for all of them >> >> http://code.google.com/p/pharo/issues/list?can=2&q=type=FailingTest >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> >

Nov. 1, 2010

Re: [Pharo-project] [ENH] Syntax extension for continuations

by Igor Stasenko

On 1 November 2010 05:33, Levente Uzonyi <leves(a)elte.hu> wrote: > On Mon, 1 Nov 2010, Igor Stasenko wrote: > >> On 1 November 2010 05:04, Levente Uzonyi <leves(a)elte.hu> wrote: > > snip > >>> foo ; bar ;; baz ; foo ;; bar ; baz. >>> >> this is incorrect syntax. > > This is correct: ((self foo; bar) baz; foo) bar; baz. > Message chaining should be equivalent with this, shouldn't it? > yes, but continuation err.. chaining ';;' takes precedence before cascade ';' which means that you can write only as: self foo zork ;; bar ;; bum ; baz ; lz but not self foo zork ; bar ;; bum ; baz ;; lz otherwise you will also need to use parens to disambiguate nested cascades. > > Levente > -- Best regards, Igor Stasenko AKA sig.

Nov. 1, 2010

Re: [Pharo-project] [squeak-dev] Re: [ENH] Syntax extension for continuations

by Levente Uzonyi

On Mon, 1 Nov 2010, Igor Stasenko wrote: > On 1 November 2010 05:04, Levente Uzonyi <leves(a)elte.hu> wrote: snip >> foo ; bar ;; baz ; foo ;; bar ; baz. >> > this is incorrect syntax. This is correct: ((self foo; bar) baz; foo) bar; baz. Message chaining should be equivalent with this, shouldn't it? Levente > > >> Note that the term 'continuation' means a totally different thing: >> http://en.wikipedia.org/wiki/Continuation . >> > > It was called so in tiny smalltalk (if i remember), when i first > learned a syntax. You name it. > > >> >> Levente >> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Nov. 1, 2010

Re: [Pharo-project] [ENH] Syntax extension for continuations

by Levente Uzonyi

On Mon, 1 Nov 2010, Igor Stasenko wrote: > Here is more examples (found by searching .sources file with 3 or more '(((' ). > > ContextPart>>handleSignal: > > (((self tempAt: 1) handles: exception) and: [self tempAt: 3]) ifFalse: [ > ^ self nextHandlerContext handleSignal: exception]. > > > self tempAt: 1 ;; handles: exception ;; and: [self tempAt: 3] ;; ifFalse: [ > ^ self nextHandlerContext handleSignal: exception]. What about this? ((self tempAt: 3) and: [ (self tempAt: 1) handles: exception ]) ifFalse: [ ^ self nextHandlerContext handleSignal: exception]. > > > Bezier3Segment. > > before: > > bezier2SegmentCount: pixelError > "Compute the number of quadratic bezier segments needed to approximate > this cubic with no more than a specified error" > | a | > a := (start x negated @ start y negated) + (3 * via1) - (3 * via2) + > (end). > ^ (((a r / (20.0 * pixelError)) raisedTo: 0.333333) ceiling) max: 1. > > after: > > bezier2SegmentCount: pixelError > "Compute the number of quadratic bezier segments needed to approximate > this cubic with no more than a specified error" > | a | > a := start x negated @ start y negated ;; + (3 * via1) - (3 * via2) + > end. > ^ a r / (20.0 * pixelError) raisedTo: 0.333333 ;; ceiling max: 1. There are 2 superfluous parenthesis in the original code (which you omitted in your code). Here's the same without them: ^(a r / (20.0 * pixelError) raisedTo: 0.333333) ceiling max: 1. If I want to be "tricky", I can even remove another parenthesis: ^(0.05 * a r / pixelError raisedTo: 0.333333) ceiling max: 1. > > > ZipArchive > > before: > > lastIndexOfPKSignature: aSignature in: data > "Answer the last index in data where aSignature (4 bytes long) > occurs, or 0 if not found" > | a b c d | > a := aSignature first. > b := aSignature second. > c := aSignature third. > d := aSignature fourth. > (data size - 3) to: 1 by: -1 do: [ :i | > (((data at: i) = a) > and: [ ((data at: i + 1) = b) > and: [ ((data at: i + 2) = c) > and: [ ((data at: i + 3) = d) ]]]) > ifTrue: [ ^i ] > ]. > ^0 > > after: > > lastIndexOfPKSignature: aSignature in: data > "Answer the last index in data where aSignature (4 bytes long) > occurs, or 0 if not found" > | a b c d | > a := aSignature first. > b := aSignature second. > c := aSignature third. > d := aSignature fourth. > data size - 3 to: 1 by: -1 do: [ :i | > data at: i ;; = a > and: [ data at: i + 1 ;; = b > and: [ data at: i + 2 ;; = c > and: [ data at: i + 3 ;; = d ]]] > ifTrue: [ ^i ] > ]. > ^0 Same as above, superfluous parenthesis. This is what you get after removing 5 of them and a bit of reformatting: data size - 3 to: 1 by: -1 do: [ :i | (data at: i) = a and: [ (data at: i + 1) = b and: [ (data at: i + 2) = c and: [ (data at: i + 3) = d ] ] ]) ifTrue: [ ^i ] ]. > > > Character > > before: > > asUppercase > "If the receiver is lowercase, answer its matching uppercase Character." > "A tentative implementation. Eventually this should consult the > Unicode table." > > | v | > v := self charCode. > (((8r141 <= v and: [v <= 8r172]) or: [16rE0 <= v and: [v <= 16rF6]]) > or: [16rF8 <= v and: [v <= 16rFE]]) > ifTrue: [^ Character value: value - 8r40] > ifFalse: [^ self] > > after: > > asUppercase > "If the receiver is lowercase, answer its matching uppercase Character." > "A tentative implementation. Eventually this should consult the > Unicode table." > > | v | > v := self charCode. > 8r141 <= v and: [v <= 8r172] ;; or: [16rE0 <= v and: [v <= 16rF6]] ;; > or: [16rF8 <= v and: [v <= 16rFE]] ;; > ifTrue: [^ Character value: value - 8r40] > ifFalse: [^ self] There's #between:and: or you can use better formatting to improve readability here: ((v between: 8r141 and: 8r172) or: [ v between: 16rE0 and: 16rF6 ] or: [ v between: 16rF8 and: 16rFE ]) ifTrue: [ ^Character value: value - 8r40]. or ((8r141 <= v and: [ v <= 8r172 ]) or: [ (16rE0 <= v and: [ v <= 16rF6 ]) or: [ 16rF8 <= v and: [ v <= 16rFE ] ] ]) ifTrue: [ ^Character value: value - 8r40]. Levente > > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Nov. 1, 2010