May 2011 - Pharo-users - lists.pharo.org

Re: [Pharo-users] become:

by Mariano Martinez Peck

2011/5/2 info(a)tomsik.cz <info(a)tomsik.cz> > > I've heard that become: is considered to be magic > and should be avoided and replaced by either AOP or proxies, > > That's "normally" true. But it depends what are you doing. For a normal app, busieness, etc, it is not likely you will need a #become:. However, if you are doing low level stuff, frameworks or hacky things you may need it. Can you tell us what are your needs and why you would like to use #become:? or you just want to know about it? > I googled a little but I couldn't find anything more concrete. > > Does anybody have any link or opinion about that? > I'd be glad to hear something more about it. > > Thx > > -- > Tato zprÃ¡va byla vytvoÅena pÅevratnÃ½m poÅ¡tovnÃm klientem Opery: > http://www.opera.com/mail/ > > -- Mariano http://marianopeck.wordpress.com

May 2, 2011

become:

by info＠tomsik.cz

I've heard that become: is considered to be magic and should be avoided and replaced by either AOP or proxies, I googled a little but I couldn't find anything more concrete. Does anybody have any link or opinion about that? I'd be glad to hear something more about it. Thx -- Tato zprÃ¡va byla vytvoÅena pÅevratnÃ½m poÅ¡tovnÃm klientem Opery: http://www.opera.com/mail/

May 2, 2011

Re: [Pharo-users] become:

by StÃ©phane Ducasse

Do not use become: for state pattern. It is not worth. Stef On May 2, 2011, at 3:11 PM, info(a)tomsik.cz wrote: > I see that #become: is hard to follow in code (either for human or analysis tools) > > I'm trying to express state-pattern: > > OpenedDoor>>close > ClosedDoor>>open > > And I would like to avoid this: > Door>>close > state close. > Door>>open > state open. > > Because if Door cannot be opened depending on its current state, IMHO no method should be > there. Which is why become: seems as the best fit. > > > I would also like to know why proxy is considered better, because #messageNotUnderstood > seems pretty magic too. (except the fact that become: can crash VM) > > > Dne Mon, 02 May 2011 14:39:40 +0200 Mariano Martinez Peck <marianopeck(a)gmail.com> napsal(a): > >> 2011/5/2 info(a)tomsik.cz <info(a)tomsik.cz> >> >>> >>> I've heard that become: is considered to be magic >>> and should be avoided and replaced by either AOP or proxies, >>> >>> >> That's "normally" true. But it depends what are you doing. For a normal app, >> busieness, etc, it is not likely you will need a #become:. >> However, if you are doing low level stuff, frameworks or hacky things you >> may need it. >> >> Can you tell us what are your needs and why you would like to use #become:? >> or you just want to know about it? >> >> >>> I googled a little but I couldn't find anything more concrete. >>> >>> Does anybody have any link or opinion about that? >>> I'd be glad to hear something more about it. >>> >>> Thx >>> >>> -- >>> Tato zprÃ¡va byla vytvoÅena pÅevratnÃ½m poÅ¡tovnÃm klientem Opery: >>> http://www.opera.com/mail/ >>> >>> >> >> > > > -- > Tato zprÃ¡va byla vytvoÅena pÅevratnÃ½m poÅ¡tovnÃm klientem Opery: http://www.opera.com/mail/ >

May 2, 2011

Re: [Pharo-users] An small "interactive art" project in Pharo, from a newbie

by Benjamin

I let you search a bit, but if you are lost at a point, I have done a similar Morph for auto vanishing balloon :) So for now, try to do it by your own, and if/when you want, I can provide you my sources ;) Ben On Apr 25, 2011, at 9:01 AM, StÃ©phane Ducasse wrote: > you can create a Morph and change its color using the step method. > and at the end delete it. > It should be quite simple to do that and a good exercise for you to learn. > > Start with BorderedMorph new openInWorld. > > Stef > > On Apr 25, 2011, at 12:53 AM, Offray Vladimir Luna CÃ¡rdenas wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi Stef, >> >> El 24/04/11 04:01, StÃ©phane Ducasse escribiÃ³: >>> Thanks offray. >>> >>> I think that you should have a look at the work on ricardo moran and use the board from pharo. >>> Now this is working well. >>> >>> Stef >> >> I have already seen that (the Physical etoys project). Now I want to >> make something not related with physical computing, but just making some >> graphic appear at a random position vanish slowly and load a >> twitter/identica feed. Any pointer on where I can find this solution? >> >> Thanks >> >> Offray >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.11 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iQEcBAEBAgAGBQJNtKoCAAoJEGiex2828ICwrsYH/RgrOvhMABG0htt3TjAXiGzt >> LwdtzZG/xTJBawQkflHDipSjbypsIkInkCnTM+9yDgA+grkdxoGxdN5D7W1MfU/r >> Y6XE7/7sSKEmbCHVXGVeJ6LllxqsEDK+UDqcEIr1eDAPfmb6NJulYS5AFna/4xTg >> I83FMPNAWQ9xWf8ggVrpAOOpvKal4X3HzCFbST6hiwcmxJDvNfEUCc1FuTp3DOQ9 >> rtBsGSkbtFEOGCePSqMp5HXhxT22PmSd5FpnLtujRhoVAZaRdIFWiI/SadYPNsez >> C+us+fprenBeuCAtjSqQM0KjI686uLslK9tLPedvgPjW/lRr2UlMFv/FoFv4krI= >> =sdJs >> -----END PGP SIGNATURE----- >> > >

