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

[Pharo-project] Pharo Sprint @ Smalltalks'10

by Alexandre Bergel

Hi! On Thursday 11 we will have a Pharo Sprint at Smalltalks'10. Please, enter your name on http://code.google.com/p/pharo/wiki/PharoSprints Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 8, 2010

Re: [Pharo-project] About SimpleMorphic

by Igor Stasenko

On 7 November 2010 22:38, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > I disagree; the layout policy should arrange the morphs it controls. Â To do otherwise demands that the morphs be able to cope with any type of layout one might want. Â The various algorithms have to go somewhere; they might as well go in the layouts. > Some layouts, like table, indeed requiring a cooperation between container morph and its submorphs. But still, i think that it should be based on a simple things: - morph should have a single layout command: lay within certain bounds. It doesn't matters where these bounds came from or how they are calculated. Then child morph could decide for itself how to lay within given bounds (like fill whole area or align to botton or top etc etc), and avoid querying parent morph or layout policy/whatever to determine own bounds, unless, of course it also having submorphs and own layout policy. So, if parent morph having no layout policy, it will simply pass its own bounds to submoprhs. And if parent having , say table layout policy, then it will calculate table cells and pass each cell bounds to each submorph for given cell. and yes, implementing this stuff is always harder than just talking about it :) > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com] > Sent: Sunday, November 07, 2010 2:50 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] About SimpleMorphic > > > > it is hard to say, what layout policies we may need, and what can be > removed/simplified. What i feel wrong with scheme, > that from message names it feels like a container morph is responsible > for layout, > while i think, that it is submorph(s) themselves should be responsible > and know how to place > them within parent morph. > > > -- Best regards, Igor Stasenko AKA sig.

Nov. 7, 2010

Re: [Pharo-project] Date time iso8601 format

by laurent laffont

On Sun, Nov 7, 2010 at 8:43 PM, Johan Brichau <johan(a)inceptive.be> wrote: > When I evaluate: > > DateAndTime now printString > > -> '2010-11-07T20:42:26+01:00' > Sometimes I feel stupid :) Thank you Johan. Indeed Amazon WS keeps telling me my TimeStamp is not in iso 8601 format. I've tried to encodeForHTTP but then it tells Signature is invalid.... the sample I'm trying to get PBE entry from Amazon: req := 'Service=AWSECommerceService&AWSAccessKeyId=mykey&Operation=ItemLookup&ItemId=3952334146&Timestamp=', DateAndTime now printString. sign :=SHA256 hashMessage: 'GET', String crlf, 'ecs.amazonaws.com', String crlf, '/onca/xml',String crlf,req. (Url absoluteFromText: 'http://webservices.amazon.fr/onca/xml?',req, '&Signature=',sign hex) retrieveContents contentStream. Laurent > > On 07 Nov 2010, at 13:50, laurent laffont wrote: > > > The other way. For example > > > > DateAndTime now printISO8601 > > > > Laurent > > > > > > On Sun, Nov 7, 2010 at 1:28 PM, Johan Brichau <johan(a)inceptive.be> > wrote: > > Laurent, > > > > DateAndTime readFrom: '2008-02-10T12:00:00Z' readStream > > > > Does that yield what you want? > > > > cheers > > Johan > > > > On 06 Nov 2010, at 15:07, laurent laffont wrote: > > > >> Hi, > >> > >> I cannot find which method to use to get a Date in iso 8601 format like > '2008-02-10T12:00:00Z' ? > >> > >> > >> Cheers, > >> > >> Laurent Laffont > >> > >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > >> Blog: http://magaloma.blogspot.com/ > > > > > > >

Nov. 7, 2010

Re: [Pharo-project] smalltalk: breaking out of a loop..

by GÃ¶ran Krampe

On 11/07/2010 08:06 PM, Guillermo Polito wrote: > #anySatisfy: does not iterate over the entire collection either. So if > you only want to know if there is one that satisfies the condition... > this is the message you're looking for. > > Cheers! > Guille And finally, a generic "trick" for breaking out of loops (not just iterations over collections): Factor out the loop in a single method, then call it. When you want to break out, just do a normal return! regards, GÃ¶ran

Nov. 7, 2010

Re: [Pharo-project] About SimpleMorphic

by Schwab,Wilhelm K

Sig, I disagree; the layout policy should arrange the morphs it controls. To do otherwise demands that the morphs be able to cope with any type of layout one might want. The various algorithms have to go somewhere; they might as well go in the layouts. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com] Sent: Sunday, November 07, 2010 2:50 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] About SimpleMorphic it is hard to say, what layout policies we may need, and what can be removed/simplified. What i feel wrong with scheme, that from message names it feels like a container morph is responsible for layout, while i think, that it is submorph(s) themselves should be responsible and know how to place them within parent morph.

Nov. 7, 2010

Re: [Pharo-project] About SimpleMorphic

by Igor Stasenko

