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

Re: [Pharo-project] how to know if an image is resuming or not

by StÃ©phane Ducasse

Yes I was reading that method yesterday and I went to sleep The embedded flag got me distracted. I will retry now. Thanks > snapshot: save andQuit: quit embedded: embeddedFlag > > answers the resuming flag. > > So, you can use it like: > > | resumedInFirstSnapshot | > resumedInFirstSnapshot := false. > > "first save" > (Smalltalk snapshot: save andQuit: false) ifTrue: [ ... "resuming here > " resumedInFirstSnapshot := true ] > "second save" > (Smalltalk snapshot: save andQuit: false) ifTrue: [ ... "resuming here > " resumedInFirstSnapshot ifFalse: [ ... ] ] > > > >> Stef >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Nov. 9, 2010

Re: [Pharo-project] how to know if an image is resuming or not

by Igor Stasenko

On 9 November 2010 09:58, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >> what about using some variable, like: >> >> RunTests := true. >> self saveimage. >> RunTests := false. >> self saveImage. >> >> and then in startUp: >> >> startUp: resuming >> >> ( resuming and: [ RunTests] ) ifTrue: [ self runTests ] >> > > but my code is executed when a menu is selected. So the interaction with startUp: is not really good. > snapshot: save andQuit: quit embedded: embeddedFlag answers the resuming flag. So, you can use it like: | resumedInFirstSnapshot | resumedInFirstSnapshot := false. "first save" (Smalltalk snapshot: save andQuit: false) ifTrue: [ ... "resuming here " resumedInFirstSnapshot := true ] "second save" (Smalltalk snapshot: save andQuit: false) ifTrue: [ ... "resuming here " resumedInFirstSnapshot ifFalse: [ ... ] ] > Stef > > > -- Best regards, Igor Stasenko AKA sig.

Nov. 9, 2010

Re: [Pharo-project] SHA256 [was: Date time iso8601 format]

by laurent laffont

> > 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. > > Wenn did you do the encodeForHTTP? You need it in any case because at least > the + sign is an encoded space that will render the date invalid. I think > you need do safe url encoding only for the string if it is included in the > url not the hash. > Yes, but then Amazon answers a signature not valid error. Indeed it seems I need to pass a secret key (given by Amazon) for SHA256 hash, but I don't find how to pass it to a SHA256 object. In PHP I would write: base64_encode(hash_mac('sha256', $signature, $secret_key)). In Pharo ? Laurent Laffont > > Norbert > > > >> >> 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. 9, 2010

Re: [Pharo-project] about tracker activities

by StÃ©phane Ducasse

It does not seem to be possible to specify an subject. It probably does it automatically. Stef On Nov 9, 2010, at 12:41 AM, Igor Stasenko wrote: > On 9 November 2010 01:32, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> it would be nice if emails can also be specified by a prefix. For example >> [ISSUE] > even better > > [ISSUE-<number>] > > >> Even if most mail client can filter by different ways, having a preffix is >> nice too. >> is that possible? >> >> On Mon, Nov 8, 2010 at 6:52 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: >>> >>> Hi: >>> >>> On 08 Nov 2010, at 22:06, StÃ©phane Ducasse wrote: >>> >>>> I think that we are not looking to the issues because we do not know >>>> that they have been entered. >>> Bye the way, your issue reporting template needs an update. It contains >>> outdated information, i.e., that you are currently working on Pharo 1.1. >>> >>> Best regards >>> Stefan >>> >>> -- >>> Stefan Marr >>> Software Languages Lab >>> Vrije Universiteit Brussel >>> Pleinlaan 2 / B-1050 Brussels / Belgium >>> http://soft.vub.ac.be/~smarr >>> Phone: +32 2 629 2974 >>> Fax: +32 2 629 3525 >>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Nov. 9, 2010

Re: [Pharo-project] update issues template in google code [was] Re: about tracker activities

by StÃ©phane Ducasse

I fixed 1 min after else this is administer > > > On 08 Nov 2010, at 22:06, StÃ©phane Ducasse wrote: > > > I think that we are not looking to the issues because we do not know that they have been entered. > Bye the way, your issue reporting template needs an update. It contains outdated information, i.e., that you are currently working on Pharo 1.1. > > grrrr I don't remember how to do that? > anyone? > > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > >

Nov. 9, 2010

Re: [Pharo-project] how to know if an image is resuming or not

by StÃ©phane Ducasse

>> > what about using some variable, like: > > RunTests := true. > self saveimage. > RunTests := false. > self saveImage. > > and then in startUp: > > startUp: resuming > > ( resuming and: [ RunTests] ) ifTrue: [ self runTests ] > but my code is executed when a menu is selected. So the interaction with startUp: is not really good. Stef