May 2, 2011

Re: [Pharo-users] WebClient for 1.2.2?

by Norbert Hartl

Am 02.05.2011 um 07:31 schrieb Sven Van Caekenberghe: > No, it does require changing the Smalltalk side, I call it a workaround because really supporting HTTPS out of the box would be much better. And the usage of client SSL certificates would be possible. With stunnel you have to hardcode them in the configuration file. Norbert

May 2, 2011

Re: [Pharo-users] WebClient for 1.2.2?

by Davorin Rusevljan

On Mon, May 2, 2011 at 7:31 AM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 02 May 2011, at 00:09, Andy Burnett wrote: > >> I haven't used stunnel before. I doesn't look too difficult to install, but >> when you say 'workaround' is it simply a case of install it, and then use it >> with Pharo. Or, do I have to make changes to Pharo to get it to take >> advantage of stunnel? > > Here is a good description: http://blog.doit.st/2011/02/23/cloudforksso-on-pharo-with-stunnel/ > > No, it does require changing the Smalltalk side, I call it a workaround because really supporting HTTPS out of the box would be much better. > > However, I must say that I did not get it to work on Mac OS X (almost ;-), then I switched to a my virtual Ubuntu GNU/Linux and it worked. This link is also handy, it describes how to get SSL with nginx: http://www.monkeysnatchbanana.com/posts/2010/06/22/faking-a-https-client-fo… Davorin Rusevljan http://www.cloud208.com/

May 2, 2011

Re: [Pharo-users] Strange results from Zinc for the www.delicious.com domain

by Sven Van Caekenberghe

On 02 May 2011, at 00:11, Andy Burnett wrote: > OK, given what you - and Matt - have found, I think I will wait until you > have a tweaked version of the code. In the meantime, it looks like the > existing HttpClient will have to suffice - I am trying to do some screen > scraping of Delicious, so I really need something that will work with that > server. Please try again, if you still have time, if not, no problem. Sven

May 2, 2011

Re: [Pharo-users] WebClient for 1.2.2?

by Sven Van Caekenberghe

On 02 May 2011, at 00:09, Andy Burnett wrote: > I haven't used stunnel before. I doesn't look too difficult to install, but > when you say 'workaround' is it simply a case of install it, and then use it > with Pharo. Or, do I have to make changes to Pharo to get it to take > advantage of stunnel? Here is a good description: http://blog.doit.st/2011/02/23/cloudforksso-on-pharo-with-stunnel/ No, it does require changing the Smalltalk side, I call it a workaround because really supporting HTTPS out of the box would be much better. However, I must say that I did not get it to work on Mac OS X (almost ;-), then I switched to a my virtual Ubuntu GNU/Linux and it worked. Sven

May 2, 2011

Re: [Pharo-users] Backward compatibility [WAS] Re: [ANN] PharoDev-1.3-13173

by Markus Fritsche

Hi, 2011/4/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > And as Marcus said, most of the times (sometimes we had some problems) we > have a deprecation process where we (usually) say which should be used > instead. >From a a-little-bit-more-than-user perspective I am looking at SmalltalkImage>>#hasBindingThatBeginsWith: aString self deprecated: 'Use Smalltalk globals'. ^globals hasBindingThatBeginsWith: aString Well, with a bit of analysis, I would be able to figure out, that the author might have intended that I should search the SystemDictionary myself. I feel like an additional comment would have been helpful. Same with the other problem I had with ServiceRegistry - it is gone and it is not easy to find out what that was supposed to do. Next step is to compare squeak and the Pharo releases to find out what happened to it (the issue tracker does not easily yield results for this, but maybe I searched in the wrong way). I know there is no easy fix for this, as "fast deprecation" was what made Pharo manageable compared to other image-based smalltalk dialects (not to mention anything specific ;)) but there is a lot of interesting code on squeaksource that naturally breaks - for those interested in that code, it would be helpful to give a bit more advice on "porting" and "the path of deprecation". Enough trolling for tonight :) Regards, Markus

May 1, 2011

Re: [Pharo-users] Strange results from Zinc for the www.delicious.com domain

by Andy Burnett

Sven Van Caekenberghe wrote: > > On 01 May 2011, at 04:28, arturus(a)gmail.com wrote: > >> ZnHttpClient is sending a Connection: close header in the request which >> is causing delicious to return the headers, but not the actual content >> entity. >> >> It's doing this in ZnHttpClient>>method:for:headers:data:limit:. >> Commenting out 'request setConnectionClose' in that method allows the get >> request to work. > > Actually it is a deeper bug, related to what Esteban reported. As far as I > can tell right now, certain servers respond to requests with 'Connection: > Close' by not including a 'Content-Length' (most notably Google GWS, but > apparently other too). The idea is then to read the content #upToEnd. > ZnEntityReader does have a provision for that, but somehow it got disabled > because this behavior is not very common (as far as I remember, but I have > to check again, 'Content-Length' is required with HTTP/1.1, but there > might be finer points in the specs). Enabling it with #allowReadingUpToEnd > should have fixed it, but seems to break lots of other code. I have to > investigate this further. > > Anyway, I now know where to look, so I'll get there. > > Sven > OK, given what you - and Matt - have found, I think I will wait until you have a tweaked version of the code. In the meantime, it looks like the existing HttpClient will have to suffice - I am trying to do some screen scraping of Delicious, so I really need something that will work with that server. Cheers Andy -- View this message in context: http://forum.world.st/Strange-results-from-Zinc-for-the-www-delicious-com-d… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 1, 2011