On 7 November 2010 21:17, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > 2010/11/7 Igor Stasenko <siguctua(a)gmail.com>: >>> Talking about complexity, let's take for example, morph layout. This is >>> started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic. >>> >>> In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in: (149), >>> #layoutProportionallyIn: (10), #computeCellArrangement:in:horizontal:target: >>> (87), #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31), >>> #computeCellSizes:in:horizontal: (30), >>> #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in: >>> (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target: (70). >>> The numbers in parenthesis are the sum of the lines of code of the >>> implementors. Total lines of code for layout (taking only these most >>> important methods) is 714. I doubt there are many people who really >>> understand all of this code. >>> >>> In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10), >>> #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45. I >>> believe any smalltalker could understand these in just minutes. >>> >> >> Indeed, a morphic layout logic always felt overly complicated to me. >> It hard, because you don't know, >> if you can remove/replace anything from there and still have a working >> code. Good to see that you have managed to deal with that. >> > > The question that immediately arises from such complexity is : > - what are the features we want to implement ? > > If we are not able to provide an answer, that means we can't even > write tests, and that also means we can't modify/refactor the code. > In such case, we tend to write more code outside existing one and so > doing are just making things worse (more code more complexity). > > I suspect (but I did not check) that Juan's work in Cuis is the best > thing to do in such case. > While at it, we should also write tests now that we have testable features. > it is hard to say, what layout policies we may need, and what can be removed/simplified. What i feel wrong with scheme, that from message names it feels like a container morph is responsible for layout, while i think, that it is submorph(s) themselves should be responsible and know how to place them within parent morph. > Nicolas > > -- Best regards, Igor Stasenko AKA sig.

Nov. 7, 2010

Re: [Pharo-project] Date time iso8601 format

by Johan Brichau

When I evaluate: DateAndTime now printString -> '2010-11-07T20:42:26+01:00' On 07 Nov 2010, at 13:50, laurent laffont wrote: > The other way. For example > > DateAndTime now printISO8601 > > Laurent > > > On Sun, Nov 7, 2010 at 1:28 PM, Johan Brichau <johan(a)inceptive.be> wrote: > Laurent, > > DateAndTime readFrom: '2008-02-10T12:00:00Z' readStream > > Does that yield what you want? > > cheers > Johan > > On 06 Nov 2010, at 15:07, laurent laffont wrote: > >> Hi, >> >> I cannot find which method to use to get a Date in iso 8601 format like '2008-02-10T12:00:00Z' ? >> >> >> Cheers, >> >> Laurent Laffont >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ > >

Nov. 7, 2010

Re: [Pharo-project] About SimpleMorphic

by Nicolas Cellier

2010/11/7 Igor Stasenko <siguctua(a)gmail.com>: >> Talking about complexity, let's take for example, morph layout. This is >> started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic. >> >> In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in: (149), >> #layoutProportionallyIn: (10), #computeCellArrangement:in:horizontal:target: >> (87), #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31), >> #computeCellSizes:in:horizontal: (30), >> #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in: >> (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target: (70). >> The numbers in parenthesis are the sum of the lines of code of the >> implementors. Total lines of code for layout (taking only these most >> important methods) is 714. I doubt there are many people who really >> understand all of this code. >> >> In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10), >> #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45. I >> believe any smalltalker could understand these in just minutes. >> > > Indeed, a morphic layout logic always felt overly complicated to me. > It hard, because you don't know, > if you can remove/replace anything from there and still have a working > code. Good to see that you have managed to deal with that. > The question that immediately arises from such complexity is : - what are the features we want to implement ? If we are not able to provide an answer, that means we can't even write tests, and that also means we can't modify/refactor the code. In such case, we tend to write more code outside existing one and so doing are just making things worse (more code more complexity). I suspect (but I did not check) that Juan's work in Cuis is the best thing to do in such case. While at it, we should also write tests now that we have testable features. Nicolas

Nov. 7, 2010

Re: [Pharo-project] smalltalk: breaking out of a loop..

by Guillermo Polito

#anySatisfy: does not iterate over the entire collection either. So if you only want to know if there is one that satisfies the condition... this is the message you're looking for. Cheers! Guille On Sun, Nov 7, 2010 at 1:27 PM, sergio_101 <sergio.rrd(a)gmail.com> wrote: > On Sun, Nov 7, 2010 at 11:08 AM, Max Leske <maxleske(a)gmail.com> wrote: > > use #dectect: > > > > perfect.. > > thanks! > -- > ---- > peace, > sergio > photographer, journalist, visionary > > http://www.CodingForHire.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > >

Nov. 7, 2010

Re: [Pharo-project] Date time iso8601 format

by StÃ©phane Ducasse

On Nov 7, 2010, at 1:55 PM, laurent laffont wrote: > > On Sun, Nov 7, 2010 at 1:50 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > The other way. For example > > DateAndTime now printISO8601 > > Laurent > > > It seems Chronos http://chronos-st.org/ has such formatters (ISO8601PrintPolicy) but AnsiStandardCalendarClock is missing in Pharo.... Why do you mean missing in pharo? When you load chronos this is not there. May be you should contact the author and ask. > > Laurent > > > > On Sun, Nov 7, 2010 at 1:28 PM, Johan Brichau <johan(a)inceptive.be> wrote: > Laurent, > > DateAndTime readFrom: '2008-02-10T12:00:00Z' readStream > > Does that yield what you want? > > cheers > Johan > > On 06 Nov 2010, at 15:07, laurent laffont wrote: > >> Hi, >> >> I cannot find which method to use to get a Date in iso 8601 format like '2008-02-10T12:00:00Z' ? >> >> >> Cheers, >> >> Laurent Laffont >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ > > >

Nov. 7, 2010