Nov. 9, 2010

Re: [Pharo-project] #& in Socket >> #waitForSendDoneFor:

by Levente Uzonyi

On Tue, 9 Nov 2010, Levente Uzonyi wrote: > On Tue, 9 Nov 2010, Philippe Marschall wrote: > >> Hi >> >> I have a case where the #& in Socket >> #waitForSendDoneFor: shows up in >> a tally (see attachment). I'm able to push about 1 Mbyte/s more when I >> replace that with #and:. So my question is this really needed or should >> I file a bug and send a patch? > > I "fixed" this once by for Squeak, but I didn't push this change. Here's the > boolean expression: > > (sendDone := self primSocketSendDone: socketHandle) not and: [ > self isConnected and: [ > "Connection end and final data can happen fast, so test in > this order" > Time millisecondClockValue < deadline] ] > > This refactoring saves one #isConnected send which may not be significant. I just realized, that you replaced #& already to #and:, so nvm. Levente > > The appearence of #& in MessageTally may be just false measurement. IIRC with > the current VMs the time spent in primitives are added to the next real > message send (for performance reasons), which means that the > #primSocketConnectionStatus: from #isConnected may be showing up there. Let > me know if this change helps. > > > Levente > >> >> This is Pharo 1.1.1 BTW. >> >> Cheers >> Philippe >> > >

Nov. 9, 2010

Re: [Pharo-project] how to change background in Pharo to plain white?

by Alain Plantec

from the settings browser you can also set the background color cheers Alain Le 09/11/2010 03:27, Mariano Martinez Peck a Ã©crit : > > > On Mon, Nov 8, 2010 at 11:18 PM, Lukas Renggli <renggli(a)gmail.com > <mailto:renggli@gmail.com>> wrote: > > I use the following code in my build scripts > (https://github.com/renggli/builder/blob/master/scripts/settings.st) > > World color: Color white. > World submorphs do: [ :each | > (#(SketchMorph ImageMorph) includes: each class name) > ifTrue: [ each delete ] ]. > > > In such case you can also do: > > LogoImageMorph default: nil. > > Lukas > > On 8 November 2010 23:14, Mariano Martinez Peck > <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: > > World backgroundMorph: nil. > > World restoreDisplay. > > > > cheers > > > > mariano > > > > On Mon, Nov 8, 2010 at 11:10 PM, Sheridan Mahoney > > <sheridan(a)sheridan-mahoney.com > <mailto:sheridan@sheridan-mahoney.com>> wrote: > >> > >> Hello, > >> > >> I want to be able to take some screenshots of the Pharo menus, > >> and would like to have a plain white background instead of > >> the 'Pharo' logo. I've tried setting : > >> System->Settings->Appearance->Desktop->color > >> to white, but it didn't have the effect I wanted. > >> > >> Any ideas? > >> > >> Many thanks in advance, > >> > >> Sheridan > >> > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch <http://www.lukas-renggli.ch> > >

Nov. 9, 2010

Re: [Pharo-project] Date time iso8601 format

by Norbert Hartl

On 07.11.2010, at 23:07, laurent laffont wrote: > 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. > Wenn did you do the encodeForHTTP? You need it in any case because at least the + sign is an encoded space that will render the date invalid. I think you need do safe url encoding only for the string if it is included in the url not the hash. Norbert > > > 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. 9, 2010

Re: [Pharo-project] #& in Socket >> #waitForSendDoneFor:

by Schwab,Wilhelm K

What does your patch do? At a minimum, it deserves a little attention. Things that come to mind are that one version does less work due to some type of optimization (and runs faster as a result) or that one is too quick to detect a loss of connection and sends less data per opportunity, appearing to run slower as a result. Can you elaborate on "I'm able to push about 1 Mbyte/s more"? I guess I'm asking how that manifests itself? Are there a bunch of connections that form, send and fail? Do they each get a little farther or do they go faster? Also, my standard objection to timeouts enters into this. IMHO, the socket should do what it is asked to do, blocking only the calling thread, and let other threads and/or the user decide when that is taking too long. Could you be getting timeouts that are causing unexpected behavior? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Philippe Marschall [kustos(a)gmx.net] Sent: Tuesday, November 09, 2010 1:11 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] #& in Socket >> #waitForSendDoneFor: Hi I have a case where the #& in Socket >> #waitForSendDoneFor: shows up in a tally (see attachment). I'm able to push about 1 Mbyte/s more when I replace that with #and:. So my question is this really needed or should I file a bug and send a patch? This is Pharo 1.1.1 BTW. Cheers Philippe

Nov. 9, 2010