June 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN]: Pharo x.5

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote >> * ZnNetworkingUtils>>isPortAvailable: (doesn't take ip6 into account) > > I am interested in this one but I can't open the package named: > 'ZnNetworkingUtils>>usedPorts', can you ? No, I can't either... but it's okay because I moved the method into Zinc-HTTPSpd ;) I was experimenting with packaging each method individually, but didn't see the point, so I changed to mirroring the packages being extended... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-ANN-Pharo-x-5-tp4693932p4693967.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 18, 2013

Re: [Pharo-dev] on:do: for shortcuts?

by ClÃ©ment Bera

On Javascript, there are : - onkeypress - onkeydown - onkeyup I think we should have same API than other languages, especially popular ones. So 1 of these 3 would be the best for me. Why not onKeyPress:do: ? 2013/6/18 Goubier Thierry <thierry.goubier(a)cea.fr> > Additionally, this is processing on a shortcut, that is possibly on a > sequence of keys... > > So, onKey:do: isn't very good. > > The replacement of asShortcut by asKeyCombination in 3.0 wasn't too good, > either. > > But, to be coherent, it should certainly be: > > onKeyCombination:do: > > Thierry > > > Le 18/06/2013 16:44, Igor Stasenko a Ã©crit : > > On 18 June 2013 15:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> >>> Hi guillermo >>> >>> I thought that we decided to change and not use >>> on: do: for shortCuts (I'm happy that we change because for me >>> it took me a while to understand that the key was not an exception. >>> >>> Could we deprecate on:do: on KMDispatcher? >>> What is the replacement? >>> >>> onKey: do: >>> >>> >>> initializeShortcuts >>> "initialize the inspector' shortcuts with the dictionary >>> defined in self shortCuts" >>> >>> self shortCuts keysAndValuesDo: [ :key :value | >>> list on: key do: value ] >>> >>> => >>> >>> initializeShortcuts >>> "initialize the inspector' shortcuts with the dictionary >>> defined in self shortCuts" >>> >>> self shortCuts keysAndValuesDo: [ :key :value | >>> list onHold: key do: value ] >>> >>> hold or press? >> >> you *press* the key, *hold* it for a while and then *release*. >> >> usually you receive 2 events - press and release. >> and you don't receive 'hold' event, since it is assumed that key is >> being held until it released. >> >> then on top of that, there is a key repeat functionality, is when user >> holds key it starts repeating >> (but again, ideally you don't receive a 'press' event, but you receive >> a synthetic 'keyChar' event) >> >> >>> Stef >>> >> >> >> >> > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 18, 2013

Re: [Pharo-dev] [ANN]: Pharo x.5

by Sean P. DeNigris

Marcus Denker-4 wrote > Keep in mind that we can integrate important fixes in 2.0â¦. someone just > needs to take initiative. Thanks for the reminder! I'm clear about that after all the work we did together getting 2.0 issues backported to 1.4 :) And... my understanding is that we have a policy to only backport bug fixes. The features in this project are either: - fixes waiting to be integrated - enhancements that do not fit the backporting policy - extensions that I find extremely useful, but I'm not clear how useful they'd be to others ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-ANN-Pharo-x-5-tp4693932p4693966.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 18, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by Esteban A. Maringolo

I did some tests with AWS EC2, and it is good to know to know Pharo is so simple to install in this provider. It looks more like a VPS provider, or am I missing something? Because I haven't seen an autoscaling (up or out) option there. Do you know if they support something similar to Elastic IP? Regards, Esteban A. Maringolo 2013/6/18 Sven Van Caekenberghe <sven(a)stfx.eu> > Hi, > > I am a fan of Amazon AWS's Cloud Services. But it is not perfect. > > Enter Digital Ocean (https://www.digitalocean.com) an easier to use, > simpler cloud hosting provider, that is cheaper and seems faster. You get a > raw machine, so you still need some basic Unix admin skills, but apart from > that it cannot get much easier. > > For just $5 a month you get this: > > As an SSD based machine, it feels very fast. I did some quick benchmarks > at the Pharo level which show that this virtualised hardware is up to 10x > faster than an Amazon AWS EC2 micro instance, and up to 3x faster than > an Amazon AWS EC2 small instance. Its just a bit slower than my top of the > line MacBook Air: > > root@stfx:~# ./pharo Pharo.image eval '1 tinyBenchmarks' > '764749813 bytecodes/sec; 94679619 sends/sec' > > To get started on the empty machine, just do > > root@stfx:~# curl get.pharo.org/30+vm | bash > > If you picked a 32 bit Ubuntu, you only need to do > > root@stfx:~# apt-get install libssl0.9.8 > > Starting a Zn server is dead easy: > > root@stfx:~# ./pharo Pharo.image eval --no-quit 'ZnServer > startDefaultOn: 1701' & > > Have a look at: > > http://82.196.12.54:1701 > > Which is a single vm+image instance. > > Local network performance is quite good: > > root@stfx:~# ab -k -n 1024 -c 4 http://localhost:1701/bytes > > Server Software: Zinc > Server Hostname: localhost > Server Port: 1701 > > Document Path: /bytes > Document Length: 64 bytes > > Concurrency Level: 4 > Time taken for tests: 0.584 seconds > Complete requests: 1024 > Failed requests: 0 > Write errors: 0 > Keep-Alive requests: 1024 > Total transferred: 243712 bytes > HTML transferred: 65536 bytes > Requests per second: 1753.68 [#/sec] (mean) > Time per request: 2.281 [ms] (mean) > Time per request: 0.570 [ms] (mean, across all concurrent requests) > Transfer rate: 407.59 [Kbytes/sec] received > > I also tried a big config based build that downloaded and compiled about > 1Gb worth of .mcz and that took less than 4 minutes which is also quite > fast. > > Of course, you get way fewer features than with Amazon AWS (the total > ecosystem). But for the price it seems hard to beat. > > Have fun ! > > Sven > > PS: Feel free to do me a favour by using this link > https://www.digitalocean.com/?refcode=6a0334a169dc > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

June 18, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by phil＠highoctane.be

I have been looking into that as well and it is indeed very nice. DO is growing very fast. Phil Le 18 juin 2013 16:27, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > Hi, > > I am a fan of Amazon AWS's Cloud Services. But it is not perfect. > > Enter Digital Ocean (https://www.digitalocean.com) an easier to use, > simpler cloud hosting provider, that is cheaper and seems faster. You get a > raw machine, so you still need some basic Unix admin skills, but apart from > that it cannot get much easier. > > For just $5 a month you get this: > > As an SSD based machine, it feels very fast. I did some quick benchmarks > at the Pharo level which show that this virtualised hardware is up to 10x > faster than an Amazon AWS EC2 micro instance, and up to 3x faster than > an Amazon AWS EC2 small instance. Its just a bit slower than my top of the > line MacBook Air: > > root@stfx:~# ./pharo Pharo.image eval '1 tinyBenchmarks' > '764749813 bytecodes/sec; 94679619 sends/sec' > > To get started on the empty machine, just do > > root@stfx:~# curl get.pharo.org/30+vm | bash > > If you picked a 32 bit Ubuntu, you only need to do > > root@stfx:~# apt-get install libssl0.9.8 > > Starting a Zn server is dead easy: > > root@stfx:~# ./pharo Pharo.image eval --no-quit 'ZnServer > startDefaultOn: 1701' & > > Have a look at: > > http://82.196.12.54:1701 > > Which is a single vm+image instance. > > Local network performance is quite good: > > root@stfx:~# ab -k -n 1024 -c 4 http://localhost:1701/bytes > > Server Software: Zinc > Server Hostname: localhost > Server Port: 1701 > > Document Path: /bytes > Document Length: 64 bytes > > Concurrency Level: 4 > Time taken for tests: 0.584 seconds > Complete requests: 1024 > Failed requests: 0 > Write errors: 0 > Keep-Alive requests: 1024 > Total transferred: 243712 bytes > HTML transferred: 65536 bytes > Requests per second: 1753.68 [#/sec] (mean) > Time per request: 2.281 [ms] (mean) > Time per request: 0.570 [ms] (mean, across all concurrent requests) > Transfer rate: 407.59 [Kbytes/sec] received > > I also tried a big config based build that downloaded and compiled about > 1Gb worth of .mcz and that took less than 4 minutes which is also quite > fast. > > Of course, you get way fewer features than with Amazon AWS (the total > ecosystem). But for the price it seems hard to beat. > > Have fun ! > > Sven > > PS: Feel free to do me a favour by using this link > https://www.digitalocean.com/?refcode=6a0334a169dc > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

June 18, 2013

Re: [Pharo-dev] Object>>#if:then:else:

by ClÃ©ment Bera

I don't like this new structure. Then people coming from non object language using all the time control structure will do : #someRandomObject if: then: else: thinking of doing a C style condition and not using at all the receiver. I like how it is now. 2013/6/18 kilon <thekilon(a)yahoo.co.uk> > Very few things are truly necessary in life, programming languages are not > amongst them. > > As I said , for me how already things work in pharo is fine concerning > ifTrue: and friends . > > > > -- > View this message in context: > http://forum.world.st/Pharo-dev-Object-if-then-else-tp4693871p4693952.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 18, 2013

Re: [Pharo-dev] on:do: for shortcuts?

by Goubier Thierry

Additionally, this is processing on a shortcut, that is possibly on a sequence of keys... So, onKey:do: isn't very good. The replacement of asShortcut by asKeyCombination in 3.0 wasn't too good, either. But, to be coherent, it should certainly be: onKeyCombination:do: Thierry Le 18/06/2013 16:44, Igor Stasenko a Ã©crit : > On 18 June 2013 15:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guillermo >> >> I thought that we decided to change and not use >> on: do: for shortCuts (I'm happy that we change because for me it took me a while to understand that the key was not an exception. >> >> Could we deprecate on:do: on KMDispatcher? >> What is the replacement? >> >> onKey: do: >> >> >> initializeShortcuts >> "initialize the inspector' shortcuts with the dictionary defined in self shortCuts" >> >> self shortCuts keysAndValuesDo: [ :key :value | >> list on: key do: value ] >> >> => >> >> initializeShortcuts >> "initialize the inspector' shortcuts with the dictionary defined in self shortCuts" >> >> self shortCuts keysAndValuesDo: [ :key :value | >> list onHold: key do: value ] >> > hold or press? > > you *press* the key, *hold* it for a while and then *release*. > > usually you receive 2 events - press and release. > and you don't receive 'hold' event, since it is assumed that key is > being held until it released. > > then on top of that, there is a key repeat functionality, is when user > holds key it starts repeating > (but again, ideally you don't receive a 'press' event, but you receive > a synthetic 'keyChar' event) > >> >> Stef > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 18, 2013

Re: [Pharo-dev] There are still lots of Delay>>wait Processes

by Igor Stasenko

On 18 June 2013 16:31, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 18 Jun 2013, at 14:43, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> You may not be the only one, but you probably are the only whose job is to address Pharo issues :) > > And we all get this warm cozy feeling when Igor fixes important low level stuff ;-) > hear hear... same about you, when you making new update for zinc stuff :) >> Ben >> >> On Jun 18, 2013, at 11:17 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 18 June 2013 11:11, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> Once igor finishes the TxModel and Athens it was planned to address the Delay problem. >>>> >>> >>> I don't think i am the only one who capable to fix it. :) >>> >>> Something broken in restoring Delay(s) after image restart (they >>> hanging for too far in the future). >>> That's my impression. >>> From other side, i do not see why Cookie should use [ Delay forEons wait] fork. >>> Instead, i would just replace implementation with code which checks >>> the time before giving answer >>> of cookie value. >>> So, if you won't use cookie value in heavy numerical-crunchy >>> calculations, this is completely fine. >>> >>>> Stef >>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> > > -- Best regards, Igor Stasenko.

June 18, 2013

Re: [Pharo-dev] on:do: for shortcuts?

by Igor Stasenko

On 18 June 2013 15:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guillermo > > I thought that we decided to change and not use > on: do: for shortCuts (I'm happy that we change because for me it took me a while to understand that the key was not an exception. > > Could we deprecate on:do: on KMDispatcher? > What is the replacement? > > onKey: do: > > > initializeShortcuts > "initialize the inspector' shortcuts with the dictionary defined in self shortCuts" > > self shortCuts keysAndValuesDo: [ :key :value | > list on: key do: value ] > > => > > initializeShortcuts > "initialize the inspector' shortcuts with the dictionary defined in self shortCuts" > > self shortCuts keysAndValuesDo: [ :key :value | > list onHold: key do: value ] > hold or press? you *press* the key, *hold* it for a while and then *release*. usually you receive 2 events - press and release. and you don't receive 'hold' event, since it is assumed that key is being held until it released. then on top of that, there is a key repeat functionality, is when user holds key it starts repeating (but again, ideally you don't receive a 'press' event, but you receive a synthetic 'keyChar' event) > > Stef -- Best regards, Igor Stasenko.

June 18, 2013

Re: [Pharo-dev] how to define menu in spec

by Goubier Thierry

Le 18/06/2013 15:35, StÃ©phane Ducasse a Ã©crit : > ok I will try to find my way but yes it would be good to offer an > infrastructure to avoid that everybody reinvent the wheel At the same time, beware of over-architecturing. I hates a framework where hacking it to do a simple subset of the "do everything" is faster than learning the "do everything" stuff. Thierry > Stef > On Jun 18, 2013, at 2:49 PM, Benjamin > <benjamin.vanryseghem.pharo(a)gmail.com > <mailto:benjamin.vanryseghem.pharo@gmail.com>> wrote: > >> For menus, there is nothing spec related here (yet). >> If you use pragmas, for defining your menus/shortcuts, there is (or >> was) a specific registration class supporting made for defining both >> in one. >> It was never adopted, so I do not know where to find it again, sorry >> >> >> Ben >> >> On Jun 18, 2013, at 1:48 PM, Goubier Thierry <thierry.goubier(a)cea.fr >> <mailto:thierry.goubier@cea.fr>> wrote: >> >>> Hi StÃ©phane, >>> >>> look into the AltBrowser code. You'll find commands that are both >>> shortcuts and menu items (subclasses of AltCommand). >>> >>> https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… >>> >>> https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… >>> >>> And it's more or less lifted from the OmniBrowser code, by the way. >>> >>> (Kind of convenient to link to st code from github) >>> >>> Thierry >>> >>> Le 18/06/2013 13:34, StÃ©phane Ducasse a Ã©crit : >>>> Hi ben >>>> >>>> I want to define some menu for my logging Tool UI. And I was >>>> wondering how >>>> >>>> - define menu >>>> - avoid duplication with shortcut >>>> >>>> I looked at the EyeInspector but it is not clear to me. Do you have a >>>> better example I could read? >>>> >>>> Stef >>>> >>>> >>>> >>> >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 18, 2013